Manual installation with podman-compose with Appwrite version 1.4.13

[ptoal]

👟 Reproduction steps

When trying to follow the "Manual Installation" steps with podman-compose, the database is not correctly configured, and the environment variables are empty.

In this case, I am attempting to use rootless podman-compose on a RHEL9 system, which is the preferred way to run containers in this environment.

I realize this is not within the current scope of the project, but if you could provide some assistance, I am prepared to do the heavy lifting to make this work.

I have run the installer to generate my initial docker-compose.yml, and .env files. I then modified them to make them work in a podman environment, by replacing image: locations to use docker.io (since this isn't the default podman registry). I updated the docker.sock location to /run/user//podman/podman.sock, and applied security_opt: label=disable to allow shared access.

All of the containers run, but visiting the site through a web browser returns: {"message":"Error: Server Error","code":500,"version":"1.4.13"}

👍 Expected behavior

It should configure the database, and start the pod.

👎 Actual Behavior

The database is rejecting connections:
Fatal error: Uncaught Exception: Failed to connect to database: Failed to create connection: SQLSTATE[HY000] [1045] Access denied for user ''@'10.89.0.175' (using password: NO) in /usr/src/code/app/http.php:82

Running: podman exec -ti appwrite vars shows all the vars, with no values in them.

Logging into the mysql container reveals that the database has been created, and the user has been created, but no privileges have been granted to the 'user'. Therefore, nothing can connect to the database.

🎲 Appwrite version

Version 1.4.x

💻 Operating system

Linux

🧱 Your Environment

Appwrite 1.4.13.
RHEL 9.2
podman-compose from EPEL

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

[ptoal]

Okay. I've tracked this down to a difference with how podman-compose works. Ref: containers/podman-compose#491

I have managed to get appwrite up and running in rootless mode with the attached podman-compose.yml file.

To make this work, you also have to enable the podman socket systemctl --user enable podman.sock.