Last checked and updated on 05 Jun 2026
What Is New in Podman 5.2
Podman 5.2 delivers a host of incremental improvements focused on container lifecycle management, networking, and developer experience. This release strengthens the existing feature set rather than introducing major breaking changes.
| Category | Key Updates |
|---|---|
| New Features | New container cleanup hooks, podman events --stream for Windows, enhanced podman generate support. |
| Improvements | Better file and image handling, networking refinements for Netavark and Aardvark-dns, service reliability. |
| Bug Fixes | Resolved issues across pods, containers, images, and the remote client. |
| Deprecations | Marked the --override-arch and --override-os flags for removal in a future release. |
What are the new hooks for container cleanup?
Podman 5.2 introduces a new pre-stop hook that executes inside the container namespace immediately before the container is stopped. This is useful for running graceful shutdown scripts or cleanup tasks that require container resources to still be available.
In practice, this allows applications to terminate connections cleanly or flush data to disk, reducing the chance of corruption when a container is being taken down. You define these hooks in your container's JSON configuration, similar to existing pre-create and post-stop hooks.
How has the events command improved on Windows?
The podman events --stream command now works on Windows, bringing it to parity with the Linux implementation. This command allows you to monitor a real-time stream of events from the Podman engine, such as container creation, start, stop, and removal.
This is a big deal for Windows developers and admins who need to observe system activity for debugging or automation. Before this, you could only get a one-time list of past events on Windows.
What enhancements were made to podman generate?
The podman generate command has been extended with new subcommands. You can now use podman generate manifest and podman generate spec to create manifest lists and OCI runtime specs, respectively.
This matters because it provides a built-in, standardized way to generate these complex configuration files directly from existing containers or pods, streamlining CI/CD and deployment workflows without relying on external tools.
What networking issues were fixed?
Several key networking improvements landed in this release. Aardvark-dns, the DNS resolver for container networks, saw fixes for handling very large DNS responses and A/AAAA record queries, making DNS more reliable in complex setups.
Netavark, the network stack, improved its handling of IPv6 DHCP and fixed an issue where it would incorrectly modify the host's /etc/resolv.conf in rootful mode. These are stability fixes that make day-to-day networking more predictable.
What got deprecated in this version?
The --override-arch and --override-os flags for podman pull and podman run have been deprecated. The functionality remains for now but will be removed in a future release.
You should start using the --platform flag instead, which accepts the standard os/arch format (e.g., linux/arm64). This change aligns Podman with the broader OCI image spec and simplifies the API.
FAQ
How do I use the new pre-stop hook?
You define it in the hooks section of your container's configuration. The hook will execute a specified command inside the container's namespace right before the container stops, allowing for graceful shutdown procedures.
Why is --stream for events on Windows a big deal?
It enables real-time monitoring of your Podman engine on Windows. This is critical for automation scripts and debugging that need to react instantly to container lifecycle events, a capability that was previously missing.
What should I use instead of --override-arch and --override-os?
Use the unified --platform flag. For example, instead of --override-os linux --override-arch arm64, you would now use --platform linux/arm64.
Were there any changes to image handling?
Yes, improvements were made to handle invalid images more gracefully and to correctly set the OS and Architecture for images loaded from a directory, preventing runtime mismatches.
Did the remote client get any updates?
Several bugs were fixed, including issues with the --preserve-fds option and handling of environment variables, making the remote client more robust for API-driven workflows.