Comment on Selfhosting Sunday! What's up?
h0rnman@lemmy.dbzer0.com 4 weeks agoCould be that lidarr is setting its own permissions for downloaded stuff (look for something like dmask or fmask in the docker config). You might also need to chmod -R so it hits all sub folders. If you have a file or directory mask option, remember that they’re inverse, so instead of 777, you’d do 000 for rwxrwxrwx.
Kaldo@fedia.io 4 weeks ago
You might be onto something, lidarr does have UMASK=002 setting in the .env file. I think the issue is when sabdnzbd puts the files and then lidarr can't read them, so what exactly is the expected permission setting then in this case? If I put it to 000 for lidarr, won't other services then be unable to add the files there?
I always feel so dumb when it comes to these things since in my head it's something that should be pretty straightforward and simple, why can't they all just use the same user and share the same permissions within this folder hierarchy...
h0rnman@lemmy.dbzer0.com 4 weeks ago
Sab might have its own mask settings - it would be worth looking at. Same thing applies here - subtract the mask part from 7 to get the real permissions. In this case, mask 002 translates into 775. This gives the uid and gid that the container is running under (probably defined in a variable somewhere) Read/Write/Execute, but anyone else Read/Execute. The “anyone else” would just be any account on the system (regardless of access method) that didn’t match on the actual uid or gid value.