Podman 6.1 Adds Volume Rename, Machine Restart, and a Quadlet ImageVolume Key
Podman 6.1 ships volume renaming, a machine restart command, Quadlet ImageVolume support, and IPv6 rootless port forwarding.
Editor's Note ·
- Correction:
- The article attributes the quote "without recreating them" (describing the new podman volume rename command) to Podman's GitHub release notes. That exact phrase does not appear in the release notes, which say only: "A new command has been added, podman volume rename, to allow renaming volumes." The phrase actually originates from Linuxiac's coverage, which is also cited in the article.
Overview
Podman 6.1 shipped on August 12, 2026, adding commands to rename volumes and restart Podman-managed virtual machines, alongside updates to Quadlet, networking, Kubernetes integration, and Docker API compatibility, according to the release notes published on GitHub. Linuxiac described the update as the latest feature release of “the popular daemonless container engine.”
What We Know
- The new
podman volume renamecommand lets users rename existing volumes “without recreating them,” though volumes created through volume drivers or currently in use by a container cannot be renamed, according to the release notes. - A new
podman machine restartcommand allows users to restart Podman-managed virtual machines directly, rather than issuing separate stop and start operations, per the release notes. - The
podman network rmcommand gains a--ignoreoption that suppresses errors when a targeted network does not exist, andpodman manifest pushadds--retryand--retry-delayoptions so failed pushes can be retried automatically, according to the release notes. - Quadlet
.containerunits now support a newImageVolume=key to configure how volumes defined in container images are handled, per the release notes. - The
podman generate kubecommand now translates container healthchecks into KuberneteslivenessProbedefinitions, according to the release notes. - A new
force_port_listenoption was added tocontainers.conffor Windows Subsystem for Linux (WSL) users, required to support port forwarding from the Windows host and automatically set on newly created Windows WSL machines, per the release notes. - The Pesto rootless port-forwarding tool now supports IPv6 with source IP preservation, and
podman infonow reports free host memory alongside used and total memory figures, according to the release notes. - The release fixes a bug where the remote Podman client could hang on some operations over SSH, a bug where
podman volume prune --all --filter label=fooincorrectly discarded the label filter and pruned all volumes instead of just labeled ones, and a race condition that could cause Quadlet to generate corrupt systemd units, per the release notes. - Quadlet’s error reporting was also changed to write to standard error rather than only to
/dev/kmsg, making errors visible to tools likesystemd-analyze --generators verify, according to the release notes. - Podman 6.1 updates its dependencies to Buildah v1.45.0, the containers/image library to v5.41.1, the containers/storage library to v1.64.0, and the containers/common library to v0.69.1, per the release notes.
- The release also continues work on Docker API compatibility, with further changes to the Compat API supporting the Docker v1.44 API and initial preparations for v1.45 API support, according to the release notes.
What We Don’t Know
The release notes do not indicate a timeline for when the new force_port_listen and IPv6 rootless port-forwarding features will be backported to earlier Podman release branches, if at all. It is also not stated whether the Docker v1.45 API compatibility work will land in the next feature release or a later one.
Analysis
The additions in 6.1 are incremental rather than architectural, focused on closing usability gaps — renaming a volume previously required deleting and recreating it — and on tightening Quadlet, the systemd-integration layer that has been a focus of recent Podman releases. The expanded Kubernetes healthcheck translation and continued Docker API compatibility work point to Podman’s ongoing effort to serve as a drop-in tool for workflows built around Docker and Kubernetes tooling.