#Postgres permissions error when supplying user in docker-compose.yml

1 messages · Page 1 of 1 (latest)

fossil copper
#

I am using the docker-compose.yml install from the official docs. I am also trying to follow the non root user info in the FAQ.
My .env and docker-compose.yml files are attached, these are straight from the docs, except the changes in the .env as needed and addition of the user for each service.

The database container fails to start with this error:

immich_postgres          | chmod: changing permissions of '/var/run/postgresql': Operation not permitted
immich_postgres          | The files belonging to this database system will be owned by user "postgres".
immich_postgres          | This user must also own the server process.
immich_postgres          | 
immich_postgres          | The database cluster will be initialized with locale "en_US.utf8".
immich_postgres          | The default database encoding has accordingly been set to "UTF8".
immich_postgres          | The default text search configuration will be set to "english".
immich_postgres          | 
immich_postgres          | Data page checksums are enabled.
immich_postgres          | 
immich_postgres          | initdb: error: could not change permissions of directory "/var/lib/postgresql/data": Operation not permitted```

I notice that the db folder is being created as owned by root, so that is probably the issue. But how do I get around this if I want to run as non root user?
`drwxr-xr-x 2 root   root   4096 Feb 27 15:27 immich_db`
📎 docker-compose.yml
harsh fernBOT
#

:wave: Hey @fossil copper,

Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich immich.

References

#

Checklist

I have...

  1. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time).
  2. :blue_square: read applicable release notes.
  3. :blue_square: reviewed the FAQs for known issues.
  4. :blue_square: reviewed Github for known issues.
  5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
  6. :blue_square: uploaded the relevant information (see below).
  7. :blue_square: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable

(an item can be marked as "complete" by reacting with the appropriate number)

Information

In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:

  • Your docker-compose.yml and .env files.
  • Logs from all the containers and their status (see above).
  • All the troubleshooting steps you've tried so far.
  • Any recent changes you've made to Immich or your system.
  • Details about your system (both software/OS and hardware).
  • Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h).
  • The version of the Immich server, mobile app, and other relevant pieces.
  • Any other information that you think might be relevant.

Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)

If this ticket can be closed you can use the /close command, and re-open it later if needed.

gray willow
#

You need to manually create the bind mount folder and chown it to the user for each container

#

This is a basic docker non root thing

fossil copper
#

Oh geez, yeah, that did the trick. Thanks!