Fly To Podman: a script that will help you to migrate from Docker

Original Article ↗ Hacker News Discussion ↗

Engineers weigh the benefits and trade-offs of migrating from Docker to Podman, a daemonless, often rootless container engine that aims for near drop‑in Docker compatibility. They highlight easier integration with systemd (via Quadlets), better security and process isolation, and reuse of existing Dockerfiles and registries, but note pain points around older distro packages, weaker Docker Compose equivalents, and tooling that still assumes a “real” Docker daemon. Several users report successful full migrations—especially on Linux and in CI—while others stick with Docker on macOS/Windows or where Podman’s compose and ecosystem gaps create too much friction.

Installation & Basic Usage

  • On Debian, users report apt install podman as sufficient, then podman run -it debian bash for a Debian container.
  • Podman uses OCI images and can pull from Docker Hub or other registries, with configurable defaults in registries.conf.
  • On Linux, it runs directly on the host kernel; on macOS/Windows it uses a VM via podman machine or similar.

Compatibility & Migration

  • Many say it’s ~90% a drop‑in replacement: podman-docker can alias docker to podman.
  • The script in the repo is seen as useful for migrating existing, hand‑configured Docker setups (containers, networks, restart policies).
  • Some note tools that talk directly to the Docker API or expect Docker‑specific labels can break.

Podman vs Docker: Architecture & Security

  • Key selling points: daemonless, rootless by design, simpler networking rules, better systemd integration (Quadlets).
  • Several praise process isolation and lack of a privileged Docker daemon; others argue Docker’s rootless mode narrows this gap.
  • Licensing is mentioned: Docker Desktop’s restrictions vs Podman’s fully open tooling.

Compose & Orchestration

  • Options: podman-compose, using Docker Compose against the Podman socket, or replacing Compose with systemd Quadlets or Kubernetes YAML (podman kube play).
  • Opinions on podman-compose diverge: some find it fine; others call it buggy, noisy, and incomplete vs the Compose spec.
  • No Swarm equivalent exists; for clustering people suggest Nomad or Kubernetes.

User Experience & Platform Notes

  • Several report Podman is now “install and run” on Linux; others still find it less polished than Docker, especially on macOS with podman machine VM issues and slower performance.
  • Good experiences are reported with Podman Desktop, Rancher Desktop+Podman, and tools like Pods (GUI), though some prefer Docker/Orbstack on macOS.
  • Rootless mode can be problematic with enterprise auth setups (e.g., AD‑joined laptops).

CI/CD, Images & Distros

  • Podman builds work in CI, sometimes needing --format=docker for non‑OCI consumers.
  • Performance in CI is generally reported as comparable to Docker.
  • Some complain Debian Stable’s Podman is too old and resort to backports or manual builds; others say the packaged version works fine.

Should You Switch?

  • One camp: stick with Docker if it works; migration adds complexity.
  • Another camp: Podman’s architecture, security model, and systemd integration justify switching, especially on Linux servers.