Podman 6.1 adds useful storage controls, but an in-place rename is not a migration shortcut for a volume still referenced by a container. The distinction matters even when that container is stopped.
What the release adds
The official v6.1.0 release is dated August 12, preceding this article's publication. It adds volume rename, machine restart and Quadlet's ImageVolume setting, and fixes a race in generated systemd units. These additions do not remove the need to inspect a deployment's existing storage references.
Stopped does not mean unreferenced
The versioned rename manual requires a local-driver volume with no container using it, running or stopped, and no current volume mount. Plugin-backed and image-driver volumes are excluded. Renaming an anonymous volume makes it named.
Suppose a stopped database container still refers to a volume called inventory. The process is inactive, but its configuration still holds the reference. The rename's refusal is therefore consistent with the documented condition. Merely stopping the service is not enough.
Our cover represents these checks as gates, not commands to delete containers. Inventory references and backup requirements before deciding how to recreate a workload. A rename also does not copy the underlying data to another disk or verify that the data is healthy.
ImageVolume is about declarations in the image
The Quadlet manual maps ImageVolume to the run option. The choices handle image-declared volumes: bind creates an anonymous named volume, tmpfs uses temporary memory-backed storage, and ignore takes no action for those declarations. The documented default is bind.
This setting should not be mistaken for a universal switch governing every explicit mount in a deployment. If a database needs durable storage, inspect its actual mounted path and named-volume configuration. Test restart and recreation behavior in a disposable environment with representative data; do not infer persistence from the word “volume” alone.
After changing Quadlet configuration, inspect the generated service and its diagnostics. An accepted source file and a healthy running application are separate outcomes. The release's generation fix is useful, but “upgrade without ceremony” was too broad: packaging, migration from earlier major versions and each workload's storage contract still need verification. No Podman or service changes were performed on a production machine for this article.
Correct release date and full rename restrictions including stopped containers and mounts; distinguish image-declared volumes from explicit mount configuration.