Closed jamess60 closed 8 months ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
This is going to be due to your permissions that you've set on your remote mounts. They need to be mounted/owned by the same user that is used for deploying the container.
Not a bug with the container, it's a configuration/permissions issue on your host.
Thanks for the quick reply.
The SMB mount is mounted as 0777, the root user is running the container, and the GID/UID is set to 1000 (unsure if it should be 0 instead?)
The user on the SMB server its self has full read write to that share. Unsure what else I could do to make this any more permissive?
Fixed - seems to work only if you create a docker smb volume, it doesnt like you mounting the smb share within linux and mapping it to a local path
Is there an existing issue for this?
Current Behavior
When SABZ is first loaded, I get two errors: /downloads is not writable at all. This blocks downloads. /incomplete-downloads is not writable at all. This blocks downloads.
Subsequent download requests that hit sabz error out with the following: Failed making (/incomplete-downloads/demo-filename) Traceback (most recent call last): File "/app/sabnzbd/sabnzbd/filesystem.py", line 762, in create_all_dirs os.mkdir(path_part_combined) PermissionError: [Errno 13] Permission deied: '/incomplete-downloads/demo-filename'
Note that from the container shell, I can touch files in both directories without issue
Expected Behavior
These errors shouldnt occur and sabz should be able to download
Steps To Reproduce
Docker compose:
/mnt/plex resides on an SMB share. fstab:
^ Yes, im aware this is too permissive, but its only for testing at this stage. I can restrict it when working
Environment
CPU architecture
x86-64
Docker creation
Container logs