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?
There is an issue with your database persistence. The file is being uploaded but it’s not being recorded in your database for some reason.
Describe in detail what your hardware and software setup is, particularly the storage and OS.
You can probably check this by trying to upload something and then checking the database files to see the last modified date.
I haven’t had time to look into this, but I think this might be the right track. Is it possible for docker to get volumes mixed up? Like, could there be a duplicate dB volume and when the stack gets restarted, docker picks one or the other?
To answer your question, I’m running docker 26.1.1 on Ubuntu server 22.04.4 LTS
The system is on an ssd and the storage is a three disk raid5