mattermost / mattermost/docker
Any support with podman-compose?
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 533
- Forks
- 284
- PR merge metrics
- No merged PRs in 30d
Description
I'm running podman compose 1.3.0 (latest version) and lots of errors, certainly due to the lack of podman support.
[postgres] | Error: Database is uninitialized and superuser password is not specified.
[postgres] | You must specify POSTGRES_PASSWORD to a non-empty value for the
[postgres] | superuser. For example, "-e POSTGRES_PASSWORD=password" on "docker run".
[postgres] |
[postgres] | You may also use "POSTGRES_HOST_AUTH_METHOD=trust" to allow all
[postgres] | connections without a password. This is *not* recommended.
[postgres] |
[postgres] | See PostgreSQL documentation about "trust":
[postgres] | https://www.postgresql.org/docs/current/auth-trust.html
[mattermost] | Error: failed to load configuration: could not create config file: open /mattermost/config/config.json: permission denied
[mattermost] | Usage:
[mattermost] | mattermost [flags]
[mattermost] | mattermost [command]
[mattermost] |
[mattermost] | Available Commands:
[mattermost] | completion Generate the autocompletion script for the specified shell
[mattermost] | db Commands related to the database
[mattermost] | export Export data from Mattermost
[mattermost] | help Help about any command
[mattermost] | import Import data.
[mattermost] | jobserver Start the Mattermost job server
[mattermost] | server Run the Mattermost server
[mattermost] | version Display version information
[mattermost] |
[mattermost] | Flags:
[mattermost] | -c, --config string Configuration file to use.
[mattermost] | -h, --help help for mattermost
[mattermost] |
[mattermost] | Use "mattermost [command] --help" for more information about a command.
[mattermost] |
Is there a plan to support podman for guys like me?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported setup with podman-compose 1.3.0 and the repository's compose configuration, checking the PostgreSQL password handling and Mattermost config-file permissions shown in the logs. Done means the deployment works under Podman or the supported limitations and required configuration are clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, postgresql
- Domain
- databases, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100