Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
sudo in Windows.Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
EDIT: For some context, I recently gave podman another go. I have a few services on my homelab server set up in docker containers, so I tried migrating to podman.
After the second major bug (open issue on github) I encountered looked like it would require completely dropping using compose files to work around, I gave up and went back to docker.
I like the idea of podman, but itโs just not stable. Iโll try again in a year or so.
As a bonus, dockerโs CLI is significantly nicer.
Home sweet home
I'm intrigued a LOT by Podman but also I'm already running some Docker stuff and it's working.
I'd really like some guides on how to switch over and what all that entails, that isn't written like I have 13 cloud certificates and this is another day at the office LOL.
So, 100% skill issue on my part.
In great news though: OpenMediaVault has Podman support in its GUI now! Love them.
Docker at home:
chroot
Podman is much better than docker though in pretty much every way
Podman is unironically the better choice. Just try to make docker comply with your firewall...
Docker bypasses your firewall and runs as root. Only an idiot would allow that shit.... I'm an idiot. But I'm fixing that.
It doesn't "bypass your firewall"... it lets you shoot yourself in the foot. You're asking it to open ports without specifying an explicit network interface so it opens them on all interfaces. Which includes opening up the firewall, because what's the point of putting up a service and blocking it in the firewall.
Also, doing it by hand would be incredibly tedious. Docker automatically adjusts the rules to match the ports and interfaces to its private container netmasks, and brings them up or down as needed when the containers start/stop.
All you have to do is bind ports to localhost or to a private interface if you don't want the service to be publicly exposed.
Beginners get bitten by this because they say ports: 9999:9999 instead of ports: 127.0.0.1:9999:9999/tcp like they should. Unfortunately most examples out there use the terse version and never explain why it's bad.
Podman is unironically the better choice.
I like the idea of podman, but itโs just not stable. This meme was inspired by my frustration of trying to switch.
Just try to make docker comply with your firewall.
I literally did this yesterday and it wasnโt that hard. You just add iptables:False to the docker config file.
This + forwarding stuff to the docker namespace is working great for me. https://wiki.archlinux.org/title/Nftables#Working_with_Docker
y'all use containers still? I run my site with native installed software configured by hand like a TRUE sysadmin!
You're that chain smoking black hat with a stack of computers, black out curtains several screens and not a single lightbulb.
Ngl after trying out Rootless Podman on my system (I was playing with Distrobox) I kinda wanna switch my whole Homelab to it, I'm just lazy, afraid the move to rootless with blow up everything and have zero fucking free time.
I am running my entire homelab from podman quadlets (systemd managed podman containers) and itโs honestly very dope. Podman gets a bad rap for being second tier to docker but they legit have a bunch of awesome features for Linux users specifically that make it way nicer. Using systemd for docker status can add some misdirection occasionally, but having the logs from containers directly in journalctl alongside the rest of my system logs is amazing
Docker became a license nest despite actual devs using k8s like a normal person should.
Meanwhile podman gave us rootless containers, CDI, and quadlets which far outweighs whatever docker is limping to the barn with.
i genuinely run all my shit bare metal
Hopefully none of those things have dependency version conflicts
they do quite regularly
I choose Podman bc it's open source and that's kind of the reason for using everything as a container bc those are often also open source. Fuck docker
I'm curious why you feel this way? I'm kinda the opposite โ podman has features I use that Docker doesn't.
This meme was inspired by my frustration from trying to switch. I like the idea of podman, but it just doesnโt work. Tbf the bugs I encountered this time were with podman compose rather than podman itself, but still, Iโd rather use the tools that work. Iโve had similar experiences when Iโve tried to switch to podman in the past.
Interesting. I don't use any of the compose tools, so I've not faced that. I find Podman works reliably in places where I can't even get Docker to start working (such as RISC-V machines), but I also typically use podman for testing before deploying to k8s
Mom, i can i have podman?
Mom: we have podman at home.
Podman at home: rootless docker
