A few jellyfin via container set up questions (lemmy.world)

submitted 1 week ago by SailorsLife@lemmy.world to c/jellyfin@lemmy.ml

13 comments fedilink hide all child comments

People resoundingly suggested using containers. So I've been reading up. I know some things about containers and docker and what not. But there are a few decision points in the jellyfin container install instructions that I don't know the "why".

Data: They mount the media from disk, which is good cause it's on a NAS. But for the cache and config they use docker volumes. Why would I want a docker volume for the config? Wouldn't I want to be able to see it from outside the container easier? What am I gaining by having docker manage the volume?

Cache: I saw a very old post where someone mentioned telling docker to use ram for the cache. That "seems" in theory like a good idea for speed. I do have 16gb on the minipc that I am running this all on. But I don't see any recent mentions of it. Any pros/cons?

The user. I know from work experience that generally you don't want things running as root in the container. But... do you want a dedicated user for each service (jellyfin, arr*)? Or one for all services, but not your personal user? Or just use your personal user?

DLNA. I had to look that up. But I don't know how it is relevant. The whole point seems to be that jellyfin would be the interface. And DLNA seems like it would allow certified devices to discover media files?

you are viewing a single comment's thread
view the rest of the comments

[-] Appoxo@lemmy.dbzer0.com 2 points 1 week ago

As for the media, a bind mount is the way to go, and I’d also recommend doing it as a read-only mount: Jellyfin doesn’t need the ability to modify that data, and in the event of a security oopsie (or a misconfigured user, or a 6 year old that gets 5 minutes alone with your mouse or…), it keeps someone from trashing your entire media library, assuming that’s something you wouldn’t want to have to spend the time gathering again.

My way to solve this:
My main user is a regular user with no deletion permissions in jellyfin. Anything that requires editing necessitates logging out and in with the admin account.
My docker container is mapped to a non-root user. Not perfectly save but sufficient (hopefully).
But my jellyfin container has R/W because I store nfo/metadata files alongside the media file.

[-] i_understand@mstdn.social 1 points 1 week ago* (last edited 1 week ago)

@Appoxo

I use 2 media folders, one for "new" media and one for existing media. Only the "new" media folder is R/W. Once it's metadata files are written out the media is moved to the existing media folder (which is mounted R-only).