That's a solid breakdown of the Docker vs. Podman debate! It's interesting to see how the daemonless architecture of Podman addresses those security and resource concerns. If you're looking for an alternative that simplifies things even more, you should check out ServBay. It's a local dev environment that handles all the setup for you
You mentioned discovering Podman pulled you into using Fedora in your homelab - can you elaborate?
This was a great read—thanks for sharing your experience with Podman! One thing worth noting for folks considering the switch: while aliasing docker=podman can work interactively in a shell, it won’t carry over to bash scripts or cron jobs. Aliases are typically not expanded in non-interactive shells unless explicitly configured, which means scripts relying on docker commands will fail unless you either update them to use podman directly or set up a symbolic link or wrapper script. Just something to keep in mind for smoother automation and CI/CD transitions.
just convert it to Kubernetes YAML. We all use Kubernetes these days
Do you actually believe it?
Thanks for writing this. I relate so much with this. I had been wanting a walkthrough like this to be laid out rather than just the excited hype and fanfare. You nailed it; now I can start my 'non-migration' across the board, incrementally. Great work here.
Enjoyed your article. Good points and illustrates how easy it is to switch to Podman. Would be better to show working with systemd using Quadlets instead of the deprecated 'podman generate systemd'.
David M
Just want to point out the reason you can just aliases docker for podman is not because podman realised its hard to make a new standard but because Podman and Docker follow the same standards as set by the OCI (Open Containers Initiative) Image and Runtime specs