Podman 6.0.2
A daemonless, rootless-capable container engine that implements the Docker CLI, runs containers as regular user processes, and generates systemd units through Quadlet.
Download TAR.GZ Project website ↗Download Mirrors
Podman runs containers without a daemon. Where Docker has a privileged background service that owns every container, Podman launches containers as ordinary child processes of your shell, which changes the security picture and the failure modes considerably.
Daemonless and rootless
No daemon means no single privileged process to compromise, and no service whose restart takes every container with it. Rootless mode goes further: containers run as your unprivileged user via user namespaces, so a container escape lands in an unprivileged account rather than root. That property is why Podman is the default container engine on Fedora and RHEL.
The CLI is the same
Podman deliberately mirrors Docker’s command line, so existing knowledge transfers directly:
podman run -d -p 8080:80 nginx
podman ps
podman logs -f mycontainer
alias docker=podman # most tutorials then work unchangedpodman compose reads the same Compose files, and Podman can pull from Docker Hub and any other OCI registry.
Quadlet instead of restart policies
For services that should survive reboots, Podman leans on systemd rather than its own supervisor. Quadlet files describe a container in systemd unit syntax and generate a real service, which means containers integrate with journalctl, dependency ordering, and everything else systemd already does.
What’s new in 6.0
Podman 6.0 added AMD GPU support for AI and graphics workloads, substantial Podman Machine improvements, expanded Quadlet functionality, and removed legacy cgroup v1 support. The 6.0.2 point release adds volume rename and machine restart, safer network and manifest commands, and fixes around rootless IPv6 forwarding.
Rootless caveats
Publishing ports below 1024 requires additional configuration, and volume ownership behaves differently under user namespaces than it does with Docker. Both are surmountable and well documented, but they are the two things that surprise people migrating.
Verify Your Download
Checksums and signatures are published alongside each release on GitHub.