{ "version": "https://jsonfeed.org/version/1", "title": "Podman Desktop Blog", "home_page_url": "https://podman-desktop.io/blog", "description": "Podman Desktop Blog", "items": [ { "id": "https://podman-desktop.io/blog/podman-desktop-release-1.26", "content_html": "

Podman Desktop 1.26 Release! πŸŽ‰

\n

\"podman-desktop-hero-1.26\"

\n

Podman Desktop 1.26 is now available. Click here to download it!

\n

This release brings exciting new features and improvements:

\n\n

Release details​

\n

Host certificate sync to Podman VMs​

\n

Working behind a corporate proxy or pulling from internal registries? You can now sync your local certificates to running Podman VMs directly from the command palette. Open the command palette with F1 and run the Podman: Synchronize certificates to all VMs command.

\n\n

Extension authentication access control​

\n

Extensions can no longer silently access your authentication sessions. When an extension tries to use an existing account or requests a new sign-in, you'll now see a prompt to allow or deny it. This prevents extensions from accessing credentials without your knowledge.

\n\"Extension\"Extension\n\"Extension\"Extension\n

Pull image workflow improvements​

\n

Users can now cancel image pulls in progress and take immediate actions after successful pulls. A new cancel button allows stopping long-running pulls, and new 'Open Details' and 'Run...' buttons appear after pulling an image, eliminating the need to navigate to the Images page to find and work with newly pulled images.

\n\"Pull\"Pull\n\"Pull\"Pull\n

Environment-based filtering​

\n

In Podman Desktop, you can manage different container environments: Docker, Podman, Apple Container for instance. If you are using Podman Desktop in this situation, you will see a new environment combo box on resource management pages, allowing you to filter containers, pods, images, volumes, and networks by their specific environment. If you have only one environment, this filter will be hidden to keep the screen simple.

\n\"Environment\"Environment\n\"Environment\"Environment\n\"Environment\"Environment\n

Additional managed configuration settings for extensions​

\n

Building on the managed configuration support introduced in 1.23, administrators can now control extension management through configuration files. Two new settings are available:

\n\n

These settings can be deployed organization-wide through the managed configuration file, giving IT teams tighter control over which extensions are available in their deployment.

\n

Troubleshooting section in Settings​

\n

A new troubleshooting entry has been added to the settings menu, providing quicker access to diagnostic tools and information. This helps users find and resolve issues without having to search through multiple pages.

\n\"Troubleshooting\"Troubleshooting\n

Confirmation dialog for connection deletion​

\n

Deleting a provider connection now displays a confirmation dialog, preventing accidental removal. This safeguard ensures users must explicitly confirm before a connection is removed, reducing the risk of unintended data loss.

\n\"Confirmation\"Confirmation\n
\n

Community thank you​

\n

πŸŽ‰ We'd like to say a big thank you to everyone who helped to make Podman Desktop even better. In this\nrelease we received pull requests from the following people:

\n\n
\n

Community meeting​

\n

If you would like to discuss any of the new features, issues or other topics, please join us at the monthly community meeting that takes place every 4th Thursday of the month. Here are the meeting details.

\n
\n

Final notes​

\n

The complete list of issues fixed in this release is available here and here.

\n

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.

\n

Detailed release changelog​

\n

feat​

\n\n

fix​

\n\n

chore​

\n\n

test​

\n\n

refactor​

\n\n

docs​

\n\n

ci​

\n", "url": "https://podman-desktop.io/blog/podman-desktop-release-1.26", "title": "Podman Desktop 1.26 Release", "summary": "Podman Desktop 1.26 has been released!", "date_modified": "2026-03-16T00:00:00.000Z", "author": { "name": "Brian Mahabir", "url": "https://github.com/bmahabirbu" }, "tags": [ "podman-desktop", "release", "kubernetes", "openshift" ] }, { "id": "https://podman-desktop.io/blog/podman-desktop-release-1.25", "content_html": "

Podman Desktop 1.25 Release! πŸŽ‰

\n

\"podman-desktop-hero-1.25\"

\n

Podman Desktop 1.25 is now available. Click here to download it!

\n

This release brings exciting new features and improvements:

\n\n

Release details​

\n

Navigation history controls (back/forward)​

\n

Moving through the app is now faster with dedicated back/forward controls. Use the toolbar arrows, jump via the command palette, or rely on shortcuts to quickly return to previous views and re-open recently visited pages.

\n

Keyboard shortcuts:

\n\n\"Navigation\"Navigation\n\"Navigation\"Navigation\n

Advanced network creation tab​

\n

Creating networks is now more flexible with a new advanced tab that exposes additional configuration options directly in the UI. Previously, you only set the network name and subnet. The advanced tab now adds:

\n\n

For full details on these options, see the podman network create documentation.

\n\"Advanced\"Advanced\n

New and improved Kubernetes capabilities​

\n

The enhanced Kubernetes features are now enabled by default, providing better stability and full Kubernetes API support for a more reliable experience. The legacy Kubernetes mode will be removed in an upcoming release, so now is the time to switch and provide feedback if you encounter any issues. You can still temporarily revert to the previous mode in Settings if needed.

\n\"Experimental\"Experimental\n

Kube play is now cancellable​

\n

Long-running Kube Play operations can now be cancelled. The cancel button remains enabled while a Kube Play run is in progress, so you can stop it at any time, and the UI provides feedback after the cancellation completes.

\n\"Kube\"Kube\n\"Kube\"Kube\n

Windows Podman installer update​

\n

Podman Desktop now uses a single MSI installer on Windows that supports both user-scope (no admin) and machine-scope installs. When updating, Podman Desktop will remove the legacy installer and migrate you to the new MSI; your containers, images, machines, and other data are preserved.

\n\"Uninstalling\"Uninstalling\n\"Installing\"Installing\n
\n

Community thank you​

\n

πŸŽ‰ We’d like to say a big thank you to everyone who helped to make Podman Desktop even better. In this\nrelease we received pull requests from the following people:

\n\n
\n

Community meeting​

\n

If you would like to discuss any of the new features, issues or other topics, please join us at the monthly community meeting that takes place every 4th Thursday of the month. Here are the meeting details.

\n
\n

Final notes​

\n

The complete list of issues fixed in this release is available here.

\n

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.

\n

Detailed release changelog​

\n

feat​

\n\n

fix​

\n\n

chore​

\n\n

test​

\n\n

ci​

\n\n

refactor​

\n\n

docs​

\n", "url": "https://podman-desktop.io/blog/podman-desktop-release-1.25", "title": "Podman Desktop 1.25 Release", "summary": "Podman Desktop 1.25 has been released!", "date_modified": "2026-01-19T00:00:00.000Z", "author": { "name": "Marcel Bertagnini", "url": "https://github.com/marskubex" }, "tags": [ "podman-desktop", "release", "kubernetes", "openshift" ] }, { "id": "https://podman-desktop.io/blog/podman-desktop-2025-journey", "content_html": "

A Year of Growth and Gratitude​

\n

Welcome to the journey of Podman Desktop in 2025, a year that marked incredible growth, deeper integrations, and continued community collaboration.

\n

This year Podman Desktop closed 1,669 issues, merged 2,814 pull requests, and welcomed 28 new contributors, with even more activity happening across extension repositories.

\n

It’s been almost a year since Podman Desktop became a CNCF Sandbox Project (November 2024) and what a journey it’s been! From passing **three million downloads** to introducing new extensions, integrations and platform support, the project has seen remarkable progress, driven by passionate contributors and an engaged community.

\n

This blog takes you through some of the key highlights of 2025.

\n

A Fresh Start in January​

\n

We kicked off the year strong with the Podman Desktop 1.16 release, setting the tone for an exciting year ahead.

\n

This release introduced a new Experimental section in Settings, giving users visibility into features under active development and linking them directly to community discussions.

\n

Highlights included:​

\n\n

Beyond the core app, the BootC extension gained traction, enabling workflows that turn containers into bootable images.

\n

A great start to a year where the ecosystem began expanding beyond just the main application.

\n

The Spring Push (March – May)​

\n

Spring brought rapid iteration across releases 1.17, 1.18, and 1.19 continuing Podman Desktop’s rhythm of monthly improvements.

\n

Key highlights:​

\n\n

Along with addition and updates to the extension catalog

\n

This phase showcased Podman Desktop’s versatility, evolving into a platform for container, Kubernetes, and AI development.

\n

Summer Growth (July – August)​

\n

Mid-year releases v1.20 and v1.21 focused on usability improvements and developer convenience.

\n

Highlights:​

\n\n

These updates reflected increasing maturity, subtle but meaningful refinements that improved everyday workflows.

\n

Broadening Horizons (September)​

\n

September was a milestone month!

\n\n

A month to remember - platform expansion, stability improvements, and community celebration all at once.

\n

Heading into Fall (October)​

\n

October brought Hacktoberfest 2025, along with new contributors and excitement.

\n

v1.22 launched with user-focused enhancements:

\n\n

At this point, Podman Desktop was clearly maturing into a cross-platform, enterprise-ready tool.

\n

Smooth Refinements with Big Upgrades (November)​

\n

v1.23.1 delivered a balanced set of polished and powerful new capabilities:

\n\n

A clean, steady November release that unlocked more power under the hood.

\n

πŸŽ‰ Community Milestones​

\n\n

Both milestones reflect a thriving community and growing trust in Podman Desktop’s direction.

\n

Capping Off the Year: Release 1.24​

\n

The final release of the year, v1.24 wrapped up 2025 with UI enhancements and improved extension reliability, setting the foundation for the next phase of project growth.

\n

These milestones highlight one thing: Podman Desktop has become a global, fast-growing, community-powered project.

\n

Looking Ahead​

\n

2025 was a defining year for Podman Desktop - showcasing the strength of open-source collaboration.

\n

From new features and platform support to crossing 3 million downloads and welcoming new contributors, this year reflected tremendous community momentum.

\n

As we step into 2026, we look forward to expanding integrations, growing the extension ecosystem, and making Podman Desktop the most accessible and open developer tool for container and Kubernetes workflows.

\n

A heartfelt thank you to the Podman Desktop Team, contributors, and users worldwide for shaping the project.

\n

Here’s to more containers, more creativity, and more collaboration ahead! πŸš€

", "url": "https://podman-desktop.io/blog/podman-desktop-2025-journey", "title": "The Journey of Podman Desktop in 2025", "summary": "The Journey of Podman Desktop in 2025 post CNCF sandbox project.", "date_modified": "2025-12-22T00:00:00.000Z", "author": { "name": "Rujuta Shinde", "url": "https://github.com/rujutashinde" }, "tags": [ "podman-desktop", "community" ] }, { "id": "https://podman-desktop.io/blog/podman-desktop-release-1.24", "content_html": "

Podman Desktop 1.24 Release! πŸŽ‰

\n

\"podman-desktop-hero-1.24\"

\n

Podman Desktop 1.24 is now available. Click here to download it!

\n

This release brings exciting new features and improvements:

\n\n

Release details​

\n

Enterprise-managed default registries and mirrors​

\n

Enterprises often use a set of specific registries as well as mirrors for security and performance. Administrators can now preconfigure default container registries and mirrors across their organization's deployment of Podman Desktop.\nThis simplifies management by directing image pulls through internal registry mirrors or blocking access to specific registries, ensuring compliance and approved workflows.\nA specific configuration file will need to be configured, see the documentation here: Configuring default registries and mirrors.

\n

Remote Podman connections visibility​

\n

When dealing with multiple connections (e.g., Podman Remote), clearly identifying the source of your resources is crucial. The UI now enhances visibility by including the connection name in resource lists. For example, in the container list, the Environment column now clearly displays the Podman connection name, making it significantly easier to differentiate and manage resources across various remote container engines and endpoints.

\n\"Containers\"Containers\n\"Multiple\"Multiple\n

Select build targets in Containerfile​

\n

Building images with multiple targets in your Containerfile is now simpler. On the Build Image page, Podman Desktop now detects automatically the available stages, and a new dropdown menu lets you select the desired build target. This feature is equivalent to the --target option in the Podman CLI and simplifies complex multi-stage builds.

\n\"Dropdown\"Dropdown\n

Podman kube play YAML deployment enhanced with 'replace' option​

\n

For users applying YAML files via Podman Kube Play (https://docs.podman.io/en/v5.5.1/markdown/podman-kube-play.1.html), support for the replace option has been added. This offers more flexibility when updating resources, allowing for smoother deployments and modifications.

\n\"Podman\"Podman\n

New task manager is now the default​

\n

Discover the redesigned task manager, now the default experience in Podman Desktop. This update offers a more intuitive and efficient way to monitor and manage all your ongoing tasks, replacing the older Legacy Task Manager. You can access the new Task Manager by clicking on the bell icon in the bottom navigation bar. You'll find a streamlined interface that provides clearer insights into task status, progress, and historical information, making it easier than ever to keep track of your operations and quickly address any issues.

\n\"New\"New\n

Performance improvement for Podman version check​

\n

This version of Podman Desktop delivers improved performance and reduced resource consumption. We've implemented a caching mechanism for version checks. This enhancement significantly reduces background operations, leading to a faster, more responsive application experience and freeing up system resources for your other critical tasks.

\n
\n

Community thank you​

\n

πŸŽ‰ We’d like to say a big thank you to everyone who helped to make Podman Desktop even better. In this\nrelease we received pull requests from the following people:

\n\n
\n

Final notes​

\n

The complete list of issues fixed in this release is available here.

\n

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.

\n

Detailed release changelog​

\n

feat​

\n\n

fix​

\n\n

chore​

\n\n

docs​

\n\n

test​

\n\n

refactor​

\n", "url": "https://podman-desktop.io/blog/podman-desktop-release-1.24", "title": "Podman Desktop 1.24 Release", "summary": "Podman Desktop 1.24 has been released!", "date_modified": "2025-12-04T00:00:00.000Z", "author": { "name": "Simon Rey", "url": "https://github.com/simonrey1" }, "tags": [ "podman-desktop", "release", "kubernetes", "openshift" ] }, { "id": "https://podman-desktop.io/blog/2025/11/20/boost-your-performance-with-search-bar", "content_html": "

We rolled out a brand-new Search Bar in Podman Desktop 1.22, giving users a faster way to navigate and discover content. With the 1.23 update, we’ve made it even better, adding smart improvements and handy features!

\n

Search Bar​

\n

The Search Bar (previously known as the Command Palette) is a powerful, keyboard-first feature that brings everything in Podman Desktop just a few keystrokes away. Located directly in the title bar, it provides unified access to commands, documentation, and navigation across your entire workspace.

\n\n

Enabling the Feature​

\n

To enable the Search Bar:

\n
    \n
  1. Navigate to Settings > Preferences > Appearance.
    2. \n
  2. Find Search Bar in the experimental features section.
    3. \n
  3. Enable it to see the search button appear in your title bar.
    4. \n
\n\"Search\"Search\n
\n
\n

Once enabled, the traditional title text is replaced with a compact search button, maximizing your workspace while keeping powerful functionality at your fingertips.

\n

Four Search Modes​

\n

The Search Bar offers four distinct modes, each optimized for different tasks:

\n

1. All (Cmd/Ctrl + Shift + P)​

\n

The default mode searches across everything - commands, documentation, containers, images, pods, and navigation pages. Perfect when you know what you want but aren't sure where to find it.

\n

2. Commands (F1 or type >)​

\n

Execute any available command directly. Simply type to filter through available commands and press Enter to execute. This mode supports command enablement and context, showing only currently available commands.

\n\"Commands\"Commands\n
\n
\n
note

You can add custom commands to this list by creating a custom extension.

\n

3. Documentation (Cmd/Ctrl + K)​

\n

Quickly search through Podman Desktop's documentation. Find help articles, guides, and references without leaving the application. Each result shows the category and description to help you find exactly what you need.

\n

4. Go To (Cmd/Ctrl + F)​

\n

Navigate instantly to any resource in your environment:

\n\n\"Go\"Go\n

Keyboard Navigation​

\n

The Search Bar is designed for maximum efficiency:

\n\n

All interactions are keyboard-driven, meaning you can accomplish complex tasks without ever touching your mouse.

\n

Why Use the Search Bar?​

\n\n

Try It Today​

\n

Enable the Search Bar in your Podman Desktop settings and experience a faster, more efficient workflow. We'd love to hear your feedback in our GitHub Discussion.

\n

Happy containerizing! πŸš€

", "url": "https://podman-desktop.io/blog/2025/11/20/boost-your-performance-with-search-bar", "title": "Leverage your productivity using the Search Bar", "summary": "Boost your performance with Search Bar component", "date_modified": "2025-11-20T00:00:00.000Z", "author": { "name": "EvΕΎen Gasta", "url": "https://github.com/gastoner" }, "tags": [ "podman-desktop", "features" ] }, { "id": "https://podman-desktop.io/blog/podman-desktop-release-1.23", "content_html": "

Podman Desktop 1.23 Release! πŸŽ‰

\n

\"podman-desktop-hero-1.23\"

\n

Podman Desktop 1.23 is now available. Click here to download it!

\n

This release brings exciting new features and improvements:

\n\n
\n

Release details​

\n

Podman network support​

\n

This release introduces a dedicated network page that brings Podman network management directly into Podman Desktop's UI. Previously, managing networks required using the command-line interface, but now you can handle all your networking needs through the new network page.

\n

The network page provides comprehensive visibility into your container networks, displaying essential information including network IDs, names, drivers, and their associated container engine environments.

\n

This feature is particularly valuable when working with complex multi-container applications that require isolated network environments, or when you need to configure custom network settings (such as DNS) for your containers.

\n

Seet he podman network command for more information.

\n\"Podman\"Podman\n\"Podman\"Podman\n

Customizable columns and dashboard sections​

\n

The new layout manager feature allows users to customize their dashboard sections and table columns to match their workflow preferences. Users can now reorder dashboard sections, show or hide specific table columns, and tailor their view to display only the most relevant information for their tasks.

\n\"Customizable\"Customizable\n\"Customizable\"Customizable\n

Enhanced search​

\n

The search bar has been enhanced with algorithmic text highlighting, quick navigation to application sections, and the ability to search for Podman resources (containers, images, pods, volumes) directly. The search bar now provides a command palette-like experience for faster navigation throughout the application.

\n

Share your thoughts on this component on our GitHub discussion.

\n\"Enhanced\"Enhanced\n

Added rootless or rootful indicator to Podman machines​

\n

Podman can run with or without root privileges, in Podman Desktop we received feedback that this nuance was not displayed in the UI, leading sometimes to some issues!

\n

We've listened! We thank those who have used our built-in feedback functionality and submitted feedback.

\n

To address this aspect following user feedback we added an indicator inside the Settings > Resources page to properly display if a machine is rootless or not.

\n

A visual indicator now shows whether each Podman machine is running in rootless or rootful mode in the resources section. This helps users quickly identify the execution mode of their machines, making it easier to diagnose permission-related issues and follow security best practices.

\n

See how you can enable/disable root privileges by editing your Podman machine.

\n\"Rootless\"Rootless\n

Update Podman to v5.7.0​

\n

Updated the Podman engine to version 5.7.0. This update fixes one critical bug CVE-2025-52881 as well as adding multiple features and bug fixes. Such as adding enhanced security support for the remote Podman client and podman system service API server, which now supports encrypting connections with TLS and mTLS, including client authentication by certificate; the podman system connection add command has been updated to use this capability when creating connections to TCP sockets.

\n

Check out the Podman 5.7 release.

\n

Support for a managed configuration​

\n

Podman Desktop now supports managed configuration. Users can add a β€œmanaged-by” configuration file to enforce specific settings. This allows system administrators to apply configurations from a global system file. With this release, administrators can deploy a managed settings file to a predefined system location, enabling centralized control over Podman Desktop configurations across an entire organization.

\n

Check out more details in this demo done by @cdrage:

\n\n

Created Docker context for Podman machine​

\n

Podman Desktop now automatically creates a Docker context for each registered Podman machine, improving interoperability with Docker tooling. Each context is prefixed with podman- and derived from the Podman machine name, allowing users to seamlessly switch between contexts using the standard docker context use command.

\n\"Docker\"Docker\n
\n

Community thank you​

\n

πŸŽ‰ We’d like to say a big thank you to everyone who helped to make Podman Desktop even better. In this\nrelease we received pull requests from the following people:

\n\n
\n

Final notes​

\n

The complete list of issues fixed in this release is available here.

\n

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.

\n

Detailed release changelog​

\n

feat πŸ’‘β€‹

\n\n

fix πŸ”¨β€‹

\n\n

chore βœ…β€‹

\n\n

test πŸš¦β€‹

\n\n

docs πŸ“–β€‹

\n\n

refactor πŸ”„β€‹

\n", "url": "https://podman-desktop.io/blog/podman-desktop-release-1.23", "title": "Podman Desktop 1.23 Release", "summary": "Podman Desktop 1.23 has been released!", "date_modified": "2025-11-19T00:00:00.000Z", "author": { "name": "EvΕΎen Gasta", "url": "https://github.com/gastoner" }, "tags": [ "podman-desktop", "release", "managed-by", "docker", "containers" ] }, { "id": "https://podman-desktop.io/blog/podman-desktop-release-1.22", "content_html": "

Podman Desktop 1.22 Release! πŸŽ‰

\n

\"podman-desktop-fall-1.22\"

\n

Podman Desktop 1.22 is now available. Click here to download it!

\n

This release introduces exciting new features, improvements and bug fixes:

\n\n
\n

Release details​

\n

Explore Features Section on the Dashboard​

\n

The new Explore Features section on the Podman Desktop Dashboard helps you quickly\ndiscover and use key features, accelerating your onboarding experience.\nFrom this intuitive section, you can easily:

\n\n\"Explore\"Explore\n

Switching Podman Machines Between Rootless and Rootful (macOS and Windows Only)​

\n

Podman allows containers to run in rootful (privileged) or rootless (non-privileged) modes,\nbalancing security, flexibility, and system access. Now you can toggle an existing Podman\nmachine between these modes using a simple β€œRun with root privileges” switch in the UI,\neliminating the need to recreate the machine.

\n\"Switching\"Switching\n

Apply Kubernetes YAML Files with Ease​

\n

The new 'Create File from Scratch' option on the Play Kubernetes YAML page provides an integrated\ntext editor where you can write YAML from scratch or paste existing YAML artifacts. With syntax\nhighlighting and validation, the editor ensures accurate YAML creation and reduces deployment\nerrors. To use it, navigate to the Play Kubernetes YAML page, select 'Create File from Scratch',\npaste or write your YAML, and click 'Apply' to deploy to your cluster. This enhancement simplifies\nKubernetes resource management, enabling developers to deploy pods, services, or other resources\nefficiently in both local and remote cluster environments.

\n\"Apply\"Apply\n

Transparent Proxy Support​

\n

To ensure applications work seamlessly with transparent proxies, developers must configure\nthe client environment appropriately. This typically involves adding the transparent proxy’s\nCA certificate to the system’s certificate store. Podman Desktop now leverages these CA\ncertificates for HTTPS requests, eliminating the Self signed certificate in certificate chain error when downloading CLI tools or interacting with services outside the local\nnetwork. This enhancement simplifies workflows in enterprise environments with transparent\nproxies, ensuring smooth access to external resources and streamlined CLI tool management.

\n

Include arm64 Podman Installer for Windows​

\n

Starting with Podman v5.5, native ARM64 binaries are available for Windows, enabling better\nperformance and compatibility on ARM-based devices. Podman Desktop now includes both ARM64\nand AMD64 Podman installers, automatically selecting the appropriate version based on your\nsystem architecture. This enhancement ensures a seamless setup experience for Windows users\non modern ARM64 devices.

\n

Podman Desktop Main Window Display Issue on Linux with Wayland​

\n

A known bug #14387\nin Podman Desktop may prevent the main window from displaying after start on Linux systems\nrunning Wayland, due to a regression issue #48430 in Electron where the ready-to-show event fails to trigger correctly.\nAs a workaround, users running binaries directly can set the environment variable\nXDG_SESSION_TYPE=x11 in the same command line (e.g., XDG_SESSION_TYPE=x11 podman-desktop)\nto force the application to use the XWayland (X11 backend) within a Wayland session, ensuring\nproper window rendering. This is necessary because the user environment may already have\nXDG_SESSION_TYPE set to wayland. This workaround is not required for Flatpak packages, as\nXDG_SESSION_TYPE=x11 is automatically added during Flatpak execution,\nmaking them unaffected by this regression.

\n
\n

Community Thank You​

\n

πŸŽ‰ We’d like to say a big thank you to everyone who helped to make Podman Desktop even better.

\n

We received pull requests from the following new contributors:

\n\n

We worked closely with the following contributors to resolve the reported issue:

\n\n
\n

Final Notes​

\n

The complete list of issues fixed in this release is available in the 1.22.0 milestone.

\n

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.

\n

Detailed Release Changelog​

\n

feat​

\n\n

fix​

\n\n

chore​

\n\n

test​

\n\n

refactor​

\n\n

docs​

\n", "url": "https://podman-desktop.io/blog/podman-desktop-release-1.22", "title": "Podman Desktop 1.22 Release", "summary": "Podman Desktop 1.22 has been released!", "date_modified": "2025-10-03T00:00:00.000Z", "author": { "name": "Denis Golovin", "url": "https://github.com/cdrage" }, "tags": [ "podman-desktop", "release", "kubernetes", "openshift" ] }, { "id": "https://podman-desktop.io/blog/hacktoberfest-2025", "content_html": "

October is here and Hacktoberfest is back! It’s the perfect opportunity to sharpen your skills, explore open source, and contribute to Podman Desktop β€” an open source tool designed to simplify working with containers and Kubernetes from your local machine.

\n

Why Contribute to Podman Desktop?​

\n

Podman Desktop is a CNCF sandbox project and has already grown into a thriving open source community with over 3 million downloads worldwide. By contributing, you’re not only helping shape a successful, widely used project, but also joining a community of developers building tools that benefit peers and the broader ecosystem.

\n

Podman Desktop is built with developers in mind. Designed by developers, for developers !!\nIt’s a cross-platform tool that helps streamline container workflows, offering features like:

\n\n

Whether you’re fixing a bug, enhancing the UI, or creating a new extension, your contributions will help shape the next generation of container tooling.

\n

Contribution Areas​

\n

Here are some ways developers can get involved:

\n\n

How to Get Started​

\n
    \n
  1. Explore our GitHub repositories for issues labeled hacktoberfest. Additional issues are available across projects like Extension: Kubernetes Dashboard
    2. \n
  2. Join our community channels for guidance and collaboration.
    3. \n
  3. Fork, code, and submit your PR. Once merged, your work counts toward Hacktoberfest!
    4. \n
\n

Learn more about Hacktoberfest Participation.

\n

Let’s Build Together​

\n

Every contribution, whether big or small, makes Podman Desktop stronger for developers everywhere. Hacktoberfest is your chance to get involved, expand your skills, and make an impact.

\n

πŸ‘‰ Start here:

\n\n

This Hacktoberfest, let’s build better container workflows together. πŸ’»πŸ”₯

", "url": "https://podman-desktop.io/blog/hacktoberfest-2025", "title": "Hacktoberfest 2025! - Contribute to Podman Desktop", "summary": "Contribute to Podman Desktop this Hacktoberfest!", "date_modified": "2025-09-30T00:00:00.000Z", "author": { "name": "Rujuta Shinde", "url": "https://github.com/rujutashinde" }, "tags": [ "podman-desktop", "hacktoberfest", "community" ] }, { "id": "https://podman-desktop.io/blog/3-million", "content_html": "

\"Banner

\n

Wooohooo!!​

\n

We are extremely excited to share that Podman Desktop just crossed 3,000,000 downloads! This is a huge step for the project and we are incredibly thankful for how each of you has helped! This milestone belongs to you. You file issues, suggest features, build extensions, teach teammates, and nudge us to make the day-to-day better. Thank you for helping turn an idea into a tool people rely on.

\n

To celebrate this milestone, and thank you, we built a small surprise:\nhttps://3m.podman-desktop.io

\n

We are grateful for all the feedback we have been receiving, here is just a short collection:

\n\n

We read every comment. Yes, even the spicy ones. That feedback shapes our roadmap and helps us focus on the work that makes the biggest difference.

\n

Here are other noteworthy milestones we’ve reached in our quest to help developers work with containers and Kubernetes.

\n

Podman Desktop is now an official CNCF Sandbox Project​

\n

Last year, we proudly contributed Podman Desktop to the Cloud Native Computing Foundation (CNCF), and we were accepted into the CNCF Sandbox on January 21, 2025. πŸŽ‰

\n

This milestone highlights our commitment to building open, community-driven tools that empower developers to seamlessly work with containers and Kubernetes. Joining the CNCF Sandbox is just the beginning. Reaching this 3 million downloads milestone shows the need to build a vibrant cloud‑native ecosystem and collaborate with the community to take Podman Desktop even further.

\n

Highlights from the past year​

\n\n

Enterprise adoption of Podman Desktop​

\n

In recent months, we’ve seen more and more enterprises adopting Podman Desktop and making it part of critical developer workflows. To highlight this, we wanted to share a recent note we received:

\n
\n

In 2023, our company studied the possible solutions to run containers on our engineers’ laptop in the most efficient way. We judged that our best bet was to migrate our thousands of engineers to Podman Desktop. That was a brave move but we believed Podman Desktop was the most promising solution. We did not know how quickly it would become the best solution of all and how right that decision would be!

\n

We migrated most engineers in 2023 and did the last mile at the beginning of 2024. Podman Desktop evolved at an insane pace. It improved release after release. And it still does. It quickly became a rock solid solution with more and more useful features to discover every month!

\n

On top of that, Podman Desktop is a Community solution which allows us to have a very healthy relationship with the contributors of the project.

\n

I am happy to hear that Podman Desktop reached 3M downloads. This means more and more people realise how good this software is. Thank you Podman Desktop. Special thanks to all the project’s contributors!

\n

Fabrice Pipart, Amadeus

\n
\n

New here? Grab the latest build​

\n\n

From all of us on the Podman Desktop team, thank you for trusting us with your workflow and for helping us get better with every release. If you haven't tried Podman Desktop in a while, grab the latest build and let us know what you think. If you are already a daily user, we would love to hear what is working and what is not, so we can make the next million downloads even more useful.

", "url": "https://podman-desktop.io/blog/3-million", "title": "3,000,000 downloads. Thank you", "summary": "We reached 3,000,000 Downloads of Podman Desktop. Let's celebrate.", "date_modified": "2025-09-22T00:00:00.000Z", "author": { "name": "Matt Demyttenaere", "url": "https://github.com/firewall" }, "tags": [ "podman-desktop", "3-million", "downloads", "celebrate" ] }, { "id": "https://podman-desktop.io/blog/apple-container-extension", "content_html": "

Apple Silicon macOS users now have a new way to manage containers locally using the Apple Container project. This tool creates and runs Linux containers inside lightweight virtual machines optimized for Apple silicon, and it's fully written in Swift.

\n

With the new Podman Desktop Apple Container extension for Podman Desktop, you can now display your containers, images, and logs, all within the Podman Desktop UI πŸ–₯️.

\n

This extension is a technology preview.

\n

\"hero\"

\n

Introduction​

\n

Apple Container is a Swift-based tool for running Linux containers using minimal virtual machines on macOS. To use this functionality, macOS 26 (Tahoe) and above is required.

\n

Until now, managing containers created with Apple Container required CLI interactions. This new extension enhances Podman Desktop, providing visibility into your containers and images without modifying the core Podman Desktop engine.

\n

Underlying Architecture​

\n

The extension uses a thin integration layer called Socktainer, written in Swift on top of the Vapor framework. Socktainer provides a REST API that aims to be compatible with the Docker REST API.

\n

This design allows Podman Desktop to communicate with Apple Container containers as if they were Docker-compatible, without needing core changes βš™οΈ.

\n

Key points about the architecture:

\n\n

Using the Container Extension​

\n

Once the extension is installed, you can:

\n
    \n
  1. View all running containers 🐳.
    2. \n
  2. Inspect images stored by Apple Container πŸ–ΌοΈ.
    3. \n
  3. Access container logs directly from the UI πŸ“„.
    4. \n
  4. Perform operations like stop, remove, or restart containers.
    5. \n
\n

This provides a seamless experience similar to Podman or Docker integration, but specifically tailored for Apple Silicon Macs 🍎.

\n
Early Access

Not all features are supported yet, as Apple Container itself is still in active development. Expect more functionality in future updates πŸ”œ.

\n

Example: Browsing Containers​

\n
    \n
  1. Open Podman Desktop.
    2. \n
  2. Navigate to the Containers tab.\n\"list
    3. \n
\n

Example: Viewing Images​

\n
    \n
  1. Navigate to the Images tab.
    2. \n
  2. All images managed by Apple Container are displayed.
    3. \n
  3. You can remove images or inspect metadata directly from the UI.
    4. \n
\n

\"list

\n

Example: Browsing Container Logs​

\n
    \n
  1. Open Podman Desktop.
    2. \n
  2. Navigate to the Containers tab.
    3. \n
  3. Select an Apple Container-managed container.
    4. \n
  4. Click Logs or Inspect to see container details.\n\"view
    5. \n
\n

Installation​

\n

You can install the Apple container extension directly inside Podman Desktop.

\n

Go to Extensions > Catalog...

\n

And search for Apple container extension. Click on the install button βœ…

\n

Conclusion​

\n

The Container extension brings Podman Desktop users a modern, native way to manage containers on Apple Silicon Macs 🍏. By leveraging Socktainer and Apple Container, developers can inspect containers and images without leaving the UI, streamlining local development workflows.

\n

Have feedback? Share it on the Podman Desktop extension issue tracker.

", "url": "https://podman-desktop.io/blog/apple-container-extension", "title": "Podman Desktop Apple Container Extension: List Containers & Images on macOS", "summary": "Explore the new container extension in Podman Desktop to manage containers and images running with Apple Container on macOS.", "date_modified": "2025-09-15T00:00:00.000Z", "author": { "name": "Florent Benoit", "url": "https://github.com/benoitf" }, "tags": [ "podman-desktop", "apple-container", "images", "containers", "macos" ] }, { "id": "https://podman-desktop.io/blog/podman-desktop-availability-on-rhel10", "content_html": "

In the ever-evolving world of containerization and AI, developers require tools that are designed for seamless integration into their daily workflows. Podman and its graphical tool, Podman Desktop, have emerged as promising tools for building applications on different platforms, including Red Hat Enterprise Linux (RHEL) 10.

\n

Podman: The foundation​

\n

Podman offers an efficient way to interact with containers and Kubernetes. It is fast and light-weight and operates with a daemonless architecture. Podman supports rootless containers, allowing you to restrict privileges without compromising functionality. Developers can pull, build, and push images, run and debug containers, and efficiently work with Kubernetes. Podman integrates smoothly with systemd, offering basic container orchestration capabilities like pod management and Quadlet systemd generation.

\n

Podman Desktop: A crucial component for developers on RHEL​

\n

Podman Desktop significantly enhances the Podman experience by providing a user-friendly interface that simplifies container and Kubernetes management. It provides a streamlined experience for building, running, and managing containers and pods. It also offers robust Kubernetes integration, enabling you to create local clusters with tools like Kind and Minikube.\nPodman Desktop simplifies the local development environment by tackling challenges like complexity, skill gaps, and inconsistencies between local and production deployments. It provides a simple onboarding process, guiding developers to move from individual applications to containers, pods, and finally to Kubernetes.

\n

Podman Desktop provides the Docker compatibility feature to support Dockerfiles and Compose, which minimizes the need for configuration changes. It allows for easy migration from Docker to Podman and even lets you run docker commands that Podman interprets.\nPodman is included with a RHEL subscription. When you install Podman Desktop from the RHEL extensions repository, Podman Desktop detects Podman and runs it to provide a simplified integration between these two tools. For developers building applications on RHEL, the integration is beneficial in providing:

\n\n

Podman AI Lab: Simplifying the AI developer workflow on RHEL​

\n

The Podman AI Lab extension is helpful for AI developers working within the RHEL ecosystem. It empowers you to run Large Language Models (LLMs) locally, simplifying the development and debugging of AI-enabled applications directly on your machine. This approach offers several benefits, including data privacy, cost control, and the ability to test and debug applications in a local environment. The extension simplifies the AI application development workflow by providing:

\n\n

This enables developers to easily get started with generative AI and integrate models into their applications.

\n

Availability and installation on RHEL 10​

\n

With Podman Desktop availability in the RHEL extensions repository channel, you can easily download and use it. This repository is a curated collection of modern developer tools, open-source libraries, and specialized utilities, ensuring reliable, up-to-date, and Red Hat-signed software.\nFor installation, you need a RHEL 10 machine that is registered with the subscription manager using either your account details or an activation key.

\n

The installation and verification procedure includes:

\n
    \n
  1. \n

    Open a terminal, and enable the RHEL extensions repository:

    \n
    $ sudo subscription-manager repos --enable rhel-10-for-$(arch)-extensions-rpms
    \n
    2. \n
  2. \n

    Enter your password when prompted.

    \n
    3. \n
  3. \n

    Install Podman Desktop:

    \n
    $ sudo dnf install podman-desktop
    \n
    4. \n
  4. \n

    Enter y to confirm the installed size.

    \n
    5. \n
  5. \n

    Enter y to import the GPG key and complete the installation.

    \n
    6. \n
  6. \n

    Enter Podman Desktop in the search box at the top of your home screen, and click the application to open it.

    \n
    7. \n
  7. \n

    Follow the prompts to complete a quick onboarding process with the application.\n\"Screenshot

    \n
    8. \n
  8. \n

    Run basic tasks, such as:

    \n\n
    9. \n
\n

Important note on support​

\n

Podman Desktop is an open-source community project. While Podman itself has supported options on RHEL, the support model for Podman Desktop for Red Hat customers falls under Cooperative Community Support. This means it is intended for non-production support and only offers benefits from community contributions, though with no or limited Service Level Agreements (SLAs). Entitled customers can use this level of support to raise non-production queries and open tickets for more complex issues.

\n

Get involved: Your feedback matters!​

\n

Podman Desktop is an evolving project, and your feedback is crucial for its continued development and improvement. We encourage you to:

\n\n

For more information, visit Podman and Podman Desktop. Dive in, explore, and help us continue to build a robust and user-friendly experience for container and AI development on RHEL 10!

", "url": "https://podman-desktop.io/blog/podman-desktop-availability-on-rhel10", "title": "Simplifying container and AI development on RHEL 10", "summary": "Simplifying container and AI development on RHEL 10 with Podman Desktop", "date_modified": "2025-08-25T00:00:00.000Z", "author": { "name": "Shipra Singh", "url": "https://github.com/shipsing" }, "tags": [ "podman-desktop", "podman", "rhel10", "installation" ] }, { "id": "https://podman-desktop.io/blog/podman-desktop-release-1.21", "content_html": "

Podman Desktop 1.21 Release! πŸŽ‰

\n

\"podman-desktop-hero-1.21\"

\n

Podman Desktop 1.21 is now available. Click here to download it!

\n

This release brings exciting new features and improvements:

\n\n
\n

Release details πŸ”β€‹

\n

✨ Enhancements​

\n

Updated dashboard notification design​

\n

Dashboard notifications now follow the same design as the latest extensions (e.g., AI Lab). This enhancement ensures consistency in the user interface by implementing the updated notification design. The change addresses the visual inconsistency between dashboard notifications and newer extension notifications, providing a more cohesive and polished user experience.

\n\"Updated\"Updated\n

Notify when multiple Podman installations are detected​

\n

Added a notification system to detect and warn users when they have multiple Podman installations (e.g., one installed through the website download and another through Homebrew). This enhancement addresses the issue where duplicate installations can lead to unexpected behavior, such as the UI displaying outdated version information even after running brew update. The notification informs users of the duplicate installation situation, allowing them to uninstall one version to resolve potential conflicts.

\n\"Updated\"Updated\n

Update Podman to v5.6.0​

\n

Updated the Podman engine to version 5.6.0, which was released on August 15, 2025. This update ensures that Podman Desktop users have access to the latest features, improvements, and bug fixes from the Podman project. The upgrade maintains compatibility and provides enhanced functionality for container management and orchestration tasks.

\n

More information about Podman release are available on Podman 5.6 Released and Podman 5.6 Released: Rosetta Status Update blog posts.

\n

Make libkrun the default when creating a Podman machine​

\n

Changed the default provider from AppleHV to libkrun when creating new Podman machines on macOS. This enhancement ensures that the default provider is synchronized with the CLI configuration, particularly for first-time users or when no existing machines are present. The change addresses the need for users to recreate machines when switching to AI model support, providing a more seamless experience.

\n

🐞 Bug Fixes​

\n

UI/UX Issues​

\n\n

Container and Pod Management​

\n\n

Extensions Issues​

\n\n
\n
\n

Community thank you​

\n

πŸŽ‰ We’d like to say a big thank you to everyone who helped to make Podman Desktop even better. In this\nrelease we received pull requests from the following people:

\n\n
\n

Final notes​

\n

The complete list of issues fixed in this release is available here.

\n

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.

\n

Detailed release changelog​

\n

features πŸ’‘β€‹

\n\n

fixes πŸ”¨β€‹

\n\n

chore βœ…β€‹

\n\n

refactor πŸ› οΈβ€‹

\n\n

test πŸš¦β€‹

\n\n

docs πŸ“–β€‹

\n", "url": "https://podman-desktop.io/blog/podman-desktop-release-1.21", "title": "Podman Desktop 1.21 Release", "summary": "Podman Desktop 1.21 has been released!", "date_modified": "2025-08-25T00:00:00.000Z", "author": { "name": "Philippe Martin", "url": "https://github.com/feloy" }, "tags": [ "podman-desktop", "release" ] }, { "id": "https://podman-desktop.io/blog/podman-desktop-release-1.20", "content_html": "

Podman Desktop 1.20 Release! πŸŽ‰

\n

\"podman-desktop-hero-1.20\"

\n

Podman Desktop 1.20 is now available. Click here to download it!

\n

This release brings exciting new features and improvements:

\n\n
\n

Release details πŸ”β€‹

\n

Bulk Start All Containers​

\n

If you have several containers to run, you no longer need to start each one individually. Podman Desktop now provides a β€œRun All” button on the Containers view to launch all selected containers with a single click. This makes it much more convenient to bring up multiple services or an entire application stack in one go. Already-running containers are intelligently skipped, so the bulk start action focuses on only starting the ones that are stopped.

\n\"Containers\"Containers\n
\n

Switch Users and Clusters​

\n

Podman Desktop’s Kubernetes integration now supports easy context switching between different clusters and user accounts. You can change your active Kubernetes cluster and user directly through the application UI without editing config files or using external CLI commands. This is especially useful for developers working with multiple environments – for example, switching from a development cluster to a production cluster (or using different user credentials) is now just a few clicks. It streamlines multi-cluster workflows by letting you hop between contexts seamlessly inside Podman Desktop.

\n\"Edit\"Edit\n
\n

Extension Search by Description​

\n

The extension marketplace search has been improved to help you discover tools more easily. Previously, searching for extensions only matched against extension names. In Podman Desktop 1.20, the search bar also looks at extension descriptions. This means you can enter a keyword related to an extension’s functionality or topic, and the relevant extensions will appear even if that keyword isn’t in the extension’s name. It’s now much easier to find extensions by what they do, not just what they’re called.

\n\"Extensions\"Extensions\n
\n

Provider Updates from Resources Page​

\n

Managing your container and Kubernetes providers just got easier. The Resources page in Podman Desktop (which lists your container engines and Kubernetes environments) now allows direct updates for those providers. If a new version of a provider – say Podman, Docker, or a Kubernetes VM – is available, you can trigger the upgrade right from Podman Desktop’s interface. No need to manually run update commands or leave the app; a quick click keeps your development environment up-to-date with the latest releases.

\n\"Resources\"Resources\n
\n

Local Extension Development Mode​

\n

Extension authors can now toggle Development Mode in Preferences and add a local folder from the new Local Extensions tab. Podman Desktop will watch the folder, load the extension, and keep it tracked across restarts, exactly as it behaves in production. You can start, stop, or untrack the extension directly from the UI, shortening the feedback loop for building and debugging add-ons without extra CLI flags or a special dev build.

\n\"Resources\"Resources\n
\n

Instantly stop live container logs​

\n

The container logs viewer can now be canceled mid-stream, allowing you to stop tailing logs when they are no longer needed.\nPreviously, once a container’s logs were opened, the output would continue streaming until the logs window was closed. With this update, an ongoing log stream can be interrupted via a cancel action without closing the logs pane, giving you more control over log monitoring. This improvement helps avoid redundant log output and unnecessary resource usage by letting log streaming be halted on demand.

\n

New Community Page​

\n

We’ve launched a new Community page on the Podman Desktop website to better connect our users and contributors. This page serves as a central hub for all community-related resources: you can find links to join our Discord channel, participate in GitHub discussions, follow us on social platforms, and more. It also highlights ways to contribute to the project, whether by reporting issues, writing code, or improving documentation. Whether you want to share feedback, meet other Podman Desktop enthusiasts, or get involved in development, the Community page is the place to start.

\n
\n

Community thank you​

\n

πŸŽ‰ We’d like to say a big thank you to everyone who helped to make Podman Desktop even better. In this\nrelease we received pull requests from the following people:

\n\n
\n

Final notes​

\n

The complete list of issues fixed in this release is available here and here.

\n

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.

\n

Detailed release changelog​

\n

feat πŸ’‘β€‹

\n\n

fix πŸ”¨β€‹

\n\n

chore βœ…β€‹

\n\n

refactor πŸ› οΈβ€‹

\n\n

test πŸš¦β€‹

\n\n

docs πŸ“–β€‹

\n\n

ci πŸ”β€‹

\n", "url": "https://podman-desktop.io/blog/podman-desktop-release-1.20", "title": "Podman Desktop 1.20 Release", "summary": "Podman Desktop 1.20 has been released!", "date_modified": "2025-07-07T00:00:00.000Z", "author": { "name": "Vladyslav Zhukovskyi", "url": "https://github.com/vzhukovs" }, "tags": [ "podman-desktop", "release", "kubernetes", "openshift" ] }, { "id": "https://podman-desktop.io/blog/2025/06/02/podman-desktop-core", "content_html": "

In the world of modern software development, containers and Kubernetes are no longer optional; they are essential. That’s where Podman Desktop comes in, your ultimate tool for building, managing, and deploying containers and Kubernetes clusters with ease and confidence. In this blogpost we will walk through a typical development workflow, creating and building a container and then testing it in a local Kubernetes cluster. Let’s dive in.

\n

Building Containerized Applications with Podman Desktop​

\n

First, let's start by building an application in a container with Podman Desktop. We need our application code and a Containerfile. For a simple application, your Containerfile might look something like:

\n
FROM docker.io/nginxinc/nginx-unprivileged

COPY <<EOF /usr/share/nginx/html/index.html
<!DOCTYPE html>
<html>
<head>
    <title>Simple NGINX Container</title>
</head>
<body>
    <h1>Hello from my Podman NGINX Container!</h1>
    <p>This content is being served by NGINX running in a Podman container.</p>
</body>
</html>
EOF
\n

To enhance security, we utilize the nginx-unprivileged image. This helps avoid root access, which is enforced by default in some Kubernetes distributions like OpenShift. The default NGINX image uses port 80, which is forbidden in rootless mode.

\n

Once your application and Containerfile are ready, Podman Desktop makes the build process straightforward:\n\"Build

\n
    \n
  1. Navigate to the \"Images\" section
    2. \n
  2. Select your Containerfile
    3. \n
  3. Provide a name for your image (e.g. webserver)
    4. \n
  4. Click \"Build\"
    5. \n
\n

After building your image, you can immediately run it with a single click, and your container will appear in the \"Containers\" list.

\n

\"Start

\n
    \n
  1. Find your container on the β€œImages” list
    2. \n
  2. Click the β€œRun Image ▢️” button
    3. \n
  3. Give your container a name we will call it: β€œwebserver”
    4. \n
\n

Container Management and Log Analysis​

\n

Now that our webserver container is running we can inspect it in the UI\n\"View

\n

We can click the Open Browser button to see the webserver in our browser:\n\"Webserver

\n

Monitoring container logs is crucial for debugging and understanding application behavior. Let's use Podman Desktop to view the logs of the newly created container.

\n
    \n
  1. Select your running container from the \"Containers\" list
    2. \n
  2. Click on the \"Logs\" tab to view the container's logs
    3. \n
  3. In the newest version of Podman Desktop you can also search in the logs!
    4. \n
\n

\"View

\n

With that, we can continue the development process. We are able to rebuild our container when we have updated code. On top of that, we can share our Containerfile with our team who will be able to reproduce the exact same environment as us to build and test their code.

\n

Working with Kubernetes and OpenShift​

\n

Now that we have a development setup up and running, it’s time to get ready for production. In today's world, it is natural for us to move to Kubernetes. Having a locally running cluster, we are able to iterate quickly but still have an environment that is as close to production as possible. This aids in a smoother migration in the future. Podman Desktop is here to help you test and execute that migration.

\n

With kind or minikube, we are able to have a locally running Kubernetes cluster in minutes. This will allow us to test our application in a Kubernetes environment. Kind comes installed together with Podman Desktop so you will be able to get started instantly.

\n
    \n
  1. Start by navigating to the β€œKubernetes” page
    2. \n
  2. Click on the β€œCreate new Kind cluster” button
    3. \n
\n

\"Create

\n
    \n
  1. Click β€œCreate”
    2. \n
  2. Wait until the kind cluster gets created
    3. \n
  3. Once the cluster is created, Podman Desktop will automatically switch your Kubernetes context to the new kind cluster. If you want to change your cluster, you can switch contexts in the statusbar.
    4. \n
\n

We now have a locally running Kubernetes cluster which we can explore on the Kubernetes dashboard.

\n

\"Kubernetes

\n

This dashboard not only gives you an overview of your cluster but it also provides quick access to the different Kubernetes objects that exist in the cluster.

\n

Creating the Pod on your local Kubernetes cluster​

\n

With a running Kubernetes cluster, we can now create our pod in the Kubernetes cluster. Using Podman Desktop, we can convert our previously created container into a Pod in our kind cluster.

\n

First we have to push our image to our kind cluster.\n\"Push

\n

Now that the image is available we can use the Podman Desktop UI to Deploy our container to a Pod\n\"Deploy

\n
    \n
  1. Navigate to the β€œContainers” section
    2. \n
  2. On the webserver container, click the β€œDeploy to Kubernetes” button
    3. \n
  3. Choose your kind cluster
    4. \n
\n

The conversion from containers to Kubernetes manifests is particularly valuable, eliminating the need to manually write YAML files for simple deployments. Podman Desktop adds imagePullPolicy: IfNotPresent to the generated Kubernetes YAML. This ensures that we use the image that we just pushed to the cluster is also the one we will use. Make sure to add this to your Kubernetes YAML or use a specific tag on your image to avoid the default pull policy (Always).

\n

Monitoring Kubernetes Events and Resources​

\n

Understanding what's happening in your Kubernetes cluster is essential for effective development. In the latest version of Podman Desktop, you can now check the events of your Kubernetes Pods in the UI.

\n

Let's check if our pod was created and running successfully.

\n
    \n
  1. Navigate to the β€œKubernetes” in the left-navigation
    2. \n
  2. Click on the β€œPods” sub-navigation
    3. \n
  3. Click on the pods you just created
    4. \n
  4. Scroll to the bottom and check the β€œEvents”
    5. \n
  5. We can see that our Pod was started and is running
    6. \n
\n

\"View

\n

We can also check out the β€œLogs” tab to see the logs of the running Pod.\n\"View

\n

Video walkthrough​

\n\n

Conclusion​

\n

Podman Desktop significantly streamlines the container and Kubernetes development experience by providing:

\n\n

Whether you're just starting with containers or managing complex Kubernetes deployments, Podman Desktop offers tools that simplify your workflow and increase productivity. As a CNCF project, it continues to evolve with the needs of the cloud-native community, making it an increasingly valuable tool in any developer's toolkit.

\n

Try Podman Desktop today and experience how it can transform your container, Kubernetes and OpenShift workflows!

", "url": "https://podman-desktop.io/blog/2025/06/02/podman-desktop-core", "title": "Containers and Kubernetes development with Podman Desktop", "summary": "A step-by-step guide for your containers and Kubernetes development with Podman Desktop", "date_modified": "2025-06-02T00:00:00.000Z", "author": { "name": "Matt Demyttenaere", "url": "https://github.com/firewall" }, "tags": [ "podman-desktop", "podman", "development", "container", "tools" ] }, { "id": "https://podman-desktop.io/blog/podman-desktop-release-1.19", "content_html": "

Podman Desktop 1.19 Release! πŸŽ‰

\n

\"podman-desktop-hero-1.19\"

\n

Podman Desktop 1.19 is now available. Click here to download it!

\n

This release brings exciting new features and improvements, including many extension updates:

\n\n

Release details πŸ”β€‹

\n

Podman v5.5​

\n

Podman Desktop aims to work offline, so it ships alongside its binary, the Podman executable.\nIn this release, the latest Podman 5.5 version provides new features, bug fixes, and better stability while using the tool.

\n

You can find the full changelog of Podman 5.5 on their release page containers/podman/releases#v5.5.0.

\n
info

While the Podman binary is updated in this release, the existing Podman machines will remain at the version in which they were created. To update your Podman machine, you must remove it and initialize a new one.

\n

Bootc Extension πŸ¦­β€‹

\n

The Podman Desktop Boot container extension (aka Bootc) has recently seen significant improvements; one of them is the usage of macadam.

\n
\n

Macadam is a cross-platform command-line tool to create and manage virtual machines. It runs on Windows, macOS, and Linux, and uses each OS's native virtualization stacks: WSL2 on Windows, Apple’s Virtualization Framework on macOS, and QEMU on Linux. Macadam reuses Podman machine code.

\n
\n

As the bootc tool applies a container image as an update to an already running Linux system, allowing the output to boot an entire OS with the container image included. To test the bootc artifact, you either need a dedicated machine or create a virtual machine from the artifact.

\n

To simplify the developer experience of testing the artifact,\nthe Podman Desktop Bootc extension offers you a way to directly create a virtual machine from the artifact you created.

\n\"Bootc\"Bootc\n
\n
\n
note

There is a known issue with the virtualization that can be found in the bootc extension readme.

\n

Another important aspect of presenting a new technology is showcasing its capabilities. Thanks to Charlie Drage and Tim deBoer, a lot of effort has been put into demonstrating bootable containers, such as kernel module management, WiFi modules, systemd unit files, and others.

\n

You can find ready-to-use examples on the Bootable Containers > Examples page.

\n\"Bootc\"Bootc\n
\n

AI Lab βœ¨β€‹

\n

The Podman Desktop AI Lab extension started as an experiment in 2024, exploring how AI workflows could be containerized,\ncelebrating more than one year of updates and progress, the extension has grown to support a wide range of tools,\nsuch as Instructlab1, llamaCPP2, WhisperCPP3 and with the latest release OpenVINO, llama-stack and MCP.

\n

OpenVINO​

\n

With the introduction of OpenVINO4 as a supported inference runtime, you can now run OpenVINO models5 locally through Podman.

\n\"AI\"AI\n
\n

llama-stack​

\n

Llama Stack standardizes the core building blocks that simplify AI application development6.

\n

With the latest version of AI Lab, we introduce support for Llama Stack, running in a containerized environment. Inference servers running inside AI Lab will be registered to the Llama Server to be used by their clients.

\n\"AI\"AI\n
\n

Model Context Protocol (MCP)​

\n

Creating a product from LLMs has proven challenging, and emerging protocols are trying to help, such as MCP.

\n
\n

MCP is an open protocol that standardizes how applications provide context to LLMs.7

\n
\n

The initial steps to support MCP in the AI Lab playground have begun, enabling developers to experiment directly through the GUI before trying to integrate it into their applications.

\n\"AI\"AI\n
\n

Minc extension πŸ“¦β€‹

\n

MicroShift is a project that optimizes OpenShift Kubernetes for small form factors and edge computing8. Similar to Kind and Minikube, an extension for creating and managing MicroShift clusters locally through Podman has been created.

\n

You can learn more about it in the MicroShift section.

\n
tip

Interested in bootable containers and MicroShift? You can refer to the blog post titled Creating a MicroShift Bootable Image with Podman Desktop.

\n

RHEL Lightspeed βš‘β€‹

\n

Red Hat Lightspeed is a generative AI assistant integrated into Red Hat's hybrid cloud platforms, such as OpenShift and Enterprise Linux.9\nIt provides natural language guidance within the console to simplify complex tasks, enhance productivity, and bridge IT skills gaps.

\n

Users can choose from various AI models, including OpenAI, Azure OpenAI, WatsonX, or deploy private models on Red Hat platforms.

\n

With a Red Hat subscription, you can experiment with Red Hat Lightspeed from anywhere, including Podman Desktop, through a new extension called RHEL Lightspeed.

\n

You can install the extension directly by navigating to the Extensions > Catalog page and clicking its Install icon.

\n\"RHEL\"RHEL\n
\n
\n
note
\n

RHEL VMs extension πŸ—ƒοΈβ€‹

\n

Through the Podman executable, Podman Desktop manages virtual machines; the cross-platform code responsible for this has been reused to create the macadam tool mentioned earlier.

\n

The RHEL VMs extension helps the user run RHEL virtual machines using the macadam tool.

\n\"RHEL\"RHEL\n
\n
\n
note

On macOS and Linux, you need to manually install the Macadam binary. See pre-requisites for more details.

\n

RHEL 10 availability πŸš’β€‹

\n

The Podman Desktop you love - simplified container management and intuitive UI - now extends to RHEL workflows.\nFor users on RHEL systems, explore the extension channel to install Podman Desktop. You'll get a familiar experience across Windows, Mac and now RHEL. Releases are happening at the same time as other platforms, so you'll get instant access to new features.

\n

Find more details about Installing Podman Desktop on RHEL 10.

\n
\n

Community thank you​

\n

πŸŽ‰ We’d like to say a big thank you to everyone who helped to make Podman Desktop even better. In this\nrelease, we received pull requests from the following people:

\n\n
\n

Final notes​

\n

The complete list of issues fixed in this release is available here and here.

\n

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.

\n

Detailed release changelog​

\n

fix πŸ”¨β€‹

\n\n

chore βœ…β€‹

\n\n

refactor πŸ› οΈβ€‹

\n\n

docs πŸ“–β€‹

\n\n

test πŸš¦β€‹

\n\n

feature πŸ’‘β€‹

\n\n\n

Footnotes​

\n
    \n
  1. \n

    https://instructlab.ai/ ↩

    \n
    2. \n
  2. \n

    https://github.com/ggml-org/llama.cpp ↩

    \n
    3. \n
  3. \n

    https://github.com/ggml-org/whisper.cpp ↩

    \n
    4. \n
  4. \n

    https://github.com/openvinotoolkit/openvino ↩

    \n
    5. \n
  5. \n

    https://huggingface.co/OpenVINO ↩

    \n
    6. \n
  6. \n

    https://github.com/meta-llama/llama-stack?tab=readme-ov-file#overview ↩

    \n
    7. \n
  7. \n

    https://modelcontextprotocol.io/introduction ↩

    \n
    8. \n
  8. \n

    https://www.redhat.com/en/topics/edge-computing/microshift ↩

    \n
    9. \n
  9. \n

    Red Hat Announces General Availability of Red Hat OpenShift Lightspeed to Supercharge Hybrid Cloud Productivity with Generative AI ↩

    \n
    10. \n
\n
", "url": "https://podman-desktop.io/blog/podman-desktop-release-1.19", "title": "Podman Desktop 1.19 Release", "summary": "Podman Desktop 1.19 has been released!", "date_modified": "2025-05-22T00:00:00.000Z", "author": { "name": "Axel Stefanini", "url": "https://github.com/axel7083" }, "tags": [ "podman-desktop", "release", "kubernetes", "openshift" ] }, { "id": "https://podman-desktop.io/blog/2025/05/21/podman-ai-lab-openvino", "content_html": "

Introduction to Podman AI Lab​

\n

Podman AI Lab is an open-source platform designed to simplify the deployment, management, and experimentation of AI workloads using container technology. It provides a user-friendly interface for running, testing, and scaling AI models locally or in the cloud, leveraging the power and flexibility of Podman containers.

\n

What is OpenVINO?​

\n

OpenVINOβ„’ (Open Visual Inference and Neural Network Optimization) is an open-source toolkit developed by Intel to accelerate AI inference on a variety of hardware, including CPUs, GPUs, and specialized accelerators. It optimizes deep learning models for fast, efficient inference, making it a popular choice for edge and cloud AI applications.

\n

Using OpenVINO in Podman AI Lab​

\n

Podman AI Lab now supports OpenVINO as an inference provider. This means you can:

\n\n
warning

This feature is only available on Intel based systems, as OpenVINO is optimized for Intel hardware. If you are using a non-Intel system, you will not be able to use OpenVINO as an inference provider.

\n

How to use:

\n
    \n
  1. Launch Podman AI Lab and navigate to the model deployment or playground section.
    2. \n
  2. When configuring your model, choose an OpenVINO compatible model.
    3. \n
  3. Start the inference server or playground.
    4. \n
\n

Starting an OpenVINO inference server​

\n
    \n
  1. Click the Podman AI Lab icon in the navigation bar.
    2. \n
  2. In the Podman AI Lab navigation bar, click Models > Services menu item.
    3. \n
  3. Click the New Model Service button on the top right.
    4. \n
  4. Select an OpenVINO compatible model in the list (e.g. OpenVINO/mistral-7B-instruct-v0.2-int4-ov) in the Model list and click the Create Service button.
    5. \n
  5. The inference server for the model is being started and after a while, click on the Open service details button.
    6. \n
\n

\"OpenVINO

\n

Using the terminal shell, execute the given curl command and see the inference result output.

\n

Starting a playground with an OpenVINO compatible model​

\n
    \n
  1. Click the Podman AI Lab icon in the navigation bar.
    2. \n
  2. In the Podman AI Lab navigation bar, click Models > Playgrounds menu item.
    3. \n
  3. Click the New Playground button on the top right.
    4. \n
  4. Select an OpenVINO compatible model in the list (e.g. OpenVINO/mistral-7B-instruct-v0.2-int4-ov) in the Model list and click the Create playground button.
    5. \n
  5. The playground for the model is being started and after a while, a chat interface is displayed.
    6. \n
\n

\"Initial

\n

Enter 'What is OpenVINO?' in the prompt and click the Send button. The OpenVINO model will respond with an answer.

\n

\"OpenVINO

\n

Consistency with OpenShift AI + OpenVINO​

\n

One of the key advantages of using OpenVINO in Podman AI Lab is the consistency it brings when transitioning workloads to OpenShift AI. Both platforms now support OpenVINO, ensuring that:

\n\n

Conclusion​

\n

By enabling OpenVINO as an inference provider, Podman AI Lab empowers users to leverage high-performance AI inference both locally and in the cloud, with a consistent experience across platforms like OpenShift AI. This integration streamlines the AI development lifecycle and unlocks new possibilities for deploying efficient, scalable AI solutions.

", "url": "https://podman-desktop.io/blog/2025/05/21/podman-ai-lab-openvino", "title": "Enabling OpenVINO Inference in Podman AI Lab", "summary": "Use Podman AI Lab to run OpenVINO inference workloads locally.", "date_modified": "2025-05-21T00:00:00.000Z", "author": { "name": "Jeff Maury", "url": "https://github.com/jeffmaury" }, "tags": [ "podman-desktop", "podman", "extension", "ai", "llm", "local", "podman-ai-lab", "openvino" ] }, { "id": "https://podman-desktop.io/blog/iterate-quickly-inner-loop-with-a-kubernetes-cluster", "content_html": "

Developers working locally often seek a fast inner loop for coding, building, and testing their OCI images and Kubernetes applications.

\n

For instance, when testing a new image in a Kubernetes pod, the image must be accessible either by pushing it to a private or public registry or by ensuring it's available on the Kubernetes cluster nodes. This often requires additional commands such as kind load docker-image, minikube cache add <image>, or publishing the image to a third-party registry.

\n

In this blog post, we’ll introduce a new extension called MINC (MicroShift IN Container), which provides a MicroShift cluster running within an existing Podman Machine environment.

\n

\"hero\"

\n
\n

Introduction​

\n

A previous blog post outlines various methods to improve the inner loop using Kind or Minikube. While these approaches can enhance performance, there are still gaps and certain complexities involved. Achieving a seamless workflow where an image is built with Podman and immediately available in the clusterβ€”often requires additional steps or tricky configurations.

\n

podman, kubernetes/cri-o and MicroShift​

\n

The CRI-O project implements the CRI interface and reuses image management from containers/image project and handles storage using containers/storage project.

\n

Podman uses these same libraries to read and write container images, storing them in the /var/lib/containers directory.

\n

The MINC extension launches a MicroShift cluster in a more efficient way for developers than previous deployments. Unlike the OpenShift Local extension, which sets up a separate virtual machine (VM), MINC (Microshift IN Container) runs a container inside your existing Podman Machine (on Windows or macOS). This avoids running two VMs, one for Kubernetes and another for Podman.

\n

A key benefit is that the MINC container shares Podman’s image storage. When you build an image with Podman, it's instantly available in the cluster, no uploading or copying required.

\n
MINC requires a rootful Podman machine

Make sure the machine is running in rootful mode, or create a new one using the --rootful option.

\n

Creating a Local Kubernetes/MicroShift Cluster​

\n
    \n
  1. Create the MicroShift cluster
    2. \n
\n

In the Resources view, click the MINC card and select \"Create new…\". For now, no customization is neededβ€”just click \"Next\". The cluster will start automatically.

\n
    \n
  1. \n

    Verify that now you see in bottom left in the status bar microshift as the default Kubernetes context and if you go in the left navbar in the Kubernetes section you can see in the Nodes entry the MicroShift node.

    \n
    2. \n
  2. \n

    Verify kubectl setup using a CLI

    \n
    3. \n
\n

MINC updates your $HOME/.kube/config file with a new microshift entry. Check in the bottom left of the status bar, you should see a microshift entry as the default Kubernetes context.

\n

Try listing all pods:

\n
kubectl get -A pods
\n

Example output:

\n
NAMESPACE              NAME                                      READY   STATUS
kube-flannel           kube-flannel-ds-wjn2f                     1/1     Running
kube-proxy             kube-proxy-jh7r8                          1/1     Running
kube-system            csi-snapshot-controller-8d97d878f-l6q6j   1/1     Running
openshift-dns          dns-default-zvdw9                         2/2     Running
openshift-dns          node-resolver-84twk                       1/1     Running
openshift-ingress      router-default-54c5757547-4jnfd           1/1     Running
openshift-service-ca   service-ca-7977bdc4d4-ssjq2               1/1     Running

\n

Create a Hello World container image​

\n

Create a Containerfile

\n
FROM nginx

RUN echo '<!DOCTYPE html><html><head><title>Hello</title></head><body><h1>Hello from MINC</h1></body></html>' \\
    > /usr/share/nginx/html/index.html
\n

Or quickly create it with:

\n
echo 'FROM nginx:alpine
RUN echo \"<!DOCTYPE html><html><head><title>Hello</title></head><body><h1>Hello from MINC</h1></body></html>\" > /usr/share/nginx/html/index.html' > Containerfile
\n

Then, using Podman Desktop, build the image providing the name minc/nginx:hello-world.

\n

Verify Image in the MicroShift Cluster​

\n

Inside the MicroShift container, run:

\n
crictl images | grep hello
\n

You should see something like:

\n
docker.io/minc/nginx                                                                     hello-world               e7032b219ab03       51.1MB
\n

The image is now available in the MicroShift cluster.

\n

Create a Pod from the UI​

\n

Click on the play button from the image to start a new container. Then select the container and click on \"Create Pod\".

\n

Deploy a pod from this image using the CLI​

\n

Use kubectl to deploy a pod from the image:

\n
kubectl run hello-world-pod --image=minc/nginx:hello-world --port=80
\n

To check if the pod is running, use:

\n
kubectl get pods
\n

Expected output:

\n
kubectl get pods
NAME              READY   STATUS    RESTARTS   AGE
hello-world-pod   1/1     Running   0          6s
\n

Deploy this podman Pod to Kubernetes/MINC

\n

Select the pod and click on Deploy to Kubernetes... in the Kebab menu.\nYour Pod is now deployed to the MINC cluster.

\n

If you want to use the CLI/manual steps :

\n

Create a Service for the Pod using the CLI

\n

Expose the pod with a service:

\n
kubectl expose pod hello-world-pod --port=80 --target-port=80 --name=hello-world-service
\n

Create a Route (Requires oc CLI)

\n

Assuming the oc CLI (OpenShift client) is available in your PATH, create a route:

\n
oc create route edge hello-world-route --service svc/hello-world-service --port 80 --wildcard-policy=None
\n

To list all routes:

\n
oc get routes
\n

Access the Nginx Container​

\n

Clicking on the route in the UI will redirect you to the page.

\n

Without the UI it's also possible to get that information.

\n

Check that the nginx container is reachable using the route. Use the -k flag with curl to ignore the self-signed certificate warning:

\n
curl -k \"https://$(oc get route hello-world-route -ojsonpath='{.status.ingress[0].host}'):9443\"
\n

You can also open the URL in your browser (you’ll need to ignore the self-signed certificate warning):

\n
open \"https://$(oc get route hello-world-route -ojsonpath='{.status.ingress[0].host}'):9443\"
\n

You should see the message: \"Hello from MINC\" πŸŽ‰

\n

This confirms that your inner development loop is working. Once the image is built, it’s instantly available in the cluster.

\n

Video walkthrough​

\n\n

Conclusion​

\n

Using MINC and the MINC extension significantly reduces the turnaround time between building and testing container images.

\n

Have feedback? Share it on the MINC extension issue tracker

", "url": "https://podman-desktop.io/blog/iterate-quickly-inner-loop-with-a-kubernetes-cluster", "title": "MINC: Speed Up Local K8s Dev", "summary": "Speed up your development inner loop using a local Kubernetes cluster powered by MicroShift in a container.", "date_modified": "2025-05-15T00:00:00.000Z", "author": { "name": "Florent Benoit", "url": "https://github.com/benoitf" }, "tags": [ "podman-desktop", "podman", "images", "kubernetes", "microshift" ] }, { "id": "https://podman-desktop.io/blog/2025/05/05/vs-code-with-podman-desktop", "content_html": "

Developing containerized applications can sometimes feel complex, but with the right tools, it can be a smooth and efficient process. In this blog post, we'll explore how to leverage the power of Visual Studio Code (VS Code) together with Podman and Podman Desktop to streamline your container development workflow. We'll cover setting up and using two VS Code extensions that integrate with Podman.

\n

VS Code: Your IDE for Container Development​

\n

VS Code is a popular and versatile code editor that can be extended to enhance its functionality. For container development, several excellent extensions integrate seamlessly with Podman.

\n

Prerequisites​

\n

Before we begin, ensure you have the following installed:

\n\n

VS Code Extensions​

\n

To integrate VS Code with Podman, we have 2 extensions as options:

\n
    \n
  1. Microsoft’s Container Tools extension: The \"Container Tools\" extension provides excellent support for container-related tasks, including building images, managing containers, and working with Containerfiles and Dockerfiles. Microsoft recently announced that they will be evolving the Docker extension into the Container Tools extension to support other tools like Podman!
    2. \n
  2. Pod Manager: This extension was created by one of the members of our community and is completely open source. It is designed to help you manage Podman containers, images, volumes, and networks directly from the VS Code interface.
    3. \n
\n

While it's unlikely that you would use both extensions simultaneously, comparing them will help you understand the strengths and weaknesses of each, ultimately making it easier to select the one that best fits your needs. So for this blog post, we'll install them one by one.

\n

Option 1: Microsoft’s Container Tools extension​

\n

To install the extension:

\n
    \n
  1. Open VS Code.
    2. \n
  2. Click on the Extensions icon in the Activity Bar (or press Ctrl+Shift+X or Cmd+Shift+X).
    3. \n
  3. Search for \"Container Tools\" and install the extension by Microsoft.
    4. \n
\n

Configuring VS Code for Podman​

\n

The Container Tools extension usually automatically detects Podman if Docker isn't running, by looking at the DOCKER_HOST environment variable. In Podman Desktop navigate to Settings > Docker Compatibility > Third-Party Tool Compatibility and make sure the option is enabled. Learn more about the Docker Compatibility in our documentation.

\n

\"enabling

\n

Option 2: Pod Manager​

\n

To install the extension:

\n
    \n
  1. Open VS Code.
    2. \n
  2. Click on the Extensions icon in the Activity Bar (or press Ctrl+Shift+X or Cmd+Shift+X).
    3. \n
  3. Search for \"Pod Manager\" and install the extension by dreamcatcher45.
    4. \n
\n

Using the VS Code Extensions​

\n

Now that we have the extensions installed and configured, let's see how to use them.

\n

Working with Containerfiles and Dockerfiles​

\n

Both extensions provide syntax highlighting, code completion, and linting for Containerfiles and Dockerfiles. Open a Containerfile in VS Code, and you'll immediately benefit from these features.

\n

You can also build images directly from VS Code:

\n
    \n
  1. Right-click on the Containerfile in the Explorer view.
    2. \n
  2. Select \"Build Image\".
    3. \n
  3. VS Code will prompt you for an image name and tag.
    4. \n
  4. The extension will then build the image using Podman.
    5. \n
  5. After that you will see the built image in the sidebar.
    6. \n
\n

If you are using the CLI commands to build images, you will also see them here.

\n

\"building

\n

Managing Containers​

\n

The extensions also allow you to manage containers directly from VS Code. You can start, stop, restart, and remove containers, as well as view their logs and inspect their configuration.

\n

To view the container logs:

\n
    \n
  1. Click on the Container icon in the Activity Bar.
    2. \n
  2. You'll see a list of your containers, images, and networks.
    3. \n
  3. Right-click on a container to perform actions.
    4. \n
\n

\"using

\n

Similarly using the Pod manager extension we can visually inspect containers, images, and volumes.

\n
    \n
  1. Click on the Pod manager icon in the Activity Bar.
    2. \n
  2. You'll see a list of your containers, images, and networks.
    3. \n
\n

\"using

\n

and manage the container lifecycle.

\n

\"using

\n

and of course troubleshoot issues with a visual interface.

\n

\"using

\n

Conclusion​

\n

In comparison, both extensions provide a nearly identical set of features, so it is really up to you which UI you prefer. Personally I will stick with the Pod Manager because the logo is a seal 🦭. Remember if you encounter any issues using these tools or with Podman Desktop let us know by starting a discussion or creating an issue.

\n

By combining the power of VS Code, Podman, and Podman Desktop, you can create a streamlined and efficient container development workflow. The VS Code extensions provide excellent integration with Podman, allowing you to manage containers, build images, and work with Containerfiles directly from your code editor. We are excited to see that Microsoft is embracing Podman and building support into their ecosystem. Podman Desktop complements this with a visual interface for managing your container environment and will help to move from your development environment to a production Kubernetes environment. Embrace these tools and elevate your container development experience!

", "url": "https://podman-desktop.io/blog/2025/05/05/vs-code-with-podman-desktop", "title": "Supercharge Your Container Development in VS Code with Podman and Podman Desktop", "summary": "How to develop apps with VS Code and Podman Desktop", "date_modified": "2025-05-05T00:00:00.000Z", "author": { "name": "Matt Demyttenaere", "url": "https://github.com/firewall" }, "tags": [ "podman-desktop", "podman", "vscode", "docker", "extension", "development", "container", "tools" ] }, { "id": "https://podman-desktop.io/blog/podman-desktop-release-1.18", "content_html": "

Podman Desktop 1.18 Release! πŸŽ‰

\n

\"podman-desktop-hero-1.18\"

\n

Podman Desktop 1.18 is now available! Click here to download it!

\n

This release brings exciting new features and improvements:

\n\n
\n

Release Details​

\n

Docker Compatibilty mode page is out of experimental mode πŸŽ‰β€‹

\n

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.

\n\"Docker\"Docker\n\"Docker\"Docker\n

Switching Kubernetes namepaces​

\n

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.

\n\"Kubernetes\"Kubernetes\n

Kubernetes Jobs​

\n

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.

\n\"Kubernetes\"Kubernetes\n\"Kubernetes\"Kubernetes\n

Experimental status bar providers enhancements​

\n

The experimental status bar providers that were introduced in v1.16 have undergone some changes to make them easier to understand and use.

\n

The new provider status icons include:

\n\n

In addition, you can now choose which available providers to show by pinning or unpinning them from the status bar:

\n\"Status\"Status\n

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.

\n

Additional changes​

\n
Breaking change

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

\n

Community Thank You​

\n

πŸŽ‰ We’d like to say a big thank you to everyone who helped to make 🦭 Podman Desktop even better. In this\nrelease we received pull requests from the following new people:

\n\n

Final notes​

\n

The complete list of issues fixed in this release is available here.

\n

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.

\n

Detailed release changelog​

\n

Chores βœ…β€‹

\n\n

Tests πŸš¦β€‹

\n\n

Docs πŸ“–β€‹

\n\n

ci πŸ”β€‹

\n\n

Feature πŸ’‘β€‹

\n\n

Fixes πŸ”¨β€‹

\n", "url": "https://podman-desktop.io/blog/podman-desktop-release-1.18", "title": "Podman Desktop 1.18 Release", "summary": "Podman Desktop 1.18 has been released!", "date_modified": "2025-04-14T00:00:00.000Z", "author": { "name": "Sonia Sandler", "url": "https://github.com/SoniaSandler" }, "tags": [ "podman-desktop", "release", "podman" ] }, { "id": "https://podman-desktop.io/blog/2025/03/06/mirror-registry-configuration-blog", "content_html": "

Lower rate limits imposed on the Docker Hub End-User License Agreement (EULA) made it difficult for community members to access the docker.io images frequently. A simple solution to this problem is to configure a mirror for the docker.io registry in the registries.conf file. This way, they can access the Docker resources whenever needed.

\n

With the Podman Desktop UI, you can add registry locations and configure their mirrors easily. Configuring a mirror redirects a registry to another location, enabling you to use its content. For example, if you have configured ghcr.io as a mirror for docker.io and try to pull a resource, Podman pulls the resource from ghcr.io instead of docker.io.

\n

The blog covers how to configure a mirror for the docker.io registry.

\n

Prerequisites​

\n\n

Configuring: A mirror for docker.io​

\n
    \n
  1. Go to the Settings > Resources page.
    2. \n
  2. Select More Options > Setup registry configuration in the Podman tile. A command palette opens.\n\"Set
    3. \n
  3. Set up your registry configuration:
    4. \n
  4. Select the Add registry configuration option from the command palette.\n\"adding
    5. \n
  5. Type the location of the registry, such as docker.io, and press the Enter key. The docker.io registry is added to the palette.\n\"docker.io
    6. \n
  6. Select docker.io from the command palette.
    7. \n
  7. Type the location where you want to mirror the registry, such as ghcr.io, and press the Enter key. The entry for the docker.io registry shows the location where it is mirrored.\n\"mirrored
    8. \n
  8. Select the End configuring registries option to end registry configuration.\n\"ending
    9. \n
\n

Verifying: the mirror​

\n

There is no direct way to verify the mirror configuration from the UI. But, you can use the CLI for verification.

\n
    \n
  1. Start an interactive session with the default Podman machine:
    2. \n
\n
$ podman machine ssh <machine_name>
\n
    \n
  1. Pull an invalid image from docker.io.
    2. \n
\n
$ podman pull docker.io/invalid
\n

An error message appears in the terminal indicating a failure to pull the image from the mirror. You receive the error message: Mirrors have also failed.

", "url": "https://podman-desktop.io/blog/2025/03/06/mirror-registry-configuration-blog", "title": "Configure a mirror registry", "summary": "Covers the end-to-end workflow to configure a mirror registry", "date_modified": "2025-03-06T00:00:00.000Z", "author": { "name": "Shipra Singh", "url": "https://github.com/shipsing" }, "tags": [ "podman-desktop", "podman", "configure-a-mirror-registry" ] } ] }