Click here to download it ! This release brings exciting new features and improvements: Podman Desktop 1. 29 brings full integration with Podman 6. This is a major milestone for the project. The Podman team has delivered a significant engine upgrade, and we have integrated those new capabilities directly into your workflow. For a complete overview of what's new in Podman 6. With Podman 6, the command-line interface defaults to using krunkit , as the desktop does.
The upgrade also brings AMD GPU support for hardware-accelerated containerized workloads, improving performance for AI, machine learning, and graphics-intensive tasks. Quadlet improvements refine systemd service file generation for more stable management of containerized services. Be sure to check out the Quadlet extension for the best experience. conf on macOS or Windows now aligns with your Podman Machine configuration. Previously, local configuration changes might not reflect inside the virtual machine. With Podman 6, this connection is tightened so your settings apply consistently across host and VM.
Running podman machine list CLI command now displays all machines across different providers in a single, unified list. Whether you are using applehv, krunkit, hyper-v, or wsl, one command gives you the full picture. On the Podman Desktop side, machine listing is also faster because it now uses a single API call instead of separate requests per provider. CA certificate synchronization is now built into the Podman 6 machine creation flow using the native --import-native-ca flag. This replaces the former built-in Podman Desktop sync command that was needed in previous versions.
Users behind SSL-inspecting proxies no longer need to manually run sync commands after creating a machine. Podman Desktop automatically appends the flag during podman machine init . Podman Desktop handles the --import-native-ca flag automatically. However, if you create machines from the command line or through custom scripts, you must explicitly include it: Without this flag, you may encounter SSL errors when pulling images or accessing registries. When migrating from Podman 5. x to Podman 6, we recommend removing all existing data and recreating your environment from scratch.