(This issue)[https://github.com/containers/podman/issues/7544] suggests it might be useable but not straightforward for distros without systemd.
I am interested in trying Podman and Rancher for alternatives to Docker, but I don’t think this article is very good at convincing anyone… Two of their three points are VERY weak
The ease of creating pods is unmatched by any other container engine, whether CLI or GUI.
I would definitely challenge that opinion. For starters, I use the Docker CLI for 99% of my use cases, so really I don’t care about the GUI but about how the CLI commands are designed. Secondly, if I am going to use a GUI for Docker, I just use Portainer which is the best GUI I’ve found so far for container management.
This point is extremely subjective.
Unlike Docker, you can pull an image while in the Podman Desktop application
This is just incorrect, and I don’t know why they couldn’t just look at the Docker Desktop documentation for two seconds to find the truth
The strongest argument they have is for the rootless containers, which my company’s shared pipeline runners are now beginning to enforce. We use buildah for that (which I believe wraps around Podman) and I appreciate the increased security and lighter load on the system
Overall, this wasn’t a very convincing article. I’m interested in Podman but if I weren’t I think I’d find it pretty easy to dismiss this one
For the most part I’ve done alias docker=“podman” and it’s been fine. Been running multiple instances of haproxy in rootless pods oh rhel8 for over a year, it’s been unstoppable.
I also use it on my workstation as the backend for distrobox. The machine is a Ryzen 9 3900X with 64GB of DDR4-3200, always running at least two VMs. Very little resource impact with both Distroboxes running (one with GUI, one without).
Anecdotal, so also not particularly strong evidence either, but probably better than a load of marketing wank.