Downloader Paths - Docker

[NZBmets]

Based on the way persistent storage that Docker uses, and the virtual paths it happens that some download agents may have a path that is different from Sonarr’s known paths. This is an unfortunate but understandable dynamic of the mapping.

For instance, in my particular setup I have Deluge running in a Docker container and Sonarr running on the actual host. When Deluge finishes a download it properly notifies Sonarr with the path it knows - however Sonarr is not then able to post process the downloaded item as it cannot access the file - it’s path is different.

It would be helpful to be able to override the completed download path on a per download agent setting to address this. Let Sonarr get the notification from the download agent but prefer the path given in a configuration if it is given.

[markus101]

Good news, you already can do this, check out Remote Path Mappings on Download Client Settings.

[NZBmets]

Thanks for the direction. I’ll give it a test for my use case. I thought there might be conflict because it wasn’t for each individual downloading agent so I stayed clear of it.

[markus101]

It uses the host and the remote fields to determine if it should apply, if the host or the start of the path doesn’t match it will skip it and move on, in the end its a bit more flexible and would let you remote map multiple paths on the remote machine using a parent path.

[NZBmets]

A terrific approach and works well. Thanks so much.