this post was submitted on 01 Apr 2026
1 points (100.0% liked)

Jellyfin: The Free Software Media System

8935 readers
1 users here now

Current stable release: 10.11.8

Community Standards

Website

Forum

GitHub

Documentation

Feature Requests

Matrix (General Information & Help)

Matrix (Announcements)

Matrix (General Development)

Matrix (Off-Topic) - Come get to know the team and blow off steam!

Matrix Space - List of all the available rooms on Matrix.

Discord - Bridged to our Matrix rooms

founded 5 years ago
MODERATORS
 

I'm pretty new to self-hosting in general, so I'm sorry if I'm not using correct terminology or if this is a dumb question.

I did a big archival project last year, and ripped all 700 or so DVDs/Blu-rays I own. Ngl, I had originally planned on just having them all in a big media folder and picking out whatever I wanted to watch that way. Fortunately, I discovered Jellyfin, and went with that instead.

So I bought a mini pc to run Ubuntu server on, and I just installed Jellyfin directly there. Eventually I decided to try hosting a few other services (like Home Assistant and BookLore (R.I.P.)), which I did through Docker.

So I'm wondering, should I be running Jellyfin through Docker as well? Are there advantages to running Jellyfin through Docker as opposed to installed directly on the server? Would transitioning my Jellyfin instance to Docker be a complicated process (bearing in mind that I'm new and dumb)?

Thanks for any assistance.

you are viewing a single comment's thread
view the rest of the comments
[–] Feyd@programming.dev 0 points 1 month ago

Do you mean the ability of jellyfin to access the internet or the ability for network access to jellyfin.

If you mean the second then you need to map ports https://docs.docker.com/get-started/docker-concepts/running-containers/publishing-ports/

If you mean the first then something is wonky, but also using host mode still doesn't negate the point. You're still only allowing the processes in the container to access only directories you've specified and isolated them from the other processes on the system. It's about limited the blast radius if an exploit against your network application occurred