Hello,
I’ve noticed that when I restart my docker compose stack, the app seems to think that the server doesn’t have copies of the latest files and re-uploads them.
The files can be seen in the filesystem of the host, but not through the web interface until they have been re-uploaded. The app uploads duplicates of all the files, at which point the web can see them again, and the fs has duplicates of everything.
This happens when I restart the stack, no upgrades to the system, just docker compose down
and docker compose up -d
My set up is using an unmodified compose file from the docs. Any ideas what I could be doing wrong?
How are you persisting Immich’s database?
Whatever was in the v1.101.0 compose file, which seems to be a docker volume.
Did you set the
UPLOAD_LOCATION
variable in your.env
file?Yes, it is set. The files persist fine and in the right location. I think Lem453 is along the right track. I think it’s a dB issue