Podman 6.1

Podman 6.1 is a point release with two additions that fix small, persistent annoyances rather than changing anything architectural. We covered it in more detail when it shipped.

Renaming volumes

The new podman volume rename command renames an existing volume in place.

podman volume rename old-name new-name

Previously, fixing a badly named volume meant creating a new one, copying the data across, updating every reference, and deleting the original. That is a lot of ceremony for a typo.

Two restrictions: volumes created through volume drivers cannot be renamed, and neither can volumes currently in use by a container. Stop the container first.

Restarting machines

podman machine restart restarts a managed VM in one step instead of requiring a separate stop and start.

podman machine restart

This matters most on macOS and Windows, where every Podman container runs inside a managed VM, but it applies anywhere you use podman machine. Configuration changes that require a VM restart were previously a two-command sequence that was easy to half-finish.

Why Podman rather than Docker

Podman runs containers without a daemon. Docker has a privileged background service that owns every container; Podman launches containers as ordinary child processes of your shell.

That changes the security picture. No daemon means no single privileged process to compromise and no service whose restart takes every container down with it. Rootless mode goes further, running containers as your unprivileged user through user namespaces, so a container escape lands in an unprivileged account rather than root. This is why Podman is the default container engine on Fedora and RHEL.

The CLI deliberately mirrors Docker’s, so existing knowledge transfers:

podman run -d -p 8080:80 nginx
podman ps
podman logs -f mycontainer
alias docker=podman     # most tutorials then work unchanged

podman compose reads the same Compose files, and Podman pulls 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 running its own supervisor. Quadlet files describe a container in systemd unit syntax and generate a real service, so containers integrate with journalctl, dependency ordering, and everything else systemd already provides.

Rootless caveats

Publishing ports below 1024 needs additional configuration, and volume ownership behaves differently under user namespaces than it does with Docker. Both are surmountable and documented, and both are what surprise people migrating.

Our Docker and Podman basics guide covers the differences in practice, and the docker run builder generates commands that work with either.

Verify Your Download

Checksums and signatures are published alongside each release on GitHub.