Last checked and updated on April 15, 2026What Is New in Podman 5.3
Podman 5.3 delivers a host of incremental improvements focused on networking, container lifecycle management, and developer experience. The update also introduces new commands and refines existing features for better day-to-day operations.
| Category | Key Updates |
|---|---|
| New Features | New podman events options, podman network label, SDNOTIFY proxy support |
| Networking | DNS improvements, port forwarding with slirp4netns, new network label support |
| Container & Image Management | New container checkpoint flags, podman image tree filter, auto-update service fixes |
| Pod & Service Management | Pod init container support, enhanced systemd unit file generation |
| Bug Fixes & Misc | Fixes for SELinux, file locks, and various command-line tools |
What networking improvements are in Podman 5.3?
This release tackles several networking pain points, particularly around DNS and port handling. The team has enhanced reliability for scenarios where containers need consistent network resolution.
A significant change allows the slirp4netns port handler to forward ports to containers using the --publish flag. This simplifies networking for rootless containers. The new podman network label command lets you add metadata to networks, which helps in organizing and identifying network resources.
How does Podman 5.3 improve container lifecycle management?
New options for the podman events command give you finer control over the event stream. You can now use --stream=false to collect events without following the live stream and --since to get events from a specific point in time.
For container checkpointing, the new --ignore-rootfs flag allows you to skip the container's root file system during the operation. This is useful for optimizing the checkpoint process for specific use cases.
What's new for container images in this release?
The podman image tree command now supports a --whatrequires filter. This lets you reverse lookup and see which images depend on a specific layer, making it easier to debug image hierarchies and dependencies.
For system integrations, Podman now supports acting as a proxy for the SDNOTIFY protocol. This means you can more easily integrate containers with systemd to notify when they are ready, improving service startup coordination.
Are there any changes for pods and systemd?
Yes, Podman 5.3 introduces support for init containers within pods. Init containers run before the main application containers in a pod, allowing you to set up the environment or perform pre-flight checks.
The systemd unit file generator has also been updated. It now correctly handles the KillMode option and properly escapes special characters in container names within the generated unit files, leading to more reliable service management.
FAQ
How do I use the new SDNOTIFY proxy feature?
Set the --sdnotify=container flag with podman run or podman create. Podman will then proxy the notify socket into the container and handle the ready notification to systemd, simplifying service startup synchronization.
What does the new --ignore-rootfs flag do for checkpoint?
It allows the podman container checkpoint command to skip the container's root file system. This creates a smaller checkpoint file and speeds up the process if you only need to preserve the container's memory state.
Can I now publish ports with slirp4netns in rootless mode?
Yes. In 5.3, the slirp4netns port handler supports the --publish (-p) flag. This makes port publishing behavior more consistent between rootless and rootful containers.
How do init containers work in a Podman pod?
You can define init containers in a pod YAML or using the CLI. These containers run (and must complete successfully) in sequence before the main application containers in the pod are started, which is ideal for setup tasks.
What was fixed for the auto-update service?
The fix ensures the podman auto-update service correctly handles the restart policy of containers. It now properly respects the policy defined in the systemd unit files, preventing unintended container restarts.