Last checked and updated on April 15, 2026What is new in Podman 5.6
Podman 5.6 introduces dedicated commands for managing Quadlets, making systemd-style container management much easier. It also brings several practical enhancements for Kubernetes YAML support, Podman machine configuration, artifact handling, and volume operations. This release focuses on improving usability for both local and remote workflows while preparing for future changes.
After working with Podman across many enterprise setups, I see these updates as especially helpful for teams using Quadlets for production deployments and those running virtual machines.
Major New Features in Podman 5.6
| Feature | Description |
|---|---|
| Quadlet Management Commands | New commands: podman quadlet install, podman quadlet list, podman quadlet print, and podman quadlet rm. These help install, list, view, and remove Quadlets for the current user (not yet available in remote client). |
| Quadlet Enhancements | .container units support environment variables without values (value taken from host). .pod units add Label= and ExitPolicy=. .image units support Policy=. .network units support InterfaceName=. |
| Podman Machine | podman machine init now supports --swap to enable and size swap space in the VM (in megabytes). |
| Kubernetes Support | podman kube play respects lifecycle.stopSignal from Pod YAML and supports CPU/memory node restrictions via annotations io.podman.annotations.cpuset/$ctrname and io.podman.annotations.memory-nodes/$ctrname. |
| Artifact Commands | The podman artifact suite is now stable and fully available in the remote client and REST API. |
Additional Improvements and Options
Podman 5.6 adds several convenient options and fixes for common tasks:
--mountoption now acceptsdest=as alias fordestination=.podman volume createsupports--uidand--gid.podman secret createadds--ignoreto succeed even if the secret exists.podman pullgains--policyfor pull behavior control.--mount type=artifactsupportsname=to set filename inside the container.--tmpfsnow acceptsnoatimeoption.podman updatesupports--latestto update the most recent container.- New
podman buildx inspectcommand for better Docker compatibility. podman volume importandpodman volume exportnow work with remote client.--build-contextsupported in remote client forpodman build.
Important Changes and Notes
Rosetta support in Podman machine VMs is disabled by default due to compatibility issues with newer Linux kernels. It may return in a future release after fixes are widely available.
A warning for the deprecated BoltDB database backend has been added (not shown by default yet -- this will change in Podman 5.7). This prepares users for its planned removal in Podman 6.0.
Other changes include more robust signal forwarding with --sig-proxy, better WSL handling on Windows, and improved artifact mounting behavior when the destination path does not exist in the image.
Bug Fixes in Podman 5.6
This version resolves several reliability issues:
- Fixed
--security-opt unmask=to properly accept comma-separated lists. - Prevented accidental killing of non-Podman processes when stopping containers with reused PIDs from exec sessions.
- Fixed
podman machine initfailures when run inside a container. - Corrected timezone information and lingering enablement for custom usernames in machines.
- Improved WSL detection on Windows and preference for the correct wsl.exe path.
- Fixed naming and joining issues for Quadlet
.podand.containerunits. - Resolved
RequiresMountsForgeneration for bind-mounted volumes in Quadlets. - Fixed emptyDir volume handling in
podman kube playto use tmpfs for memory-backed volumes. - Addressed issues with
--rmcontainers not always being removed after reboot.
Frequently Asked Questions about Podman 5.6
What makes the new Quadlet commands useful?
They provide simple CLI tools to install, list, view, and remove Quadlet units, simplifying management of systemd-integrated containers without editing files manually.
Should I enable swap when creating a Podman machine?
Use the new --swap option on podman machine init if your workloads need additional memory swapping inside the virtual machine.
Is Rosetta still supported in Podman 5.6 machines?
It is disabled by default due to kernel compatibility issues. You can follow the official blog for updates on when it may be re-enabled.
Do I need to do anything about the BoltDB warning?
Not immediately. The warning prepares you for the future removal in Podman 6.0. Plan your migration to SQLite when convenient.
Summary of Podman 5.6
Podman 5.6 strengthens Quadlet support with new management commands and flexible configuration options. It improves Kubernetes integration, machine setup, and remote client capabilities while fixing important bugs. These changes make Podman more convenient for developers and administrators working with containers in various environments.