Red Hat recently announced the release of the new version of your project "Podman Desktop 1.2", which includes many new features, bug fixes, and improvements to the container management experience.
For those who don't know about Podman Desktop, you should know that this allows developers without knowledge systems administration build, run, test, and publish microservices and applications developed for insulation systems From containers on your workstation before deploying them to production environments.
Integration with Kubernetes and OpenShift platforms is supported, as well as using various runtimes to run containers, such as Podman Engine , Podman Lima, crc, and Docker Engine.
About Podman Desktop
The environment on the developer's local system can mirror the configuration of the production environment in which finished applications run (among other things, multi-node Kubernetes clusters and OpenShift environments can be simulated on the local system).
Besides that, provides the ability to create plugins to support release engines of additional containers, Kubernetes providers, and toolkits. For example, plugins are available to run a single node OpenShift Local cluster locally and connect to the OpenShift Developer Sandbox cloud service.
Also provides tools for managing container images, work with pods and partitions, create images from Containerfile and Dockerfile, connect to containers via terminal, download images from OCI container registries and publish your images to them, manage resources available in containers (memory, CPU, storage).
Of the main key features Podman Desktop highlights the following:
- Cross-platform, can be installed and run on Windows, macOS, and Linux
- Configure and install via Podman, Kind, Red Hat OpenShift Local, Developer Sandbox for Red Hat OpenShift
- Allows you to create, run, manage, and debug containers and pods
- You can run pods with or without Kubernetes
- It has an integrated terminal to access the containers
- Allows management of multiple container engines
- Compatible with Docker Compose
- Lets run Kubernetes YAML
- Generate Kubernetes YAML from Pods
- Podify and Kubify: Turn containers into pods and Kubernetes
- VPN and proxy settings
- Image registration management
- Configure multiple OCI records
- Air-Gapped Installation
- Bridge between local and remote environments
- Enables remotely managed services locally
- Ability to extend container engines or Kubernetes providers
- Extension points to add actions, menus, settings and enrich the user interface with specific capabilities
Main new features of Podman Desktop 1.2
The new version that is presented of Podman Desktop 1.2 implements few changes, since there are more corrections implemented, but it is worth mentioning that the new changes are quite important to be implemented in a new release.
And it is that, for example, it stands out that added buttons to start, stop, delete and restart container groups that run on Docker Compose and Podman Compose, since previously only one group of containers could be controlled.
Another of the changes that stands out is the ability to switch between different Kubernetes contexts with just a couple of clicks, since it is enough to open the drop-down list to make the change. The widget has been added to the system tray widget.
In addition to this, it is also worth noting that a button to quickly rename images, with which it is now easier to change the name or add a label to an image.
On the other hand, it is noted that added protocol controller support that allow you load extensions directly from a script or terminal. For example, to load the openshift-local extension, you can specify "podman-desktop:extension/redhat.openshift-local".
Of the other changes that stand out of this new version:
- Added page for troubleshooting.
- Provided an option to skip certificate verification when uploading a registry image.
- Added ability to add insecure registry/skip certificate verification
- Icon contribution support
- Added a warning dialog that the virtual machine has a low memory limit
- Propose indexed name for new pod
- Added reset button after enable/disable mac os support
- Added auxiliary constants related to the environment
- Allow entry point and cmd when starting container
Finally, If you are interested in knowing more about it, you can check the details in the following link
As for interested in trying or installing Podman Desktop on their system, they should know that ready-made builds are offered for Linux, Windows and macOS.