jswanson04

No, my shared volume is just another folder on my cache drive. The reason I am leaning away from the permissions not being set up correctly originally is there was not an issue before. All of the dockers interacted with the shared location without an issue. Unless there was something that was changed where before the docker was running as root, but now it is not and that is the issue.

Here were the following steps I used. I don't think it is 100% as I am still getting some issues in the Sab Log (lots of "Suspect error in downloader", not sure if that is related) Note: I only did the following on my "shared volume" between Sab/Sickbeard/Couch Potato. I did not have to do this to my Docker Folders. Same idea may apply, but I did not test. Proceed at your own risk. First navigate to the location of your "shared volume" using cd (should be on your cache drive) Run the following command: ls -l You should see a list of all the sub-directories and their permissions. My "shared volume" was "root root" and I changed it to "nobody users", using the following command: chown -R nobody:users sharedVolumeLocation Then you can re-run the ls command to confirm. Again, this worked for me and I do not know the implications this might have. However it is currently working for me, which is good for now until I hear the "official" solution.

Hello, I recent updated to the new version of the docker and now I'm getting some permission issues. I have the postProcessing (Sab -> SickBeard) script running and now I'm getting the following error from Sab: PostProcessing was aborted (Cannot create final folder /UnprocessedShare/tv/TVShowNameHere) /UnprocessedShare is set up as a volume for the Sab container I also just deleted the perms.txt file and forces an update Do I need to somehow set permissions now? EDIT: I just ran a quick test without the post-processing. I think it is because I try to move the files from the Downloads location, to a different location on the new volume. I don't think it has anything to do with the post-process script. Hope that helps EDIT 2: Temporary fix for now: I looked at the permissions of my "shared volume" and they were root root. I believe that was the cause of the problems. I modified it to nobody:users and I am able to create the folders and finish the download process. I am assuming this is not the ideal solution, but I think it's a stop-gap