Podman Desktop 1.18 is now available! Click here to download it!
This release brings exciting new features and improvements:
brew
. It also detects and notifies you when Podman can't bind the Docker socket.The experimental Docker Compatibility page that was introduced in v1.13 has been moved out of experimental mode. Now everything related to Docker compatibility can be found in one place. In addition, new Docker compatibility related notifications have been added to make the set up process easier and less guesswork when running into problems.
Until now, only switching Kubernetes contexts was supported in Podman Desktop. With this update, you can now switch between namespaces from within Podman Desktop without having to do anything outside the app. The selection does not modify your Kube config and is persistent across the app, so if you select a specific namespace in one place, it will be used everywhere else in Podman Desktop.
As part of our ongoing Kubernetes improvement and enhancement efforts, a new tab has been added for Kubernetes Jobs. You can now view the jobs, all in one place, with details page for each one, and have the ability to delete and view condition statuses.
The experimental status bar providers that were introduced in v1.16 have undergone some changes to make them easier to understand and use.
The new provider status icons include:
In addition, you can now choose which available providers to show by pinning or unpinning them from the status bar:
If you have any feedback or thoughts about our experimental features (or any aspect of Podman Desktop at all), feel free to let us know in the relevant experimental feature github discussion, which can be accessed from the experimental tab in the settings page, or by clicking on the comment icon in the lower right side of Podman Desktop and filling out the feedback form.
As part of the migration to svelte 5, breaking changes were introduced in the DetailsPage
and FormPage
components of the @podman-desktop/ui-svelte
package v1.18.0.
Please use {#snippet <snippet-name>()}
instead of slots in those components