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.)
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.
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.
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.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
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.
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, https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/using_selinux/configuring-selinux-for-applications-and-services-with-non-standard-configurations_using-selinux
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.
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.
Use the APT repository