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?
You must log in or register to comment.
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_LOCATIONvariable in your.envfile?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
Are you using a web proxy? I am guessing it may be doing partials because of upload limit of the proxy.
It is sitting behind caddy, not sure if that’s considered a proxy
Yes that is a proxy.
I haven’t set a Max size, and from what I can understand in the docs, caddy doesn’t have a default Max upload
I’ve no idea about the max size hypothesis. I’m simply confirming that Caddy is a proxy in this context.
https://caddy.its-em.ma/v1/docs/limits you appear to be correct it’s something else. Reviewing logs of Immich and if the images uploaded can be accessed would be good info to start with.
The images are definitely uploaded. They’re on the fs, and in the correct folders
