SABnzbd app cannot create directories, but can from shell [docker / portainer]
Posted: October 14th, 2022, 10:47 am
A bit confused as to what is going on. Moving SABnzbd from Dockers on Windows to Portainer on Linux. Everything was going smoothly but after getting SABnzbd up I get the following error for Intermediate and Completed folders:
PermissionError: [Errno 13] Permission denied
(tried posting full error but it keeps yelling at me for links)
Obvisously, I figured it was a permissions issue so I pulled up the shell for the container and have zero issues parsing the folders or making directories. Even if I make the directory for it, SABnzbd is yelling at me that it can't access it.
If I let it make the /config directory (local) it works fine. If I use the data directory this is where I have issues - but as mentioned only when the py file is trying to make the directory. I considered a chmod but was concerned this would just break on the next container pull as the environement would technically be different.
Any thoughts?
*** Fix Update***: After poking at this for a bit I am guessing the app wasn't correctly pulling the right Uid or Group ID. I moved the share I was trying to use to also be a mounted linux volume and had similar issues. Then I opened the mount under sudo -i and ran "chown -R 777" on the entire volume. After that, things worked like a charm. Certainly not the most secure way to do it, but it has no direct path to the internet and works for what I need it to do.
PermissionError: [Errno 13] Permission denied
(tried posting full error but it keeps yelling at me for links)
Obvisously, I figured it was a permissions issue so I pulled up the shell for the container and have zero issues parsing the folders or making directories. Even if I make the directory for it, SABnzbd is yelling at me that it can't access it.
If I let it make the /config directory (local) it works fine. If I use the data directory this is where I have issues - but as mentioned only when the py file is trying to make the directory. I considered a chmod but was concerned this would just break on the next container pull as the environement would technically be different.
Any thoughts?
*** Fix Update***: After poking at this for a bit I am guessing the app wasn't correctly pulling the right Uid or Group ID. I moved the share I was trying to use to also be a mounted linux volume and had similar issues. Then I opened the mount under sudo -i and ran "chown -R 777" on the entire volume. After that, things worked like a charm. Certainly not the most secure way to do it, but it has no direct path to the internet and works for what I need it to do.