Container Start Error at first initialization attempt
I am currently trying to install immich on Ubuntu Server.
My docker version is 27.5.1. The machine learning, redis containers start up and enter a "healthy" state, postgress stays "running" while the immich server itself continues to stay "starting".
The volumes are mapped to a mount point on my NAS. Docker had the rights to create the specified subfolder itself.
The Immich Server logs repeat the following indefinitely
Does anyone have any idea what is causing this and how to fix it?
9 Replies
:wave: Hey @Nikodemus,
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. :blue_square: 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. :ballot_box_with_check: 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.The postgress container logs repeat everything apart from the first paragraph
The used yaml is unchanged. The env holds:
The db password has no special caracters anymore since https://github.com/immich-app/immich/discussions/15353 advised against that.
https://github.com/immich-app/immich/issues/16054 seems similar but restarting was no solution yet
Are you mounting the DB on the NAS as well?
Your db can't write to wherever it is set too
nas_share is the mount point yes.
That's why I specified that docker was able to make the subdirectory just fine.
Should the yaml be changed from the default when using network shares in the cifs standard?
You shouldn't use a network share for the DB. It's bound to cause issues
Hmmm, what sizes does the DB grow to?
< 10 GB for a normal to large instance
It grows with your assets
mine is 3 GiB for 140k assets/550GiB
Huh, that seems to have done the trick.
Thank you so much!