Having some troubles with my overseerr update.

[restive trout]

Few days ago I moved dockers, and duplicated my overseerr volume on the new host. with some assistance, I was able to get it back up and running on the old data. I had created a volume named overseerr-data, and everything was working fine until I updated this morning.

Stopped and removed container, pulled update, and when i tried to restart i was presented with the setup screen

run -d --name overseerr -e LOG_LEVEL=debug -e TZ=Canada/Eastern -p 5055:5055 -v /overseerr-data:/app/config --restart unless-stopped sctx/overseerr

I can see this volume in docker, but it never goes In Use with the above command. If I remove the / from /overseerr-data:/app/config (just overseer-data:/app/config), the volume becomes used by the container, however I get the 'app/config not mounted properly error in Overseer itself, and it still asks for setup.

I am clearly missing something here regarding volumes. previous i was trying /overseerr-data/_data:/app/config, however i was explained that /overseerr-data/_data is a path, and overseer-data is a volume.

[valid chasm]

/overseerr-data is a path because of the leading slash. overseerr-data is a named volume, which is either created beforehand with a source path on the host machine, or non-persisting.

[clear holly]

When using a named volume, you can safely ignore the warning.