Unable to upgrade from 1.139.4 to any newer release with latest compose.yml
Hi,
first, thank you for this wonderful piece of software, it's been improving steadily and I'm using it as my main photo storage (at my own risk) for a while now.
I lately noticed that despite me re-deploying immich with the latest compose.yml, I am still ending up with version 1.139.4 - did I miss any announcement about special steps required to get past that version?
compose.yaml and .env are attached.
I'm managing this via dockge, so what I usually do to upgrade is copying the latest compose.yaml, adding my additional volumes and hitting "deploy". It does download the containers and everything starts correctly, but once I go to the server, it still stays 1.139.5
7 Replies
:wave: Hey @Soukyuu,
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.
Successfully submitted, a tag has been added to inform contributors. :white_check_mark:Btw, link to FAQs 404s on me...
You hit the exact moment where we're migrating the website lol
just my luck lol
I don't know how dockge handles it, but a
docker compose pull should pull the latest versionYou should just need to hit the
update button in dockge on your immich stackI feel kind of dumb right now. I guess that after updating the yaml and hitting deploy I saw dockge re-creating the container and assumed it also pulled the new version. But you're absolutely right, clicking 'update' ... updates ... to the latest release 😅
Sorry for wasting your time