Immich server infinite restart loop after updating to v2.2.1 on Raspberry Pi 4B (8GB)
Dear Immich staff,
After updating from v2.2.0 to v2.2.1 this morning the immich server container keeps restarting in docker. I have been using immich just fine, but a while back the same issue occurred with a different version update which got fixed.
I was wondering whether I am doing things wrong or some bug has been reintroduced that breaks things on Raspberry Pi.
I am using OpenMediaVault (latest version) on a Raspberry Pi 4B with 8GB RAM, the docker-compose plugin for OpenMediaVault to then run the docker images for immich on.
I'll check the checklist and upload relevant info soon.
19 Replies
:wave: Hey @StudieBoi,
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. :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 contents of my docker-compose file below:
that doesn't say much... can you attach your logs?
Successfully submitted, a tag has been added to inform contributors. :white_check_mark:
is that all? I there's only redis logs there. anything from server?
I only have logs from the server from yesterday and before that, but the server was on v2.2.0 then, and it worked fine.
Right now I checked docker ps again, it does the same as it did this morning.
immich-server keeps restarting (1)...
can you try starting without daemon mode, to get the logs before the restart?
euhh I am not that big of a docker pro, how does that work?
docker compose up
I'm not familiar with OMV, I'm assuming you have access to a terminal
yeah I do
it's taking me a while to get into the docker part of it but it is possible (I don't do this often)
ok something is going wrong with environment files, sorry for the wait but I am trying some things to get it running without -d
ls in this folder gets me :
compose.override.yml immich.env immich.yml
Hey, back again: I have something that might be more useful. I followed the logs of just the immich_server container and got the following:
uhhh wut
try removing and re-pulling the image
to double check: you mean
1 -> docker down,
2 -> pull,
3 -> up -d
No, you need to actually remove the image
docker image rm etcoh ok
is it safe to also run down because I keep getting an error that the image is used by a stopped container
Yes
ok. I will be running
1: down
2: remove immich server
3: pull
4: up -d
That took a while huh, but great news! It is up and running now. I also tried restarting the container once to test if that also works, but re-pulling the image somehow fixed things. Thank you very much for your help!
should I mark this issue as solved myself or is that something the admins do here?
This thread has been closed. To re-open, use the button below.