Remote Path Mappings and Docker Containers [SOLVED]

Help & Support
1

Sonarr version (exact version): 2.0.0.4204
Mono version (if Sonarr is not running on Windows): 4.4.0 (tarball Tue Jun 14 13:41:51 UTC 2016)
OS: Running in Docker container on Debian (linuxserver/sonarr image)
((Debug logs)) (posted to hastebin or similar): https://paste.ee/p/e8pUi
Description of issue:

Built deluge inside a docker container. Docker container has a remote path mapping to the torrent download file. Sonarr should be able to see this file, but deluge is reporting it as the docker path (e.g., ~/downalods) rather than /media/XXXX/Torrents as it is on the local machine.

I know I need to set up remote path mappings, but I don’t know how to get inside the docker container. Obviously it’s running on the same “host,” but the docker container is its own host. How should I set this up?

2

The host field needs to match the host field you entered in Sonarr’s Deluge settings.

3

So let’s say that’s “localhost” and the port is 8112.

Then do I need to put into the HOST field for Remote Mapping “localhost:8112” or just “localhost”?

And let’s say within my docker container /media/XXXX/Torrents is mapped as /downloads/

Is the remote path simply “/downloads/” and the local path “/media/XXXX/Torrents?”

4

localhost

Yes, that should do it, assuming that local path points at /downloads on the other system

5

Solved! Thank you, Markus.

1 Like
6

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.