I’m going to be running a Jellyfin server, and I don’t want to maintain it a lot, I just want it to work. Would using Docker be the easier way to maintain Jellyfin, or would using Podman be better? (I don’t want to deal with SELinux, firewalls, port forwarding, etc.)
I haven’t used Jellyfin with docker before, just with podman and as a pod in k3s. Both work great and are easy to maintain. If you’re more familiar with podman then docker, then I’d recommend using podman.
there is a famous quote i like to use for this kind of question: "in the end it doesn’t […] matter’. maintenance should be about the same (if you update manually, which is better in my opinion, because you don’t come home to something not working because of breaking changes in the software)
I run Docker containers on a Pi 4 using the RPi OS. For the longest time I’ve been using Plex. I wanted to give Jellyfin a go though, so just created a new compose file and mounted my TV/Movies directories. Other than the first time setup of Jellyfin I don’t touch it now. Plex and Jellyfin run side by side. To update I just do a docker-compose pull every so often. Super simple.
SELinux should not be an issue if you stick to common directories and use :Z flag after the mount path with docker, afaik podman uses the same mechanism. There’s even a tool for selinux container policies: github.com/containers/udica
Regarding firewall stuff, disable it on your machine and you are fine. Port forwarding in containers is necessary to connect to services, now way around.
Regarding firewall stuff, disable it on your machine and you are fine.
How do you know OP doesn’t have a bunch of unsecured services sticking out into their LAN ready to be a target for the next cryptolocking scam?
Slightly sarcastic, but yeah, OP, do not just turn your firewall without understanding pros and cons of doing such. At the very least, see what your server exposes to the network (ss -tunlp will give you a good starting point), and see if there’s nothing unexpected in there that might be abused.
I don’t but lots of people stick anyways to a single network with some kind of crappy router and from OPs post I assumed that OP doesn’t really care about security, see SELinux
The container method used should be whatever you are more familiar with or prefer. They both have their own quirks, pros, & cons.
SELinux - If you don’t want to deal with SELinux then set it to permissive mode. If you want to keep in enforcing mode you need to create the appropriate policies, …redhat.com/…/configuring-selinux-for-application…
Firewall - If you don’t want it’s protection then look up instructions to stop & disable it on your distro.
Port forwarding - From linux container side you either need to specify host networking or the ports you want to allow through, there is no avoiding that if it needs to be network accessible. If you want it internet accessible then you need to setup port forwarding on your router.
Have you looked into something like yunohost? It may be the kind of thing you’re looking for.
podman-compose is a made in Python, and is not official, but works great. Just rename your docker-compose.yml file to podman-compose.yml, and you’re good to go.
Like other commenter said, regardless of podman or docker you will need to handle port forwarding, and any firewall changes.
Port forwarding through docker or podman is pretty similar, if not identical.
I have heard good things about podman but I personally had some strange issues when moving from docker to podman, specifically transferring docker networks to the podman equivalent.
Add comment