this post was submitted on 26 Dec 2023
35 points (97.3% liked)

Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

54716 readers
269 users here now

⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.

Rules • Full Version

1. Posts must be related to the discussion of digital piracy

2. Don't request invites, trade, sell, or self-promote

3. Don't request or link to specific pirated titles, including DMs

4. Don't submit low-quality posts, be entitled, or harass others

Loot, Pillage, & Plunder

📜 c/Piracy Wiki (Community Edition):

💰 Please help cover server costs.

Ko-Fi Liberapay
Ko-fi Liberapay

founded 1 year ago
MODERATORS
db0@lemmy.dbzer0.com
sunbrothersco@lemmy.dbzer0.com
dataprolet@lemmy.dbzer0.com
Flatworm7591@lemmy.dbzer0.com
RandomLegend@lemmy.dbzer0.com
35
Permission problems with sonarr/radarr (lemmy.world)
submitted 11 months ago by Hercules@lemmy.world to c/piracy@lemmy.dbzer0.com
5 comments fedilink hide all child comments
 

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!

you are viewing a single comment's thread
view the rest of the comments
[–] Shimitar@feddit.it 3 points 10 months ago

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.