Any support with podman-compose?

[alexisfrjp]

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?

[heriklesDM]

Hey I did not use podman compose, but it works with base podman.

Quick Note: I did not copy and paste

Simply create the containers manually:
It should work rootless though I did not test it.
Create a network for your proxy solution, I used caddy
Pull your containers individually, I am on Centos and used the cockpit UI as the CLI threw some errors, but after running the compose you should have the images anyways.

Use an .env file with your postgres info:
DOMAIN=mm.example.com
POSTGRES_DB=mattermost
POSTGRES_USER=mmuser
POSTGRES_PASSWORD=mmuser_password

First get the database up and running:
sudo podman container create --name mattermost_db --pod Mattermost --env-file .env -v ./volumes/app/db/data:/var/lib/postgresql/data postgres:13-alpine

sudo podman container create --name mattermost --pod Mattermost --env-file .env
-v ./volumes/app/mattermost/config:/mattermost/config
-v ./volumes/app/mattermost/data:/mattermost/data
-v ./volumes/app/mattermost/logs:/mattermost/logs
-v ./volumes/app/mattermost/:/mattermost/plugins
-v ./volumes/app/mattermost/client:/mattermost/client/plugins
-v ./volumes/app/mattermost/bleve-indexes:/mattermost/bleve-indexes
mattermost/mattermost-team-edition:10.5.2

(quotes to keep formatting - pull the container first)

Make sure to change the config.json to use the correct database path:
"DataSource": "postgres://mmuser:mostest@mattermost_db/mattermost?sslmode=disable\u0026connect_timeout=10\u0026binary_parameters=yes"

I didnt use the environment variable so I could change it on the fly without recreating the container constantly.
Note that the mattermost_db is the name of my database container.
If they are in the same pod, this works perfectly.

Then simply create a network for your reverse proxy:
sudo podman network create mattermost
and add your caddy and pod container to it
sudo podman network connect mattermost caddy
sudo podman network connect mattermost mattermost_pod (rename your [something]-infra pod container to mattermost_pod first)
and simply point the proxy to mattermost:8065 - the best part is that you dont even need public facing ports if your proxy is also in podman and the network.

Hope this helped - even though its not the full compose.

[netsgnut]

Sorry for reviving an old thread, but in case anyone stumbles upon this, you can try making the following changes to spin up a Mattermost service with Podman Compose. It works for me, but admittedly, it may not be best practice. Take it with a grain of salt:

1. For mattermost service, add: (adjust the user ID according to the system UID that you are running the containers with)

mattermost:
    env_file: .env
    user: 1000:1000
    userns_mode: "keep-id"

2. For postgres service, add:

postgres:
    env_file: .env

3. Disable pod

x-podman:
  in-pod: False

---

Tested on a Debian 13 Trixie server.

podman-compose version 1.3.0
podman version 5.4.2