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.
this post was submitted on 26 Dec 2023
35 points (97.3% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
54539 readers
201 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 |
founded 1 year ago
MODERATORS
I am not using docker, but I solved the permission issues by running them under the same user.
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!
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.