Edit - marking as solved.
- Remote path: /home/seedit4me
- local path: /data
This is now working, I don't know why it wasn't before. ‐------------
I have followed the docs and have the recommended folder structures for my Plex and arrs setup.
sonarr has a volume set as /data which gives it access to e.g. /data/usenet/downloads This is working fine with SABnzdb
I am using a seedbox for torrents. Looking at ruTorrent on the seedbox, I can see that the local download folder there is set to: /home/seedit4me/torrents/rtorrent
sonarr is reporting "No files found are eligible for import in:
- /home/seedit4me/torrents/rtorrent/Completed/tv-sonarr/filename.mkv
I have set a remote path in the download clients page in sonarr as follows:
- Host - ****.seedit4.me
- Remote path: /home/seedit4me
- local path: /data
I have ftp'd the mkv file to actual folder structure:
- /data/torrents/rtorrent/Completed/tv-sonaar/filename.mkv
The permissions on this file are:
- -rw-rw-r--
the folder permissions are:
- drwxrwxr-x 2 myacct myacct 4096 Aug 2 11:41 .
- drwxrwxr-x 3 myacct myacct
My uid=1000(my acct), same for gid I have set these as the PUID and PGID env variables in sonarr
The log file in sonarr is reporting: |Error|DownloadedEpisodesImportService|Import failed, path does not exist or is not accessible by Sonarr: /home/(removed)/torrents/rtorrent/Completed/tv-sonarr/filename.mkv
Seeing this, i tried mapping /home/(removed)/ to /data/ but that doesn't work either.
Can anyone guide me on what I am doing wrong? I feel like I've checked everything so I can't understand the issue at all.---
There may be a much better way to do this but I use folder binding instead of volumes. What I usually do is map another folder structure for both sonarr and whatever DL client I am using.
So for example I do some kind of /mnt/docker/download. This is mapped in the containers as the directory as well as the path on my system.
I have this extra line in all containers that need access to the downloaded files. Then in my download client I change the default directory that it downloads to from /data to this /mnt/docker/download. Then in Sonarr/Radarr I tell it that this is the download directory. This then becomes a directory that they all have access to and can then use without error or without extra complex options in docker.
Less secure in its production practice but this is essentially a temp folder that will only ever have 1-3 files in it prior to them being processed.
I don't think the issue is the volume because sonarr is finding my usenet downloads.
The actual folder structure is /data/usenet/download. sonarr is given the volume mount: /data
It gets the download location from SAB. All works fine.
Equating this to my situation, I am expecting the folder mapping to put the download in the location /data/torrents/rtorrent etc Again this matches the info sonarr receives from rutorrent. And the volume mount /data should be allowing access same as it gets to the usenet folders.