Updating my immich-server image fails with 504
My server image url is ghcr.io/immich-app/immich-server:release.
Im using portainer on Synology.
I was updating all images without problems, except for the server image.
The portainer frontend does not give any exact information, just
Request failed with status code 504
which is not very helpfull.
I have not changed the docker compose for a long time, but have verified that ghcr.io is still in play by reading the latest docker compose on github.
I have never had this problems before when updating immich images.
16 Replies
:wave: Hey @maximumiq58,
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. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time).
2. :blue_square: read applicable release notes.
3. :blue_square: reviewed the FAQs for known issues.
4. :blue_square: reviewed Github for known issues.
5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
6. :blue_square: uploaded the relevant information (see below).
7. :blue_square: 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.Does the error show when you run
docker compose pull? Can you capture a screenshot where the error message show up?I do this, then at the UI of the container, a popup just says this:
immich-server:
image: ghcr.io/immich-app/immich-server:release
container_name: Immich-SERVER
hostname: immich-server
user: 1026:100
security_opt:
- no-new-privileges:true
env_file:
- stack.env
ports:
- 2283:2283
volumes:
- /volume1/docker/immich/upload:/usr/src/app/upload
restart: on-failure:5
depends_on:
immich-redis:
condition: service_healthy
immich-db:
condition: service_started
Is this synology?
Oh yes, it is. They have issues pulling sometimes, I have seen before in help tickets
@Tempest I think you have seen this before maybe? Or I am remembering wrong
Oh, Is it then just about trying and trying until success. I have never seen it, and have updated Immich often
Can see more here: https://community.synology.com/enu/forum/1/post/159445
I don't use synology so I'm not sure
Could it be a spooked entry in the synology hosts. I shouyld try complete restart....
I don't use portainer on synology, it has container manager already setup for a gui, and it's running legacy code. I'd image issues would arise.
@maximumiq58 When you do have an issue it's best to use ssh as the gui will not be very helpful as you're finding out, which is why everyone is asking for the output / results of running ssh commands directly
I've been busy, but now I should really report back on this issue. After a power down due to failing water heater (one reason I've been busy :-)), the Synology was also reset. If that is the reason or other external to my home is the cause, things are now back to normal.
I was able to update Immich a few days back without any issues. But today, I see there is a new version, and get the same problem again. I use portainer, and recreate Immich DB image, no problems, I recreate Immich redis image, no problems, I recreate Immich learning image, no problems, finally I recreate Immich server image, boom 504. Is there a performance issue with the server for ghcr.io/immich-app/immich-server:release
There is not
You'll want to shut down the containers, remove the container images (not volumes or storage!) and re-pull
Sometimes a layer gets corrupted and subsequent pulls don't correct that
alright, i've been using re-create in portainer without problems until recently.
What is a 'layer' in this context.
Im reluctant to delete the server image, since if getting the new image fails, I can still start the server with the old image. Maybe some functions fails to work properly due to different versions in images, but still I can get to my photos. If I have no server image and have to leave it there, I cant get to may photos.
You can list the images and only delete the one's you're not using
https://docs.docker.com/get-started/docker-concepts/building-images/understanding-image-layers/
a docker layer is, summarized heavily, an edit on top of a base image
it "layers" the edits on top of the previous edits, so you can have reproducible changes, and minimal downloads
OK, thanks. I'll look into it and try read more 🙂
Well, I found that I had a registry entry for the server, but it was named incorrectly. CHCR instead of GHCR, and the server name in that was also incorrect. With this, how could it even work sometimes. Weird.
I tried recreate on immich server again after that, and just updated it.