search

Crivaledaz / Mattermost-LDAP

This module provides an external LDAP authentication in Mattermost for the Team Edition (free).
MIT License
359 stars 71 forks source link

Database not being created in container? #82

Open billunger opened 2 years ago

billunger commented 2 years ago

I am running through the steps to create a containerized version on Ubuntu, but get these errors. Note that the .env file is properly configured with relevant passwords.

Starting mattermostldap_mattermost-ldap_1 ... done Attaching to mattermostldap_db_1, mattermostldap_mattermost-ldap_1 db_1 | Error: Database is uninitialized and superuser password is not specified. db_1 | You must specify POSTGRES_PASSWORD to a non-empty value for the db_1 | superuser. For example, "-e POSTGRES_PASSWORD=password" on "docker run". db_1 | db_1 | You may also use "POSTGRES_HOST_AUTH_METHOD=trust" to allow all db_1 | connections without a password. This is not recommended. db_1 | db_1 | See PostgreSQL documentation about "trust": db_1 | https://www.postgresql.org/docs/current/auth-trust.html

billunger commented 2 years ago

Follow Up:

If I type docker-compose config, it returns all values as being null. It acts as though the yaml file isn't seeing the .env file.

Crivaledaz commented 2 years ago

Hi,

Seems like variables in the .env file are not imported during the docker-compose up. I don't know why, but you can specify variables directly in the docker-compose.yaml file, as it is in the Demo/docker-compose.yaml file. This should workaround the problem.

I also noticed that podman-compose is not working with .env file. So I think I will remove the env.example file in a next release, in favor of a unique docker-compose.yaml file containing all parameters and their associated values.

Please let me know if this solved your issue,

Regards