Podman Desktop

Docker Desktop moved to paid subscriptions for larger companies in 2021, which left many teams discovering that a daily development tool now required a procurement process. Individuals and small teams still use it free, but "will these licensing terms change again" became a legitimate concern.

Podman is Red Hat's open-source container engine, and Podman Desktop is its graphical interface. Apache-2.0, 7,927 stars, and free regardless of company size.

Migration costs less than expected:

• CLI compatibility. podman run, podman build and podman ps take the same arguments as Docker's, and many people simply alias docker=podman and carry on.
• Images are interchangeable. It uses OCI standard images, so anything on Docker Hub pulls and runs normally.
• Compose support. It runs docker-compose.yml files, and can also convert Compose definitions into Kubernetes manifests.

Architecturally there is one substantive difference: it is daemonless. Docker requires a resident root daemon that owns every container as a child process; Podman launches containers directly as your own user (rootless) with no background service. That yields a clearer security boundary — a container escape does not hand over root — and no permanently running service just to keep one container alive.

The GUI handles containers, images, volumes and networks, log viewing, shelling into a container, image builds, pod management for grouping containers, and spinning up a local Kubernetes cluster (Kind or Minikube) to push images into for testing. An extension mechanism connects it to the Docker engine, Lima and various clouds.

To be clear about:

• On Windows and macOS it runs inside a virtual machine. Containers are Linux technology, so Podman uses a lightweight Linux VM (podman machine, backed by WSL2 on Windows) — exactly as Docker Desktop does. Not a drawback, but it consumes memory and the first run downloads a VM image.
• The ecosystem and documentation still trail Docker's. Search results for a problem will mostly be about Docker; most translate directly, occasionally they do not.
• A few tools that depend deeply on Docker internals — some CI tooling, or containers that mount docker.sock to drive the host's Docker — need extra configuration.

Who it suits: teams affected by Docker Desktop's licensing, anyone who wants the rootless security model, and people doing Kubernetes work. For personal learning the two feel much alike, and Podman's advantage is mainly not having to think about licensing at all.