Docker install, just need help understanding the error

[gizlonk]

Sonarr version (exact version): 2.0.0.5338
Mono version (if Sonarr is not running on Windows):5.20.1.19
OS: Ubuntu 18.10
Debug logs: https://drive.google.com/file/d/1QT9LmyPGb-0Uj7ggKXRezWSR6B9me4jQ/view?usp=sharing
Description of issue: Docker on ubuntu, linuxserver/* containers, containers run fine. Using uTorrent container (and Lidarr, Radarr). Sonarr is able to add downloads, uTorrent set to stop once seeding goal reached (0%), that works. Sonarr is unable to import the download. The user inside the container is user “abc” with a UID and GUID of 1001. I have a user on the host server called “abc” with UID and GUID of 1001 as well. That user owns a directory called /mnt/Downloads, recursively, and that directory has full open permissions, as in, 777 right through. uTorrent container, as well as Lidarr and Radarr are running. Radarr is able to import downloaded files correctly, and all the containers have a user called “abc” running with UID and GUID of 1001.

I have stopped all other containers but sonarr, and it is still unable to import the download. “lsof | grep /mnt/Downloads” shows that there is nothing else using the files in question on the host machine.

I just want to know if someone smarter than I can see what the error may be in the logs? Or perhaps someone who has experienced this issue before? Obviously I see the “access denied” but I dont see how it could be - its the same user right through out the entire process.

Any help, or guidance appreciated.

[markus101]

Sonarr is able to read the files because it’s getting to a point where it’s trying to import the download, so the issue likely is with the destination (/tv).

[gizlonk]

Thanks for the reply markus101 - I rechecked, and this is really weird, but there were a few files in the /tv directory that where not owned by abc, but by root. None of these files are relevant to Sonarr, but somehow, changing their ownership to abc seems to have solved this issue.

So, to summarise, mount points on the main host should be owned by the user of the application inside the docker container - if there is even one file that has the incorrect permissions, its seems to have permissions issues.