September 19, 20223 yr Hi team. I spun up a second instance of a docker today, something i have done many times before. Did the usual best practices, used a different branch and container creator, different ports. Different appdata folder. The container in question is sonarr. After a bit of playing around with the new sonarr container, my original long standing one had no logo. I went to investigate, and was met with the screenshot attached. The path mappings are all, well, weird. the /data ---> /mnt/user/appdata/data is not a path I've ever had configured Sonarr itself is running fine, but im worried about restarting it etc. Not really sure how too proceed to resolve this. The appdata folder is there, with a backup from yesterday. Im also not able too install from template, as sonarr simply isnt in the list. Is this as simple as removing this container, reinstalling sonarr with the mappings i have and pointing the config folder at the already existing appdata/binhex-sonarr folder? magnus-diagnostics-20220919-1737.zip
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.