#THE /CONFIG VOLUME MOUNT WAS NOT CONFIGURED PROPERLY.

4 messages · Page 1 of 1 (latest)

marble scarab
#

I am receiving this message on a new docker install, but I have confirmed the path is correct and went through the setup. After the setup of overseerr was completed and I could access it, I powered off the container and powered it back on just to make sure all the data was still there and it was. Is it safe to assume this can be ignored?

vale axle
#

Are you using a named volume? If so, you can safely ignore this message -- Overseerr is unable to detect those.

marble scarab
#

Yes, I am using a named volume. I read that elsewhere as well, thank you for confirming! 🙂

vale axle