Sonarr version (3.0.8.1507):
Mono version (6.12.0.122):
QTS 5.0.0.1986:
2022-05-07 14:51:14.6|Error|DownloadedEpisodesImportService|Import failed, path does not exist or is not accessible by Sonarr: /share/CACHEDEV1_DATA/Multimedia/Shared Videos/Videos/TV/Diners.Drive-Ins.and.Dives.S42E12.Plating.Up.Puerto.Rico.720p.WEBRip.X264-KOMPOST-xpost. Ensure the path exists and the user running Sonarr has the correct permissions to access this file/folder
:
I have Sonarr installed on 1 QNap Docker Container.
Sonarr will grab the file and SABnzb will download the file and move it to /share/CACHEDEV1_DATA/Multimedia/Shared Videos/Videos/TV/.
Then Sonarr tries to move the file to the correct folder but cannot because of permissions.
In the Sonarr settings I have “Set Permissions” checked
and
“chmod Folder” is 777
Is there anything else I need to do?
Please be kind as I'm not a QNAP/Linux/Docker expert at all.
Docker/Sonarr permissions.
-
Fubie
- Starting out
- Posts: 36
- Joined: Fri Apr 18, 2014 8:14 pm
Docker/Sonarr permissions.
TS-453be with 2x WD 3TB Reds and 2x WD 4TB Reds
TS-470 Pro with 2x WD 8TB Reds and 2x WD 10TB Reds
QTS 5.0.0.1986
Windows 11 Pro
TS-470 Pro with 2x WD 8TB Reds and 2x WD 10TB Reds
QTS 5.0.0.1986
Windows 11 Pro
-
testure
- New here
- Posts: 7
- Joined: Sat Apr 18, 2015 10:59 pm
Re: Docker/Sonarr permissions.
Did you find a solution?
I'm dealing with a very similar issue but I am using NZBGet vs SABnzb.
NZBGet is a qpkg version and trying to run Sonarr in a container.
I can't find a way to present the path /share/CACHEDEV1_DATA/* to the Sonarr container.
I can create a share to a point in the path and get access via the container.
However NZBGet is using the full /share/CACHEDEV1_DATA/* path and Sonarr picks that up.
And I can't seem to get NZBGet to access a path via a share.
Guess maybe it is time to move NZBGet into a container.
UPDATE: Rebuilt Sonarr container and added PUID and GUID set to 0 (which should be admin) just as a test.
Still got same error messages.
Thanks!
I'm dealing with a very similar issue but I am using NZBGet vs SABnzb.
NZBGet is a qpkg version and trying to run Sonarr in a container.
I can't find a way to present the path /share/CACHEDEV1_DATA/* to the Sonarr container.
I can create a share to a point in the path and get access via the container.
However NZBGet is using the full /share/CACHEDEV1_DATA/* path and Sonarr picks that up.
And I can't seem to get NZBGet to access a path via a share.
Guess maybe it is time to move NZBGet into a container.
UPDATE: Rebuilt Sonarr container and added PUID and GUID set to 0 (which should be admin) just as a test.
Still got same error messages.
Thanks!
-
testure
- New here
- Posts: 7
- Joined: Sat Apr 18, 2015 10:59 pm
Re: Docker/Sonarr permissions.
Ok, just to close the loop.
I ended up moving to NZBGet in a container vs qpkg version.
This solved all of my, what I would call, pathing issues.
It was not a straight forward move but all the items that came up I was able to overcome.
The main issue was permissions as it seems (at least on my setup) all native qpkg run under admin.
In the end, I'm probably in a better situation with both Sonarr and NZBGet running in containers.
And I'm learning some more about Docker containers.
I ended up moving to NZBGet in a container vs qpkg version.
This solved all of my, what I would call, pathing issues.
It was not a straight forward move but all the items that came up I was able to overcome.
The main issue was permissions as it seems (at least on my setup) all native qpkg run under admin.
In the end, I'm probably in a better situation with both Sonarr and NZBGet running in containers.
And I'm learning some more about Docker containers.