Skip to content

Init container lacks command line argument for mariadb #770

@Wolfgang1966

Description

@Wolfgang1966

Describe your Issue

Since a few releases the init container that checks for availability of the database no longer works correctly for mariadb. As a consequence the database check constantly fails and nextcloud itself never comes up.

Logs and Errors

The logs of the init container show repeatedly:

ERROR 2026 (HY000): TLS/SSL error: SSL is required, but the server does not support it  

The fix is to add the command line flag --skip-ssl to the command line of the init container. However, as I don't know whether this may break other setups I did not simply create a PR containing this flag. A more elaborate solution may be required, e.g. introducing a value that can be set optionally.

Describe your Environment

  • Kubernetes distribution: k3s

  • Helm Version (or App that manages helm):
    controlled by fluxcd

  • Helm Chart Version: 7.0.3
    (but also happened with a few previous versions already)

  • values.yaml:
    (relevant part)

    mariadb:
      enabled: true
      auth:
        existingSecret: "mariadb-secret"
      primary:
        persistence:
          enabled: true

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions