Immich v1.102.0 - ⚠️ Breaking Changes (OPT-IN ONLY)
Immich v1.102.0 - ⚠️ Breaking Changes (OPT-IN ONLY)
github.com
v1.102.0 - 30,000 Stars Release 🌟 · immich-app immich · Discussion #8930
12 comments
-
-
I mounted that volume the first time I opened immich's compose file, glad they changed it =)
-
lol same I like to know exactly where the data is
-
-
Just did the upgrade. Only went and copied the docker folder for the volume.
# docker inspect immich_pgdata | jq -r ".[0].Mountpoint" /var/lib/docker/volumes/immich_pgdata/_dataInside that folder were all the DB files, so I just copied that into the new folder I created for
./postgresI thought there would be issues with the file permissions, but not, everything went smoothly and I can't see any data loss.
(This even was a migration from 1.94 to 1.102, so I also did the pgvecto-rs upgrade) -
I really wish they get to the point where we can expect long term with no breaking changes. I love it but I have been burnt twice, which is not a lot, but it was very annoying both times
-
-
Who was pulling the dicker compose and just straight up running the GitHub version on their server. That seems crazy. Even pulling :latest tag seems crazy to me but this is another level.
This change is only breaking if you are running someone else's docker compose on your server without looking at it.
Also who was running their entire photo album in a docker volume rather than a mount point on the host. Another insane decision. To be fair, the default docker compose never should have had that. It should have been a mount point right from the start.
-
I don’t run Immich specifically but all other software I run is on :latest tags and unattended-upgrades on Debian. It works so, why bother?
-
12 comments
Who the hell is pulling the docker-compise.yml automatically every release? I find myself already crazy by pulling the latest release but the compose file is just a disaster waiting to happen.
Complete insanity.
Then again it seems like people were using a docker volume to save all their precious photos rather than a mount point on the host. Also seems insane to me.
Could you explain a bit more about why it's insane to have it as a docked volume instead of a mount point on the host? I'm not too well-versed with docker (or maybe hosting in general)
Edit: typo