Podman v6.0.0

Original Article ↗ Hacker News Discussion ↗

Visual design and accessibility

  • Several commenters dislike the Podman v6 site styling: low-contrast gray text on beige and serif fonts feel harder to read, like a half-loaded stylesheet.
  • Others note HN itself uses higher-contrast black-on-beige and find Podman’s gray-on-beige clearly worse from a readability perspective.

Why Docker remains more popular

  • Strong brand and first-mover advantage: people still say “Docker container” and often don’t know the term “OCI”.
  • Many tools, PaaS offerings, and company workflows are explicitly Docker-centric (Docker Desktop, testcontainers, Coolify, ECR/ECS/Fargate, etc.).
  • Inertia and “it works, why switch?” dominate in teams; perceived Podman gains (security, architecture) are indirect.

Podman strengths

  • Rootless operation and no long-running root daemon are major draws; avoids the “docker group == root” problem and silent iptables rewrites.
  • Quadlet + systemd integration is widely praised for servers and homelabs, replacing k3s or Docker Compose and making monitoring/logging simpler.
  • Some report significant build-speed improvements and reduced power use versus k3s.
  • Ability to act as a Docker API backend (podman-docker, aliasing docker to podman) eases migration.
  • New features in v6: improved networking (pasta/pesto), quadlet tooling (quadlet list), automatic BoltDB→SQLite migration, and adherence to XDG/UAPI config specs.

Pain points and incompatibilities

  • Docker Compose compatibility is the biggest recurring negative:
    • podman-compose and podman compose work for many, but others hit flaky volume handling, missing features, networking differences, and broken healthcheck/dependency semantics.
    • Some tools (skaffold, certain testcontainers, buildx flows) misbehave or need workarounds.
  • Rootless + SELinux/UID mapping often causes confusing permission issues on volumes; some say this is mostly solved, others still struggle.
  • Networking bugs are mentioned (IPv6 connectivity from host, broadcast handling, macOS fs events/inotify).
  • macOS experience is mixed: Podman Desktop is seen as less polished than Docker Desktop, OrbStack, Colima, Rancher Desktop, or new micro-VM tools; architecture and file-notify quirks show up more there.

Packaging and distro support

  • On Ubuntu, Podman versions lag in the official repos; some see this as a blocker and contrast it with Docker’s own apt/yum repos.
  • Others prefer distro-packaged versions for stability and consistency, arguing that keeping up-to-date packages is primarily the distro’s job, not Podman’s.