Hi Mayanayza,

First of all, great work on this project — the UI is very clean, and the setup process through Docker was straightforward.

I’ve run into an issue when deploying the application directly on a Proxmox host.
When running the same Docker Compose stack inside a standard VM or from Portainer, everything works perfectly.
However, when running it directly on the Proxmox host, the PostgreSQL container fails to start properly.

Here’s the key part of the container log:

PostgreSQL Database directory appears to contain a database; Skipping initialization
LOG:  starting PostgreSQL 17.6 on x86_64-pc-linux-musl
LOG:  listening on IPv4 address "0.0.0.0", port 5432
LOG:  could not create Unix socket for address "/var/run/postgresql/.s.PGSQL.5432": Permission denied
FATAL:  could not create any Unix-domain sockets
LOG:  database system is shut down

The container keeps restarting because of this fatal error.
It seems to be a permissions issue with the /var/run/postgresql or /tmp directory inside the container.
I’ve tried re-chowning the data directory and also running with elevated privileges, but the issue only happens when Docker is running directly on the Proxmox host (not inside a VM).

Would you please confirm if this could be related to how the container handles socket paths or user permissions in environments like Proxmox?
Any recommended workaround would be appreciated.

Thanks in advance for your help — and again, great work on this app!