I've been having some strange behavior from my docker apps and I've come to believe it's docker itself causing an issue. I set up rutorrent and it was having issues. I tried 2 different docker containers. It was weird seemingly random behavior but here is what I think is happening. It seems like settings changed either aren't being applied or they are very delayed. I would be tinkering with the autolablel system and I would turn it off and it would still function as if it were on. I'd restart and it would still be on. I'd add another path to the docker container and it doesn't show up. I've also noticed with the Sonarr docker I changed one of the path mappings for the docker container and from within the app it shows the old one as well as the new one. I am using beta 21. Is anyone else had these kinds of issues?

I've also noticed with the Sonarr docker I changed one of the path mappings for the docker container and from within the app it shows the old one as well as the new one. I am using beta 21. Is anyone else had these kinds of issues?

Don't know anything about the ruTorrent problem, but sonarr you should post a screen shot of the Advanced Settings when you edit the template (and also click the Show Advanced something or other at the bottom of the volume list), along with a screenshot of where you are seeing the incorrect path in sonarr.

I deleted the docker image and am working on some other stuff so I can't get a screenshot within Sonarr but already had one of the advanced settings. I had changed 'tv' to 'TV' and in Sonarr it showed both, I'm positive about that. I also at one point removed '/root/TV' and it was still there. Another example, I was having was a weird issue with Sonarr sending magnet links to rutorrent with the label 'tv-sonarr'. Once it downloaded the .torrent file the label would be removed and the torrent stopped. Turns out it was a bad combination of the autolabel tool and the wrong default download directory. However, this issue with the delayed settings made trouble shooting the label problem very difficult because the problem with the labels would seemingly resolve itself and then break again. It seemed like the issue was random because I would make no changes to settings and it would suddenly work or I would change a setting that should have fixed it and it wouldn't. I even deleted and redid the rutorrent docker from scratch with default settings, keeping the docker image but having an empty config directory. The new installation would retain custom settings from the previous installation. It seems as if the docker image contains a config directory that is over-ridding the one I have set.

 

Another time I decided to leave it for a while to see what happened. I had changed the default download directory in rutorrent from '/root/' to '/root/downloads/'. Hours later I came back and just watched it, didn't touch anything. It was the usual time Sonarr starts to send files over. Three downloads got sent over. The first one or maybe two had saved to the old default download directory '/root/'. The last one downloaded to the one I had changed it to hours before '/root/downloads/'. I'm pretty certain something is up.

I deleted the docker image and am working on some other stuff so I can't get a screenshot within Sonarr but already had one of the advanced settings. I had changed 'tv' to 'TV' and in Sonarr it showed both, I'm positive about that. I also at one point removed '/root/TV' and it was still there. Another example, I was having was a weird issue with Sonarr sending magnet links to rutorrent with the label 'tv-sonarr'. Once it downloaded the .torrent file the label would be removed and the torrent stopped. Turns out it was a bad combination of the autolabel tool and the wrong default download directory. However, this issue with the delayed settings made trouble shooting the label problem very difficult because the problem with the labels would seemingly resolve itself and then break again. It seemed like the issue was random because I would make no changes to settings and it would suddenly work or I would change a setting that should have fixed it and it wouldn't. I even deleted and redid the rutorrent docker from scratch with default settings, keeping the docker image but having an empty config directory. The new installation would retain custom settings from the previous installation. It seems as if the docker image contains a config directory that is over-ridding the one I have set.

 

Another time I decided to leave it for a while to see what happened. I had changed the default download directory in rutorrent from '/root/' to '/root/downloads/'. Hours later I came back and just watched it, didn't touch anything. It was the usual time Sonarr starts to send files over. Three downloads got sent over. The first one or maybe two had saved to the old default download directory '/root/'. The last one downloaded to the one I had changed it to hours before '/root/downloads/'. I'm pretty certain something is up.

Any directory referenced within the app that doesn't exist will get created within the docker.img.  So, at one point you had told sonarr to look in (or copy to) /tv, while you had passed through /TV    Deleting the docker.img fixed it, so don't worry about it.

I deleted the docker image and am working on some other stuff so I can't get a screenshot within Sonarr but already had one of the advanced settings. I had changed 'tv' to 'TV' and in Sonarr it showed both, I'm positive about that. I also at one point removed '/root/TV' and it was still there. Another example, I was having was a weird issue with Sonarr sending magnet links to rutorrent with the label 'tv-sonarr'. Once it downloaded the .torrent file the label would be removed and the torrent stopped. Turns out it was a bad combination of the autolabel tool and the wrong default download directory. However, this issue with the delayed settings made trouble shooting the label problem very difficult because the problem with the labels would seemingly resolve itself and then break again. It seemed like the issue was random because I would make no changes to settings and it would suddenly work or I would change a setting that should have fixed it and it wouldn't. I even deleted and redid the rutorrent docker from scratch with default settings, keeping the docker image but having an empty config directory. The new installation would retain custom settings from the previous installation. It seems as if the docker image contains a config directory that is over-ridding the one I have set.

 

Another time I decided to leave it for a while to see what happened. I had changed the default download directory in rutorrent from '/root/' to '/root/downloads/'. Hours later I came back and just watched it, didn't touch anything. It was the usual time Sonarr starts to send files over. Three downloads got sent over. The first one or maybe two had saved to the old default download directory '/root/'. The last one downloaded to the one I had changed it to hours before '/root/downloads/'. I'm pretty certain something is up.

Any directory referenced within the app that doesn't exist will get created within the docker.img.  So, at one point you had told sonarr to look in (or copy to) /tv, while you had passed through /TV    Deleting the docker.img fixed it, so don't worry about it.

 

I'm not worried about that. I'm about everything else I mentioned. Settings seem to not change or take forever to change, causing a lot of unexpected behaviors.