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.)
You must log in or register to comment.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
Fewer Letters More Letters Plex Brand of media server package RPi Raspberry Pi brand of SBC SBC Single-Board Computer
2 acronyms in this thread; the most compressed thread commented on today has 5 acronyms.
[Thread #308 for this sub, first seen 28th Nov 2023, 07:55] [FAQ] [Full list] [Contact] [Source code]
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.
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: https://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.
Ah and read this: https://stopdisablingselinux.com/
It has a reason why it exists.
I just want it to work
Use the APT repository
They do effectively the same, but most software is build with docker in mind. podman should work but be prepared for some frustration using it.
docker nor podman fix your firewall or port for you by the way
I have used Docker, currently using Podman. Using literally the same compose file.
How do you use compose with Podman?
podman-composeis a made in Python, and is not official, but works great. Just rename yourdocker-compose.ymlfile topodman-compose.yml, and you’re good to go.Just rename it to compose.yml :)
