Podman Desktop is a free, open source application for building and managing containers and working with Kubernetes on Windows, macOS and Linux. It gives developers a graphical view of images, running containers, pods and cluster resources, with controls for moving between those parts of a containerized application.
The desktop interface works with a container engine that executes the workloads. On Windows and macOS, Podman runs inside a Linux virtual machine. Podman Desktop can create that machine and let you assign its processors, memory and disk space, so the local execution environment can be managed alongside the applications it runs.
Container images
An image can come from a registry or from an application’s Containerfile or Dockerfile. For a build, you select the file, review the directory used as the build context and give the resulting image a name. Build arguments pass values into arguments defined in the file, while platform selection lets a build target different processor architectures.
Podman Desktop lists the resulting images with their summaries and history. You can change image names and tags, save images locally, import saved images into the engine or use an image to create a container.
Registry connections handle image distribution. Podman Desktop includes connection settings for services such as Docker Hub, Quay and GitHub, and accepts a custom registry address. Credentials allow Podman to pull private images or push images to a repository. The image’s fully qualified name identifies the registry and repository that receive it.
Running containers
Starting an image creates a container after you review its configuration. The Containers view shows the instances available on the engine and whether they are running or stopped. You can search the list, start, stop or restart an instance, export it, or remove selected containers.
Opening a container exposes more than its current status. Logs show the program’s output, inspection reveals its configuration, and a terminal lets you interact inside the running container. If the application exposes a port, the interface can open that service in a browser.
Podman pods
With the Podman engine, selected containers can become a pod. You choose the members, name the pod and check the exposed ports before creating it. The Pods view then brings together the group, its logs and the states of its individual containers. Pod controls let you start, restart, stop or delete the group.
Podman Desktop can generate a pod definition from a Podman container and display it in the Kube tab. That configuration can be copied to a YAML file and reused to create a pod on Podman or on a Kubernetes cluster. Pods can also be created from an existing Kubernetes YAML definition.
Compose
Podman Desktop also recognizes applications defined in Compose files. After Compose has been configured, you launch the file through a terminal command. The Compose engine labels the resources it creates, and Podman Desktop uses those labels to identify their application group. The Containers list displays the related instances together with a Compose suffix, preserving their association with the same multi-container application.
Kubernetes
A Kubernetes context connects Podman Desktop to a cluster. You can work with an existing environment or use integrations such as Kind and Minikube for local clusters. Selecting the context establishes the target for deploying a container or pod and managing the resulting Kubernetes resources.
The Kubernetes view handles resources beyond running pods. Deployments control application replicas, Services expose applications, and configuration and storage objects supply data and persistent storage requests. You can apply YAML files to create resources, inspect an object’s details, or edit its configuration in the Kube tab and apply the changes directly to the connected cluster. Service port forwarding provides access to a cluster service from the local computer.
Podman Desktop extensions
Podman Desktop uses extensions to connect container engines, cluster tools and additional development functions. Integrations include Docker, Compose, Kind, Minikube and Lima; individual extensions can be enabled or disabled. Its Docker compatibility settings also configure Docker commands and tools to work against the Podman engine. Developers can build extensions that add menus, commands or interface components for their own workflows.




