Podman 4.9: What's New, Release History & EOL Status

What Is New in Podman 4.9

The Podman 4.9 release delivers a solid set of enhancements focused on container networking, security, and core operational commands. This update refines existing features and introduces new capabilities for managing containerized environments more effectively.

What networking improvements were made?

Podman 4.9 brings significant clarity and control to container networking. The new podman network inspect command now includes a --format flag, allowing you to filter output and extract specific network configuration details programmatically. This is a huge time-saver for automation scripts.

For developers, the --ip flag has been fixed to work correctly with the slirp4netns port driver. This resolves a long-standing annoyance where static IP assignment wasn't functioning as expected in rootless mode, bringing more predictability to your local development environment.

How is container checkpoint and restore enhanced?

The checkpoint/restore functionality gets more flexible with new flags for the podman container restore command. You can now use --ignore-static-ip and --ignore-static-mac to restore a container without being bound to its original network identities.

In practice, this means you can restore a checkpointed container onto a different host or network environment without IP conflicts. It removes a major operational hurdle for using this advanced feature in production scenarios involving live migration.

What's new with the Podman API?

The Podman HTTP API now supports tunneling the Attach and Exec endpoints over a single connection. This architectural change simplifies how clients interact with these streaming operations, making the API more robust and easier to implement for third-party tools.

Several bugs were also squashed, including a fix for the /images/prune API endpoint. It was incorrectly reporting pruned images' sizes, which could throw off your monitoring and cleanup scripts. Now you get accurate data back.

Are there any changes to volume management?

Volume handling is more consistent. The podman volume create command now properly honors the --ignore flag. If you try to create a volume that already exists and use this flag, Podman won't error out—it will just silently skip the operation and return success.

This change is perfect for idempotent setup scripts. You can define your volume creation steps without wrapping them in complex existence checks, making your infrastructure-as-code configurations cleaner and more reliable.

What security tweaks should I know about?

SELinux labeling for named volumes has been improved for better consistency. Furthermore, the handling of container secrets is now more precise, ensuring that sensitive data is managed correctly throughout the container lifecycle.

These aren't groundbreaking changes, but they close subtle gaps that could cause headaches. For teams running under strict SELinux policies, the volume labeling improvements will prevent unexpected permission denied errors.