--- title: "Podman 1.0: daemonless and rootless container engine" description: "Podman 1.0 (January 2019) by Red Hat: container engine with Docker-compatible CLI, daemonless architecture, rootless support, Kubernetes-style pods. Part of the buildah + skopeo ecosystem for Linux container management." url: "https://www.noze.it/en/insights/podman-1-0/" lang: "en" alternate: "https://www.noze.it/insights/podman-1-0/" published: "2019-01-14" author: "noze S.r.l." keywords: "Open Source, Web, Podman, Red Hat, Container, Daemonless, Rootless, Buildah, Skopeo" --- # Podman 1.0: daemonless and rootless container engine Podman 1.0 (January 2019) by Red Hat: container engine with Docker-compatible CLI, daemonless architecture, rootless support, Kubernetes-style pods. Part of the buildah + skopeo ecosystem for Linux container management. 14 January 2019 ## A container engine without a daemon Docker is built around a **privileged daemon** (`dockerd`) handling all operations. This architecture has two perceived issues: - **Single point of failure** — if the daemon crashes, all containers fall - **Privilege model** — the daemon runs as root; whoever can talk to the Docker socket has root privileges **Podman** (from 2018) responds with a **daemonless** architecture: every `podman` command is an independent process using **runc/crun** directly, without persistent intermediaries. Developed by **Red Hat** under **Apache 2.0**, on **14 January 2019** Podman reaches stable **version 1.0**. ## Docker-compatible CLI Podman mimics the Docker CLI API: `podman run`, `podman build`, `podman pull`, `podman push` work like Docker counterparts. The alias `alias docker=podman` runs many existing scripts unchanged. Not full identity: Podman does not natively support `docker-compose` (but has `podman-compose`, third-party, and later `podman play kube` for K8s-style YAML). ## Rootless Podman supports **rootless mode** natively: a non-root user can run containers without sudo. Uses **user namespaces** and **subuid/subgid** for ID mapping. Advantages: - Reduced attack surface - Easier multi-tenancy - Compatibility with HPC environments (where users are not root) Docker is expected to add rootless support in a later release, partly driven by Podman. ## Pods Podman introduces the **pod** concept — a group of containers sharing network namespace, analogously to Kubernetes pods. The `podman pod create` command creates a pod, then containers are added with `podman run --pod `. Allows local prototyping of K8s-like configurations. ## Buildah and Skopeo Podman is part of a Red Hat ecosystem: - **Buildah** — OCI image build without daemon, script-friendly, more flexible than `docker build` - **Skopeo** — OCI image inspection, copy, signing between registries without local pull - **CRI-O** — K8s-native runtime (same team, covered elsewhere) Together they form Red Hat’s **“container-tools”** stack, complementary to Docker but with different architecture. ## Adoption - **Red Hat Enterprise Linux 8** (due in 2019) will have Podman as default instead of Docker - **Fedora** — Podman as default - **OpenShift 4** — buildah + CRI-O as building/running stack ## In the Italian context Italian RHEL-based companies will adopt Podman automatically with RHEL 8 upgrade. OpenShift adoption in public administration will bring Podman into related container management scenarios. Update — 2024 **RHEL 8** (May 2019) and **Fedora 31+** adopt Podman as default instead of Docker. **Docker 20.10** (December 2020) adds rootless support partly driven by Podman. **Podman Desktop** (2022, cross-platform GUI alternative to Docker Desktop) and native `docker-compose` support via `podman compose` follow. Podman becomes standard for CI/CD in GitLab runners and for enterprise use on RHEL. --- _References: Podman 1.0 (14 January 2019). Red Hat. Apache 2.0 licence. Ecosystem components: Buildah (image build), Skopeo (image management), CRI-O (K8s runtime). Rootless mode. Docker CLI compatibility._