Migrate from Docker to Podman in Minutes – A Practical Startup Guide

Overview

Podman is a daemon‑less, rootless container engine that can be used as a drop‑in replacement for Docker. It provides native Docker‑compatible CLI commands, integrates Buildah for image builds, and can generate Kubernetes manifests directly.

Step 1 – Install Podman

Podman runs on Linux, macOS, Windows, and WSL2.

Linux (Ubuntu/Fedora)

sudo apt update
sudo apt install -y podman

macOS (Homebrew)

brew install podman
podman machine init
podman machine start

Windows (Winget)

winget install -e --id RedHat.Podman
podman machine init
podman machine start

Verify the installation: podman info The output should contain rootless: true, confirming that Podman is running without a privileged daemon.

Step 2 – Alias Docker to Podman

To keep existing scripts unchanged, create a shell alias: alias docker=podman After this, any Docker command (e.g., docker ps) will be executed by Podman.

Step 3 – Run Existing Containers

Podman can run any Docker‑compatible image: podman run -d -p 8080:80 nginx Common management commands:

podman ps
podman stop <container-id>
podman logs <container-id>

Step 4 – Build and Push Images from Dockerfiles

Dockerfiles work unchanged with Podman. Example workflow:

# Build the image
podman build -t myapp:v1 .

# Tag for a remote registry
podman tag myapp:v1 myregistry.com/myapp:v1

# Push to the registry
podman push myregistry.com/myapp:v1

Podman uses Buildah under the hood, which can reduce image size and improve build speed.

Step 5 – Generate Kubernetes Manifests

Podman can export a local image as a Kubernetes YAML file and run it without a full cluster:

podman generate kube myapp > myapp.yaml
podman play kube myapp.yaml

Step 6 – Verify Rootless Security

Podman runs containers as the invoking user, eliminating the need for a root daemon. Confirm user‑namespace isolation: podman unshare cat /proc/self/uid_map The output shows a mapping of the container’s UID to the host user’s UID, proving sandboxed execution.

Step 7 – Common Pitfalls and Solutions

Compose volume permissions : create a rootless volume with podman volume create --opt o=uid=1000.

Cannot connect to the Podman socket : start the virtual machine using podman machine start.

Slow network on macOS : enable the DNS proxy in Podman Desktop settings.

Build cache issues : add the --layers flag to podman build for better caching.

Step 8 – CI/CD Automation

Podman can be installed and used in CI pipelines. Example GitHub Actions fragment builds and pushes an image without a Docker daemon:

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Install Podman
        run: sudo apt-get install -y podman
      - name: Build & Push
        run: |
          podman build -t myapp:${{ github.sha }} .
          podman push myapp:${{ github.sha }} docker://ghcr.io/myorg/myapp:${{ github.sha }}

TL;DR – Why Podman Beats Docker

Daemonless : no single point of failure.

Rootless by design : containers run as normal user processes, reducing attack surface.

Native Kubernetes YAML support : podman generate kube creates manifests instantly.

Drop‑in compatibility : alias Docker to Podman and keep existing workflows.