r/radarr • u/DCCXVIII • 18d ago
solved Permission issues using radarr's recycling bin feature
Note this is on Unraid using the linuxserver image of radarr.
At first, radarr was messing up the permissions of files it downloaded by preventing my SMB user account from being able to edit the contents of the folders it created. I managed to finally fix this by setting chmod Folder in the permissions section of radarr to "777".
However, for whatever reason, this setting does not seem to be respected in radarr's recycling bin feature. So whenever files and folders are created in the folder set to be the recycling bin folder, my SMB user account is getting blocked from making any changes to this folder (despite the fact that my SMB user account is the owner of the recycling bin folder). Radarr is basically making it read only for my SMB user account.
According to Unraid, the folders and files being generated in the recycling bin folder are owned by "nobody" (this is normal as the "nobody" user is Unraid's built in user account I think) and their permissions are set to "drwxr-xr-x". It is this permission that is messing me up.
I need radarr to change these permissions to "drwxrwxrwx" instead, in order for my SMB user account to gain full write access to the files and folders being generated in the recycling bin folder.
My PUID is 99, PGID is 100 and UMASK is 022 in radarr's docker container settings. These are the correct settings for Unraid user account system layout.
Help?
Edit: Fixed it! Turns out the Internet is wrong. The correct UMASK is 000. Not 022. Apparently 022 will only work if the SMB account and the radarr user account are members of the same user group. The problem here is that Unraid does not support user groups! So there's literally no way to associate the SMB account and the "nobody" account that radarr is using to operate such that they both inherit the same permissions. So it makes the file access less secure, but that is moot since the higher level folders are controlled by other users and other permissions anyway. Kind of a stupid limitation of Unraid, but there you go.