I have Immich Server Version: v1.115.0. They’re up to v1.129.0. I am guessing there have been lots of breaking changes in that range, since that was true the last time I updated.
Is there a safe way now to update without making me read all the release notes and carefully craft my docker compose file in multiple steps to make sure I don’t lose anything in the process of getting caught up?
Thanks for any tips.
ETA: Or just, how do you handle your Immich (in Docker) updates in general?
2ND EDIT: I did read the release notes. After a lot of reading, there was 1 change (updating their internal Port # for the main service to 2283) It’s done. Thanks y’all. My cats appreciate you all.
I’d take a backup, first, and then just send it. Then, if that doesn’t work out, do it the hard and slow way.
I neglected to update for like seven “major” versions recently. I took the safe-ish route to just read every release note as I go and install the last minor version of each major version release, then start, quick check, stop, next one. It turned out fine.
edit: Backup, backup, backup. Then you can’t fail.
I just had to do this. Don’t skip the release notes. They’re really good at highlighting potential pitfalls, just scroll back through and look for the heading “Breaking Changes.”
In my case there were a few, but they were only for API calls I’m not using, so I just did the update in one go and it worked out great. (Of course, I made sure to take a backup first.)
Yeah when I was way behind I just scrolled through releases and did each one where it said it may have breaking changes. Only one time I got messed up but mainly because I run a seperate postgres database that i also use for other apps - somehow the vector plugin got messed up.
I yoloed from a year old version up to the latest, it was fine.
Love that for you.
However, that is not everyone’s experience and doesn’t really answer op’s question.
You’re going to have to read every single release with breaking changes.
That’s one of the reasons I favour Semantic Versioning…
Good opportunity to test your backups.
Restore to a new directory, update that and see what happens. If it works do it to the original.
I just update. If it breaks, I read the notes. Probably the wrong way but it worked. And I use it for a long time. To me, it was never that unstable. And since a couple of months it’s very stable. Backup first.
Yum-cron is the way.
Maybe immich will see the way.
Yum-cron
Hmmm, I’ve heard some people use watchtower too.
Make backup do yolo. So far backup has not been nessasary.
Lol, i was going to post the same question one of these days. I too am almost on the same version and I was hoping some kind soul would help me out.
On top of it I’m not very well versed with docker backups so I’m doubly scared. What I am going to do is to take a mirror image of my whole OS drive in my zfs mount that I use as backup, give a release notes a glance and go YOLO based on what I can make out.
Your post gives me a lot of hope. Thank you!
