Remote path and Docker

[bentleyjackson]

I know this has been covered everywhere more than once, but I have spent hours and hours trying to set up Sonarr and Sabnzb both in their own Docker containers on my Synology and I can’t get the file paths correct.

Anyone know what I am not doing properly here? I would like to download and store content to /media/content name. So media/tv, for instance. I have the volume set up as /media/tv and /music in Docker. Sonarr has all the existing files pulled in, but won’t pull the downloaded files back and throws errors. Sabnzb correctly is downloading files to the /media folder.

Any suggestions on how to link this and get it going? @markus101 any thing to try?

Thanks so much.

[Thirrian]

From a quick read, you’re using /media for both sorted files (= location where sonarr will place files) and downloads (what sab is using)?
You need separate directories. E.g. /media/tv and /media/downloads will work, where the first directory is exclusive to sonarr and the second one for sab/sonarr combined (sab will use it to save downloads, sonarr will use it to move files to /media/tv).

Also, you refer to errors. Can you turn on debug logs? All information on how to do that is available when you create a new topic in the Help & Support category, but here it is:

Sonarr version (exact version):
Mono version (if Sonarr is not running on Windows):
OS:
Debug logs:
Description of issue:

Additional Information:

• Information on the log files is here: https://github.com/Sonarr/Sonarr/wiki/Log-Files
• Make sure debug logging is enabled in settings
• Post the log file, not a line or two, or just the error from the Logs table
• Post the full log to hastebin/pastebin/dropbox/google drive or something similar and link it here
• Do not post them directly here. Post in .txt not .doc, .rtf or some other formatted document

[rhom]

so long as your containers can see the exact same path as the other containers that need to see that path then it will work, so just make sure the volume mappings in the container configs are all setup the same (if you cant be bothered working out which ones are only needed for each container).

eg, this is from my sonarr and transmission containers

linuxserver/transmission
--mount type=bind,source=/volume3/docker/transmission,target=/config
--mount type=bind,source=/volume3/downloads,target=/downloads

linuxserver/sonarr
--mount type=bind,source=/volume3/docker/sonarr,target=/config
--mount type=bind,source=/volume3/downloads,target=/downloads
--mount type=bind,source=/volume1/data/media,target=/media

my transmission client is setup to save completed jobs to /downloads/transmission/completed but it could be anywhere under the /downloads folder and it will work.

all you should have to do is make sure that the download categories in sab are setup to save under /downloads/sab/completed/category (or something along those lines) and you should be ok

the common /downloads volume mapping is what allows sonarr to see where transmission (or sab in your case) has put the completed file. sonarr can then move it from there to where it belongs under /media (because thats where i told it all my media files lived)

[bentleyjackson]

@Thirrian

you’re using /media for both sorted files (= location where sonarr will place files) and downloads (what sab is using)?
You need separate directories. E.g. /media/tv and /media/downloads will work, where the first directory is exclusive to sonarr and the second one for sab/sonarr combined (sab will use it to save downloads, sonarr will use it to move files to /media/tv ).

Also, you refer to errors. Can you turn on debug logs? All information on how to do that is available when you create a new topic in the Help & Support category, bu

Here’s what I have configured for volumes in Docker.

[Thirrian]

That looks correct, so probably more related to permissions… Maybe the guid/pgid settings?