Podman: from Docker networks to pods, kube play, and going rootless
If you know Docker, Podman Desktop will feel familiar. Podman maintains a high level of compatibility with the Docker CLI, so your existing commands and workflows carry over, including networks. On top of that, Podman brings a concept Docker doesn't have: the pod, where containers talk to each other over localhost instead of a network, just like in Kubernetes. You can even run a pod straight from a Kubernetes YAML file with kube play. That's handy for exercising a workload the way it will run in production, but kube play doesn't enforce Kubernetes admission or OpenShift SCC rules by itself, for that you still need a real cluster or a local one like Kind, covered later in this post.
This post walks through networks, pods, and kube play, before landing on one of Podman's key differences from Docker: its rootless design. There's a nuance worth keeping in mind though: while the podman CLI and podman machine init default to rootless, Podman Desktop's "Create a Podman machine" dialog defaults to a rootful connection instead, notably because Kind on Windows requires it.
