immich_server and immich_machine_learning not starting after 1.133.0 update
Hi, I performed an update to 1.133.0, making the necessary changes my
docker-compose.yml as indicated by the Github release notes.
After the modifying docker-compose.yml, I ran sudo docker compose pull && sudo docker compose up -d .
The images pulled fine, but while the immich_redis and immich_postgres started up fine, the immich_machine_learning and immich_server have been starting up for hours at this point. The storage device immich is running from is a fast M.2 SSD inside an old gaming laptop, and I don't see any resource-intensive processes running on the system.
Did something go wrong with the update, or is something misconfigured on my end?
36 Replies
:wave: Hey @HorrayPhobic,
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.Neither immich_server or immich_machine_learning have any log output.
Successfully submitted, a tag has been added to inform contributors. :white_check_mark:
Can you try running docker compose down then docker compose up again?
See what is from the logs of the whole stack
It seems that the two problematic containers do not want to stop.
Just ctrl c
Then run docker ps
If the two are still up, run docker container rm <container-id>
can you do
docker compose up and monitor the logs for all contianers?And show us
sudo df -hT and sudo lsblkRunning
docker compose up just shows the following message, and nothing after. Also attached the outputs of the other commands.
Hi, are there any more logs and/or info I can provide? I still haven't managed to get the two containers to start up. Thank you.
can you run
docker compose down then docker ps?
The machine learning and server containers never seem to stop when I run
docker compose downcan you restart your system?
then run
docker ps after restartingRestarted:
and now compose up of course
you might also want to do this so you don't need to run sudo for every docker command https://docs.docker.com/engine/install/linux-postinstall/
Docker Documentation
Post-installation steps
Find the recommended Docker Engine post-installation steps for Linux users, including how to run Docker as a non-root user and more.
Thanks for the tip, but I prefer it this way, since from my understanding, adding the user running a container to the docker group is equivalent to unrestricted root, since they can do
docker run --privilegedI see you modified some in your docker compose file, can you try using the stock docker-compose file?
I backed up my current compose file with the stock one available at https://github.com/immich-app/immich/releases/latest/download/docker-compose.ym, but while the docker images pulled fine, the "recreate" step of
docker compose up just keeps on running with the system at idle
Do you see any logs?
No, it just seems to be stuck on recreating the images:
hmm something is up with docker on your system it seems
How did you install docker?
I have Docker and the Compose plugin installed on an Arch Linux system from the Arch Linux repositories:
Client:
Version: 28.1.1
API version: 1.49
Go version: go1.24.2
Git commit: 4eba377327
Built: Mon Apr 21 13:12:23 2025
OS/Arch: linux/amd64
Context: default
Server:
Engine:
Version: 28.1.1
API version: 1.49 (minimum version 1.24)
Go version: go1.24.2
Git commit: 01f442b84d
Built: Mon Apr 21 13:12:23 2025
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: v2.1.1
GitCommit: cb1076646aa3740577fafbf3d914198b7fe8e3f7.m
runc:
Version: 1.3.0
GitCommit:
docker-init:
Version: 0.19.0
GitCommit: de40ad0hmm those look fine
I am not sure why it keeps hanging though
I can try and transplant the Immich data from my Arch home NAS system to my main desktop, which also runs Arch, and see if it works. Would that be a reasonable approach?
probably
you live dangerously running arch on your home server 😛
normally you'd prefer something more stable
At this point, I've broken so many Debian and Fedora installs that I just decided to run what I'm familiar with everywhere
I'll send a message when I'm done moving the Immich folder to my main system
Have you tried not breaking things 🤔
I've tried running my Immich instance on a different system with the stock compose file. It seems that a fresh system + stock compose file have fixed the issue. I will try and reinstall Docker, Compose, and the Nvidia Container Toolkit on my NAS system, and update this thread with the results.
I have reinstalled
docker docker-compose containerd nvidia-container-toolkit libnvidia-container libseccomp on my NAS system, and reverted to using the stock docker-compose.yml file. I haven't yet checked if HW accelerated transcoding and ML work, so I've just disabled them for now. I think the issue might stem from my original docker-compose.yml using the Redis 6.2 image, instead of the Valkey image, probably stemming from me forgetting to update my compose file at some point.
Thank you everyone who helped me troubleshoot this.This thread has been closed. To re-open, use the button below.