2025-01-21, 05:03 PM
(This post was last modified: 2025-01-21, 05:07 PM by 4r5hw45twh. Edited 2 times in total.)
Ok, so this is where I get lost.
You said, "So if you had to sudo to open the file in nano, then your container can't access it" but isn't it the other way around or no? I just let Docker do whatever it does. But when I copied the config.json from wherever it was in Docker and it had a lock on it, doesn't that mean I can't access it from my host and not the other way around?
This is where I'm lost. How do I go about doing this? My web-config.json file is located at:
/home/username/Dockers/Jellyfin/Config
And since I made those directories and web-config.json myself, it doesn't lock those out or anything. Only locked file was when I copied regular config.json from Docker to my Documents area.
You said, "So if you had to sudo to open the file in nano, then your container can't access it" but isn't it the other way around or no? I just let Docker do whatever it does. But when I copied the config.json from wherever it was in Docker and it had a lock on it, doesn't that mean I can't access it from my host and not the other way around?
(2025-01-21, 04:56 PM)TheDreadPirate Wrote: So you will need to chown and/or chmod the file and folders config.json so that your user doesn't need to use sudo to open it.
This is where I'm lost. How do I go about doing this? My web-config.json file is located at:
/home/username/Dockers/Jellyfin/Config
And since I made those directories and web-config.json myself, it doesn't lock those out or anything. Only locked file was when I copied regular config.json from Docker to my Documents area.