2025-01-21, 04:49 PM
(This post was last modified: 2025-01-21, 04:51 PM by 4r5hw45twh. Edited 1 time in total.)
(2025-01-21, 03:32 PM)TheDreadPirate Wrote: Did you provide a user ID in the docker compose config? If not, then root is running the container and shouldn't have any restrictions. If you did provide a user ID, that user needs access to web-config.json and all the folders leading to it.
If you had to use sudo to open it, Docker probably can't read it. Meaning only root could open it.
The docker compose config for Jellyfin? It is set to "1000:1000". Should I just remove that line and re-run the compose.yml file? The user stuff is all default how it came out of Ubuntu. I assumed when it asked me to name the account being made, I'd have full access to everything at anytime 9which is what I want). Typing "sudo" for most stuff is annoying. So, how would I make myself (the current and only user that'll ever be on the PC) sudo/root/whatever? On the host, I can access the folder directory fine because I created the folders myself. Just not the config.json file it copied from Docker.