submitted 2 days ago by nile_istic@lemmy.world to c/jellyfin@lemmy.ml

22 comments fedilink hide all child comments

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 1 points 18 hours 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

[-] nile_istic@lemmy.world 1 points 18 hours ago

Jellyfin isn't running in a docker container, so it's working fine. I've just noticed that everything I am running in a container doesn't have network access, unless I change network mode to host in that container's compose yml. So I guess docker's network bridge isn't configured correctly? Which makes sense, as I have basically no idea what I'm doing lmao. So until I figure out what's going on there, I think I'll just let my JF server run as is. I'd prefer it in a container I think, but not before I figure out what exactly I broke.