#lost data after updating overseerr (Docker Windows)
37 messages · Page 1 of 1 (latest)
You didn't mount your config volume correctly
https://docs.overseerr.dev/getting-started/installation#docker read the warning at the top
im using windows, and i used this
docker run -d --name overseerr -e LOG_LEVEL=debug -e TZ=America/Toronto -p 5055:5055 -v "overseerr-data:/app/config" --restart unless-stopped sctx/overseerr:latest
is this not right?
Unless you have also created a volume beforehand with the name overseerr-data then that volume does not persist, like stated in the docs linked above.
So what would i need to do to update in this case?
You need to define a config volume that points to an actual location on the host machine. Use an absolute path. https://docs.docker.com/storage/volumes/
But I'm using Docker for Windows. Is it the same thing?
Yes, it's the same thing. Docker on Windows runs on a virtualization layer so it's technically running a virtual Linux machine.
so ideally something like this?
docker run -d --name overseerr -e LOG_LEVEL=debug -e TZ=America/Toronto -p 5055:5055 -v "B:\overseerr-data:/app/config" --restart unless-stopped sctx/overseerr:latest
Yes, that looks correct. I don't use Windows myself, but I don't see any issues.
i tried it and it's saving my overseerr-data in my actual drive rather than the virtual machine linux. so it makes sense now. thanks for the help!
On Windows, we recommend following our install docs and using a named volume.
Follow the instructions here: https://docs.overseerr.dev/getting-started/installation#windows
so like this then? docker run -d --name overseerr -e LOG_LEVEL=debug -e TZ=Asia/Tokyo -p 5055:5055 -v "overseerr-data:/app/config" --restart unless-stopped sctx/overseerr:latest
Follow the steps to create the volume first. Read the docs please
Everything you need is there 🙂
yeah that's what i had followed previously. but then while making an update it deleted the old volume
Did you do this?
yes, then i ran the other command i shared
How did you update Overseerr?
using this info
Not sure why your data was wiped, then.
i completely wiped my docker and reinstalled wsl as well. so i will try it this way again installing an older version then test the update
so ideally i should see "overseerr-data" in the volumes tab on docker right?
if you reinstalled WSL you would have wiped all data
because the data lives inside your WSL install
yes, but i meant after reinstalling everything and running the commands back
but yes, you should see the named volume listed.
not sure what you mean by this
when i reinstall overseerr now, i should see overseerr-data in volumes tab right?
but you answered yes already so it's okay haha. ill try everything again. i think my linux distro was corrupted when i did it before
if you're starting over, just follow the instructions in our docs and you should be golden 🙂
yeah that's what i had done previously and never had issues, so i was confused quite a bit.
and as it says, seeing the warning message for /app/config is normal for windows right?
It's normal when using a named volume
okay thanks for the help!