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
this post was submitted on 27 Nov 2023
16 points (86.4% liked)
Selfhosted
40183 readers
498 users here now
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).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
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.
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.
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
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.
I have used Docker, currently using Podman. Using literally the same compose file.
How do you use compose with Podman?
podman-compose
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.
Just rename it to compose.yml :)
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]
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)
Eh I update automatically at 2 Am. I have had so few issues that I don't even think about it anymore.
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.
I just want it to work
Use the APT repository
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.