I know we had posts like this before, but Immich deserves 👏
One more update, one less container, the best Google Photos alternative, its just amazing!!
Don’t forget to edit your docker-compose before updating
I know we had posts like this before, but Immich deserves 👏
One more update, one less container, the best Google Photos alternative, its just amazing!!
Don’t forget to edit your docker-compose before updating
Noticed it stopped working yesterday, wasnt at home so I couldn’t really get into it, just checked the docker logs via portainer on the go and was like “wtf is this error?!” Was relieved when I learned what the issue was and that it’s just a restructuring of the containers.
While it can be unnerving that they don’t shy away from breaking things in order to improve the service, it’s actually a very good thing and keeps the app from getting bogged down in some "but backwards compatibility"legacy code hell (wonder what some people in Redmond would know about that). Let’s just hope that they never publish an update that permanently breaks things when you haven’t followed a very strict weird update procedure or something.
you should exclude the immich stack from auto-updating and subscribe to immich releases.
most of the time will just be a
docker compose pull && docker compose up -d && docker compose logs -fAnd for the love of god don’t go for latest, just stick to the release tags
They have mentioned that once out of dev/alpha status they will figure out proper release versioning so you can pin a major version and not get breaking changes.
Do not have docker containers auto update.
Or, if you do have it auto-update (like I do) prepare for things to break every now and then. I auto-update just about all containers except those that would break either my home automation or my ability to login to my network and fix things. Everything else auto-updates, including Immich.
My Immich broke this weekend when they switched the stack over to
pgvecto, to use vector searching in Postgres. Easily fixed, but took me a solid minute to figure out what had changed.Which is kinda weird they didn’t communicate this one so well. In the lead-up to v.1.88.0, Alex made an announcement on Github to let people know the breaking change was the removal of the web container from the stack, rolling the webserver into the main server container itself. That was a good move, as all I did was flip my Watchtower container on that host to monitor only.
Dunno why they didn’t do something similar for the Postgres change. Was just as breaking.
Updating software that’s in such early development without reading the release notes is foolish.
Is it hard to breathe in that rarified air, up on your high horse?
I’ll keep taking my calculated risks. You keep judging strangers on the internet. 👍
roofuskit is right. Unless you use it as secondary method of backing up your memories - it is foolish. There are constant breaking changes that requires modification to Docker-Compose for Immich project. But you do you. :) I am not Google to tell you what to do. 😅
Immich saves pictures on the filesystem, where they are easily picked up by all my backup solutions. My pictures also get uploaded on NextCloud before being moved to Immich’s auto-upload folder.
… Where exactly is the risk for my precious memories? The bloody thing could
rm -rf /*for all I care.Unless the container follows semver and only auto updates minor versions.
Edit : Which Immich isn’t.