Podman — Daemonless Container Engine for OCI Containers

What it is

Podman is a daemonless container engine for developing, managing, and running OCI-compliant containers and pods. Unlike Docker, Podman does not require a background daemon process running as root. Each container runs as a child process of the Podman command, which improves security and simplifies process management.

Podman targets developers and sysadmins who want Docker-compatible container tooling with better security defaults. It is the default container tool on Red Hat Enterprise Linux, Fedora, and CentOS Stream.

How it saves time or tokens

Podman is a drop-in replacement for the Docker CLI. Most docker commands work by simply replacing docker with podman. Existing Dockerfiles, docker-compose files (via podman-compose), and CI scripts require minimal changes. You get rootless containers by default without modifying your workflow.

No daemon means no daemon crashes. If Docker's daemon dies, all running containers stop. With Podman, containers are independent processes that survive Podman restarts.

How to use

1. Install Podman:

# macOS
brew install podman
podman machine init
podman machine start

# Fedora/RHEL
sudo dnf install podman

# Ubuntu/Debian
sudo apt install podman

1. Run containers exactly like Docker:

podman run -d --name web -p 8080:80 nginx
podman ps
podman logs web

1. Build images from Dockerfiles:

podman build -t myapp:latest .
podman push myapp:latest registry.example.com/myapp:latest

Example

Running a pod (group of containers sharing a network namespace):

# Create a pod
podman pod create --name my-stack -p 8080:80 -p 5432:5432

# Add containers to the pod
podman run -d --pod my-stack --name db postgres:16
podman run -d --pod my-stack --name app nginx

# Containers share localhost
podman exec app curl localhost:5432

Pods mirror Kubernetes pod semantics, making local development closer to production.

Related on TokRepo

• AI tools for DevOps -- Container and infrastructure tools
• Self-hosted tools -- Self-hosted development infrastructure

Common pitfalls

• Assuming docker-compose works natively. Use podman-compose or podman compose (with the compose plugin). Not all docker-compose features are supported identically.
• Rootless networking limitations. Rootless containers cannot bind to ports below 1024 without extra configuration. Use sysctl net.ipv4.ip_unprivileged_port_start=80 or run with --network=slirp4netns.
• Volume permission issues in rootless mode. UID mapping between host and container can cause permission denied errors. Use podman unshare chown to fix ownership.