podman-container-tools/podman

What Podman does

Podman is a container engine for managing OCI and Docker images, containers, volumes and pods. Unlike a daemon-based engine, it has no long-running manager process, which reduces idle resource use and removes a central privileged service. The same repository contains libpod, the Go library behind container lifecycle management, and the tool exposes a Docker-compatible CLI plus a REST API with additional Podman-specific capabilities.

Podman runs natively on Linux and can run as an unprivileged user through user namespaces. On macOS and Windows it runs inside a Podman-managed virtual machine, and Podman Desktop offers a graphical front end for local development with Podman and Kubernetes. Image building is delegated to Buildah, networking to Netavark and Aardvark DNS, and monitoring of OCI runtimes to Conmon; the runtime itself can be crun or runc.

Quick start

1. Install Podman for your platform using the installation guide. Distribution packages are the usual path on Linux; macOS and Windows users need the virtual machine support provided by podman machine.
2. Run the hello image to confirm the installation:

podman run quay.io/podman/hello

The command pulls quay.io/podman/hello, starts it, and prints an ASCII container greeting with project links; image pulls, blobs and signature copying are shown in the output. Docker users can consult the command transfer table when moving existing workflows. For GUI use, install Podman Desktop and point it at the local Podman installation.

Constraints and scope

Rootless operation needs some host configuration by an administrator before it works; the required setup and known rootless limitations are documented separately. Rootless containers never gain more privileges than the user who launched them, even with elevated container options. The most recent release receives upstream support, with occasional LTS versions; releases are PGP signed and published on a four-per-year major/minor cadence. Image signing and specialized registry pushing are out of scope and handled by Skopeo, while the Kubernetes CRI interface belongs to CRI-O. Podman does not share container storage with Buildah, so containers created in one are not visible in the other.

HotRepo's take

Podman appeared on HotRepo's Go weekly list for 2026-11-11 at position 18, with 73 stars gained that week and totals of 33,242 stars and 3,456 forks. It is a long-running project created in 2017, and this single snapshot does not establish a trend. What stands out technically is the architecture: a Docker-compatible CLI and API without a managing daemon, rootless execution as a first-class mode, and clear separation from Buildah and CRI-O rather than trying to cover every container-tooling role.