#lost data after updating overseerr (Docker Windows)

37 messages · Page 1 of 1 (latest)

crisp sundial
#

I just installed last week. i saw on the site that the /app/config warning was fine.
I just updated overseerr today and when i opened the website it asks me to reconfigure anything.

any idea why this happened? did i install it incorrectly?

any help is appreciated.

timber torrent
#

You didn't mount your config volume correctly

crisp sundial
#

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?

stoic glacier
crisp sundial
#

So what would i need to do to update in this case?

stoic glacier
crisp sundial
#

But I'm using Docker for Windows. Is it the same thing?

stoic glacier
crisp sundial
#

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

stoic glacier
#

Yes, that looks correct. I don't use Windows myself, but I don't see any issues.

crisp sundial
distant pawn
#

On Windows, we recommend following our install docs and using a named volume.

crisp sundial
#

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

distant pawn
#

Follow the steps to create the volume first. Read the docs please

#

Everything you need is there 🙂

crisp sundial
#

yeah that's what i had followed previously. but then while making an update it deleted the old volume

distant pawn
#

Did you do this?

crisp sundial
#

yes, then i ran the other command i shared

distant pawn
#

How did you update Overseerr?

crisp sundial
#

using this info

distant pawn
#

Not sure why your data was wiped, then.

crisp sundial
#

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?

distant pawn
#

if you reinstalled WSL you would have wiped all data

#

because the data lives inside your WSL install

crisp sundial
#

yes, but i meant after reinstalling everything and running the commands back

distant pawn
#

but yes, you should see the named volume listed.

distant pawn
crisp sundial
#

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

distant pawn
#

if you're starting over, just follow the instructions in our docs and you should be golden 🙂

crisp sundial
distant pawn
#

It's normal when using a named volume

crisp sundial
#

okay thanks for the help!