Failing to upgrade to V1.131.0 on docker
I'm getting a manifest error when trying to pull the image. (sanitized)
Compose and env file to follow.
24 Replies
:wave: Hey @Krispy,
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.Allow 30 minutes for new images to propagate and check again please
will do. I'm sourcing from ghcr.io
this is a bug, the team is looking into the fix
WUD also didn't discover an updated image for the CUDA machine learning image.
This is a different issue actually
The ML build is delayed as there's some other jobs running that are holding it up
gotcha, i'll hold updating for a while
If you want, you can monitor https://github.com/immich-app/immich/actions/runs/14179298526/job/39721496184 to see when it gets going
There it goes
Just got unstuck
Should be available now @Krispy
trying now
machine learning container is unhealthy. Is this me, or a bug? I can start posting logs if needed
compose file
.env file
hwacell.ml.yml
docker ps output:
logs
Or logs seperately instead of via the compose logs command...
machine learning:
ML container is unhealthy for me too
Basically the same log
I see a .1 just got published
I updated to 1.131.1 and it still has the issue for me
Honestly it's weird that it's showing unhealthy
Logs look okay
Issue has been found 🙂
It's literally the file that does the healthcheck inside the container that's missing
Ah gotcha! Thank you for your hard work!
So, .2 on the way?
Probably not that fast considering it's not breaking anything other than being annoying
But I imagine the wait won't be too long, no promises though 👀 I'm not a dev
Totallyy fine!