immich_server exited with code 0
Hey!
I'm having a really weird issue in which the container is refusing to start. I'm very used to docker and I have never experienced anything like this; the whole process seems to be refusing to start. I've tried just about everything. Everytime I start the stack it does this: https://pastebin.com/z1uV5vXp Here is my docker-compose: https://pastebin.com/iC60GEfg
Pastebin
immich_machine_learning | [07/16/24 13:33:04] INFO Starting gu...
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
Pastebin
name: immichservices: immich-server: container_name: immich_ser...
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
7 Replies
:wave: Hey @Matthieu,
Thanks for reaching out to us. Please follow the recommended actions below; 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 compose ps docs
- Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
Checklist
1. :blue_square: I have verified I'm on the latest release(note that mobile app releases may take some time).
2. :blue_square: I have read applicable release notes.
3. :blue_square: I have reviewed the FAQs for known issues.
4. :blue_square: I have reviewed Github for known issues.
5. :blue_square: I have tried accessing Immich via local ip (without a custom reverse proxy).
6. :blue_square: I have uploaded the relevant logs, docker compose, and .env files, making sure to use code formatting.
7. :blue_square: I have 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)
If this ticket can be closed you can use the /close command, and re-open it later if needed.I should mention that I have tried disabling network volumes, and using an absolute path. I've even tried disabling every fancy feature and using the absolute default config and it still does this. The container just loops with not a single error message
Do you have the latest container images?
Yes! I am using the release tag
I even tried pruning my images and pulling again
I am goign to try with ghcr.io/immich-app/immich-server:v1.107.2
That worked, and so did manually adding v1.108.0
But for some reason when I add the :release tag, it doesn't pull the image and tries to run an empty container
I've never experiencing anything like that with docker
The release tag is a rolling tag, if you have anything with that tag locally it'll use that
You need to use
docker compose pull to explicitly pull the latest version when updating
(or even better, set a specific version tag like you did now)Indeed, but i even pruned all my unusued docker images, but yes indeed, if I use the release tag it pulls and empty image
very strange
hey Matthieu have you found an answer, i'm having the same problem in my debian x64 setup
i can get any logs from immich_server, that's weird part, it immediately got killed at the startup. I'm using latest version of immich and docker engine.
weird but i tried this one more time (after 5 times) and worked