v1.102.0 ⚠️ Breaking Changes (OPT-IN ONLY) CautionFor people always pulling the latest compose file, this is a breaking change! Disregarding the notes will result in (temporary) data loss! Backgrou...
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.
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.
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.
I honestly never once thought to do this. Ever. No likey.
Especially since the original doesn’t care about selinux and it would overwrite everything.
And it doesn’t specify a repository which breaks auto updates of podman
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.
What’s the difference? The docker volume, on my setup anyway, is in /mnt/md0/docker-data/immich_upload/_data/
It’s still a directory on the host either way? Although I guess if it’s a mount point it won’t get removed when removing volumes in docker.
That last point is the important one. For important data, I want the setup to be as easily accessible and system agnostic as possible.