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 (1 children)

Isolating network services from the rest of your system is a good thing

[–] nile_istic@lemmy.world 0 points 1 month ago (1 children)

Bearing that in mind, I now have a new problem, which is that apparently none of my containers actually have internet access? I hadn't noticed because I mostly just run local media servers, and I tend to clean up all the metadata before I upload anything (i.e. I usually clean up my ebooks in Calibre before I send them to BookLore, so I've never had to actually use BookLore to fetch anything from the web).

Only way I was able to get internet access in any of my containers was adding

network_mode: "host"

to the docker-compose.yml files, which, if I'm understanding correctly, negates the point of isolating network services, no? So something is broken somewhere but I have no idea what it is or how to fix it, so I guess my JF server is staying on bare metal for now lol

[–] 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