Correct permissions of database folders
Hello everybody,
I was setting up Immich on my debian server with an AI because I'm really new to Docker and linux in general.
I put the databases on another disk at /mnt/data.
At some point the AI tell me to check the user that Immich is using and to change the ownership of the DB;
Run this to check the user ID in the Immich container
docker inspect immich_server | grep -i user
7. Set correct permissions
sudo chown -R root:root /opt/stacks/immich
sudo chmod -R 755 /opt/stacks/immich
sudo chown -R 1001:1001 /mnt/data/immich
So I did a compose up to start the container and it seemed to work, then I tried to get the user ID of Immich but it comes out empty:
docker inspect immich_server | grep -i user
"UsernsMode": "",
"User": "",
"DB_USERNAME=postgres",
I checked in /etc/passwd and there is no Immich user.
Does it matter witch user Immich is using?
Should I change the ownerships like shown above?
Is Immich using my user since I started the compose up?
If I set up a immich.service, will the user be root then?
Thank you guys for your answers.
7 Replies
:wave: Hey @Ankil,
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
- Container Logs:
docker compose logs docs
- Container Status: docker ps -a docs
- Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
- Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA
Checklist
I have...
1. :ballot_box_with_check: 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.You should never need to mess with ownership like that, Docker is meant to handle it for you
I would strongly discourage using an LLM to guide you through this kind of stuff. If you don't learn the details yourself, you'll be in trouble when (not if) things break. And pasting commands from an LLM without knowing exactly what it's doing is a great way to break things as well
That's a good point, but it is really intimidating to get into all of this without something looking over my shoulder
So Immich will be able to acess the database on /mnt/data without me changing anything?
Let docker create the folder, then everything should be set right
Oh so I better delete the folders, then compose up to let docker create them?
This thread has been closed. To re-open, use the button below.
Thanks for your help, closing because it worked :)