Hello, I am new to the world of Overseerr and plex. I've setup Overseerr running docker for desktop and portainer. Although when restarting the server, the data Overseerr saves gets reset. I think it was something about trying to do a mount that I couldn't fix myself. I decided to run a VM with overseerr instead, but had no luck either. I was wondering if there was someone else that has the same issue as me and potentially has a fix for it.
#Overseerr restting when restarting server
21 messages · Page 1 of 1 (latest)
I've been using Overseerr for awhile now and since updating to a newer version I get this too.
I'm using Windows 10 and running Overseerr through Docker. I lack the fundamental understanding of how Linux works and how to mount the config directory to the correct place.
I have read through the installation page and read where it notes that Windows handles things differently from Linux and I understand what I need to do just don't quite no how to do it.
I'm going to search through the rest of support and see if I find any similar posts.
Any help would be appreciated.
I think I found the solution, mine works now
by pressing duplicate/edit on overseerr container
going to the bottom of the page, pressing volume and change the volume location
I don't know if this was a great fix, although now i can safely restart my server or docker without the loss of data.
What are you using? I don't recognize the UI. Is that a separate docker management type system? I'm just using the stock Docker Desktop program in windows.
Oh you need to install portainer first, before you can get overseerr
Im using docker for desktop and installed portainer
I was able to access the '\wsl$' directory with file explorer (which I tried before and it never worked, using the full directory path given on the docs.overseerr page, but got to work by just using '\wsl$\docker-desktop-data\data\docker\volumes').
From there I created an app\config (app folder and config folder within that) directory and copied the db folder into that.
That seemed to have worked? Maybe? I quit docker all together and it still ran correctly with no loss of settings when I started Overseerr again.
No idea if that's the way to do it or if it'll stay fixed though.
I was running Overseerr for a few months before this issue popped up so we'll see.
But I'll look into Portainer.
Oh and I made an app/config folder in overseerr-data/_data for good measure.
That should do it 
creating a volume with Docker like docker volume create overseerr-data would do execute the same steps as you did
Though manually creating the folder like you did will result in Docker not being able to manage it
Can you check if the volume shows up in the Volumes tab of Docker Desktop?
Looks like I have an "app" volume within Docker desktop that was created "2022 years ago." That's is "not in use" within that there is no data to be displayed. : \
Assuming that's not right (doesn't really seem like it) if I were to create a new app volume and place a config folder within that, how do I associate it with the overseerr container? Can I have two volumes (app/config and overseerr-data) within one container?
You can't use 2 at the same time for this purpose
But you can create a new volume how docker needs you to, then copy your data to that new volume. Then use that volume for the Overseerr container