2025-01-21, 04:56 PM
(This post was last modified: 2025-01-21, 04:58 PM by TheDreadPirate. Edited 1 time in total.)
1000:1000 is fine. It is better to run containers as a less priviliged user instead of root.
BTW, 1000 is the ID for your user. So if you had to sudo to open the file in nano, then your container can't access it. 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.
The user you create during setup is not a "super user". Root is the only super user on the system and you cannot make your user a permanent super user. This is by design.
You can temporarily run as root by typing "sudo su". This will elevate you to root's shell, but it is best practice to only do this when you have to.
BTW, 1000 is the ID for your user. So if you had to sudo to open the file in nano, then your container can't access it. 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.
The user you create during setup is not a "super user". Root is the only super user on the system and you cannot make your user a permanent super user. This is by design.
You can temporarily run as root by typing "sudo su". This will elevate you to root's shell, but it is best practice to only do this when you have to.
Jellyfin 10.10.7 (Docker)
Ubuntu 24.04.2 LTS w/HWE
Intel i3 12100
Intel Arc A380
OS drive - SK Hynix P41 1TB
Storage
4x WD Red Pro 6TB CMR in RAIDZ1
![[Image: GitHub%20Sponsors-grey?logo=github]](https://img.shields.io/badge/GitHub%20Sponsors-grey?logo=github)
Ubuntu 24.04.2 LTS w/HWE
Intel i3 12100
Intel Arc A380
OS drive - SK Hynix P41 1TB
Storage
4x WD Red Pro 6TB CMR in RAIDZ1