Podman 6.1.0: Volume Renaming, Machine Restarts, and a Long List of Bug Fixes

Podman 6.1.0 is here, and while it’s not a flashy release, it’s the kind of update that quietly makes day-to-day container work smoother. This release focuses on rounding out long-requested quality-of-life commands, tightening up podman machine reliability across Windows, macOS, and WSL, and squashing a healthy batch of bugs in Quadlet, healthchecks, and the API layer.

Here’s what’s new in v6.1.0.

Headline Features

podman volume rename is here. You can now rename a volume without having to create a new one and manually copy data over. Note that volumes created with external volume drivers, or volumes currently attached to a running container, can’t be renamed yet.

podman machine restart gives you a one-command way to restart a Podman-managed VM, instead of chaining together stop and start.

podman network rm –ignore suppresses errors when you try to remove a network that doesn’t exist — handy for idempotent scripts and cleanup automation where you don’t want to special-case “already gone.”

podman manifest push –retry / –retry-delay add automatic retry logic to manifest pushes, which should help smooth over transient registry flakiness without wrapping every push in your own retry loop.

podman generate kube now maps healthchecks to livenessProbe, so container healthchecks defined in Podman translate more faithfully when you generate Kubernetes YAML from an existing container or pod.

WSL gets a force_port_listen option in containers.conf. This is required for port forwarding from the Windows host to work correctly, and Podman now sets it automatically on newly created podman machine VMs using the WSL provider.

The newly added pasta forwarding mode for rootless network has been reworked to correctly support ipv6 port forwarding.

podman info now reports free memory alongside used and total memory, giving you a fuller picture of host resource availability at a glance.

And many more bug fixes.

API Updates

The Compat API continues to close the gap with Docker’s v1.44 API, including deprecating fields that Docker itself removed in that release. There’s also a fix ensuring the exec session create endpoint (/containers/$CID/exec) properly honors the ConsoleSize parameter. And keep an eye out — the changelog notes that groundwork for Docker v1.45 API support is already underway.

Under the Hood

Several core dependencies got bumped as part of this release:

• Buildah → v1.45.0
• image library → v5.41.1
• storage library → v1.64.0
• common library → v0.69.1

Getting v6.1.0

Installers and static binaries are available directly from the v6.1.0 release page, including packages for macOS (arm64), Windows (amd64/arm64), and check your linux distribution package for the update.

If you’re managing containers on WSL or Hyper-V, the machine reliability fixes alone make this a worthwhile upgrade. And if you’ve ever wanted to rename a volume without a song and dance, podman volume rename is waiting for you.