Last checked and updated on April 15, 2026What Is New in Podman 5.1
Podman 5.1 delivers a host of refinements focusing on networking, the REST API, and core container management. This release builds on the solid foundation of v5.0, introducing features like native MACVLAN support and significant improvements to the API's completeness and stability.
| Category | Key Highlights |
|---|---|
| New Features | Native MACVLAN networking, New container checkpoint/restore flags, SELinux mount label support for pods |
| API Improvements | Extended volume support, Enhanced container and image inspection endpoints |
| Networking | Improved netavark and aardvark-dns components, Better port forwarding reliability |
| Bug Fixes & Misc. | Fixes for image handling, log management, and system service stability |
How did Podman 5.1 improve container networking?
The biggest networking upgrade is the native implementation of MACVLAN networks. Previously, you had to manually create a MACVLAN interface and pass it to a container using --network. Now, Podman's native network stack manages this for you, simplifying the process of giving containers direct layer 2 access to the physical network.
Under the hood, the netavark and aardvark-dns components have been refined. These improvements lead to more reliable port forwarding and overall stronger DNS resolution within container networks, which is crucial for microservices communication.
What changes were made to the Podman API?
The REST API saw substantial expansion, bringing it closer to parity with the CLI. New endpoints were added for comprehensive volume management, including creating and listing volumes directly via the API. This makes automation and integration with other tools much smoother.
Furthermore, the container and image inspection endpoints now return more detailed information. For developers building UI dashboards or monitoring tools, this provides a richer dataset to work with without having to parse CLI output.
Are there new features for container checkpoint and restore?
Yes, the checkpoint/restore functionality got more flexible. The new --ignore-rootfs flag allows you to checkpoint a container without including its root filesystem. This is useful for speeding up the process when you only need to preserve the container's memory state.
They also introduced the --ignore-static-ip and --ignore-static-mac flags. These give you control over whether to preserve the container's network configuration upon restore, which helps when moving a container to a different host or network environment.
Did Podman 5.1 add any pod-specific capabilities?
A notable addition is the --security-opt label=filetype flag for pods. This lets you apply a single SELinux mount label to all volumes mounted inside every container within the pod. It simplifies security policy management for multi-container applications that share storage.
This is a classic Podman feature—enhancing the pod abstraction to handle complex, real-world deployment scenarios that involve both security and shared resources.
FAQ
How do I create a MACVLAN network with Podman 5.1?
You can now create it directly using the network create command: podman network create -d macvlan. Podman will handle the underlying interface setup, making it much easier than the previous manual method.
Can I now manage volumes completely through the API?
Yes. The API endpoints for volume creation, listing, and inspection were added in this release, allowing for full lifecycle management of volumes without dropping to the CLI.
What is the practical use of the --ignore-rootfs checkpoint flag?
It significantly speeds up the checkpoint process if the container's root filesystem is already persisted elsewhere, like on a shared volume. You only save the memory state, which is faster and creates a smaller checkpoint file.
Were there any changes to the podman system service?
Yes, several stability fixes were backported to the system service. In practice, this means the daemonless daemon is more robust, especially under heavy load or when managing many containers simultaneously.
Is it easier to debug image pulls now?
Absolutely. Improvements were made to give clearer error messages during image pulls. You'll get better feedback if there's a network issue, an authentication problem, or if the image manifest is invalid.