2024-09-17, 08:53 PM
(This post was last modified: 2024-09-17, 08:53 PM by TheDreadPirate.)
The "user" parameter only controls what user the container runs as. And that user only needs permissions to writeable portions of the container, /config and /cache. The rest of the container is, essentially, read-only to whatever user is defined.
I tested with the Linuxserver image of Jellyfin, since it uses PUID and PGID environment variables, but I wasn't able to get the namo plugin to overwrite index.html.
You could explore having docker run post startup scripts/commands. But I'm not certain when during the startup process those run. Whether they run when the container starts, but before Jellyfin finishes starting, etc.
I tested with the Linuxserver image of Jellyfin, since it uses PUID and PGID environment variables, but I wasn't able to get the namo plugin to overwrite index.html.
You could explore having docker run post startup scripts/commands. But I'm not certain when during the startup process those run. Whether they run when the container starts, but before Jellyfin finishes starting, etc.
Jellyfin 10.9.11
Ubuntu 24.04 LTS (bare metal)
Intel i3 12100 on Asus Prime H610M-E D4 mATX
32GB DDR4-3600
Intel Arc A380
OS drive - SK Hynix P41 1TB
Storage
WD Green 3TB (Samba shares)
WD Red 3TB CMR (WIP Media, Test libraries)
3x WD Red Pro 6TB CMR in RAIDZ1 (JF Library)
Fractal Meshify 2
Corsair CX430
Ubuntu 24.04 LTS (bare metal)
Intel i3 12100 on Asus Prime H610M-E D4 mATX
32GB DDR4-3600
Intel Arc A380
OS drive - SK Hynix P41 1TB
Storage
WD Green 3TB (Samba shares)
WD Red 3TB CMR (WIP Media, Test libraries)
3x WD Red Pro 6TB CMR in RAIDZ1 (JF Library)
Fractal Meshify 2
Corsair CX430