← All insightsBest Practices

Podman best practices for teams

Nir Geier, CodeWizard · 18 July 2025 · 3 min read · Intermediate

Podman rewards a little discipline. These are the practices that keep it maintainable as a team and a codebase grow.

The practices

  • Prefer rootless containers and Quadlet/systemd for services
  • Use podman generate kube to bridge to Kubernetes
  • Pin base images and scan them like with Docker

What good looks like

Run a rootless container and generate a systemd unit.

bash
podman run -d --name web -p 8080:80 nginx:alpine
podman generate systemd --new --name web > ~/.config/systemd/user/web.service
systemctl --user enable --now web

Anti-patterns to retire

  • Assuming 100% Compose parity (use podman-compose or Quadlet)
  • Rootless port <1024 binding issues
  • Mixing docker and podman socket expectations in tooling

Want senior help putting Podman to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.

Like where this is going?

Get hands-on help from the engineers who write these posts.

Book a free consult