And in the directory in Windows 11 /Users/power/overseerr/overseerr_data there is overseerr data in there.
Yet every time I restart my PC (or Watchtower updates it) Overseerr resets itself.
However, if I reboot the PC and start Docker Desktop and then stop the container, then in terminal cd into the overseerr directory and rerun docker compose up -d, then navigated to http://192.168.50.6:5055/ Overseerr loads with all its data again. So I’m not sure why it’s doing this, if anyone knows I’d be more than appreciative.
What is the difference between the PC restarting and rebooting the PC? Don’t these mean the same? Or do you think the problem could be only when the PC restarts automatically and doing something differently?
I guess you mean start the container.
As long as you have the volume after restarting automatically it’s up to the application to load the data again, but I have a couple of ideas:
If everything starts automatically after an auto restart on Windows, maybe Docker Desktop can’t start correctly and the mounted data is missing from the container even if it looks like itis mounted according to the metafdata which wouldn’t change just because of restarting.
If watchtower updates the image, it is not just restarting the container, it is deleting the old container and creating a new one. I don’t know Overseerr, but if it has an instance ID which changes when it’s newly created and the id is saved in a different folder, not in the mounted folder, even if the data is still there, Overseerr might not recognize it as its own data.
It could be something with the connection of WSL 2 (on which Docker Desktop is based) and the Windows host. The folder has to be mounted into the virtual machine (meaning WSL 2) and if WSL 2 fails to do that, the folder will be empty.
It seems you mount the fodler from the Windows host through WSL, which could cause performance issues or basically any issue due to the filesystem difference. You could try to enable WSL integration, start your own WSL 2 distribution, and run the docker client from there. Then your compose file could refer to local folders which would be local in the WSL distribution which would be a Linux filesystem and not NTFS.
You could also try an actual volume instead of mounting a host folder.
I assume you checked the container logs as well. Did you see any suspicious?
By the way you are clearly not using a Windows container so I moved the topic out of the chosen “Windows containers” category.
How do i do that? I tried creating a volume in Docker Desktop i.e. overseerr_data, then when setting the volumes in docker desktop for overseerr I put overseerr_data:/config and that didn’t work, the container didn’t use that volume.
Thanks for the reply, by the way, I’m still learning all about docker. Lots I don’t understand.
The part you shared about creating a volume is correct, but it is only a part of it. Unless you share the whole config, we can’t tell if it is really correct. The container can’t ignore a volume, so it would help if you could share what exactly happened. Was the data folder empty?in the container after recreating it? Also if something deletes the volume too, a new volume will be created
The volume overseerr_data was created in Docker desktop for Windows, and no data was added to the volume after creating the Overseerr container. Rather, docker seem to create a volume with random numbers and letters. This volume did not persist, and any data I had in it for Overseerr was deleted on restart of Docker. I’m not sure why Docker did not use the volume overseerr_data that I created in Docker Desktop.
Does that sound like it’s impossible? You say that Docker can’t ignore the overseerr_data volume I created in Docker Desktop, but it sort of sounds like it did.
