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
I mounted that volume the first time I opened immich’s compose file, glad they changed it =)
I’m not using immich in docker. Can you explain what this breaking is there to fix?
The datbase files were saved in an internal docker directory and the breaking change is that the location is now different, outside of docker.
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
deleted by creator
Didn’t know it, so from readme: Immich, a high performance self-hosted photo and video management solution.
Me, an intellectual, who was already mounting the database data folder to the host filesystem.
deleted by creator
What does it mean that it’s “opt-in”? Meaning, my opt-out is just to never update Immich again?
So the way I read it, if you want to opt in, you make the new changes they state in your yml. I didn’t and just hit upgrade to pull the new images and it worked fine. I don’t see any issues, but I’ll be glad if someone says I did it wrong.
I think it’s only breaking if you pull the new yml and don’t move your data.
First time im not completely sure how to proceed with update. This part is unclear to me:
Unfortunately there isn’t a “proper” way to export a docker volume. The recommended method is to mount the volume and the directory (you want to copy your data to) to an arbitrary container, get a shell inside that container and copy the folder manually.
I know how to stop the container and dump db, but need some help here
Thx ill give it a try
