Executive summary
Podman v6.1.4 is a maintenance release, not a feature release - it contains one important bugfix for WSL users and one security patch in gvproxy. Besides that, there's a version bump for two core dependencies: Buildah and Storage.
Issues resolved
The most striking one for me is bug #29749: it turns out Podman didn't run at all when run under WSL 3. This isn't a cosmetic bug - if the tool doesn't "function" (not function), that means a total blocker for anyone using Podman on Windows via WSL. On the other hand, there's CVE-2026-107935 which is patched via the gvproxy update to v0.9.0. gvproxy is the networking component Podman uses for rootless networking (especially in Mac/WSL setups), so a CVE there could potentially affect the container's network path - not just a functionality issue.
Key features and code example
The release notes don't mention any new API or flags - it's purely a bugfix plus dependency bump (gvproxy v0.9.0, Buildah v1.45.2, Storage v1.64.2). So there's no new syntax to show. What's relevant instead is how to verify after upgrading, to make sure the version and networking component have been updated:
# ilustrasi: cek versi Podman dan backend network setelah upgrade ke v6.1.4
podman version
podman info --format '{{.Host.NetworkBackend}}'Impact and upgrade notes
For teams running Podman on top of WSL, I consider this upgrade to v6.1.4 mandatory - the previous bug meant Podman didn't run at all on WSL, so this isn't just a nice-to-have. For all other users, the CVE-2026-107935 patch in gvproxy is also a strong reason to update, since this is the component that handles rootless networking. The bump of Buildah to v1.45.2 and Storage to v1.64.2 is likely just carrying along fixes from their respective upstreams - the release notes don't detail what's included, so I don't want to speculate here.
---
First announced on Podman releases. Read the original source for full details.