Because every once in a while sonarr doesn't move a show over, I can only assume it's because of this error
You are running an old and unsupported version of Mono. Please upgrade Mono for improved stability.

The last time i attempted to update mono i screwed the update management to the point I wasn't able to get new updates and had to resinstall OMV

OK @majorpayne. As I mentioned before, all of my path mapping is done in a single storage container, which is then attached to every other container. The paths are s follows:

I use rutorrent instead of Deluge for torrent downloading. The concept, though, is the same. Here is a screenshot of the downloads directory as specified in the rutorrent web UI itself. Notice that the download directory in rutorrent is a match for one of the paths on the right side of my storage container, both labeled by "1."Your Deluge container has a path mapped as "/downloads" and therefore you should also type "/downloads" into Deluge when it asks for your download directory. My suspicion is that you have the full /srv/... path):

Similarly, I use NZBGet to download shows for Sonarr and movies for Radarr from Usenet. Again, the paths I specify inside the NZBGet interface have to be a perfect match for the paths specified on the RIGHT side of the Docker container, marked with "2," "3," and "4." See below:

The post was edited 1 time, last by flvinny521 (Feb 18th 2018, 4:06am).

OK @majorpayne. As I mentioned before, all of my path mapping is done in a single storage container, which is then attached to every other container. The paths are s follows:

I use rutorrent instead of Deluge for torrent downloading. The concept, though, is the same. Here is a screenshot of the downloads directory as specified in the rutorrent web UI itself. Notice that the download directory in rutorrent is a match for one of the paths on the right side of my storage container, both labeled by "1."Your Deluge container has a path mapped as "/downloads" and therefore you should also type "/downloads" into Deluge when it asks for your download directory. My suspicion is that you have the full /srv/... path):

Similarly, I use NZBGet to download shows for Sonarr and movies for Radarr from Usenet. Again, the paths I specify inside the NZBGet interface have to be a perfect match for the paths specified on the RIGHT side of the Docker container, marked with "2," "3," and "4." See below:

What container do you use for storage? Is it safe to assume that you are using a docker container for that?

I have working Docker installs for Sonarr and Deluge, with Sonarr connecting to Deluge.

While it appears that Sonarr requires a few more bits to be fully functional, an indexer, etc. it is connecting to storage locations as indicated below:
____________________________________________________

I've tested Deluge for connectivity to the data disk and pulled a few torrents with it.
(Debian DVD install Disks, 3 each, all are 3+GB files)

Deluge - interestingly - doesn't download to "/downloads" , by default, as the the doc's on this Docker seem to suggest.
It downloaded to /root/Downloads which is internal to the container. (Not good for those using thumbdrives to boot.)
To "fix it", a change was required in preferences. I set Download to: to /downloads so the containers default Volume and Bind point mapping works correctly. The disk free space, lower right, shows Deluge is connected to the storage disk/directory.

(On a side note, I was surprised at Deluge's speed. It brought down the ISO's at speeds north of 3MBS.)
____________________________________________________________

On differences in configuration:

First:
Where network ports do not interfere with the operation of host, using the HOST mode for networking is the general rule of thumb. Bridged could be used but, in general, it's only needed when container ports must be remapped.
(And while off topic, Macvlan is used when there's an irreconcilable host/container port conflict, requiring the use of a separate IP address.)

Second:
I didn't set up a docker user. Where PUID's and PGID's are needed, as I believe they are in this case with direct data disk access, I use the root account and the users group.

- While this is speculation on the permissions problem;
Where I think @majorpayne may has a problem is with the PUID and PGID. I set PUID for my root account "0" and my PGID for "100" my users group.

From what I've seen in earlier screen shots, @majorpayne should be using PUID 0 and PGID 100 as well.

The above permissions should work for your containers and give all Samba share users at least read access to /Downloads.

While I didn't do it in the above; since you're likely to have a number of sub-directories under /Downloads, I'd check the box for Set group, owner and permissions recursively. (Leave permissions on /srv and /dev-disk-by-label-* as they are.)

_______________________________________________________________

On the Docker configurations - the user added parts

The following is what I have for Deluge.

In the above, note the folder icon in Volumes and Bind mounts. Use it to browse to your data storage location, when setting Host paths. If you can browse to the location, and with the right PGID and PUID, deluge should be able to write the location.
________________________________________________________________________

With the exception of the TZ (time zone) variable, there's really nothing new in the Sonarr config following,
(Really, according to the Docker author, you should add the TZ variable to the deluge docker as well.)

The correct entry, for your time zone, can be found here->Time Zones in the TZ column.

All locations were created and assigned the permissions, noted in the graphic WinSCP above, so I could browse to them. While it's not visible in this screen shot, again, I used the folder icon to "click navigate" to storage locations.
(When a host path location is actually selected, the background turns a light yellow.)

I suggest not running containers as root to get around problems with system storage path permissions and ownerships.

Fix the permissions and ownerships of the storage files and folders instead so that you can run the container as an ordinary user, one that has the appropriate rights to the files and folders.

PUID and PGID refer to a system user and a system group,not a user and group within the container.

I know, but I still don't see how setting a PUID turns over control of the container to the OMV root. The container has it's own root.

Even if that is the case (where setting a PUID puts the OMV root in control of the container- versus the container's root), the assumption would have to be that there's a security gain, somehow, by not running the Docker container as the OMV root.

While I've seen the recommendation, I can't seem to find anything, anywhere, that explains the "why" of it. Essentially, from a security viewpoint; there would be no difference between running the Deluge plugin, which is controlled by the OMV root, or a Deluge Docker run by the same.

I am not talking about the container or its root. I am talking about the container being able to have the read/write access to directories and files on the system's data storage drives it needs, outside the container, without having to be run as the system root user.

You should never, ever run any process as the system root user unless it absolutely required. That includes docker containers. The security gain here is not allowing a container's processes be able to destroy your system.

OMV's deluge plugin installs deluged and supporting files. It's up to the user to configure it and run it properly. I don't run it as root here. It's not necessary.

On my OMV, I have myself as a user which is a member of the users group. All my docker containers run as that user and group. So does deluged which was manually installed. None of these things need to run as root, so they aren't.

All of the data drives that these programs need access to have directories owned by this user and group with appropriate permissions. The folders and files within have the same ownership permissions on them.

What if you were asking questions in some forum about some docker, and some user pointed you to an image that he claimed would solve your problem or otherwise meet all your needs. Suppose all it really did was format all your hard drives, but you didn't know that. It was cleverly designed to misbehave unless run as root, so you did that................ Now what?

Well, this thread is convoluted, but I think it contains what is needed to get your dockers running, while taking care of @gderf 's security precaution. (He's right about giving a container the potential to navigate all of the host's files and folders.)

First, the file permissions you've already set on your folders (Fileserver and Downloads) will work as they are, but I'd give thought to changing them to those pictured in post 49.

While noting the need to create a dockeruser and the change of PUID entries, etc., in post 56, - post 49 should get things going.

Before getting carried away with a lot of container folders;
I'd do the default required folders first, and add more as needed after getting the containers on line.

While it's no longer relevant to getting your configuration up and running - just trivia:
Using Symlinks does work with both dockers. With Symlinks, Deluge can write files to /Downloads, on the data drive, without PUID and PGID entries (no host permissions at all). However, Sonarr is picky. Sonarr requires PUID and PGID entries, regardless. It crashes without them.

An easy way to visualize this is to determine what user:group on the system has sufficient rights to access the files and folders that a docker needs to read and write to. Then just run the container as that user:group.

And no, root does not count

All my data drive directories and files are owned by the only user I created on the system - myfirstname, who belongs to the users group. So, all my dockers run with PUID: myfirstname and PGID:users.

This isn't something I had to force things into or reconfigure to get dockers working. The directories and files had that ownership and permissions long before I ever got started with dockers.

I have it mostly working now. Sonarr is speaking with Deluge and Jackett. Deluge is saving the file to the proper place. Sonarr is not even attempting to check for the download show. I'm very close now.

EDIT: Ok found out that a permission was missing and it made the group 911 which i assume means help something is wrong?

I changed it and now it's able to move/extract the file.

The post was edited 3 times, last by majorpayne (Feb 20th 2018, 4:39am).