Permission problems with sonarr/radarr

Hercules@lemmy.world to Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ@lemmy.dbzer0.com – 35 points –

Hey i was playing around with my sonarr/radarr containers, i wanted to get the permissions right. Everything was just 777. They are in containers with -e PUID=1000 -e PGID=1000. When i set their folders to 700 and chown 1000:1000 the folder. If i go in the container i can read write all i want and outside the container the permission is like excpected to the 1000 user, but when i wanna add it as root path it shows the top dir but nothing below it.

Does someone know how to fix this? Now i set the dir back to 777 and its working but i would like to restrict it more. Thanks for your time!

5

Docker sucks with user management. I installed them all on bare metal each one on its own user. They all belong to a common "media" group and inset 750 as umask.

Its a bad bad idea to have 777 files and folders lying around, don't do it.

I am not using docker, but I solved the permission issues by running them under the same user.

Not sure I follow what the issue is, it sounds like permissions are working as expected. If you want your normal user account to have permissions you can create a group with ID of 1000 in the host OS, add your user to that group, and set permission to 770.

Try the chown command again with the -R flag to make it recursive, thereby granting ownership of all subdirectories as well.

Something like

sudo chown -R 1000:1000

I already did that but nothing changed, stillthankqs for the input!