synology immich update from v1.111.0 - best strategie?
Hi
I managed to install Immich last year on my Synology NAS DS223.
So my Installation was v1.111.0
Since I'm so happy with Immich and it reminds me about all the new versions, I thought, now it's the time to update and get all the good goodies.
Do this first for ANYBODY who has no knowledge about container manager like me and want's to update, it saved my work!
https://immich.app/docs/administration/backup-and-restore
I happily made a backup from ssh:
sudo docker exec -t immich_postgres pg_dumpall --clean --if-exists --username=postgres | gzip > "/volume1/docker/immich-app-backup/backup/v1.111.sql.gz"
But my Container Manager didn't show any new versions.
So I did, what maybe you shouldn't do?
I changed my .env file from:
not sure if the value was "latest" or "release"
IMMICH_VERSION=release
to
IMMICH_VERSION=v1.129.0
It did download and install everything without any erorrs, but after this I couldn't access Immich anymore.
I managed to restore the containers again to "IMMICH_VERSION=v1.111.0" and make a "clean" build, so I could restore the DB, since it was "corrupt" after the v.129.0.
After searching all links, I found this:
https://github.com/immich-app/immich/releases?page=3
and managed to update from v1.111.0 to v1.117.0 again, with just changing
IMMICH_VERSION=v1.117.0
Since this was the first version with "Breaking changes".
So is my idea, how to update on synology container manager correct?
1. make a DB backup from the current running version.
2. read the release notes from existing to next and as soon a breaking changes is noted, take this "major" version
3. just adjust the IMMICH_VERSION placeholder and run rebuild and only check my "docker-composer.yml" if explicitly noted in the "braking changes"
I know this is a beginner question, but I didn't find any youtube videos on updating Immich with Synology. Only First installation - which are good.
I'm not sure, if I'm doing it the right way.
Any Tipps are welcome
thank you
4 Replies
:wave: Hey @nowak,
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. :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.Yes that process sounds correct
thx... so I will go on with updating 😉
This thread has been closed. To re-open, use the button below.