Containers are typically deployed in Kubernetes clusters. However, for smaller-scale use cases such as on a single-node server or during development, Kubernetes can be overkill.
Whatβs a more lightweight solution for running autonomous applications with multiple interacting containers?
In this blog, we'll dive into what Quadlets are, their benefits, and how to use them within Podman Desktop.
Podman Desktop 1.16 Release! π
Podman Desktop 1.16 is now available! Click here to download it!
This release brings exciting new features and improvements:
BootC extension 1.6 Release! π
BootC (Bootable Container) is an extension for Podman Desktop that builds bootable container disk images. Go from a standard container image to a full bootable-on-a-usb-stick OS!
You can update or install the extension via the Podman Desktop extension catalog.
This release introduces exciting new features and improvements:
Each example now includes a dedicated detail page! Click on More Details in the Examples section to view step-by-step instructions for each example.
No need to manually create a custom build config. Use our interactive build configuration creator to easily generate your own build config through a user-friendly form.
Linux support is now available for running virtual machines on generated images! Look for the new Virtual Machine (Experimental) tab or the dedicated VM launch button on the Disk Images page.
packages/backend/yarn.lock by @benoitf in #1001bootc-image-builder image by @cdrage in #1078
Podman Desktop serves as a powerful tool for managing and visualizing cloud-native applications and can interact seamlessly with a range of CNCF (Cloud Native Computing Foundation) projects.
It's an accessible platform for developers working with single-container applications, multi-container configurations with Compose files, and complex, distributed applications on Kubernetes clusters.
Podman Desktop brings together three powerful features for managing small to large-scale projects:
Minikube is a local Kubernetes development cluster which allows for an easy way to learn and develop for Kubernetes.
Minikube can be seamlessly integrated with Podman Desktop, enabling Kubernetes development workflows within Podmanβs environment. This is made possible by installing the Minikube extension, which allows creating, managing, and deploying clusters directly from the Podman Desktop.
The following video provides a complete guide from installation to cluster creation:
Backstage is an open-source platform for building developer portals, designed by Spotify. It empowers engineering teams to create customized, centralized hubs for managing and documenting their services, applications, and infrastructure. Backstageβs extensible architecture includes features for cataloging software components, organizing documentation, managing cloud resources, and tracking workflows.
A popular method for deploying Backstage is through a Helm chart. Once deployed, you can view Backstageβs services in the Kubernetes Dashboard to monitor components and ensure proper configuration:
You can also access your deployed Backstage instance by using Podman Desktop's port forwarding feature. This feature allows you to securely forward a local port to the Backstage service running on your Kubernetes cluster, making it easy to access the instance from a local browser.
Dapr (Distributed Application Runtime) is an open-source, event-driven runtime designed to help developers build resilient, stateless, and stateful applications that can run seamlessly on cloud or edge environments.
Dapr abstracts the complexities of distributed systems, offering building blocks for service invocation, state management, publish/subscribe messaging, and resource bindings, which simplify the development of microservices and cloud-native applications.
Dapr can be deployed in a local environment using Podman by following their self-hosted podman setup.
To initialize Dapr with Podman after installing the Dapr CLI, execute the following command:
$ dapr init --container-runtime podman
Once initialized, you can manage and interact with Dapr directly within Podman Desktop:
Additionally, Podman Desktop provides a "Launch Browser" button, allowing quick and convenient access to the Dapr UI for monitoring and management:
Whether youβre managing Kubernetes clusters, harnessing the power of Backstage for developer portals, or deploying microservices with Dapr, Podman Desktop provides a unified environment to streamline your workflows.
Check out the list of graduate and incubating projects to discover even more possibilities with Podman Desktop.
Podman Desktop 1.15 Release! π
Podman Desktop 1.15 is now available! Click here to download it!
This release brings exciting new features and improvements:
In the 1.15 release, we introduced a redesigned feedback form to streamline issue reporting. With our growing user base, itβs vital to provide a convenient way to submit feedback directly to GitHub via our main repository: podman-desktop/podman-desktop/issues.
While retaining our internal anonymous feedback system, this update also enables users to preview their issues on GitHub, ensuring better communication.
We now offer three distinct feedback categories:
Back in the 0.13 release, we introduced the Task Manager. With an increasing number of long-running tasks, weβve revamped it to improve usability. This updated version is available as an experimental feature!
To try it out, go to Settings > Preferences > Tasks and enable the Manager option.
Key changes include:
This year, weβve been steadily adding Kubernetes capabilities to Podman Desktop. While this effort is ongoing, version 1.15 introduces support for Kubernetes Events. These events are now available for resources like Nodes, Services, and Pods.
A frequent user request has been the ability to establish an SSH connection to a Podman machine for debugging or configuration purposes. In this release, you can now directly connect to your Podman machine from its details page.
π Weβd like to say a big thank you to everyone who helped to make Podman Desktop even better. In this release, we received pull requests from the following people:
The complete list of issues fixed in this release is available here.
Get the latest release from the Downloads section of the website and boost your development journey with Podman Desktop. Additionally, visit the GitHub repository and see how you can help us make Podman Desktop better.
KubePort component by @axel7083 in #9876utf16le ecoding in powershell call for Virtual Machine Platform detection by @dgolovin in #9594
Red Hat provides an extension to Podman Desktop, Podman AI Lab, which lets developers discover examples of applications by using large language models (LLMs), and gives them a framework to create their own AI-based applications and share them with their team.
We will discover, through this article, the different steps to create our first AI application, and to add it to the catalog of recipes of Podman AI Lab.
For our first experiment, we will work on a micro-service for the podman-desktop.io website. The micro-service would receive the search terms from the website, and would ask the model to find the best matching pages, before returning the result to the website.
If you haven't done it yet, first install Podman Desktop and its extension Podman AI Lab.
To have a better experience, it is recommended to use the GPU acceleration to serve the model. If you have such a GPU on your machine, you will need to create a Podman machine with the LibKrun provider (on MacOS). More details on the GPU support for Podman AI Lab.
At the time of writing, the GPU support is still experimental on Podman AI Lab. You will need to enable the option on the Preferences to enable it.
Podman AI Lab provides a catalog of open source models that can be used locally. You can go to the Models > Catalog page to download the model of your choice. For this article, we will use the Mistral-7B-instruct model.
Once a model is downloaded, we can test and interact with this model to try to find the best prompt for our application. For chat models, Podman AI Lab provides a Playground, so we can test different prompts and validate that the responses of the model are adequate.
Let's start a new playground (from the Models > Playgrounds menu), and send our first prompt:
Give me a list of pages in the website podman-desktop.io related to "build an image"
The model should reply with some list of pages, in a human-readable form (see the screenshot below, for the response we received).
The problem is that the response is in human-readable form, but we don't want the API to return this response as is. We want to have the name and the url of the pages, and send them to the website, so the website can display these pages with its preferred format.
For this, we can try to ask the model to reply with a structured response, with the following prompt:
Give me a list of pages in the website podman-desktop.io related to "build an image" as JSON output as an array of objects with 2 fields name and url
This time, we received a response in JSON format, which is more suitable for our needs.
We don't expect the user to ask such a precise question, and we would prefer to send to the model the exact question of the user, without modifying it in real time. To achieve this, chat models provide a system prompt feature. The system prompt can be defined at the beginning of the chat session.
Podman AI Lab supports this feature, let's restart a Playground session with the following system prompt:
Give me a list of pages in the website podman-desktop.io related to the request as JSON output as an array of objects with 2 fields name and url
Then, send the prompt build an image, to simulate a realistic search input of a user.
We can see in the screenshot below that the model still returns a response suitable for our use case.
Please note that this section was not a course on writing the best prompt, I'm sure you will find much more efficient prompts for this purpose. The purpose of this section is to demonstrate how you can iterate with Podman AI Lab to refine the prompts you want to use for your application.
Now that we have a suitable prompt to use for our application, it is time to start our application itself.
Many developers prefer to have a working example of application to start with, and Podman AI Lab provides such examples with a catalog of recipes, visible in the page AI Apps > Recipe Catalog.
Let's select the Chatbot recipe (More details link on the Chatbot card), and start it with the Mistral model (by pressing the Start button and filling the form).
Once the application is started, we can access the list of running apps in the AI Apps > Running page, and we can access the app's UI by clicking on the Open AI App link.
We can test again by typing our prompt (not the one with a system prompt, as the recipe does not support providing a system prompt), and see that the response is very similar to the one received from the playground.
Back to the recipe's details page, we can access the sources of the recipe by clicking on the Open in VSCode button, the respository's link or the link Local clone.
The entrypoint of a recipe is the file ai-lab.yaml present in the repository of the recipe.
Let's examine the content of this file (the syntax of the file is specified in this documentation) for the chatbot example.
version: v1.0
application:
type: language
name: ChatBot_Streamlit
description: Chat with a model service in a web frontend.
containers:
- name: llamacpp-server
contextdir: ../../../model_servers/llamacpp_python
containerfile: ./base/Containerfile
model-service: true
backend:
- llama-cpp
arch:
- arm64
- amd64
ports:
- 8001
image: quay.io/ai-lab/llamacpp_python:latest
- name: streamlit-chat-app
contextdir: app
containerfile: Containerfile
arch:
- arm64
- amd64
ports:
- 8501
image: quay.io/ai-lab/chatbot:latest
The file defines two containers, one for the inference server and one for the application itself.
The first container, for the inference server, is generic and can be reused for any app using a chat model.
The second one is the one we are particularly interested in. It defines how the container's image for the application is built. It points to the Containerfile used to build the image, on which we can find the source code for the app: in the app/chatbot_ui.py file.
Looking at the Python source file, we can see that the application uses the streamlit framework for the UI part, and the langchain framework for discussing with the model.
We can adapt this source code, by replacing the UI part with a framework to make the app a REST service, and keep the langchain part.
An interesting part of the source code is that the recipe does not expose to the user the system prompt, but defines one internally (You are world class technical advisor):
prompt = ChatPromptTemplate.from_messages([
("system", "You are world class technical advisor."),
MessagesPlaceholder(variable_name="history"),
("user", "{input}")
])
This is exactly what we want to do in our application, we will be able to indicate here the system prompt we have found earlier.
Adapting the source code for the purpose of our application is out of the scope of this article, let's see the result in our app repository.
As discussed in the previous section, we have replaced the streamlit part with the flask framework to create a REST API with two endpoints: one for the health check on / necessary for Podman AI Lab, and another one on /query, which will be the endpoint on which the micro-service's user will send requests.
We have also indicated our own system prompt:
prompt = ChatPromptTemplate.from_messages([
("system", """
reply in JSON format with an array of objects with 2 fields name and url
(and with no more text than the JSON output),
with a list of pages in the website https://www.podman-desktop.io related to my query
"""),
MessagesPlaceholder(variable_name="history"),
("user", "{input}")
])
To iterate during the development of our app, we can test our app locally in our host system, while using the model served by Podman AI Lab. For this, we need to start a new model service from the page Models > Services, by clicking the New Model Service, then choosing the appropriate model (Mistral-7B-instruct in our case), and specifying a port number (let's say 56625).
Then, we can run our app, by specifying through the MODEL_ENDPOINT environment variable how to access the model service.
Finally, we can send a request to this app running locally, and listening in the port 5000, and we can check in the screenshot below that the response is, as expected, a list of pages (name and url) in JSON format:
The last step is to add this application to the Podman AI Lab recipe catalog.
Podman AI Lab provides a way for a user to extend the provided catalog with its own recipes. This can be done by adding a file in a specific directory, as described in this documentation.
{
"version": "1.0",
"recipes": [
{
"id": "search-podman-desktop-io",
"description": "Search on Podman-desktop.io website",
"name": "Search Podman-desktop.io",
"repository": "https://github.com/redhat-developer/podman-desktop-demo",
"ref": "main",
"icon": "natural-language-processing",
"categories": ["natural-language-processing"],
"basedir": "ai-lab-demo/recipe",
"readme": "",
"recommended": ["hf.TheBloke.mistral-7b-instruct-v0.2.Q4_K_M"],
"backend": "llama-cpp"
}
]
}
By creating the file $HOME/.local/share/containers/podman-desktop/extensions-storage/redhat.ai-lab/user-catalog.json with the content above, you should now be able to see a new recipe Search Podman-desktop.io in the recipe catalog of Podman AI Lab, and run it as any other recipe. And, of course, you can share this file with your colleagues to share with them your latest experiment.
Today, we're thrilled to announce our application for Podman Desktop to join the Cloud Native Computing Foundation (CNCF) as a Sandbox project.This is a huge milestone for our project and our community, and we're incredibly excited for what the future holds.
Podman Desktop builds upon the innovations brought by Podman, offering a powerful yet user-friendly environment for containerized development. Podman provides a daemonless, rootless container engine that enhances security and flexibility, while Podman Desktop delivers an intuitive graphical interface for managing containers and interacting with Kubernetes. Enhanced by a plug-in system that allows developers to customize their inner loop container workflows to their needs and offers flexible extension points for other projects as well as other container engines.
The CNCF is a vital organization for the cloud-native world, supporting collaboration and driving innovation for critical projects like Kubernetes, Prometheus, and Envoy. As a CNCF project, Podman Desktop will benefit from increased visibility, a neutral home for open governance, and access to a wealth of resources and expertise. CNCF projects will take a renewed interest in collaborating with us. This move will help us grow our community, ensure the project's long-term sustainability, and accelerate its development.
Developing with containers can be complex. Podman Desktop simplifies this by providing an intuitive interface and powerful tools for building, managing, and running containers. This allows developers to focus on writing code, not wrestling with infrastructure. Why is this important? Because in today's complex world, developer productivity is paramount. By removing friction and simplifying workflows, Podman Desktop empowers developers to deliver value faster. Podman Desktop enables developers to run Kubernetes locally, mirroring their production environment. This eliminates the "works on my machine" problem and allows for early detection of configuration issues. By closing the gap between development and production, Podman Desktop reduces deployment risks and accelerates the feedback loop. This leads to higher quality software and faster release cycles.
We believe in the power of open source. Open source software fosters transparency, encourages collaboration, and drives innovation. By donating Podman Desktop to the CNCF, we're ensuring it remains open and accessible to all, fostering a vibrant community around it. The CNCF is the perfect home for Podman Desktop because it champions open source values and provides a neutral ground for collaborative development. This ensures that Podman Desktop remains vendor-neutral and driven by the needs of its users, keeping options open and avoiding vendor lock-in.
Furthermore, while the CNCF has fostered incredible innovation and many developers profit from the number of projects available through the CNCF, there's a recognized need for more developer-focused tooling. Podman Desktop fills this gap perfectly by providing a developer-centric, streamlined, and intuitive experience for containerizing, managing, and deploying cloud-native applications. Podman Desktop has a natural affinity to Kubernetes due to its design and features that seamlessly bridge the gap between local container development and Kubernetes deployments. This close relationship aligns perfectly with the CNCF's mission to drive the adoption of cloud-native technologies.
As a CNCF project, we have the opportunity to open our doors to a wider community of contributors and users. We believe that open source thrives on collaboration and diverse perspectives. By broadening our contributor base, we can accelerate innovation, improve the quality of Podman Desktop, and ensure it meets the needs of a diverse range of users.
Reporting issues: If you encounter bugs or have suggestions for improvements, you can report them on the GitHub issue tracker. Be sure to provide detailed information and steps to reproduce the issue.
Working on issues: You can browse the issue tracker and contribute by fixing bugs or implementing new features. This involves forking the repository, making changes, and submitting pull requests.
Contributing code: Beyond addressing existing issues, you can propose and contribute entirely new features or enhancements to Podman Desktop's functionality, user interface, or integrations with other tools. Learn more about how to contribute.
Contributing plug-ins: Feel like there is an integration missing? You can contribute your own plug-in functionality for Podman Desktop. Check out the guide.
Improving documentation: Clear and comprehensive documentation is essential. You can contribute by improving existing documentation, adding new guides, or creating tutorials.
Providing website contributions: The Podman Desktop website is also open source. You can contribute to its content, design, or translations.
Becoming an Adopter: If you are a happy user, weβd love to know and share the word. Consider adding yourself or your organization to the list of adopters with a pull request.
Before you start contributing, it's helpful to familiarize yourself with the project's contribution guidelines and code architecture. These resources provide valuable information on coding style, testing procedures, and the overall development process. You can also join #podman-desktop on the Kubernetes Slack to connect with other contributors and get help.
We are at KubeCon NA 2024 in Salt Lake, to officially announce this exciting news and share more about Podman Desktop and our roadmap. Stop by the Red Hat booth to say hello, contribute to the project, and help us shape the future of cloud-native development.
We're incredibly excited about this new chapter for Podman Desktop and can't wait to see what we can achieve together with the CNCF community.
Visit our website: https://podman-desktop.io/
Join our community: #podman-desktop on the Kubernetes Slack
Contribute to the project: https://github.com/podman-desktop/podman-desktop/
Read 10 Reasons Why Developers Should Consider Podman Desktop
If you're unfamiliar with BootC, it offers an impressive method for deploying applications directly to bare metal from either a single Containerfile or a pre-existing bootc-supported image.
A "bootable" image, known as a BootC container image, allows you to use a simple container image to create a full bootable operating system, whether it's a raw virtual machine image or an iso for USB installation!
This capability is ideal for a variety of uses, from a simple HTTP server to an OS powering a full-stack application.
In this tutorial, we'll deploy an OpenShift derivative called MicroShift, an edge-optimized version of OpenShift designed for single-node setups on resource-constrained configurations. Think of it as a compact version of OpenShift!
This entire process is carried out using a single Containerfile (or Dockerfile).
Before starting the tutorial, ensure you have:
First, we'll build the initial BootC container image from which we'll later create a bootable OS.
Before proceeding, download the Red Hat Authentication extension from the catalog to enable access to Red Hat registries:
Then log into your account:
Download your pull secret.
This is downloaded as pull-secret.txt. Put it in a secure location.
The Containerfile is crucial for creating the bootable image.
It's important to note that we will be providing one argument during the build and that is the PASSWORD in order to access the Virtual Machine that will be logged in via the redhat username.
We will be using the Containerfile from the MicroShift image mode GitHub documentation.
Copy the Containerfile from the above link to a new file which we will be building with Podman Desktop:
$ curl https://raw.githubusercontent.com/openshift/microshift/main/docs/config/Containerfile.bootc-rhel9 -o Containerfile
Select the Containerfile and build it within Podman Desktop.
You will need to provide:
redhat user that will be created in the Containerfile.Pass the argument as USER_PASSWD in the build page arguments.
Install the BootC Podman Desktop extension from the extensions catalog:
Now, create the bootable image from our container image!
Click the new BootC icon on the navigation bar and go to build:
Once the build is complete, you'll see a confirmation on the dashboard.
Next, select the image we built and choose an appropriate output format for testing the bootable image. RAW is a common choice for local testing with QEMU and other VM software like libvirt.
Explore various ways to test your image, using local software or cloud platforms. Here are some common steps for using the RAW output bootable image.
This guide doesn't cover all methods for running a virtual machine, but here are the most common:
When using Hyper-V, create a .vhd image with BootC:
.vhd option.When building, select the .raw option and ARM64 architecture.
Install QEMU:
$ brew install qemu
disk.raw file:$ cd ~/output
qemu command:$ qemu-system-aarch64 \
-m 8G \
-M virt \
-accel hvf \
-cpu host \
-smp 4 \
-serial mon:stdio \
-nographic \
-netdev user,id=mynet0,hostfwd=tcp::2222-:22 \
-device e1000,netdev=mynet0 \
-drive file=/opt/homebrew/share/qemu/edk2-aarch64-code.fd,format=raw,if=pflash,readonly=on \
-drive file=disk.raw,if=virtio,cache=writethrough,format=raw
With the above qemu command, a port has now been opened locally at :2222 to SSH forward to the bootable image. You can now access your virtual machine by doing the following:
$ ssh redhat@localhost -p 2222
When building, select the .raw option and AMD64 architecture.
Navigate to the directory containing your disk.raw file:
$ cd ~/output
qemu command:$ qemu-system-x86_64 \
-m 8G \
-cpu Broadwell-v4 \
-nographic \
-netdev user,id=mynet0,hostfwd=tcp::2222-:22 \
-device e1000,netdev=mynet0 \
-snapshot disk.raw
With the above qemu command, a port has now been opened locally at :2222 to SSH forward to the bootable image. You can now access your virtual machine by doing the following:
$ ssh redhat@localhost -p 2222
After you boot your virtual machine, you can now configure MicroShift as well as verify the connection.
Before proceeding with verifying OpenShift, the OpenShift pull secret must be copied over so that MicroShift can download Red Hat registry-authenticated container images.
Below we will copy the OpenShift secret you had previously downloaded to the virtual machine.
Download your OpenShift pull secret which is downloaded as pull-secret.txt
Use scp to copy over to the virtual machine:
$ scp -P 2222 pull-secret.txt redhat@localhost:~/
$ ssh redhat@localhost -p 2222
/etc/crio/openshift-pull-secret:$ sudo mv pull-secret.txt /etc/crio/openshift-pull-secret
microshift service:$ sudo systemctl restart microshift
Below we will SSH into the virtual machine and confirm that MicroShift is deploying Pods correctly:
$ ssh redhat@localhost -p 2222
kubeconfig file to ~/.kube/config:$ mkdir -p ~/.kube
$ sudo cp /var/lib/microshift/resources/kubeadmin/kubeconfig ~/.kube/config
$ sudo chown redhat ~/.kube/config
oc or kubectl:$ kubectl get pods -A
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system csi-snapshot-controller-856bb8b9bc-9n7lj 1/1 Running 1 3d23h
kube-system csi-snapshot-webhook-7c64d4d4d7-98v6l 1/1 Running 1 3d23h
openshift-dns dns-default-n2td4 2/2 Running 2 3d23h
openshift-dns node-resolver-7cslg 1/1 Running 1 3d23h
openshift-ingress router-default-7cbc67954b-nqqc6 1/1 Running 1 3d23h
openshift-ovn-kubernetes ovnkube-master-zcqw5 4/4 Running 5 3d23h
openshift-ovn-kubernetes ovnkube-node-crnn9 1/1 Running 2 3d23h
openshift-service-ca service-ca-6799f567-k7lsc 1/1 Running 1 3d23h
Alternatively, you can copy the MicroShift configuration file to your local machine and test it remotely on Podman Desktop.
.kube directory if it does not exist already:$ mkdir ~/.kube
kubeconfig file to a local configuration file:Within MicroShift, a kubeconfig file is automatically created at /var/lib/microshift/resources/kubeadmin/kubeconfig.
Copy the file over to your local system:
scp -P 2222 redhat@localhost:/var/lib/microshift/resources/kubeadmin/kubeconfig ~/config
If you already have a ~/.kube/config, copy the contents of config to the ~/.kube/config file.
Podman Desktop will automatically detect your .kube/config file.
Note: You may need to modify your .kube/config file to reflect the correct domain or IP address of your cluster.
By default, storage configuration requires an LVM partition and LVMS storage manager will not be deployed. This is due to a limitation when building a RAW image. An alternative non-local storage solution is required to use OpenShift artifacts with storage capabilities. The feature to add LVM support is tracked in this pull request.
This tutorial provided a step-by-step guide on deploying a bootable MicroShift image using Podman Desktop and the BootC extension. By leveraging tools such as BootC and Podman, we've streamlined the process of creating a lightweight, yet fully functional, OpenShift environment suitable for single-node edge computing scenarios.
Thank you for following along, and happy deploying!
Podman Desktop 1.14 Release! π
Podman Desktop 1.14 is now available. Click here to download it!
This release includes:
Extensions are a powerful tool to customize and extend the functionality of Podman Desktop. Whether you want to add new container management features, streamline current workflows, or create custom UI elements specific to your tech stack, building extensions allows you to tailor the Podman Desktop experience to your specific needs.
In this guide, we'll introduce how you can build your own Podman Desktop extension, with links to detailed documentation that covers each part of the process.
Extensions are abundant in Podman Desktop and can be found in the Extensions -> Catalog section.
Each extension expands on Podman Desktop, such as providing Kubernetes development clusters with Minikube or even analyzing your image layers.
Below is an example of the layers explorer extension and how it integrates into Podman Desktop:
The first step in creating your extension is setting up the project environment. To learn how to configure the project and add basic components, check out the Templates for creating an extension guide, which walks you through initializing your project from an official template.
One of the most common tasks when creating an extension is adding a user interface. Whether itβs adding buttons, panels, or icons, UI components help make your extension more interactive and accessible. Adding a UI component is totally optional and an extension can be ran without UI components. Learn more about this in the Adding UI components documentation, where youβll find instructions on creating and integrating components into the applicationβs UI.
Icons are a great way to make your extension more visually unique. You can learn how to add and style custom icons by following the Adding icons documentation.
Below is an example of how the bootc extension added icons to the image list within Podman Desktop:
Extensions often integrate with existing menus and navigation to offer users easy access to new commands and features. If you want to add items to the context menu, explore the Menu configuration documentation, which explains how to add commands to menus and control when they are displayed using When Clauses.
Below is an example of how the bootc extension added a new menu command to image list:
Commands are the backbone of most extensions, allowing users to interact with the application and trigger specific actions.
If you need to define and register custom commands, the Commands guide will show you how to create commands that respond to user actions or input, and tie them into your extensionβs workflow.
You can also configure these commands to appear in different contexts. Check out the When clause Contexts documentation to learn more about restricting commands to specific scenarios.
Commands are heavily influenced by VS Code commands and can be configured similarly. See our commands guide for more information.
Creating a smooth onboarding experience is essential to help users get started with your extension. This includes steps for CLI binary installations or other initial setup values.
You can provide guidance, tutorials, or initial setup steps using the Onboarding workflow guide.
Below is an example of how the built-in compose extension adds onboarding for the compose CLI binary installation:
Once youβve built your components and commands, you may want to setup configuration settings for advanced usage of your extension.
The Configuration documentation outlines the configuration file structure and how to link everything together to use user-specific values.
Publishing enables users to install your extension, you can compile your extension into a container image for users to easily consume. Follow the Publishing guide to learn how to distribute your extension.
Creating an extension opens up endless possibilities to customize Podman Desktop to your specific needs.
It is also easy to package and publish your extension for others to use.
Have fun exploring our documentation on how to create an extension and happy coding!
Podman Desktop 1.13 Release! π
Podman Desktop 1.13 is now available. Click here to download it!
This release includes:
The integration of Podman Desktop with Kubernetes helps you to run your application on a Kubernetes cluster, such as Kind or Minikube.
This blog covers the following aspects:
With this blog, you will build a containerized application that uses:
To do so, you can pull the relevant images from the quay.io registry.
Go to the Images component page.
Click Pull.
Start the first container:
quay.io/podman-desktop-demo/podify-demo-backend.
redis-server.
Start the second container:
Enter the image name to pull from a registry. For example, quay.io/podman-desktop-demo/podify-demo-frontend.
Click Pull image and then Done.
Click the Run Image icon corresponding to the new image added.
Enter the container name python-app.
If the default port is already in use, you can specify a different port in the Port mapping field.
Select the Networking tab and enter hostname as redis-server and IP address as 10.88.0.2 to enable communication with the Redis server.
You can find the IP address in the Inspect tab of the redis-server Container Details page.
Click Start Container.
Click the Logs tab to view that the application is running on port 5000.
Click the Open browser icon on the right side of the page.
View the running front-end application.
You can use both the containers to create a pod. This way both the front-end and back end container applications can share resources, such as storage and network.
Pod creation with existing containers
Alternative: Pod creation with Kubernetes YAML
You can generate a Kubernetes manifest for any existing pod or container and use it to create a local Kubernetes YAML file. Then, you can customize that file and create a pod from it.
At the time of pod creation, you can select a runtime to indicate whether you want to run the pod on a Podman engine or a Kubernetes cluster. Based on the selection, you get to see the newly created pod running in that environment on the Pods component page.
The following procedure creates a pod that runs on a Podman engine.
Podman container engine.After creating the pod, set up a local Kubernetes cluster to deploy the pod.
You can set up a local Kubernetes cluster. Once the cluster is connected and running, you can deploy your application on it.
Based on your preference, use the Kind or Minikube extension:
Once a kubernetes cluster is created, you can view a running control plane node and a running Kubernetes service on the Kubernetes component page. The page also shows that the cluster is connected.
You can deploy the application pod to a Kubernetes cluster that has an active connection and access it through a service. Also, any container that is part of a pod is deployable to a Kubernetes cluster.
Select your Kubernetes context.
Go to the Pods component page.
Click the overflow menu icon corresponding to the pod.
Select the Deploy to Kubernetes option from the dropdown list.
Select the checkbox to expose the service locally using the ingress controller.
When you configure custom port mapping while running an image, you get the option to select an Ingress host port from the dropdown list.
Otherwise, you do not see the option.
Click Deploy and then Done.
Go the Kubernetes component page.
Perform the following steps:
my-pod-5000.
my-pod.
Use the Apply YAML button to directly apply a Kubernetes YAML file to create a resource.
Podman Desktop 1.12 Release! π
Podman Desktop 1.12 is now available. Click here to download it!
This release includes:
libkrun is now a selectable provider type to allow GPU passthrough enablement.
Red Hat provides a tool called Image Builder that allows developers to build their own custom image of RHEL in a variety of formats. Recently, Image Builder added WSL as a target, enabling you to run RHEL on Windows as a WSL distribution.
This article details the steps and actions required to build and run your RHEL WSL image.
The purpose of this article is to describe the options needed for the RHEL WSL distribution so that it can be used as a Podman machine.
To use the RHEL WSL image as a Podman machine, ensure that the following packages are installed:
Luckily, all but the last package are available from the pre-configured RHEL 9 repositories. The last package (systemd-networkd) is available from the EPEL 9 repository and will need to be configured when building the image.
Navigate to image builder
On the upper right menu, enable the Preview mode.
Click Add blueprint to open the Create image dialog wizard.
On the Image output page, select the following:
.tar.gz).On the Register page, select Automatically register and enable advanced capabilities.
On the OpenSCAP page, as it is not supported for WSL images, click Next.
On the File system configuration page, select Recommended: Use automatic partitioning.
On the Content page, complete the following steps to add additional packages to your image:
On the Repository snapshot step:
On the Custom repositories step:
Click on the Create and manage repositories here link. This will open a new tab
Click Add repositories now
Click Add repositories
On the Add custom repositories page, select the following:
https://dl.fedoraproject.org/pub/epel/9/Everything/x86_64/https://dl.fedoraproject.org/pub/epel/RPM-GPG-KEY-EPEL-9Close the tab and switch back to the previous one
Click Next
On the Additional packages step:
On the First boot script configuration page:
On the Details page:
On the Review page:
The image is being built. Once the build is finished, the download link will be available. Click on the Download (.tar.gz) link and save the downloaded file to one of your local folders.
Launch Podman Desktop and go to the Settings -> Resources page:
On the Podman provider, click on Create new ...
On the Create Podman machine page, click the Browse button for the Image Path field and select the file downloaded from Image Builder.
Click on the Create button: the machine will be created and started. After a short time, the operation status should be reported.
Go to the Images page and pull the httpd image
Click on Done
Start the image by clicking on the Run image icon
Once the container is started, the Apache server can be accessed on localhost:9000
Podman Desktop 1.11 Release! π
This release introduces:
Podman Desktop 1.11 is now available. Click here to download it!
Podman Desktop 1.10 Release! π
This release introduces:
Podman Desktop 1.10 is now available. Click here to download it!
Podman Desktop 1.9 Release! π
This release introduces: π¦ a splash of innovation, a wave of excitement, and an ocean of possibilities!
Podman Desktop 1.9 is now available. Click here to download it!
Podman Desktop 1.8 Release! π
We've got a new release with a ton of seal appeal! This release introduces:
Podman Desktop 1.8 is now available. Click here to download it!
π¦ Podman 4.9.3 includes key fixes for stability and reliability issues reported by our users - especially if you are using Apple silicon architecture. If you've been floundering we highly recommend updating!
Progressively introduced in past releases as an experimental feature, we're ready to expand our capabilities to help developers transition from containers to Kubernetes. In this release we are introducing a new set of features that enable the developers to work with more Kubernetes resources, offering more granular and interactive control over your applications.
Now available in π¦ Podman Desktop is a new Kubernetes Explorer with the ability to work with Deployments, Services, Ingresses, and Routes, in addition to the existing support for Pods. For each of those resources, π¦ Podman Desktop provides real-time information about the status of resources on the cluster. From the top right of this overview page you can also click Apply YAML to create or update resources on the cluster similar to 'kubectl apply -f', and see the current connection status.
Just like with local containers or images, you can click for more details on Summary, Inspect, and Kube (YAML) pages.
See a problem? You can edit and apply changes direct from the Kube tab.
π¦ Podman Desktop continues to bridge the gap and discrepancies to empower developers working with containers with efficient workflows to target Kubernetes from their local workstation. This is all in addition to some of the great features already available:
Configuring and setting up a local environment is now easier with the introduction of a new wizard-based onboarding flow. In this flow developers can pick the different tools that they need, and π¦ Podman Desktop will walk them through the configuration and setup of each of these tools.
The global onboarding flow allows developers to configure Podman, Compose, and kubectl (needed for working with Kind and Minikube or remote Kubernetes environments). This makes the transition to π¦ Podman Desktop becomes simpler, as any needed dependencies are automatically configured.
In this release, we've added a Learning Center on the Dashboardm enabling developers to discover, learn, and expand their knowledge on related topics to containerization. These guides are handy and easily accessible, and cover topics from learning how to containerize an existing application to discovering the latest features of π¦ Podman Desktop and how to best use them.
We continued spent a lot of time adding new extension API to give upcoming extensions more capabilites and even better integration into π¦ Podman Desktop:
We've added over 40 features this release, here are some other highlights:
We've also made some significant progress on implementing light mode:
We squashed a lot of bugs this release, including the following:
Along with this new version of π¦ Podman Desktop the documentation has had the following improvements:
π Weβd like to say a big thank you to everyone who helped make π¦ Podman Desktop even better. In this release we received pull requests from the following people:
The complete list of issues fixed in this release is available here.
Get the latest release from the Downloads section of the website and boost your development journey with Podman Desktop. Additionally, visit the GitHub repository and see how you can help us make Podman Desktop better.
Weβre honored to announce that Podman Desktop has been recognized with the prestigious 2024 DEVIES Award in the category of Containers & Kubernetes. This award is a testimony to the effectiveness of the Podman Desktop team and greater open-source community's efforts to help developers. Podman Desktop increases developer container workflow efficiency as well as provides an easy transition of applications from containers to Kubernetes, the leading open-source container orchestration platform.
βWhile Podman Desktop only went into general availability last year, the community response has been very impressive and incredibly gratifying. We are extremely proud to receive this outstanding recognition which celebrates passion, commitment and innovation for shaping the future of container development backed by the vibrant open-source standards that Red Hat supports. β said StΓ©van Le Meur, Product Manager on the Podman Desktop team.
The DEVIES Awards, presented by DeveloperWeek, recognize the most innovative and impactful tools, platforms, and technologies in the software development community. Podman Desktop's win as the best innovation in Containers & Kubernetes highlights its significant impact on the industry and its role in revolutionizing the way developers build, ship, and run their applications. DEVIES Award winners are selected from hundreds of nominees by the independent, industry-leading DevNetwork Advisory Board.
Weβre excited to be receiving this award on stage at DeveloperWeek 2024, happening on February 21-23, 2024, in Oakland, CA and February 27-29, 2024 (Virtually). In addition, Red Hat developer advocate Cedric Clyburn will be presenting a session on Podman Desktop, titled βGoing from Containers, to Pods, to Kubernetes β Help for Your Developer Environments!β, with a full presentation on Podman, a demonstration of the Podman Desktop experience, and a multi-tier application going from containers, to pods, to finally Kubernetes!
Finally, it would be seal-y to not include and acknowledge that this award was earned by the entire Podman Desktop community of contributors! We also thank the DevNetwork Advisory Board and DeveloperWeek for this honorable award, and for the opportunity to share Podman Desktop's innovations with the greater developer community.
Seamlessly run WebAssembly/Wasm binaries on macOS and Windows
You might have heard excitement recently about Wasm and WASI. Imagine a world where you can effortlessly run Wasm binaries and distribute them using Open Container Initiative (OCI) container images β a singular image deployable across multiple architectures.
Though the concept seemed straightforward, accomplishing this task proved to be quite challenging, particularly on macOS and Windows. The complexity comes from the additional virtual machine running Linux. This machine needs all of the dependencies and prerequisites correctly setup.
The wait is over. Our blog post unveils the solution, guiding you through the process of enabling Wasm workloads on both macOS and Windows.
Podman Desktop 1.7 Release! π
We've got a new release with a ton of seal appeal! This release introduces:
Podman Desktop 1.7 is now available. Click here to download it!
π¦ Podman 4.9 includes key fixes for stability and reliability issues reported by our users. If you've been floundering we highly recommend updating!
If you are on a Mac M3, we are aware of a critical issue in Podman and expect to update very soon to pick up this fix: #21353 - Update to new QEMU (based on #1990 - QEMU issue on M3). If you are hitting this problem there is a workaround here and there.
We have spent a lot of time this release adding new extension API to give upcoming extensions more capability and even better integration into π¦ Podman Desktop. We have added support for full page webviews, image badges, icons, a navigation API, and API access to more function from the container engine:
We have been working the last couple months to expand our support for Kubernetes. This support isn't ready to set sail yet, but if you're working with a Kubernetes cluster we'd love to start getting your feedback on the direction!
To 'break the seal' and try it out, go to Settings > Preferences > Kubernetes, and enable the Experimental option:
This will add three new items to the main navigation, allowing you to view Deployments, Services, and Ingress & Routes:
In this release you can click on deployments and services to view additional details (like the Summary, Inspect, and YAML tabs), but not yet for ingresses or routes.
We hope things go swimmingly for you, but please open Github issues to let us know what else you'd like to see.
When building an image you can now chose which platform(s) to build the image for:
We've upgraded the Pods view to use the same table component as images and volumes. This allowing sorting and better column scaling:
Having trouble and want a fresh start? The Troubleshooting page has switched to tabs and there is an option to purge your existing install:
We added over 40 features this release, here are some of the other highlights:
We squashed over 25 bugs this release, including the following:
Labels property #5632Along with this new version of π¦ Podman Desktop the documentation has had the following improvements:
π Weβd like to say a big thank you to everyone (yes, that means you, Anders!) who helped make π¦ Podman Desktop even better. In this release we received pull requests from the following people:
The complete list of issues fixed in this release is available here.
Get the latest release from the Downloads section of the website and boost your development journey with Podman Desktop. Additionally, visit the GitHub repository and see how you can help us make Podman Desktop better.
In this blog post we will learn how take a multi-container Compose application and use it within Podman Desktop.
podman compose up.Compose is a specification for defining and running multi-container Docker applications. With pose, you use a YAML file to configure your applicationβs services, networks, and volumes. This allows you to capture in a single file the entire configuration necessary to run a set of interconnected containers as an application. For example, if you have an application that requires a web server, a database, and a caching service, you can define these components and their relationships in your Compose file.
To use the Compose YAML, you can use a specification implementation such as podman compose and docker compose.
If you do not have Compose installed, let's go through the onboarding process to install the Compose implementation binary:
Confirm that you are able to run podman compose:
podman compose
Run compose workloads via an external provider such as docker-compose or podman-compose
Description:
This command is a thin wrapper around an external compose provider such as docker-compose or podman-compose. This means that podman compose is executing another tool that implements the compose functionality but sets up the environment in a way to let the compose provider communicate transparently with the local Podman socket. The specified options as well the command and argument are passed directly to the compose provider.
...
Our example application is located at github.com/redhat-developer/podman-desktop-demo.
We will use git clone so we can build the Go binary web application:
git clone https://github.com/redhat-developer/podman-desktop-demo
cd podman-desktop-demo/guestbook-compose
Run podman compose up -d to start the application:
podman compose up -d
>>>> Executing external compose provider "/usr/local/bin/docker-compose". Please refer to the documentation for details. <<<<
[+] Running 3/3
β Container redis-replica Started 0.0s
β Container web Started 0.0s
β Container redis-leader Started 0.0s
Within Podman Desktop, you can now see that all three containers are up and operational.
Click the "Open Browser" button to view the web application:
Within the Guestbook web application, you can:
/env: View the container's environment variables./info: View information about the Redis cluster.
Using Podman Desktop, you can also access the container's terminal directly from the GUI and modify the database.
Click "Open Terminal" to access the redis-leader terminal:
Modify the database as if you are doing database administration:
redis-cli within the container to access the Redis database.LPUSH guestbook "Hello World!" and you will see your web application update in real-time.DEL guestbook and you will see that your database drops the guestbook key and clears the database.
Changes will reflect in real-time on the guestbook.
You can further modify the database and see the changes propagate to the Redis replicas.
For example, view the logs of the redis-replica, and you will notice that there are periodic database synchronizations as well as reads to the database:
A quick overview of how the architecture works in this multi-container scenario:
redis-leader and redis-replica on port 6379.There is a set of environment variables that the web application can modify in the Compose application:
REDIS_LEADER: The default is redis-leader.REDIS_REPLICAS: The default is redis-replica. Can be comma-separated, such as redis-replica-1,redis-replica-2.REDIS_PORT: The default is 6379.SERVER_PORT: The default is 8080.Want to scale more replicas? This can be achieved by adding an environment variable to your compose.yaml and duplicating your redis-replica entry.
Modify your compose.yaml as follows:
services:
redis-leader:
container_name: redis-leader
image: redis:latest
ports:
- '6379'
redis-replica:
container_name: redis-replica
image: redis:latest
ports:
- '6379'
command: redis-server --replicaof redis-leader 6379
redis-replica-2:
container_name: redis-replica-2
image: redis:latest
ports:
- '6379'
command: redis-server --replicaof redis-leader 6379
web:
container_name: web
build: ./web
environment:
- REDIS_REPLICAS=redis-replica1,redis-replica2
ports:
- '8080:8080'
Run podman compose up -d again to ensure the new container has been added and the new environment variable has propagated:
podman compose up -d
>>>> Executing external compose provider "/usr/local/bin/docker-compose". Please refer to the documentation for details. <<<<
[+] Running 4/4
β Container redis-replica-2 Started 0.0s
β Container redis-leader Running 0.0s
β Container web Started 0.0s
β Container redis-replica Running 0.0s
Podman Desktop 1.6 Release! π
This release introduces:
Podman Desktop 1.6 is now available. Click here to download it!
For developers who need to run Kubernetes locally and reproduce an environment close to production for development and experimentation purposes, Podman Desktop allows users to easily set up that environment on a local machine. There are two extensions providing the capability to configure a open source Kubernetes cluster locally, you can either choose between Kind or Minikube.
The Minikube extension allows you to install Minikube on your workstation and also to setup a Kubernetes cluster locally running in a container! Yes, you read that correctly - in a container similar to how Kind works. The advantage is that it's lighter and faster to start. With Minikube, one of the advantage, is that you can build your images locally with Podman and get them automatically available in your local Kubernetes cluster - which will speed up your turnarounds when you want to test your application. If you want to learn more this, read the following blog post.
Configuring and managing your setup is getting easier with the addition of a new section in the Settings to manage command-line tools. In Podman Desktop, extensions can list command-line tools that are helpful to their users or required to make use of the installed extensions.
There are two command-line tools within Podman Desktop that allows you to view whether they are installed or require an update:
From the settings you can see the command-line tools that are installed, and you can see the version - and when a new version is available, you'll get a small notification to allow you easily update to that version.
We are introducing a new screen available from the Settings which allows you to easily manage your Kubernetes contexts. Podman Desktop was already providing the handy context switcher available from the status bar, but when you get to work with multiple Kubernetes environments, it's not uncommon to end with a big and long list of Kubernetes contexts.
The new Kubernetes Contexts screen allows you to easily see all your registered Kubernetes contexts. You can use the screen to clean up your registered contexts, or set the current (default) context.
A Podman machine is a virtual environment specifically designed to run Podman containers on Mac and Windows. It allows users to manage and operate containerized applications in an isolated and controlled setting. When creating a Podman machine, you configure its settings: memory, CPU(s) and disk size.
We've received the feedback regarding the ability to reconfigure your Podman machine on the go. This is now possible for macOS users, and particularly useful when you start with an environment and need to scale it up based on new needs and containers you would like to run in your Podman environment.
You'll notice we improved the sliders to configure the Podman machine's options - and also introduced a way to enter numeric values directly.
Being able to quickly identify the containers and the pods you are working with is critical when you are iterating on the development of your application. For this reason, we added filters at the top of the lists of Containers and Pods that allow you to easily view all the containers/pods, only those that are running, or only those that are stopped.
The lists of Volumes and Images have improved and are now have the ability to be sorted by the criteria of your choice. You can for example filter images by their size - which can be convenient when you want to clean up your environment.
Podman Desktop is able to work with multiple providers: it could work with multiple container engines and multiple Kubernetes environments too. In order to make it easier to identify the containers and the pods and differentiate them depending on which environment they are running onto, we are introducing a new environment column in the list of Containers and Pods to display a badge.
The list of Pods has been refined to provide easier visibility and access to the containers running within each of them. Each of the containers now have one dot and you can hover each dot to display the info about the container - and if you click on it you'll be able to access the details of the container.
The π¦ Podman Desktop extension API received many improvements, including:
/events if disconnected #4809Coming with this new version of π¦ Podman Desktop, the documentation has been getting the following improvements:
π Weβd like to say a big thank you to everyone who helped to make π¦ Podman Desktop even better. In this release we received pull requests from the following people:
afbjorklund in fix: add website target for running vale, docs: the main lima command is limactl, docs: lima provider cleanup after the merge, docs: make it possible for lima to provide both, fix: don't link to k8s cluster server, feat: show the k8s namespace, docs: show location of lima podman socket
axel7083 in refactoring: item formats from renderer/preferences in separate files, feat: adding optional abort controller to dockerode api
ReadingShades in docs: Added the environment variable set commands of the common windows terminal emulators
jannikbertram in chore: add close button to troubleshooting and help page
singodiyashubham87 in fix: header line height issue on website
itecompro in docs: remove duplicate text from windows troubleshooting
ecrookshanks-rh in fix: added text beside icon for create pods
The complete list of issues fixed in this release is available here.
Get the latest release from the Downloads section of the website and boost your development journey with Podman Desktop. Additionally, visit the GitHub repository and see how you can help us make Podman Desktop better.
As developers we constantly improve and refine our applications. One of the challenges we face is quickly iterating when working with container images and kubernetes deployments/pods.
For example, when we want to try a new image in a kubernetes pod, this image needs to be available on a private/public registry or on the nodes of the kubernetes cluster.
Sometimes we need to call extra commands such as kind load docker-image or minikube cache add <image> or publish the image first to a 3rd party registry.
You'll agree that trying out a new image in a Kubernetes pod should be as seamless as building the image itself.
In this blog post, we will explore the best practice for streamlining the image iteration process in Kubernetes with Podman Desktop.
Podman Desktop 1.5 Release! π
With this release of Podman Desktop, we're introducing a new onboarding feature that we hope will earn your π¦ seal of approval! But wait... there's so much more!
Podman Desktop 1.5 is now available. Click here to download it!
We are introducing a new feature providing guided flows for the initial setup of specific π¦ Podman Desktop extensions. Release 1.5 features two new onboarding flows: Podman and Compose.
To start the Podman onboarding flow, you can start from the dashboard notification by clicking the "Set up" button:
Visit Settings > Resources screen and click the Compose "Setup ..." button in order to start Compose onboarding:
A new, search-driven command palette is now available to enable quick access to various commands available across π¦ Podman Desktop. You can try this new tool out by hitting the F1 key. #4081 && #3979
Kubernetes pods now offer a more comprehensive set of information under the "Summary" tab, including networking, volumes, environment variables, and other key metadata.
When creating a container from the Images list, there's now an option to provide an environment file to set env variables for the new container. #4026 && #4025
The user experience for enabling or disabling Docker compatibility is improved, with a new entry in the Settings > Preferences screen that includes contextual guidance. #4093
The user experience around state changes for containers, pods, and other objects in the UI is improved, with clear status messages and improved animated visual indicator of state changes. #4056
The π¦ Podman Desktop extension API received many improvements, including:
In addition to pushing and listing image from an extension, it's now possible to pull images from a π¦ Podman Desktop extension #4155
The π¦ Podman Desktop extension API has been enhanced with both the ability to list images & networks and the ability to create containers & networks. #4172
π¦ Podman Desktop extensions now have a consistent way to run administrative tasks. #4049
Extensions now have the ability to register a custom Kubernetes config generator. #3970
The ability of extensions to add commands to UI menus has been extended; previously for action menus it was only available in the Image list screen. It is now possible for extensions to add commands to the action menus of items listed on the Containers list screen as well. #3947 & #3963
Extensions have gained the ability to contribute menu items in the UI based on specific conditions. #3959
Enhanced logic for displaying or hiding properties listed under the Settings > Preferences screens is now available. #4159
New support for adding spin animations to icons is now available. #4188
There is a new indeterminate progress bar type available for the task manager; this is meant for providing limited status for actions whose APIs do not provide detailed status information. #4016
For authenticating as admin to perform administrative tasks, π¦ Podman Desktop now provides touchID support for macOS. #4050
Support for connecting to interactive terminals for containers via tty was added. #3900
It's now more clear which container/pod providers will autostart when π¦ Podman Desktop starts. Previously autostart had both a global and a per-provider setting. It has been simplified by removing the global setting. #3840
The "Working with containers" section of the documentation has been reworked and improved. #3951
The disable registry command was not blocking subsequent pulls from disabled registries. This has been corrected. #4183
Some users behind network proxies were unable to complete workflow involving the download of online resources. The mechanism for fetching these resources has been fixed to be proxy compatible to address this issue. #3994
The status of pods running in Kubernetes that are undergoing the deletion process is now accurately reflected in the π¦ Podman Desktop UI. #3877
The image details page always listed the image as being "not used" even when it was. This has been corrected. #3985
Previously, deleting a specific image tag would cause all tags with the same Image ID to be deleted. This has been fixed so only the selected image tag will be deleted. #3837
Could not view the pod details for some remote Kubernetes cluster pods due to an encoding error. #4371
Error logs were being tracked separately from the actions they applied to. This has been addressed for kind cluster creation failure #4427 and Compose installation failure #4407.
For Linux users, π¦ Podman Desktop previously did not appear under the "Development" menu when installed via Flatpak; it appeared under "Utilities." π¦ Podman Desktop now appears under the "Development" menu. #3911
Podman Machine names are no longer prefixed with the "Podman Machine" string. #3878
The initial action state of pods and containers was being displayed as "STARTING" regardless of actual state; this has been corrected. #3889
Resizing the application window no longer makes the last lines of a container's terminal invisible. #3993
An issue with incorrect terminal behavior in response to long lines in the terminal attached to a container has been resolved. #3955
A spacing issue on the run image form has been corrected. #4089
The "podify" icon & button on the Containers list was unusually large in release 1.4. That regression has been corrected in this release. #4122
An error in the instructions for Windows users on migrating from Docker has been corrected. #4157
π Weβd like to say a big thank you to everyone who helped to make π¦ Podman Desktop even better. In this release we received pull requests from the following people:
afbjorklund in #4373 - docs: fix broken links and add lima onboarding, #4372 - docs: clear up lima column on containers page, #4091 - fix: avoid errors with unexpected JSON input, #4098 - docs: Lima onboarding details, and #3854 - fix: check if machine init rootful flag supported
axel7083 in #4061 - feat: adding task progress for kind, #3970 - feat: extension can register custom kube generator, #3959 - feat: add when property to extensions menus, #4016 - feat: indeterminate progress bar, #3963 - fix: ContainerList propagating containers in ComposeActions and PodActions, and #3947 - feat: extend menus capabilities
foxydeveloper in #4157 - docs: Correct windows instructions for migrating from docker
harsh-solanki21 in #4162 - fix: Removed fullstop from summary
shelar1423 in #4221 - chore: document property setting in EXTENSIONS.md
We have a discussion board topic where we have posted known issues with this release. If you run into problems, please check this list before filing a bug - if we already have an issue open for it, it saves you the time and trouble of filing, and there may be a workaround posted in the issue.
The complete list of issues fixed in this release is available here.
Get the latest release from the Downloads section of the website and boost your development journey with Podman Desktop. Additionally, visit the GitHub repository and see how you can help us make Podman Desktop better.
Podman Desktop 1.4 Release! π
This is essentially a bug-fix release to fix various issues in UI, but as usual we also added a few new features.
Volumes pagebash if available.Podman Desktop 1.4 is now available. Click here to download it!
When starting a new container, you can now map a port range between host and container. If the range is not valid between host and container, an error is raised.
When a terminal is opened for a container, it can now be reused after you switched to another part of the Podman Desktop UI.
The Volumes tab now has a Create volume button. The Create volume UI has a single field for the volume name.
When a terminal is opened for a container, if bash is available within the container, it will be used. Otherwise, sh will be used.
π Weβd like to say a big thank you to everyone who helped to make Podman Desktop even better.
A warm welcome to @tomgoren, @Julian, @Gelob and @cedricclyburn who made their first contribution to the project in this release.
The complete list of issues fixed in this release is available here.
Get the latest release from the Downloads section of the website and boost your development journey with Podman Desktop. Additionally, visit the GitHub repository and see how you can help us make Podman Desktop better.
Podman Desktop 1.3 Release! π
This is essentially a bug-fix release to fix various issues in UI, extension engine and featured extensions, but as usual we also added a few new features.
Node's container image field can be used to specify the Kubernetes version used for the control-planedPodman Desktop 1.3 is now available. Click here to download it!
When clicking on the group of containers, you can now view the logs of the entire group of compose containers and don't need to open log for every component individually.
Certain VPN setups or other specialized networking configs will block traffic from the virtual WSL networking device, resulting in the podman WSL backend from being unable to contact systems on the VPN, and potentially losing internet access altogether. The new switch allows you to create a podman VM machine configured to work correctly in mentioned above networking environments.
Compose group Summary tab shows all containers in the group and let you navigate to Details page for specific container.
Compose group Inspect tab shows an array of "container inspect" from docker / podman.
Deploy to kubernetes in compose actions #3299βA button to deploy to kubernetes added to Compose group.
Generate Kube in Compose actions and Kube tab in compose details #3253βGenerate Kube item added to Compose actions and "Kube" tab is now available in Compose details view.
An Extension pack introduced in Extension engine is a way to declare set of extensions to install them all at once.
Extensions now can customize icons for list elements using when clause.
If you click on the arrow icon next to a resource name it will open up a details page (similarly to how clicking on a container in the container list opens up a details page).
Node's container image field added to Create a Kind cluster form #3508βThe new Node's container image field can be used to specify the Kubernetes version used for the control-planed.
Podman Desktop now loads the containers in the backend as described in the vm section of extension descriptor the same way as Docker Desktop does.
This is the initial implementation for the onboarding feature. It only covers a simple onboarding for podman. Check system requirements -> install podman -> yay! Done!
π Weβd like to say a big thank you to everyone who helped to make Podman Desktop even better.
A warm welcome to @rostalan and @axel7083 who made their first contribution to the project in this release.
The complete list of issues fixed in this release is available here.
Get the latest release from the Downloads section of the website and boost your development journey with Podman Desktop. Additionally, visit the GitHub repository and see how you can help us make Podman Desktop better.
Podman Desktop 1.2 Release! π
We're excited to announce the release of Podman Desktop version 1.2.0! This release includes many new features (Kubernetes, Compose and extension support!), bug fixes, and improvements to enhance your container management experience. Here's a summary of the key changes in this release:
open podman-desktop:extension/redhat.openshift-localPodman Desktop 1.2 is now available. Click here to download it!
In the last month we've been addind support for more Compose features. Before you were only able to control a group of containers if they were in a Pod. Now we have added the ability to control a group of Compose containers. You can now start, stop, delete and restart a group of containers launched by either docker-compose or podman-compose.
Stay tuned as we add even more features to Compose! If you have any feedback or feature requests, feel free to open an issue or start a discussion on GitHub.
With Kubernetes context on the status bar, you can switch from one context to another in just a couple of clicks. Easily switch to a different cluster all together. If there are multiple contexts available, you can now click and pick which one to use.
Deployed an image but now you need to rename it / add a new tag? Podman Desktop allows you to edit an image now. Thanks to an awesome contributor @tuckerrc who added the new feature.
Developing an extension for Podman Desktop? Want to view the logs of Podman Desktop as well as ping your container connection? We now have a troubleshooting page!
Click on the lightbulb button on the bottom right to access the page.
Podman Desktop now supports protocol handling when using the terminal! Want to access your favourite extension directly from a script or the terminal? If you type in open podman-desktop:extension/redhat.openshift-local in the terminal, Podman Desktop will automatically load up to the correct extension.
π Weβd like to say a big thank you to everyone who helped to make Podman Desktop even better.
A big shoutout to @afbjorklund, @tuckerrc and @evanshortiss who contributed to this release!
The complete list of issues fixed in this release is available here and here.
Get the latest release from the Downloads section of the website and boost your development journey with Podman Desktop. Additionally, visit the GitHub repository and see how you can help us make Podman Desktop better.
Podman Desktop 1.1 Release! π
This is primarily a bug-fix release to fix a few important issues, but we've managed to squeeze in a few enhancements along the way.
Podman Desktop 1.1 is now available. Click here to download it!
Podman Desktop 1.0 Release! π
We still have many things planned, but with a little polish and a few more bug fixes we felt we've reached a level of maturity and it is now time to declare our 1.0 release.
Thank you to everyone who has been with us on this journey so far! Please keep the feedback coming!
Podman Desktop 1.0 is now available. Click here to download it!
Podman Desktop 0.15 - Cleanliness is next to Podliness!
It has only been two weeks since our last release, but we really wanted to complete a few scenarios, fix a few bugs, and show off several design updates and UI improvements that we have been working on.
Podman Desktop 0.15 is now available. Click here to download it!
In this blog post you will learn to use Podman Desktop to run the Kubernetes documentation example: Deploying PHP Guestbook application with Redis.
On the agenda:
Podman Desktop 0.14 - Our Kind-est release yet!
We have been working on a Kind extension for a while now, and decided it is time to promote it into a release just in time for KubeCon and CloudNativeCon Europe!
We're especially excited about releasing Kind because it finally shows the full purpose of Podman Desktop: not just local container engines, but Kubernetes too. More importantly, providing tools that allow you to manage both environments and seamlessly move between them.
Some of these features were available in development mode over the last few releases, but since they are now in the release build, we will do a full roundup and talk about all the Kind features.
Podman Desktop 0.14 is now available. Click here to download it!
This release note covers Podman Desktop 0.13 release changes.
Podman Desktop 0.13 is now available. Click here to download it!
The 5 things to know being a Docker user by using Podman Desktop:
rootless mode or containers without root privileges.
This release note covers Podman Desktop 0.12 release changes.
Podman Desktop 0.12 is now available. Click here to download it!
This release note covers Podman Desktop 0.11 release changes.
Podman Desktop 0.11 is now available. Click here to download it!
This release note covers Podman Desktop 0.10 release changes.
Podman Desktop 0.10 is now available. Click here to download it!
GitHub announced last week that Codespaces is available for everyone and it includes free minutes.
Let see how we can use a Development Container having all the tools to build and run Podman Desktop. The Development Container works locally using Visual Studio Code but in this blog post we will see how it works directly with a simple click from GitHub.
The challenges are to run a desktop tool (Podman Desktop) and running a container engine (Podman) inside this Development Container without using too many memory !