immich server fails as non-root
Hello, I'm trying to set up Immich in a Docker-Container on openMediaVault but i can't access the Web GUI if the Immich-server container runs as non-root. It seems that the connection between the Immich-Container and the redis-Container/immich-postgres fails.
28 Replies
:wave: Hey @oneabe,
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. :ballot_box_with_check: read applicable release notes.
3. :ballot_box_with_check: reviewed the FAQs for known issues.
4. :ballot_box_with_check: reviewed Github for known issues.
5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
6. :blue_square: uploaded the relevant information (see below).
7. :ballot_box_with_check: 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.There’s no problems with these logs
thought i would send all logs in, problem is seen in immich_server logs
Ok but why haven’t your shared those then?
had a little problem with discord
Try setting REDIS_HOSTNAME=redis
As an env
changed it to redis
And that error keeps coming? Multiple. Times?
yes
you didn’t mount a volume for Redis
Oh wait I see it now
Do you have any weird network stuff setup? This looks like a DNS issue
You can try assigning an IP to the Redis container and connect in that way
how can i do that
You can Google how to assign docker container IP
It shouldn’t be needed but you seem to have a nonstandard setup
ok, will try then.Thank you
Immich is now running with the assigned ip adresses but machine learning Container stays unhealthy,will that be a problem?
hi
hi
captcha is broken, it is so hard to accces here as human
probably easier for robots
I started my immmich server on ubuntu using docker
It works well on web locally
Are you aware that you're in someone else's help desk thread?
But when I expose it using npm proxy (nginx) i have 504 error
Can I have any help here?
?
yes
:HUH:
I am not able to write even on welcome chat
why?
You should be able to write in #immich and you should also be allowed to create a new help desk thread
thanks
Found the solution for both problems. The docker user did not have acees to
/etc/hosts
and /etc/resolv.conf
.By mounting and creating them, all Container stay healthy and i don't need the second Docker-Network with the assigned ip adresses anymore.This thread has been closed. To re-open, use the button below.