From 007db2d0dcb4ed47fedc03bfe760f0784a59c1fa Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Thu, 21 Sep 2023 19:40:10 +0000 Subject: [PATCH] deploy: 6018a2f34f5f3e03ff08189fe1360ee4070dfd8d --- 404.html | 4 ++-- assets/js/1df93b7f.9b5882c1.js | 1 + assets/js/1df93b7f.e2fef33f.js | 1 - .../js/{runtime~main.231fa618.js => runtime~main.39df3c7b.js} | 2 +- blog.html | 4 ++-- blog/5-things-to-know-for-a-docker-user.html | 4 ++-- blog/archive.html | 4 ++-- blog/develop-using-devcontainer.html | 4 ++-- blog/podman-desktop-release-0.10.html | 4 ++-- blog/podman-desktop-release-0.11.html | 4 ++-- blog/podman-desktop-release-0.12.html | 4 ++-- blog/podman-desktop-release-0.13.html | 4 ++-- blog/podman-desktop-release-0.14.html | 4 ++-- blog/podman-desktop-release-0.15.html | 4 ++-- blog/podman-desktop-release-1.0.html | 4 ++-- blog/podman-desktop-release-1.1.html | 4 ++-- blog/podman-desktop-release-1.2.html | 4 ++-- blog/podman-desktop-release-1.3.html | 4 ++-- blog/podman-desktop-release-1.4.html | 4 ++-- ...unning-a-local-kubernetes-cluster-with-podman-desktop.html | 4 ++-- blog/tags.html | 4 ++-- blog/tags/codespaces.html | 4 ++-- blog/tags/compose.html | 4 ++-- blog/tags/devcontainer.html | 4 ++-- blog/tags/docker.html | 4 ++-- blog/tags/kind.html | 4 ++-- blog/tags/kubernetes.html | 4 ++-- blog/tags/migrating.html | 4 ++-- blog/tags/openshift.html | 4 ++-- blog/tags/podman-desktop.html | 4 ++-- blog/tags/release.html | 4 ++-- blog/tags/story.html | 4 ++-- core-values.html | 4 ++-- docs/compose.html | 4 ++-- docs/compose/running-compose.html | 4 ++-- docs/compose/setting-up-compose.html | 4 ++-- docs/extensions.html | 4 ++-- docs/extensions/install.html | 4 ++-- docs/extensions/publish.html | 4 ++-- docs/extensions/write.html | 4 ++-- docs/extensions/write/when-clause-context.html | 4 ++-- docs/installation.html | 4 ++-- docs/installation/linux-install.html | 4 ++-- .../installing-podman-desktop-from-a-compressed-tar-file.html | 4 ++-- .../installing-podman-desktop-from-a-flatpak-bundle.html | 4 ++-- docs/installation/macos-install.html | 4 ++-- docs/installation/windows-install.html | 4 ++-- ...podman-desktop-and-podman-in-a-restricted-environment.html | 4 ++-- ...ng-podman-desktop-silently-with-the-windows-installer.html | 4 ++-- .../installing-podman-desktop-with-chocolatey.html | 4 ++-- .../windows-install/installing-podman-desktop-with-scoop.html | 4 ++-- .../installing-podman-desktop-with-winget.html | 4 ++-- docs/intro.html | 4 ++-- docs/kubernetes.html | 4 ++-- .../configuring-access-to-a-kubernetes-cluster.html | 4 ++-- docs/kubernetes/deploying-a-container-to-kubernetes.html | 4 ++-- docs/kubernetes/deploying-a-pod-to-kubernetes.html | 4 ++-- docs/kubernetes/kind.html | 4 ++-- .../kind/building-an-image-and-testing-it-in-kind.html | 4 ++-- docs/kubernetes/kind/pushing-an-image-to-kind.html | 4 ++-- .../kubernetes/kind/working-with-your-local-kind-cluster.html | 4 ++-- docs/kubernetes/lima.html | 4 ++-- docs/kubernetes/minikube.html | 4 ++-- .../building-an-image-and-testing-it-in-minikube.html | 4 ++-- .../minikube/configuring-podman-for-minikube-on-windows.html | 4 ++-- docs/kubernetes/minikube/creating-a-minikube-cluster.html | 4 ++-- docs/kubernetes/minikube/deleting-your-minikube-cluster.html | 4 ++-- docs/kubernetes/minikube/installing-minikube.html | 4 ++-- docs/kubernetes/minikube/pushing-an-image-to-minikube.html | 4 ++-- .../kubernetes/minikube/restarting-your-minikube-cluster.html | 4 ++-- .../minikube/working-with-your-local-minikube-cluster.html | 4 ++-- docs/kubernetes/openshift.html | 4 ++-- .../openshift/configuring-access-to-a-developer-sandbox.html | 4 ++-- .../openshift/creating-an-openshift-local-cluster.html | 4 ++-- ...selecting-current-kubernete-context-in-the-status-bar.html | 4 ++-- .../viewing-and-selecting-current-kubernete-context.html | 4 ++-- docs/migrating-from-docker.html | 4 ++-- .../emulating-docker-cli-with-podman.html | 4 ++-- docs/migrating-from-docker/importing-saved-containers.html | 4 ++-- docs/migrating-from-docker/using-podman-mac-helper.html | 4 ++-- .../using-the-docker_host-environment-variable.html | 4 ++-- .../verifying-your-tools-are-using-podman.html | 4 ++-- docs/onboarding.html | 4 ++-- docs/onboarding/containers.html | 4 ++-- .../creating-a-lima-instance-with-podman-desktop.html | 4 ++-- .../creating-a-podman-machine-with-podman-desktop.html | 4 ++-- .../installing-podman-with-openshift-local-on-windows.html | 4 ++-- .../installing-podman-with-podman-desktop-on-windows.html | 4 ++-- docs/onboarding/kubernetes.html | 4 ++-- docs/onboarding/kubernetes/kind.html | 4 ++-- .../kind/configuring-podman-for-kind-on-windows.html | 4 ++-- docs/onboarding/kubernetes/kind/creating-a-kind-cluster.html | 4 ++-- .../kubernetes/kind/deleting-your-kind-cluster.html | 4 ++-- docs/onboarding/kubernetes/kind/installing-kind.html | 4 ++-- .../kubernetes/kind/restarting-your-kind-cluster.html | 4 ++-- docs/proxy.html | 4 ++-- docs/proxy/using-a-proxy-in-your-containers.html | 4 ++-- docs/proxy/using-a-proxy-on-linux.html | 4 ++-- docs/proxy/using-a-proxy-requiring-a-custom-ca.html | 4 ++-- docs/proxy/using-a-proxy.html | 4 ++-- docs/proxy/using-a-vpn-on-windows.html | 4 ++-- docs/tags.html | 4 ++-- docs/tags/chocolatey.html | 4 ++-- docs/tags/compose.html | 4 ++-- docs/tags/containers.html | 4 ++-- docs/tags/extension.html | 4 ++-- docs/tags/flathub.html | 4 ++-- docs/tags/flatpak.html | 4 ++-- docs/tags/images.html | 4 ++-- docs/tags/installing.html | 4 ++-- docs/tags/kind.html | 4 ++-- docs/tags/lima.html | 4 ++-- docs/tags/linux.html | 4 ++-- docs/tags/mac-0-s.html | 4 ++-- docs/tags/mac-os.html | 4 ++-- docs/tags/macos.html | 4 ++-- docs/tags/migrating-from-docker.html | 4 ++-- docs/tags/migrating-to-kubernetes.html | 4 ++-- docs/tags/minikube.html | 4 ++-- docs/tags/onboarding.html | 4 ++-- docs/tags/openshift-local.html | 4 ++-- docs/tags/openshift.html | 4 ++-- docs/tags/podman-desktop.html | 4 ++-- docs/tags/podman.html | 4 ++-- docs/tags/pods.html | 4 ++-- docs/tags/proxy.html | 4 ++-- docs/tags/publishing.html | 4 ++-- docs/tags/registries.html | 4 ++-- docs/tags/restricted-environment.html | 4 ++-- docs/tags/scoop.html | 4 ++-- docs/tags/vpn.html | 4 ++-- docs/tags/when-clause.html | 4 ++-- docs/tags/windows.html | 4 ++-- docs/tags/winget.html | 4 ++-- docs/tags/writing.html | 4 ++-- docs/troubleshooting.html | 4 ++-- docs/troubleshooting/troubleshooting-openshift-local.html | 4 ++-- docs/troubleshooting/troubleshooting-podman-on-linux.html | 4 ++-- docs/troubleshooting/troubleshooting-podman-on-macos.html | 4 ++-- docs/troubleshooting/troubleshooting-podman-on-windows.html | 4 ++-- docs/troubleshooting/troubleshooting-podman.html | 4 ++-- docs/working-with-containers.html | 4 ++-- docs/working-with-containers/creating-a-pod.html | 4 ++-- docs/working-with-containers/images.html | 4 ++-- docs/working-with-containers/images/building-an-image.html | 4 ++-- docs/working-with-containers/images/pulling-an-image.html | 4 ++-- .../images/pushing-an-image-to-a-registry.html | 4 ++-- docs/working-with-containers/registries.html | 4 ++-- .../authenticating-to-a-preconfigured-registry.html | 4 ++-- .../working-with-containers/registries/insecure-registry.html | 4 ++-- docs/working-with-containers/starting-a-container.html | 4 ++-- .../switching-podman-machine-default-connection.html | 4 ++-- downloads.html | 4 ++-- downloads/linux.html | 4 ++-- downloads/macos.html | 4 ++-- downloads/windows.html | 4 ++-- extend.html | 4 ++-- features.html | 4 ++-- index.html | 4 ++-- search.html | 4 ++-- 160 files changed, 316 insertions(+), 316 deletions(-) create mode 100644 assets/js/1df93b7f.9b5882c1.js delete mode 100644 assets/js/1df93b7f.e2fef33f.js rename assets/js/{runtime~main.231fa618.js => runtime~main.39df3c7b.js} (99%) diff --git a/404.html b/404.html index aee87d935b4..46082955b34 100644 --- a/404.html +++ b/404.html @@ -13,13 +13,13 @@ - +
Skip to main content

Page Not Found

We could not find what you were looking for.

Please contact the owner of the site that linked you to the original URL and let them know their link is broken.

- + \ No newline at end of file diff --git a/assets/js/1df93b7f.9b5882c1.js b/assets/js/1df93b7f.9b5882c1.js new file mode 100644 index 00000000000..9755b010332 --- /dev/null +++ b/assets/js/1df93b7f.9b5882c1.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkdocs=self.webpackChunkdocs||[]).push([[3237],{33099:(e,t,a)=>{a.d(t,{Z:()=>r});var l=a(27378),n=a(76457);function r(e){let{children:t,fallback:a}=e;return(0,n.Z)()?l.createElement(l.Fragment,null,t?.()):a??null}},544:(e,t,a)=>{a.d(t,{Z:()=>r});var l=a(27378),n=a(161);const r=function(){function e(){if(!document?.documentElement)return;const e=document.documentElement;"dark"===e.dataset?.theme?(e.classList.add("dark"),setTimeout((()=>{e.classList.add("dark")}),100)):(e.classList.remove("dark"),setTimeout((()=>{e.classList.remove("dark")}),100))}return(0,l.useEffect)((()=>{n.Z.canUseDOM&&e()}),[n.Z.canUseDOM]),(0,l.useEffect)((()=>{if(!n.Z.canUseDOM)return;const t=new MutationObserver((t=>{t.forEach((t=>{"attributes"!==t.type||"data-rh"!==t.attributeName&&"data-theme"!==t.attributeName||e()}))}));return t.observe(document.documentElement,{attributes:!0,childList:!1,subtree:!1}),()=>{t.disconnect()}}),[n.Z.canUseDOM]),l.createElement("div",null)}},35223:(e,t,a)=>{a.r(t),a.d(t,{default:()=>k});var l=a(27378),n=a(20432),r=a(81884),s=a(33099),m=a(544),c=a(92739),i=a(9928),o=a(19374),d=a(14034),x=a(98948);function u(){let e,t="",a="macos";const n=navigator.userAgent;let s,m;return-1!==n.indexOf("Windows")?(t="Windows",a="windows",e="faWindows"):-1!==n.indexOf("Mac")?(t="macOS",a="macos",e="faApple"):-1!==n.indexOf("Linux")&&(t="Linux",a="linux",e="faLinux"),""!==t?(s=l.createElement("div",null,l.createElement(r.Z,{className:"no-underline hover:no-underline inline-flex text-white hover:text-white bg-violet-600 border-0 py-4 px-8 mt-6 mb-1 focus:outline-none hover:bg-violet-700 rounded text-lg",to:"/downloads/"+a},l.createElement(c.G,{size:"2x",icon:e,className:"px-2"})," Download Now"),l.createElement("caption",{className:"block mt-0 dark:text-gray-400"},"For ",l.createElement("strong",null,t)," ",l.createElement("em",null,"(browser-detected)"))),m=l.createElement("div",null,l.createElement(r.Z,{className:"underline font-semibold hover:underline ml-4 inline-flex py-2 px-6 my-4 focus:outline-none text-lg",to:"/downloads"},"Other downloads"))):s=l.createElement(r.Z,{className:"no-underline hover:no-underline inline-flex text-white hover:text-white bg-indigo-500 border-0 py-2 px-6 focus:outline-none hover:bg-indigo-600 rounded text-lg",to:"/downloads"},"Download Page"),l.createElement("div",{className:"flex justify-center flex-col"},s,m)}function f(){return l.createElement("div",{className:"flex justify-center"},l.createElement(r.Z,{className:"no-underline hover:no-underline inline-flex text-white hover:text-white bg-indigo-500 border-0 py-2 px-6 focus:outline-none hover:bg-indigo-600 rounded text-lg",to:"/downloads"},"Download Page"))}function g(){return l.createElement("section",{className:"text-gray-900 dark:text-gray-400 body-font"},l.createElement("div",{className:"container mx-auto flex px-5 pb-24 pt-4 items-center justify-center flex-col"},l.createElement("div",{className:"text-center lg:w-2/3 w-full bg-hero-pattern bg-no-repeat bg-center"},l.createElement("div",{className:"bg-white/30 dark:bg-transparent"},l.createElement("h1",{className:"title-font sm:text-4xl text-3xl lg:text-6xl mb-8 font-medium text-gray-900 dark:text-white"},"Containers and Kubernetes for application developers"),l.createElement("p",{className:"text-base md:text-lg"},"Podman Desktop is an open source graphical tool enabling you to seamlessly work with containers and Kubernetes from your local environment."),l.createElement("div",{className:"flex-none"},l.createElement(s.Z,{fallback:l.createElement(f,null)},(()=>l.createElement(u,null)))))),l.createElement("div",{className:"sm:pl-8 md:pl-12 lg:pl-36 text-center w-full"},l.createElement("img",{className:"sm:w-full md:w-full lg:w-10/12",alt:"Podman Desktop home page",src:"img/features/homepage.webp"}))))}function p(e){return l.createElement("div",null,l.createElement("p",{className:"inline-block px-3 py-px mb-4 text-xs font-semibold tracking-wider text-purple-800 uppercase rounded-full dark:bg-purple-400 bg-purple-400"},e.name))}function E(){return l.createElement("section",{className:"text-gray-900 dark:text-gray-400 dark:bg-charcoal-800 bg-zinc-100 body-font"},l.createElement("div",{className:"container px-5 py-24 mx-auto flex flex-wrap"},l.createElement("div",{className:"flex flex-col text-center w-full mb-5"},l.createElement(p,{name:"update"}),l.createElement("h2",{className:"max-w-lg mb-6 font-sans text-3xl font-light leading-none tracking-tight text-gray-900 dark:text-white sm:text-4xl md:mx-auto"},"Install and keep up to date ",l.createElement("span",{className:"font-bold"},"Podman"))),l.createElement("div",{className:"flex flex-col w-full text-center"},l.createElement("div",{className:"mx-10"},l.createElement(c.G,{size:"3x",icon:o.mHK,className:"ml-2 mb-4 text-gray-900 dark:text-gray-300"})),l.createElement("div",{className:"flex flex-col items-center"},l.createElement("p",{className:"leading-relaxed text-base"},"Install Podman and other dependencies directly from Podman Desktop if not yet installed."),l.createElement("p",{className:"leading-relaxed text-base"},"Check for updates and get notified about new changes."),l.createElement("p",{className:"leading-relaxed text-base"},"Available on"," ",l.createElement("a",{href:"/downloads/windows",className:"text-purple-600 dark:text-purple-400",target:"_blank"},"Windows")," ","and"," ",l.createElement("a",{href:"/downloads/macos",className:"text-purple-600 dark:text-purple-400",target:"_blank"},"macOS"),"!")))))}function h(){return l.createElement("section",{className:"text-gray-900 dark:text-gray-400 dark:bg-charcoal-600 bg-zinc-200 body-font"},l.createElement("div",{className:"container px-5 py-24 mx-auto flex flex-wrap"},l.createElement("div",{className:"flex flex-col text-center w-full mb-5"},l.createElement(p,{name:"extensibility"}),l.createElement("h2",{className:"max-w-lg mb-6 font-sans text-3xl font-light leading-none tracking-tight text-gray-900 dark:text-white sm:text-4xl md:mx-auto"},"Bring new features with Podman Desktop plug-ins or Docker Desktop Extensions.")),l.createElement("div",{className:"flex flex-col w-full text-center"},l.createElement("div",{className:"mx-10"},l.createElement(c.G,{size:"3x",icon:o.oso,className:"ml-2 mb-4 text-gray-900 dark:text-gray-300"})),l.createElement("ul",{className:"list-disc list-inside text-center"},l.createElement("li",null,"Container engines are plugged through extension points"),l.createElement("li",null,"JavaScript extensions can contribute new behaviour"),l.createElement("li",null,"Reuse existing extensions such as Trivy and OpenShift directly in Podman Desktop")),l.createElement("div",{className:"flex flex-col items-center"},l.createElement("div",{className:"text-left my-4"},l.createElement("p",{className:"-ml-5 text-base"},"Current Podman Desktop plugins: Podman, Docker, Lima, Kubernetes, and OpenShift Local with the Podman preset."))),l.createElement(d.Z,{className:"sm:w-full md:w-full lg:w-10/12 sm:pl-8 md:pl-12 lg:pl-24 text-center",alt:"Reuse Docker Desktop extensions",sources:{light:(0,x.Z)("img/ddextensions/dd-support.png"),dark:(0,x.Z)("img/ddextensions/dd-support.png")}}),l.createElement("div",{className:"flex flex-col items-center"},l.createElement(r.Z,{title:"Extend Podman Desktop",className:"no-underline hover:no-underline text-gray-900 dark:text-white hover:dark:text-violet-600 ",to:"/extend"},l.createElement("div",{className:"mt-3 text-purple-800 dark:text-purple-400 inline-flex items-center"},"Learn More",l.createElement("svg",{fill:"none",stroke:"currentColor","stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2",className:"w-4 h-4 ml-2",viewBox:"0 0 24 24"},l.createElement("path",{d:"M5 12h14M12 5l7 7-7 7"}))))))))}function b(){return l.createElement("section",{className:"text-gray-900 dark:text-gray-400 dark:bg-charcoal-800 bg-zinc-100 body-font py-24"},l.createElement("div",{className:"container px-5 mx-auto flex flex-wrap"},l.createElement("div",{className:"flex flex-col text-center w-full mb-5"},l.createElement(p,{name:"Configure"}),l.createElement("h2",{className:"max-w-lg mb-6 font-sans text-3xl font-bold leading-none tracking-tight text-gray-900 dark:text-white sm:text-4xl md:mx-auto"},"Multiple configuration options")),l.createElement("div",{className:"container px-5 pb-5 mx-auto"},l.createElement("div",{className:"flex flex-wrap sm:-m-4 -mx-4 -mb-10 -mt-4 md:space-y-0 space-y-6"},l.createElement("div",{className:"p-4 md:w-1/4 flex"},l.createElement("div",{className:"w-12 h-12 inline-flex items-center justify-center rounded-full bg-gray-700 text-purple-700 mb-4 flex-shrink-0"},l.createElement(c.G,{size:"2x",icon:o.Kb6,className:"w-6 h-6 "})),l.createElement("div",{className:"flex-grow pl-6"},l.createElement("h2",{className:"text-gray-900 dark:text-gray-100 text-lg title-font font-medium mb-2"},"Registries"),l.createElement("p",{className:"leading-relaxed text-base"},"Manage OCI registries. Add/edit/delete registries."))),l.createElement("div",{className:"p-4 md:w-1/4 flex"},l.createElement("div",{className:"w-12 h-12 inline-flex items-center justify-center rounded-full bg-gray-700 text-purple-700 mb-4 flex-shrink-0"},l.createElement(c.G,{size:"2x",icon:o.Kb6,className:"w-6 h-6 "})),l.createElement("div",{className:"flex-grow pl-6"},l.createElement("h2",{className:"text-gray-900 dark:text-gray-100 text-lg title-font font-medium mb-2"},"Proxy"),l.createElement("p",{className:"leading-relaxed text-base"},"Configure your proxy settings."))),l.createElement("div",{className:"p-4 md:w-1/4 flex"},l.createElement("div",{className:"w-12 h-12 inline-flex items-center justify-center rounded-full bg-gray-700 text-purple-700 mb-4 flex-shrink-0"},l.createElement(c.G,{size:"2x",icon:o.Kb6,className:"w-6 h-6 "})),l.createElement("div",{className:"flex-grow pl-6"},l.createElement("h2",{className:"text-gray-900 dark:text-gray-100 text-lg title-font font-medium mb-2"},"Resources Utilization"),l.createElement("p",{className:"leading-relaxed text-base"},"Configure CPU/Memory/Disk of Podman machines."))),l.createElement("div",{className:"p-4 md:w-1/4 flex"},l.createElement("div",{className:"w-12 h-12 inline-flex items-center justify-center rounded-full bg-gray-700 text-purple-700 mb-4 flex-shrink-0"},l.createElement(c.G,{size:"2x",icon:o.Kb6,className:"w-6 h-6 "})),l.createElement("div",{className:"flex-grow pl-6"},l.createElement("h2",{className:"text-gray-900 dark:text-gray-100 text-lg title-font font-medium mb-2"},"Container Engines"),l.createElement("p",{className:"leading-relaxed text-base"},"Handle multiple container engines at the same time: Podman, Docker.")))))))}function N(){return l.createElement("section",{className:"text-gray-900 dark:text-gray-400 dark:bg-charcoal-600 bg-zinc-200 body-font py-24"},l.createElement("div",{className:"container px-5 mx-auto flex flex-wrap"},l.createElement("div",{className:"flex flex-col text-center w-full mb-5"},l.createElement(p,{name:"enterprise"}),l.createElement("h2",{className:"max-w-lg mb-6 font-sans text-3xl font-bold leading-none tracking-tight text-gray-900 dark:text-white sm:text-4xl md:mx-auto"},"Enterprise ready")),l.createElement("div",{className:"container px-5 pb-5 mx-auto"},l.createElement("h1",{className:"sm:text-3xl text-2xl font-medium title-font text-center text-gray-900 dark:text-gray-100 mb-20"},"Match configuration options."),l.createElement("div",{className:"flex flex-wrap sm:-m-4 -mx-4 -mb-10 -mt-4 md:space-y-0 space-y-6"},l.createElement("div",{className:"p-4 md:w-1/3 flex"},l.createElement("div",{className:"w-12 h-12 inline-flex items-center justify-center rounded-full bg-gray-700 text-purple-700 mb-4 flex-shrink-0"},l.createElement(c.G,{size:"2x",icon:o.Ua$,className:"w-6 h-6 "})),l.createElement("div",{className:"flex-grow pl-6"},l.createElement("h2",{className:"text-gray-900 dark:text-gray-100 text-lg title-font font-medium mb-2"},"Code signing"),l.createElement("p",{className:"leading-relaxed text-base"},"Signed binaries for both macOS and Windows"))),l.createElement("div",{className:"p-4 md:w-1/3 flex"},l.createElement("div",{className:"w-12 h-12 inline-flex items-center justify-center rounded-full bg-gray-700 text-purple-800 mb-4 flex-shrink-0"},l.createElement(c.G,{size:"2x",icon:o.zoY,className:"w-6 h-6 "})),l.createElement("div",{className:"flex-grow pl-6"},l.createElement("h2",{className:"text-gray-900 dark:text-gray-100 text-lg title-font font-medium mb-2"},"Proxy"),l.createElement("p",{className:"leading-relaxed text-base"},"Configure proxy within the tool. Avoid any painful files to edit."))),l.createElement("div",{className:"p-4 md:w-1/3 flex"},l.createElement("div",{className:"w-12 h-12 inline-flex items-center justify-center rounded-full bg-gray-700 text-purple-800 mb-4 flex-shrink-0"},l.createElement(c.G,{size:"2x",icon:o.Kb6,className:"w-6 h-6 "})),l.createElement("div",{className:"flex-grow pl-6"},l.createElement("h2",{className:"text-gray-900 dark:text-gray-100 text-lg title-font font-medium mb-2"},"Registries"),l.createElement("p",{className:"leading-relaxed text-base"},"Manage OCI registries. Add/edit/delete registries.")))))))}function w(){return l.createElement("section",{className:"text-gray-900 dark:text-gray-400 dark:bg-charcoal-600 bg-zinc-200 body-font"},l.createElement("div",{className:"container px-5 py-24 mx-auto flex flex-wrap"},l.createElement("div",{className:"flex flex-col text-center w-full mb-5"},l.createElement("h2",{className:"max-w-lg mb-6 font-sans text-3xl font-bold leading-none tracking-tight text-gray-900 dark:text-white sm:text-4xl md:mx-auto"},"Available on Windows, Mac and Linux"),l.createElement("p",{className:"text-base text-gray-900 md:text-lg dark:text-gray-400"},"Use the same UI across different operating systems")),l.createElement("div",{className:"flex flex-wrap w-full justify-center"},l.createElement(r.Z,{title:"Download for Windows",className:"p-4 w-11/12 md:w-1/2 lg:w-1/3 no-underline hover:no-underline hover:text-white text-gray-900 dark:text-white",to:"/downloads/Windows"},l.createElement("div",{className:"flex rounded-lg h-full bg-zinc-100 hover:bg-purple-500 dark:hover:bg-purple-700 dark:bg-charcoal-800 bg-opacity-60 p-8 flex-col"},l.createElement("div",{className:"flex items-center mb-3 flex-col"},l.createElement(c.G,{size:"4x",icon:i.ts2}),l.createElement("div",{className:"inline-flex items-center justify-center rounded-full text-gray-900 dark:text-gray-400 flex-shrink-0"}),l.createElement("h2",{className:" text-lg title-font font-medium"}," Windows")),l.createElement("div",{className:"flex-grow"},l.createElement("div",{className:"flex-grow w-full"},l.createElement("p",{className:"text-base text-center"},"exe or setup.exe"))))),l.createElement(r.Z,{title:"Download for macOS",className:"no-underline hover:no-underline hover:text-white text-gray-900 dark:text-white p-4 w-11/12 md:w-1/2 lg:w-1/3",to:"/downloads/macOS"},l.createElement("div",{className:"flex rounded-lg h-full bg-zinc-100 hover:bg-purple-500 dark:hover:bg-purple-700 dark:bg-charcoal-800 bg-opacity-60 p-8 flex-col"},l.createElement("div",{className:"flex items-center mb-3 flex-col"},l.createElement(c.G,{size:"4x",icon:i.Av$}),l.createElement("div",{className:"inline-flex items-center justify-center rounded-full text-gray-900 dark:text-gray-400 flex-shrink-0"}),l.createElement("h2",{className:" text-lg title-font font-medium"}," macOS")),l.createElement("div",{className:"flex-grow w-full"},l.createElement("p",{className:"text-base text-center"},"arm64, x64 or unified dmg")))),l.createElement(r.Z,{title:"Download for Linux",className:"no-underline hover:no-underline hover:text-white text-gray-900 dark:text-white p-4 w-11/12 md:w-1/2 lg:w-1/3",to:"/downloads/Linux"},l.createElement("div",{className:"flex rounded-lg h-full bg-zinc-100 hover:bg-purple-500 dark:hover:bg-purple-700 dark:bg-charcoal-800 bg-opacity-60 p-8 flex-col"},l.createElement("div",{className:"flex items-center mb-3 flex-col"},l.createElement(c.G,{size:"4x",icon:i.qJE}),l.createElement("div",{className:"inline-flex items-center justify-center rounded-full text-gray-900 dark:text-gray-400 flex-shrink-0"}),l.createElement("h2",{className:" text-lg title-font font-medium"}," Linux")),l.createElement("div",{className:"flex-grow"},l.createElement("p",{className:"text-base text-center"},"Flatpak or AMD64 binary (tar.gz)")))))))}function v(){return l.createElement("section",{className:"text-gray-900 dark:text-gray-400 dark:bg-charcoal-800 bg-zinc-100 body-font py-24"},l.createElement("div",{className:"container px-5 mx-auto flex flex-wrap"},l.createElement("div",{className:"flex flex-col text-center w-full mb-5"},l.createElement(p,{name:"features"}),l.createElement("h2",{className:"max-w-lg mb-6 font-sans text-3xl font-bold leading-none tracking-tight text-gray-900 dark:text-white sm:text-4xl md:mx-auto"},"Build, run and manage containers.")),l.createElement("div",{className:"container px-5 pb-5 mx-auto"},l.createElement("div",{className:"flex flex-wrap sm:-m-4 -mx-4 -mb-10 -mt-4 md:space-y-0 space-y-6"},l.createElement("div",{className:"p-4 md:w-1/4 flex"},l.createElement("div",{className:"w-12 h-12 inline-flex items-center justify-center rounded-full bg-gray-700 text-purple-700 mb-4 flex-shrink-0"},l.createElement(c.G,{size:"2x",icon:o.Obi,className:"w-6 h-6 "})),l.createElement("div",{className:"flex-grow pl-6"},l.createElement("h2",{className:"text-gray-900 dark:text-gray-100 text-lg title-font font-medium mb-2"},"Build"),l.createElement("p",{className:"leading-relaxed text-base list-disc"},l.createElement(c.G,{icon:o.ESn,className:"text-purple-700 w-3 h-3 mt-1 mr-2"}),"Build images from Containerfile or Dockerfile"))),l.createElement("div",{className:"p-4 md:w-1/4 flex"},l.createElement("div",{className:"w-12 h-12 inline-flex items-center justify-center rounded-full bg-gray-700 text-purple-700 mb-4 flex-shrink-0"},l.createElement(c.G,{size:"2x",icon:o.tMT,className:"w-6 h-6 "})),l.createElement("div",{className:"flex-grow pl-6"},l.createElement("h2",{className:"text-gray-900 dark:text-gray-100 text-lg title-font font-medium mb-2"},"Run"),l.createElement("p",{className:"leading-relaxed text-base list-disc"},l.createElement(c.G,{icon:o.Bkj,className:"text-purple-700 w-3 h-3 mt-1 mr-2"}),"Pull images from remote registries"),l.createElement("p",{className:"leading-relaxed text-base list-disc"},l.createElement(c.G,{icon:o.ESn,className:"text-purple-700 w-3 h-3 mt-1 mr-2"}),"Start / Stop / Restart containers"))),l.createElement("div",{className:"p-4 md:w-1/4 flex"},l.createElement("div",{className:"w-12 h-12 inline-flex items-center justify-center rounded-full bg-gray-700 text-purple-800 mb-4 flex-shrink-0"},l.createElement(c.G,{size:"2x",icon:o.ESn,className:"w-6 h-6 "})),l.createElement("div",{className:"flex-grow pl-6"},l.createElement("h2",{className:"text-gray-900 dark:text-gray-100 text-lg title-font font-medium mb-2"},"Inspect"),l.createElement("p",{className:"leading-relaxed text-base list-disc"},l.createElement(c.G,{icon:o.tMT,className:"text-purple-700 w-3 h-3 mt-1 mr-2"}),"Get a terminal in your container"),l.createElement("p",{className:"leading-relaxed text-base list-disc"},l.createElement(c.G,{icon:o.tMT,className:"text-purple-700 w-3 h-3 mt-1 mr-2"}),"Inspect logs"))),l.createElement("div",{className:"p-4 md:w-1/4 flex"},l.createElement("div",{className:"w-12 h-12 inline-flex items-center justify-center rounded-full bg-gray-700 text-purple-800 mb-4 flex-shrink-0"},l.createElement(c.G,{size:"2x",icon:o.Bkj,className:"w-6 h-6 "})),l.createElement("div",{className:"flex-grow pl-6"},l.createElement("h2",{className:"text-gray-900 dark:text-gray-100 text-lg title-font font-medium mb-2"},"Push"),l.createElement("p",{className:"leading-relaxed text-base list-disc"},l.createElement(c.G,{icon:o.tMT,className:"text-purple-700 w-3 h-3 mt-1 mr-2"}),"Push images to OCI registries"),l.createElement("p",{className:"leading-relaxed text-base list-disc"},l.createElement(c.G,{icon:o.tMT,className:"text-purple-700 w-3 h-3 mt-1 mr-2"}),"Deploy & Test images on Kubernetes")))))),l.createElement("div",{className:"container px-5 mx-auto flex flex-wrap"},l.createElement("div",{className:"flex flex-col text-center w-full mb-5"},l.createElement(r.Z,{title:"Discover More",className:"no-underline hover:no-underline text-gray-900 dark:text-white hover:dark:text-violet-600 ",to:"/features"},l.createElement("div",{className:"mt-3 text-purple-800 dark:text-purple-400 inline-flex items-center"},"Discover More",l.createElement("svg",{fill:"none",stroke:"currentColor","stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2",className:"w-4 h-4 ml-2",viewBox:"0 0 24 24"},l.createElement("path",{d:"M5 12h14M12 5l7 7-7 7"})))))))}function y(){return l.createElement("section",{className:"text-gray-900 dark:text-gray-400 dark:bg-charcoal-600 bg-zinc-200 body-font py-24"},l.createElement("div",{className:"container px-5 mx-auto flex flex-wrap"},l.createElement("div",{className:"flex flex-col text-center w-full mb-5"},l.createElement(p,{name:"features"}),l.createElement("h2",{className:"max-w-lg mb-6 font-sans text-3xl font-bold leading-none tracking-tight text-gray-900 dark:text-white sm:text-4xl md:mx-auto"},"Work with Pods and Kubernetes")),l.createElement("div",{className:"container px-5 pb-5 mx-auto"},l.createElement("div",{className:"flex flex-wrap sm:-m-4 -mx-4 -mb-10 -mt-4 md:space-y-0 space-y-6"},l.createElement("div",{className:"p-4 md:w-1/2 flex"},l.createElement("div",{className:"w-12 h-12 inline-flex items-center justify-center rounded-full bg-gray-700 text-purple-700 mb-4 flex-shrink-0"},l.createElement(c.G,{size:"2x",icon:o.Obi,className:"w-6 h-6 "})),l.createElement("div",{className:"flex-grow pl-6"},l.createElement("h2",{className:"text-gray-900 dark:text-gray-100 text-lg title-font font-medium mb-2"},"Working with pods"),l.createElement("p",{className:"leading-relaxed text-base list-disc"},l.createElement(c.G,{icon:o.Bkj,className:"text-purple-700 w-3 h-3 mt-1 mr-2"}),l.createElement("a",{href:"/docs/working-with-containers/creating-a-pod"},"Create Pods from existing containers")),l.createElement("p",{className:"leading-relaxed text-base list-disc"},l.createElement(c.G,{icon:o.ESn,className:"text-purple-700 w-3 h-3 mt-1 mr-2"}),"Create, start, inspect and manage pods"))),l.createElement("div",{className:"p-4 md:w-1/2 flex"},l.createElement("div",{className:"w-12 h-12 inline-flex items-center justify-center rounded-full bg-gray-700 text-purple-800 mb-4 flex-shrink-0"},l.createElement(c.G,{size:"2x",icon:o.ESn,className:"w-6 h-6 "})),l.createElement("div",{className:"flex-grow pl-6"},l.createElement("h2",{className:"text-gray-900 dark:text-gray-100 text-lg title-font font-medium mb-2"},"Working with Kubernetes"),l.createElement("p",{className:"leading-relaxed text-base list-disc"},l.createElement(c.G,{icon:o.tMT,className:"text-purple-700 w-3 h-3 mt-1 mr-2"}),"Play Kubernetes YAML directly with Podman Engine"),l.createElement("p",{className:"leading-relaxed text-base list-disc"},l.createElement(c.G,{icon:o.tMT,className:"text-purple-700 w-3 h-3 mt-1 mr-2"}),"Generate Kubernetes YAML from pods"),l.createElement("p",{className:"leading-relaxed text-base list-disc"},l.createElement(c.G,{icon:o.tMT,className:"text-purple-700 w-3 h-3 mt-1 mr-2"}),l.createElement("a",{href:"/docs/kubernetes/deploying-a-pod-to-kubernetes"},"Deploy to existing Kubernetes environments")),l.createElement("p",{className:"leading-relaxed text-base list-disc"},l.createElement(c.G,{icon:o.tMT,className:"text-purple-700 w-3 h-3 mt-1 mr-2"}),l.createElement("a",{href:"/docs/kubernetes/kind"},"Running Kubernetes on your workstation with Kind and Podman"))))))),l.createElement("div",{className:"container px-5 mx-auto flex flex-wrap"},l.createElement("div",{className:"flex flex-col text-center w-full mb-5"},l.createElement(r.Z,{title:"Discover More",className:"no-underline hover:no-underline text-gray-900 dark:text-white hover:dark:text-violet-600 ",to:"/features"},l.createElement("div",{className:"mt-3 text-purple-800 dark:text-purple-400 inline-flex items-center"},"Discover More",l.createElement("svg",{fill:"none",stroke:"currentColor","stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2",className:"w-4 h-4 ml-2",viewBox:"0 0 24 24"},l.createElement("path",{d:"M5 12h14M12 5l7 7-7 7"})))))))}function k(){return l.createElement(n.Z,{title:"Podman Desktop - Containers and Kubernetes",description:"Podman Desktop - An open source graphical tool for developing on containers and Kubernetes"},l.createElement(m.Z,null),l.createElement(g,null),l.createElement(w,null),l.createElement(v,null),l.createElement(y,null),l.createElement(b,null),l.createElement(h,null),l.createElement(E,null),l.createElement(N,null))}}}]); \ No newline at end of file diff --git a/assets/js/1df93b7f.e2fef33f.js b/assets/js/1df93b7f.e2fef33f.js deleted file mode 100644 index 103ae1f3c9c..00000000000 --- a/assets/js/1df93b7f.e2fef33f.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkdocs=self.webpackChunkdocs||[]).push([[3237],{33099:(e,t,a)=>{a.d(t,{Z:()=>r});var l=a(27378),n=a(76457);function r(e){let{children:t,fallback:a}=e;return(0,n.Z)()?l.createElement(l.Fragment,null,t?.()):a??null}},544:(e,t,a)=>{a.d(t,{Z:()=>r});var l=a(27378),n=a(161);const r=function(){function e(){if(!document?.documentElement)return;const e=document.documentElement;"dark"===e.dataset?.theme?(e.classList.add("dark"),setTimeout((()=>{e.classList.add("dark")}),100)):(e.classList.remove("dark"),setTimeout((()=>{e.classList.remove("dark")}),100))}return(0,l.useEffect)((()=>{n.Z.canUseDOM&&e()}),[n.Z.canUseDOM]),(0,l.useEffect)((()=>{if(!n.Z.canUseDOM)return;const t=new MutationObserver((t=>{t.forEach((t=>{"attributes"!==t.type||"data-rh"!==t.attributeName&&"data-theme"!==t.attributeName||e()}))}));return t.observe(document.documentElement,{attributes:!0,childList:!1,subtree:!1}),()=>{t.disconnect()}}),[n.Z.canUseDOM]),l.createElement("div",null)}},35223:(e,t,a)=>{a.r(t),a.d(t,{default:()=>k});var l=a(27378),n=a(20432),r=a(81884),s=a(33099),m=a(544),c=a(92739),i=a(9928),o=a(19374),d=a(14034),x=a(98948);function u(){let e,t="";const a=navigator.userAgent;let n,s;return-1!==a.indexOf("Windows")?(t="Windows",url="windows",e="faWindows"):-1!==a.indexOf("Mac")?(t="macOS",url="macos",e="faApple"):-1!==a.indexOf("Linux")&&(t="Linux",url="linux",e="faLinux"),""!==t?(n=l.createElement("div",null,l.createElement(r.Z,{className:"no-underline hover:no-underline inline-flex text-white hover:text-white bg-violet-600 border-0 py-4 px-8 mt-6 mb-1 focus:outline-none hover:bg-violet-700 rounded text-lg",to:"/downloads/"+url},l.createElement(c.G,{size:"2x",icon:e,className:"px-2"})," Download Now"),l.createElement("caption",{className:"block mt-0 dark:text-gray-400"},"For ",l.createElement("strong",null,t)," ",l.createElement("em",null,"(browser-detected)"))),s=l.createElement("div",null,l.createElement(r.Z,{className:"underline font-semibold hover:underline ml-4 inline-flex py-2 px-6 my-4 focus:outline-none text-lg",to:"/downloads"},"Other downloads"))):n=l.createElement(r.Z,{className:"no-underline hover:no-underline inline-flex text-white hover:text-white bg-indigo-500 border-0 py-2 px-6 focus:outline-none hover:bg-indigo-600 rounded text-lg",to:"/downloads"},"Download Page"),l.createElement("div",{className:"flex justify-center flex-col"},n,s)}function f(){return l.createElement("div",{className:"flex justify-center"},l.createElement(r.Z,{className:"no-underline hover:no-underline inline-flex text-white hover:text-white bg-indigo-500 border-0 py-2 px-6 focus:outline-none hover:bg-indigo-600 rounded text-lg",to:"/downloads"},"Download Page"))}function g(){return l.createElement("section",{className:"text-gray-900 dark:text-gray-400 body-font"},l.createElement("div",{className:"container mx-auto flex px-5 pb-24 pt-4 items-center justify-center flex-col"},l.createElement("div",{className:"text-center lg:w-2/3 w-full bg-hero-pattern bg-no-repeat bg-center"},l.createElement("div",{className:"bg-white/30 dark:bg-transparent"},l.createElement("h1",{className:"title-font sm:text-4xl text-3xl lg:text-6xl mb-8 font-medium text-gray-900 dark:text-white"},"Containers and Kubernetes for application developers"),l.createElement("p",{className:"text-base md:text-lg"},"Podman Desktop is an open source graphical tool enabling you to seamlessly work with containers and Kubernetes from your local environment."),l.createElement("div",{className:"flex-none"},l.createElement(s.Z,{fallback:l.createElement(f,null)},(()=>l.createElement(u,null)))))),l.createElement("div",{className:"sm:pl-8 md:pl-12 lg:pl-36 text-center w-full"},l.createElement("img",{className:"sm:w-full md:w-full lg:w-10/12",alt:"Podman Desktop home page",src:"img/features/homepage.webp"}))))}function p(e){return l.createElement("div",null,l.createElement("p",{className:"inline-block px-3 py-px mb-4 text-xs font-semibold tracking-wider text-purple-800 uppercase rounded-full dark:bg-purple-400 bg-purple-400"},e.name))}function E(){return l.createElement("section",{className:"text-gray-900 dark:text-gray-400 dark:bg-charcoal-800 bg-zinc-100 body-font"},l.createElement("div",{className:"container px-5 py-24 mx-auto flex flex-wrap"},l.createElement("div",{className:"flex flex-col text-center w-full mb-5"},l.createElement(p,{name:"update"}),l.createElement("h2",{className:"max-w-lg mb-6 font-sans text-3xl font-light leading-none tracking-tight text-gray-900 dark:text-white sm:text-4xl md:mx-auto"},"Install and keep up to date ",l.createElement("span",{className:"font-bold"},"Podman"))),l.createElement("div",{className:"flex flex-col w-full text-center"},l.createElement("div",{className:"mx-10"},l.createElement(c.G,{size:"3x",icon:o.mHK,className:"ml-2 mb-4 text-gray-900 dark:text-gray-300"})),l.createElement("div",{className:"flex flex-col items-center"},l.createElement("p",{className:"leading-relaxed text-base"},"Install Podman and other dependencies directly from Podman Desktop if not yet installed."),l.createElement("p",{className:"leading-relaxed text-base"},"Check for updates and get notified about new changes."),l.createElement("p",{className:"leading-relaxed text-base"},"Available on"," ",l.createElement("a",{href:"/downloads/windows",className:"text-purple-600 dark:text-purple-400",target:"_blank"},"Windows")," ","and"," ",l.createElement("a",{href:"/downloads/macos",className:"text-purple-600 dark:text-purple-400",target:"_blank"},"macOS"),"!")))))}function h(){return l.createElement("section",{className:"text-gray-900 dark:text-gray-400 dark:bg-charcoal-600 bg-zinc-200 body-font"},l.createElement("div",{className:"container px-5 py-24 mx-auto flex flex-wrap"},l.createElement("div",{className:"flex flex-col text-center w-full mb-5"},l.createElement(p,{name:"extensibility"}),l.createElement("h2",{className:"max-w-lg mb-6 font-sans text-3xl font-light leading-none tracking-tight text-gray-900 dark:text-white sm:text-4xl md:mx-auto"},"Bring new features with Podman Desktop plug-ins or Docker Desktop Extensions.")),l.createElement("div",{className:"flex flex-col w-full text-center"},l.createElement("div",{className:"mx-10"},l.createElement(c.G,{size:"3x",icon:o.oso,className:"ml-2 mb-4 text-gray-900 dark:text-gray-300"})),l.createElement("ul",{className:"list-disc list-inside text-center"},l.createElement("li",null,"Container engines are plugged through extension points"),l.createElement("li",null,"JavaScript extensions can contribute new behaviour"),l.createElement("li",null,"Reuse existing extensions such as Trivy and OpenShift directly in Podman Desktop")),l.createElement("div",{className:"flex flex-col items-center"},l.createElement("div",{className:"text-left my-4"},l.createElement("p",{className:"-ml-5 text-base"},"Current Podman Desktop plugins: Podman, Docker, Lima, Kubernetes, and OpenShift Local with the Podman preset."))),l.createElement(d.Z,{className:"sm:w-full md:w-full lg:w-10/12 sm:pl-8 md:pl-12 lg:pl-24 text-center",alt:"Reuse Docker Desktop extensions",sources:{light:(0,x.Z)("img/ddextensions/dd-support.png"),dark:(0,x.Z)("img/ddextensions/dd-support.png")}}),l.createElement("div",{className:"flex flex-col items-center"},l.createElement(r.Z,{title:"Extend Podman Desktop",className:"no-underline hover:no-underline text-gray-900 dark:text-white hover:dark:text-violet-600 ",to:"/extend"},l.createElement("div",{className:"mt-3 text-purple-800 dark:text-purple-400 inline-flex items-center"},"Learn More",l.createElement("svg",{fill:"none",stroke:"currentColor","stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2",className:"w-4 h-4 ml-2",viewBox:"0 0 24 24"},l.createElement("path",{d:"M5 12h14M12 5l7 7-7 7"}))))))))}function b(){return l.createElement("section",{className:"text-gray-900 dark:text-gray-400 dark:bg-charcoal-800 bg-zinc-100 body-font py-24"},l.createElement("div",{className:"container px-5 mx-auto flex flex-wrap"},l.createElement("div",{className:"flex flex-col text-center w-full mb-5"},l.createElement(p,{name:"Configure"}),l.createElement("h2",{className:"max-w-lg mb-6 font-sans text-3xl font-bold leading-none tracking-tight text-gray-900 dark:text-white sm:text-4xl md:mx-auto"},"Multiple configuration options")),l.createElement("div",{className:"container px-5 pb-5 mx-auto"},l.createElement("div",{className:"flex flex-wrap sm:-m-4 -mx-4 -mb-10 -mt-4 md:space-y-0 space-y-6"},l.createElement("div",{className:"p-4 md:w-1/4 flex"},l.createElement("div",{className:"w-12 h-12 inline-flex items-center justify-center rounded-full bg-gray-700 text-purple-700 mb-4 flex-shrink-0"},l.createElement(c.G,{size:"2x",icon:o.Kb6,className:"w-6 h-6 "})),l.createElement("div",{className:"flex-grow pl-6"},l.createElement("h2",{className:"text-gray-900 dark:text-gray-100 text-lg title-font font-medium mb-2"},"Registries"),l.createElement("p",{className:"leading-relaxed text-base"},"Manage OCI registries. Add/edit/delete registries."))),l.createElement("div",{className:"p-4 md:w-1/4 flex"},l.createElement("div",{className:"w-12 h-12 inline-flex items-center justify-center rounded-full bg-gray-700 text-purple-700 mb-4 flex-shrink-0"},l.createElement(c.G,{size:"2x",icon:o.Kb6,className:"w-6 h-6 "})),l.createElement("div",{className:"flex-grow pl-6"},l.createElement("h2",{className:"text-gray-900 dark:text-gray-100 text-lg title-font font-medium mb-2"},"Proxy"),l.createElement("p",{className:"leading-relaxed text-base"},"Configure your proxy settings."))),l.createElement("div",{className:"p-4 md:w-1/4 flex"},l.createElement("div",{className:"w-12 h-12 inline-flex items-center justify-center rounded-full bg-gray-700 text-purple-700 mb-4 flex-shrink-0"},l.createElement(c.G,{size:"2x",icon:o.Kb6,className:"w-6 h-6 "})),l.createElement("div",{className:"flex-grow pl-6"},l.createElement("h2",{className:"text-gray-900 dark:text-gray-100 text-lg title-font font-medium mb-2"},"Resources Utilization"),l.createElement("p",{className:"leading-relaxed text-base"},"Configure CPU/Memory/Disk of Podman machines."))),l.createElement("div",{className:"p-4 md:w-1/4 flex"},l.createElement("div",{className:"w-12 h-12 inline-flex items-center justify-center rounded-full bg-gray-700 text-purple-700 mb-4 flex-shrink-0"},l.createElement(c.G,{size:"2x",icon:o.Kb6,className:"w-6 h-6 "})),l.createElement("div",{className:"flex-grow pl-6"},l.createElement("h2",{className:"text-gray-900 dark:text-gray-100 text-lg title-font font-medium mb-2"},"Container Engines"),l.createElement("p",{className:"leading-relaxed text-base"},"Handle multiple container engines at the same time: Podman, Docker.")))))))}function N(){return l.createElement("section",{className:"text-gray-900 dark:text-gray-400 dark:bg-charcoal-600 bg-zinc-200 body-font py-24"},l.createElement("div",{className:"container px-5 mx-auto flex flex-wrap"},l.createElement("div",{className:"flex flex-col text-center w-full mb-5"},l.createElement(p,{name:"enterprise"}),l.createElement("h2",{className:"max-w-lg mb-6 font-sans text-3xl font-bold leading-none tracking-tight text-gray-900 dark:text-white sm:text-4xl md:mx-auto"},"Enterprise ready")),l.createElement("div",{className:"container px-5 pb-5 mx-auto"},l.createElement("h1",{className:"sm:text-3xl text-2xl font-medium title-font text-center text-gray-900 dark:text-gray-100 mb-20"},"Match configuration options."),l.createElement("div",{className:"flex flex-wrap sm:-m-4 -mx-4 -mb-10 -mt-4 md:space-y-0 space-y-6"},l.createElement("div",{className:"p-4 md:w-1/3 flex"},l.createElement("div",{className:"w-12 h-12 inline-flex items-center justify-center rounded-full bg-gray-700 text-purple-700 mb-4 flex-shrink-0"},l.createElement(c.G,{size:"2x",icon:o.Ua$,className:"w-6 h-6 "})),l.createElement("div",{className:"flex-grow pl-6"},l.createElement("h2",{className:"text-gray-900 dark:text-gray-100 text-lg title-font font-medium mb-2"},"Code signing"),l.createElement("p",{className:"leading-relaxed text-base"},"Signed binaries for both macOS and Windows"))),l.createElement("div",{className:"p-4 md:w-1/3 flex"},l.createElement("div",{className:"w-12 h-12 inline-flex items-center justify-center rounded-full bg-gray-700 text-purple-800 mb-4 flex-shrink-0"},l.createElement(c.G,{size:"2x",icon:o.zoY,className:"w-6 h-6 "})),l.createElement("div",{className:"flex-grow pl-6"},l.createElement("h2",{className:"text-gray-900 dark:text-gray-100 text-lg title-font font-medium mb-2"},"Proxy"),l.createElement("p",{className:"leading-relaxed text-base"},"Configure proxy within the tool. Avoid any painful files to edit."))),l.createElement("div",{className:"p-4 md:w-1/3 flex"},l.createElement("div",{className:"w-12 h-12 inline-flex items-center justify-center rounded-full bg-gray-700 text-purple-800 mb-4 flex-shrink-0"},l.createElement(c.G,{size:"2x",icon:o.Kb6,className:"w-6 h-6 "})),l.createElement("div",{className:"flex-grow pl-6"},l.createElement("h2",{className:"text-gray-900 dark:text-gray-100 text-lg title-font font-medium mb-2"},"Registries"),l.createElement("p",{className:"leading-relaxed text-base"},"Manage OCI registries. Add/edit/delete registries.")))))))}function w(){return l.createElement("section",{className:"text-gray-900 dark:text-gray-400 dark:bg-charcoal-600 bg-zinc-200 body-font"},l.createElement("div",{className:"container px-5 py-24 mx-auto flex flex-wrap"},l.createElement("div",{className:"flex flex-col text-center w-full mb-5"},l.createElement("h2",{className:"max-w-lg mb-6 font-sans text-3xl font-bold leading-none tracking-tight text-gray-900 dark:text-white sm:text-4xl md:mx-auto"},"Available on Windows, Mac and Linux"),l.createElement("p",{className:"text-base text-gray-900 md:text-lg dark:text-gray-400"},"Use the same UI across different operating systems")),l.createElement("div",{className:"flex flex-wrap w-full justify-center"},l.createElement(r.Z,{title:"Download for Windows",className:"p-4 w-11/12 md:w-1/2 lg:w-1/3 no-underline hover:no-underline hover:text-white text-gray-900 dark:text-white",to:"/downloads/Windows"},l.createElement("div",{className:"flex rounded-lg h-full bg-zinc-100 hover:bg-purple-500 dark:hover:bg-purple-700 dark:bg-charcoal-800 bg-opacity-60 p-8 flex-col"},l.createElement("div",{className:"flex items-center mb-3 flex-col"},l.createElement(c.G,{size:"4x",icon:i.ts2}),l.createElement("div",{className:"inline-flex items-center justify-center rounded-full text-gray-900 dark:text-gray-400 flex-shrink-0"}),l.createElement("h2",{className:" text-lg title-font font-medium"}," Windows")),l.createElement("div",{className:"flex-grow"},l.createElement("div",{className:"flex-grow w-full"},l.createElement("p",{className:"text-base text-center"},"exe or setup.exe"))))),l.createElement(r.Z,{title:"Download for macOS",className:"no-underline hover:no-underline hover:text-white text-gray-900 dark:text-white p-4 w-11/12 md:w-1/2 lg:w-1/3",to:"/downloads/macOS"},l.createElement("div",{className:"flex rounded-lg h-full bg-zinc-100 hover:bg-purple-500 dark:hover:bg-purple-700 dark:bg-charcoal-800 bg-opacity-60 p-8 flex-col"},l.createElement("div",{className:"flex items-center mb-3 flex-col"},l.createElement(c.G,{size:"4x",icon:i.Av$}),l.createElement("div",{className:"inline-flex items-center justify-center rounded-full text-gray-900 dark:text-gray-400 flex-shrink-0"}),l.createElement("h2",{className:" text-lg title-font font-medium"}," macOS")),l.createElement("div",{className:"flex-grow w-full"},l.createElement("p",{className:"text-base text-center"},"arm64, x64 or unified dmg")))),l.createElement(r.Z,{title:"Download for Linux",className:"no-underline hover:no-underline hover:text-white text-gray-900 dark:text-white p-4 w-11/12 md:w-1/2 lg:w-1/3",to:"/downloads/Linux"},l.createElement("div",{className:"flex rounded-lg h-full bg-zinc-100 hover:bg-purple-500 dark:hover:bg-purple-700 dark:bg-charcoal-800 bg-opacity-60 p-8 flex-col"},l.createElement("div",{className:"flex items-center mb-3 flex-col"},l.createElement(c.G,{size:"4x",icon:i.qJE}),l.createElement("div",{className:"inline-flex items-center justify-center rounded-full text-gray-900 dark:text-gray-400 flex-shrink-0"}),l.createElement("h2",{className:" text-lg title-font font-medium"}," Linux")),l.createElement("div",{className:"flex-grow"},l.createElement("p",{className:"text-base text-center"},"Flatpak or AMD64 binary (tar.gz)")))))))}function v(){return l.createElement("section",{className:"text-gray-900 dark:text-gray-400 dark:bg-charcoal-800 bg-zinc-100 body-font py-24"},l.createElement("div",{className:"container px-5 mx-auto flex flex-wrap"},l.createElement("div",{className:"flex flex-col text-center w-full mb-5"},l.createElement(p,{name:"features"}),l.createElement("h2",{className:"max-w-lg mb-6 font-sans text-3xl font-bold leading-none tracking-tight text-gray-900 dark:text-white sm:text-4xl md:mx-auto"},"Build, run and manage containers.")),l.createElement("div",{className:"container px-5 pb-5 mx-auto"},l.createElement("div",{className:"flex flex-wrap sm:-m-4 -mx-4 -mb-10 -mt-4 md:space-y-0 space-y-6"},l.createElement("div",{className:"p-4 md:w-1/4 flex"},l.createElement("div",{className:"w-12 h-12 inline-flex items-center justify-center rounded-full bg-gray-700 text-purple-700 mb-4 flex-shrink-0"},l.createElement(c.G,{size:"2x",icon:o.Obi,className:"w-6 h-6 "})),l.createElement("div",{className:"flex-grow pl-6"},l.createElement("h2",{className:"text-gray-900 dark:text-gray-100 text-lg title-font font-medium mb-2"},"Build"),l.createElement("p",{className:"leading-relaxed text-base list-disc"},l.createElement(c.G,{icon:o.ESn,className:"text-purple-700 w-3 h-3 mt-1 mr-2"}),"Build images from Containerfile or Dockerfile"))),l.createElement("div",{className:"p-4 md:w-1/4 flex"},l.createElement("div",{className:"w-12 h-12 inline-flex items-center justify-center rounded-full bg-gray-700 text-purple-700 mb-4 flex-shrink-0"},l.createElement(c.G,{size:"2x",icon:o.tMT,className:"w-6 h-6 "})),l.createElement("div",{className:"flex-grow pl-6"},l.createElement("h2",{className:"text-gray-900 dark:text-gray-100 text-lg title-font font-medium mb-2"},"Run"),l.createElement("p",{className:"leading-relaxed text-base list-disc"},l.createElement(c.G,{icon:o.Bkj,className:"text-purple-700 w-3 h-3 mt-1 mr-2"}),"Pull images from remote registries"),l.createElement("p",{className:"leading-relaxed text-base list-disc"},l.createElement(c.G,{icon:o.ESn,className:"text-purple-700 w-3 h-3 mt-1 mr-2"}),"Start / Stop / Restart containers"))),l.createElement("div",{className:"p-4 md:w-1/4 flex"},l.createElement("div",{className:"w-12 h-12 inline-flex items-center justify-center rounded-full bg-gray-700 text-purple-800 mb-4 flex-shrink-0"},l.createElement(c.G,{size:"2x",icon:o.ESn,className:"w-6 h-6 "})),l.createElement("div",{className:"flex-grow pl-6"},l.createElement("h2",{className:"text-gray-900 dark:text-gray-100 text-lg title-font font-medium mb-2"},"Inspect"),l.createElement("p",{className:"leading-relaxed text-base list-disc"},l.createElement(c.G,{icon:o.tMT,className:"text-purple-700 w-3 h-3 mt-1 mr-2"}),"Get a terminal in your container"),l.createElement("p",{className:"leading-relaxed text-base list-disc"},l.createElement(c.G,{icon:o.tMT,className:"text-purple-700 w-3 h-3 mt-1 mr-2"}),"Inspect logs"))),l.createElement("div",{className:"p-4 md:w-1/4 flex"},l.createElement("div",{className:"w-12 h-12 inline-flex items-center justify-center rounded-full bg-gray-700 text-purple-800 mb-4 flex-shrink-0"},l.createElement(c.G,{size:"2x",icon:o.Bkj,className:"w-6 h-6 "})),l.createElement("div",{className:"flex-grow pl-6"},l.createElement("h2",{className:"text-gray-900 dark:text-gray-100 text-lg title-font font-medium mb-2"},"Push"),l.createElement("p",{className:"leading-relaxed text-base list-disc"},l.createElement(c.G,{icon:o.tMT,className:"text-purple-700 w-3 h-3 mt-1 mr-2"}),"Push images to OCI registries"),l.createElement("p",{className:"leading-relaxed text-base list-disc"},l.createElement(c.G,{icon:o.tMT,className:"text-purple-700 w-3 h-3 mt-1 mr-2"}),"Deploy & Test images on Kubernetes")))))),l.createElement("div",{className:"container px-5 mx-auto flex flex-wrap"},l.createElement("div",{className:"flex flex-col text-center w-full mb-5"},l.createElement(r.Z,{title:"Discover More",className:"no-underline hover:no-underline text-gray-900 dark:text-white hover:dark:text-violet-600 ",to:"/features"},l.createElement("div",{className:"mt-3 text-purple-800 dark:text-purple-400 inline-flex items-center"},"Discover More",l.createElement("svg",{fill:"none",stroke:"currentColor","stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2",className:"w-4 h-4 ml-2",viewBox:"0 0 24 24"},l.createElement("path",{d:"M5 12h14M12 5l7 7-7 7"})))))))}function y(){return l.createElement("section",{className:"text-gray-900 dark:text-gray-400 dark:bg-charcoal-600 bg-zinc-200 body-font py-24"},l.createElement("div",{className:"container px-5 mx-auto flex flex-wrap"},l.createElement("div",{className:"flex flex-col text-center w-full mb-5"},l.createElement(p,{name:"features"}),l.createElement("h2",{className:"max-w-lg mb-6 font-sans text-3xl font-bold leading-none tracking-tight text-gray-900 dark:text-white sm:text-4xl md:mx-auto"},"Work with Pods and Kubernetes")),l.createElement("div",{className:"container px-5 pb-5 mx-auto"},l.createElement("div",{className:"flex flex-wrap sm:-m-4 -mx-4 -mb-10 -mt-4 md:space-y-0 space-y-6"},l.createElement("div",{className:"p-4 md:w-1/2 flex"},l.createElement("div",{className:"w-12 h-12 inline-flex items-center justify-center rounded-full bg-gray-700 text-purple-700 mb-4 flex-shrink-0"},l.createElement(c.G,{size:"2x",icon:o.Obi,className:"w-6 h-6 "})),l.createElement("div",{className:"flex-grow pl-6"},l.createElement("h2",{className:"text-gray-900 dark:text-gray-100 text-lg title-font font-medium mb-2"},"Working with pods"),l.createElement("p",{className:"leading-relaxed text-base list-disc"},l.createElement(c.G,{icon:o.Bkj,className:"text-purple-700 w-3 h-3 mt-1 mr-2"}),l.createElement("a",{href:"/docs/working-with-containers/creating-a-pod"},"Create Pods from existing containers")),l.createElement("p",{className:"leading-relaxed text-base list-disc"},l.createElement(c.G,{icon:o.ESn,className:"text-purple-700 w-3 h-3 mt-1 mr-2"}),"Create, start, inspect and manage pods"))),l.createElement("div",{className:"p-4 md:w-1/2 flex"},l.createElement("div",{className:"w-12 h-12 inline-flex items-center justify-center rounded-full bg-gray-700 text-purple-800 mb-4 flex-shrink-0"},l.createElement(c.G,{size:"2x",icon:o.ESn,className:"w-6 h-6 "})),l.createElement("div",{className:"flex-grow pl-6"},l.createElement("h2",{className:"text-gray-900 dark:text-gray-100 text-lg title-font font-medium mb-2"},"Working with Kubernetes"),l.createElement("p",{className:"leading-relaxed text-base list-disc"},l.createElement(c.G,{icon:o.tMT,className:"text-purple-700 w-3 h-3 mt-1 mr-2"}),"Play Kubernetes YAML directly with Podman Engine"),l.createElement("p",{className:"leading-relaxed text-base list-disc"},l.createElement(c.G,{icon:o.tMT,className:"text-purple-700 w-3 h-3 mt-1 mr-2"}),"Generate Kubernetes YAML from pods"),l.createElement("p",{className:"leading-relaxed text-base list-disc"},l.createElement(c.G,{icon:o.tMT,className:"text-purple-700 w-3 h-3 mt-1 mr-2"}),l.createElement("a",{href:"/docs/kubernetes/deploying-a-pod-to-kubernetes"},"Deploy to existing Kubernetes environments")),l.createElement("p",{className:"leading-relaxed text-base list-disc"},l.createElement(c.G,{icon:o.tMT,className:"text-purple-700 w-3 h-3 mt-1 mr-2"}),l.createElement("a",{href:"/docs/kubernetes/kind"},"Running Kubernetes on your workstation with Kind and Podman"))))))),l.createElement("div",{className:"container px-5 mx-auto flex flex-wrap"},l.createElement("div",{className:"flex flex-col text-center w-full mb-5"},l.createElement(r.Z,{title:"Discover More",className:"no-underline hover:no-underline text-gray-900 dark:text-white hover:dark:text-violet-600 ",to:"/features"},l.createElement("div",{className:"mt-3 text-purple-800 dark:text-purple-400 inline-flex items-center"},"Discover More",l.createElement("svg",{fill:"none",stroke:"currentColor","stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2",className:"w-4 h-4 ml-2",viewBox:"0 0 24 24"},l.createElement("path",{d:"M5 12h14M12 5l7 7-7 7"})))))))}function k(){return l.createElement(n.Z,{title:"Podman Desktop - Containers and Kubernetes",description:"Podman Desktop - An open source graphical tool for developing on containers and Kubernetes"},l.createElement(m.Z,null),l.createElement(g,null),l.createElement(w,null),l.createElement(v,null),l.createElement(y,null),l.createElement(b,null),l.createElement(h,null),l.createElement(E,null),l.createElement(N,null))}}}]); \ No newline at end of file diff --git a/assets/js/runtime~main.231fa618.js b/assets/js/runtime~main.39df3c7b.js similarity index 99% rename from assets/js/runtime~main.231fa618.js rename to assets/js/runtime~main.39df3c7b.js index 2b1401cb831..cb36d049b48 100644 --- a/assets/js/runtime~main.231fa618.js +++ b/assets/js/runtime~main.39df3c7b.js @@ -1 +1 @@ -(()=>{"use strict";var e,f,a,c,b,d={},t={};function r(e){var f=t[e];if(void 0!==f)return f.exports;var a=t[e]={exports:{}};return d[e].call(a.exports,a,a.exports,r),a.exports}r.m=d,e=[],r.O=(f,a,c,b)=>{if(!a){var d=1/0;for(i=0;i=b)&&Object.keys(r.O).every((e=>r.O[e](a[o])))?a.splice(o--,1):(t=!1,b0&&e[i-1][2]>b;i--)e[i]=e[i-1];e[i]=[a,c,b]},r.n=e=>{var f=e&&e.__esModule?()=>e.default:()=>e;return r.d(f,{a:f}),f},a=Object.getPrototypeOf?e=>Object.getPrototypeOf(e):e=>e.__proto__,r.t=function(e,c){if(1&c&&(e=this(e)),8&c)return e;if("object"==typeof e&&e){if(4&c&&e.__esModule)return e;if(16&c&&"function"==typeof e.then)return e}var b=Object.create(null);r.r(b);var d={};f=f||[null,a({}),a([]),a(a)];for(var t=2&c&&e;"object"==typeof t&&!~f.indexOf(t);t=a(t))Object.getOwnPropertyNames(t).forEach((f=>d[f]=()=>e[f]));return d.default=()=>e,r.d(b,d),b},r.d=(e,f)=>{for(var a in f)r.o(f,a)&&!r.o(e,a)&&Object.defineProperty(e,a,{enumerable:!0,get:f[a]})},r.f={},r.e=e=>Promise.all(Object.keys(r.f).reduce(((f,a)=>(r.f[a](e,f),f)),[])),r.u=e=>"assets/js/"+({10:"33942509",24:"902d9f40",53:"935f2afb",70:"86f2a982",114:"e665718d",138:"54590fd2",182:"c276ecb2",205:"83d480e9",397:"6194ac84",465:"f7b7f9b7",506:"9aa62c0e",522:"308aae28",533:"b2b675dd",563:"c685778b",592:"b39cdcf9",628:"2c93bfff",649:"512fbd77",692:"6b600968",743:"61d4c13a",759:"e5878f42",809:"840a98fb",873:"cabda5f8",899:"b985118d",921:"c37b4a03",944:"b2e1a0c8",945:"df322e14",1021:"1a0737b6",1032:"a67ca768",1074:"9e8f4e9c",1297:"34cf6fc7",1335:"7327116e",1342:"a766a857",1441:"382c5d2b",1476:"44f02f2c",1477:"b2f554cd",1625:"de311ed4",1676:"819ef483",1705:"94fb813f",1713:"a7023ddc",1724:"5087625a",1830:"b00bc883",1981:"b799648a",2079:"1a16e8bf",2082:"e85ba0e6",2173:"36eac8b2",2178:"ba322490",2217:"d7fbbe43",2284:"4117ac4b",2323:"6c80b6fe",2364:"8cdb21e1",2385:"8f92bc29",2472:"65a10ffa",2535:"814f3328",2549:"5c63ba15",2557:"28726be2",2609:"6269f1c0",2667:"368cce37",2778:"608238a8",2896:"abc85917",2938:"c95aa39f",2965:"4384f6ba",3010:"56c3a9b2",3089:"a6aa9e1f",3154:"c6346fcf",3163:"232c546d",3207:"6603ef13",3232:"1f35373c",3237:"1df93b7f",3259:"03ccf92d",3296:"181ef600",3317:"846a5e19",3324:"1ce91f4c",3414:"35a7a45c",3505:"72486833",3584:"ed75cfcb",3608:"9e4087bc",3636:"8b4dd820",3691:"7be672a3",3714:"894e67a6",3751:"3720c009",3820:"a5e1f61e",3870:"5df556a2",3879:"2d629ea6",3952:"1b710012",3973:"f523fb3f",4013:"01a85c17",4059:"9cb03f5d",4112:"9f02b2b5",4121:"55960ee5",4157:"83e10f72",4356:"a9a76bf7",4386:"ae79aff5",4551:"3b161fd7",4617:"95366386",4735:"0c1dc3b8",4781:"12f1535e",4929:"330dfcdb",5018:"cd509849",5076:"b4561fd7",5240:"22de4147",5248:"6101b3fc",5375:"97615df2",5376:"bebbf51e",5468:"b9bde34b",5478:"df1d8f19",5591:"c9181a9f",5625:"657ac0bc",5708:"f0057c03",5776:"f0e3a130",5803:"ff8f5ed0",5974:"f20fb67e",6026:"51dec273",6038:"c9c860ee",6049:"f213dd13",6082:"a233b66e",6088:"88efc5aa",6103:"ccc49370",6120:"d4840880",6308:"e8dc4d98",6328:"c0d19596",6536:"3ed6e2e9",6608:"5099f3e0",6623:"b104dd1e",6690:"4816649b",6692:"2ae2e7fe",6719:"2e0c1e3c",6766:"e5638e51",6843:"9f97f9d1",7007:"8593ff01",7034:"3e03f778",7134:"0b40a488",7138:"38a042e4",7141:"b5abacaa",7149:"822c343e",7220:"7591d420",7239:"d9e85037",7251:"ba5b9f11",7274:"be315de3",7350:"8bedf5f0",7363:"583db3ef",7365:"652d909c",7366:"75281220",7370:"dba48714",7377:"708d858d",7438:"9c021584",7480:"eb17771c",7526:"016d7603",7536:"f6e0e63c",7573:"48b6ff5f",7622:"dbbb982f",7653:"31de1779",7679:"83245ae6",7698:"cd23aec9",7714:"7bdcd7a7",7739:"3ede2625",7741:"7d88b63f",7759:"ff38b1ce",7847:"43b416ef",7881:"2658ced2",7918:"17896441",7920:"1a4e3797",8065:"53f302bb",8145:"006e489c",8215:"1cfced13",8221:"6af14956",8242:"cbe6e75d",8262:"059d1c6a",8290:"3fe48f60",8445:"99245987",8502:"b4657d81",8514:"d651e2ee",8533:"f3d54061",8566:"9dce5486",8610:"6875c492",8800:"e6fb1369",8811:"3289a752",8860:"0d040286",8893:"ba1dc56d",8970:"68b843fc",8989:"d4bf7e47",9019:"771d7520",9043:"473de3ed",9106:"72dd8f7e",9133:"02e265ea",9179:"79551407",9209:"d2117a98",9341:"a35cf155",9372:"07f59c2a",9387:"b0f1c099",9395:"415c4e0e",9469:"3b85f227",9514:"1be78505",9671:"0e384e19",9817:"4f561e31",9924:"df203c0f",9944:"08570680"}[e]||e)+"."+{10:"b3b53e4f",24:"c9c02d31",53:"3ed5b938",70:"6082feaf",114:"22a38c18",138:"01cf4745",182:"c229eebf",205:"7ed9f2aa",397:"727a973d",465:"1cbd3a08",506:"3f0bed63",522:"d7cd5912",533:"b092fb30",563:"4744a638",592:"20325692",628:"7140d154",649:"10a887e2",692:"99e3d625",743:"89c00deb",759:"721f9cf0",809:"06decfd8",873:"919ad21c",899:"7e8cb215",921:"f0615854",944:"a49ec1c2",945:"faae8bea",1021:"4ab01d95",1032:"22c424dc",1074:"ead1b706",1297:"dee27ee5",1335:"b2b0cf3e",1342:"478736f2",1441:"dfb53e35",1476:"3a468864",1477:"f9bb77ec",1625:"35d33fff",1676:"8a2bafc1",1705:"fa2462b2",1713:"e07968c5",1724:"2461c2e7",1830:"740a117d",1947:"bda1afcc",1981:"4e218966",2079:"e37eaeb3",2082:"bc14e954",2173:"10c12339",2178:"13069292",2217:"60800c25",2284:"21e267ca",2323:"f0b907ab",2364:"9cad35d4",2385:"07336b58",2472:"afc2f917",2535:"5cc4827f",2549:"f76e17c6",2557:"9fd5df8f",2609:"dbc29b18",2667:"88023070",2778:"04ce1efb",2896:"eab98cda",2938:"3c5797b2",2965:"a212fb0d",3010:"d11d7eb3",3089:"cf7d6632",3154:"a51fa70f",3163:"4913f1cb",3207:"a9afbcd8",3232:"9528760d",3237:"e2fef33f",3259:"d48e5470",3296:"b7616ae4",3317:"7ce74ef2",3324:"3cf78b95",3414:"f68026ae",3505:"6cbf58b2",3584:"4a5a7db3",3608:"6b194cc3",3636:"bac4874d",3691:"09a183f0",3714:"176b91ec",3751:"e6a1ff2c",3820:"75a6ed57",3866:"6f22f670",3870:"045cc138",3879:"b182e077",3893:"43838999",3952:"271e9a6e",3973:"9a8bb6e1",4013:"17c10467",4059:"2e148b4d",4112:"1b206455",4121:"47f9361b",4157:"b189e4c1",4178:"a197f856",4356:"982cf786",4386:"194fc2a2",4551:"b79d0bd2",4617:"61371bc1",4670:"c6602195",4735:"f27330d3",4781:"007e12d4",4929:"a0707feb",5018:"9d824327",5076:"9abee33b",5240:"641ec7fc",5248:"e7820b8e",5375:"f19ca62b",5376:"106682fc",5468:"f089dbbd",5478:"e9e824b5",5591:"9621308b",5625:"c4b6a5f2",5708:"9e67218b",5776:"9289db31",5803:"7724e22b",5974:"5ef63543",6026:"6c6a5338",6038:"f7180e21",6049:"2f6bc428",6082:"3694c963",6088:"0e41b8ce",6103:"0a9a510b",6120:"11c2c21b",6308:"326b3a51",6328:"0458dc90",6536:"e236509f",6608:"5cf78b44",6623:"3c07d980",6690:"0738083d",6692:"9034be99",6719:"56f34a53",6766:"90588983",6843:"efcf1441",7007:"e073c454",7034:"e478b99c",7134:"0d536e2b",7138:"66534a1a",7141:"aa741b27",7149:"663ec94f",7171:"ed520d1e",7220:"ab5b2baa",7239:"4f656480",7251:"75e3d1b3",7274:"c42d9b9e",7350:"9b125618",7363:"9fcc6d04",7365:"9acd3eb7",7366:"b9ad9349",7370:"f73e8663",7377:"b821d601",7438:"a0f3d6c3",7480:"d849bbc6",7526:"61e556ee",7536:"3a66b423",7573:"f26b658c",7622:"b17356bb",7653:"ee3ea3e0",7679:"f15da8d9",7698:"a0fbf744",7714:"2f0eeee5",7735:"b12007f7",7739:"9cc24e77",7741:"ff546f54",7759:"315bf772",7847:"2c70676d",7849:"bb1a7e66",7881:"de8f5c25",7918:"e15ec73f",7920:"a7306422",8065:"546ab956",8145:"16412c4f",8215:"bcf97e6c",8221:"82e37ffd",8242:"b4cf6364",8262:"c004698d",8290:"c415179d",8306:"5f30899d",8445:"4fc783d0",8502:"7b175b26",8514:"e4ec655c",8533:"9a7a6392",8566:"636842d6",8610:"51bd3ba5",8777:"e2ef1f93",8800:"a0bdbe06",8811:"f2b0882a",8860:"b24be5ae",8893:"3281bcfc",8970:"4c411332",8989:"17f0efbe",9019:"5add45ab",9043:"c48512f7",9106:"3d077178",9127:"02f87f8d",9133:"7057011c",9179:"b5281c34",9209:"e11404ca",9341:"dc82cf1a",9372:"7bc1a408",9387:"f0f7a6a7",9395:"aac52386",9469:"14c4eb5c",9514:"0e6e9a66",9671:"cab46598",9817:"5036f126",9924:"dc218f14",9944:"91801d8b"}[e]+".js",r.miniCssF=e=>{},r.g=function(){if("object"==typeof globalThis)return globalThis;try{return this||new Function("return this")()}catch(e){if("object"==typeof window)return window}}(),r.o=(e,f)=>Object.prototype.hasOwnProperty.call(e,f),c={},b="docs:",r.l=(e,f,a,d)=>{if(c[e])c[e].push(f);else{var t,o;if(void 0!==a)for(var n=document.getElementsByTagName("script"),i=0;i{t.onerror=t.onload=null,clearTimeout(s);var b=c[e];if(delete c[e],t.parentNode&&t.parentNode.removeChild(t),b&&b.forEach((e=>e(a))),f)return f(a)},s=setTimeout(l.bind(null,void 0,{type:"timeout",target:t}),12e4);t.onerror=l.bind(null,t.onerror),t.onload=l.bind(null,t.onload),o&&document.head.appendChild(t)}},r.r=e=>{"undefined"!=typeof Symbol&&Symbol.toStringTag&&Object.defineProperty(e,Symbol.toStringTag,{value:"Module"}),Object.defineProperty(e,"__esModule",{value:!0})},r.p="/",r.gca=function(e){return e={17896441:"7918",33942509:"10",72486833:"3505",75281220:"7366",79551407:"9179",95366386:"4617",99245987:"8445","902d9f40":"24","935f2afb":"53","86f2a982":"70",e665718d:"114","54590fd2":"138",c276ecb2:"182","83d480e9":"205","6194ac84":"397",f7b7f9b7:"465","9aa62c0e":"506","308aae28":"522",b2b675dd:"533",c685778b:"563",b39cdcf9:"592","2c93bfff":"628","512fbd77":"649","6b600968":"692","61d4c13a":"743",e5878f42:"759","840a98fb":"809",cabda5f8:"873",b985118d:"899",c37b4a03:"921",b2e1a0c8:"944",df322e14:"945","1a0737b6":"1021",a67ca768:"1032","9e8f4e9c":"1074","34cf6fc7":"1297","7327116e":"1335",a766a857:"1342","382c5d2b":"1441","44f02f2c":"1476",b2f554cd:"1477",de311ed4:"1625","819ef483":"1676","94fb813f":"1705",a7023ddc:"1713","5087625a":"1724",b00bc883:"1830",b799648a:"1981","1a16e8bf":"2079",e85ba0e6:"2082","36eac8b2":"2173",ba322490:"2178",d7fbbe43:"2217","4117ac4b":"2284","6c80b6fe":"2323","8cdb21e1":"2364","8f92bc29":"2385","65a10ffa":"2472","814f3328":"2535","5c63ba15":"2549","28726be2":"2557","6269f1c0":"2609","368cce37":"2667","608238a8":"2778",abc85917:"2896",c95aa39f:"2938","4384f6ba":"2965","56c3a9b2":"3010",a6aa9e1f:"3089",c6346fcf:"3154","232c546d":"3163","6603ef13":"3207","1f35373c":"3232","1df93b7f":"3237","03ccf92d":"3259","181ef600":"3296","846a5e19":"3317","1ce91f4c":"3324","35a7a45c":"3414",ed75cfcb:"3584","9e4087bc":"3608","8b4dd820":"3636","7be672a3":"3691","894e67a6":"3714","3720c009":"3751",a5e1f61e:"3820","5df556a2":"3870","2d629ea6":"3879","1b710012":"3952",f523fb3f:"3973","01a85c17":"4013","9cb03f5d":"4059","9f02b2b5":"4112","55960ee5":"4121","83e10f72":"4157",a9a76bf7:"4356",ae79aff5:"4386","3b161fd7":"4551","0c1dc3b8":"4735","12f1535e":"4781","330dfcdb":"4929",cd509849:"5018",b4561fd7:"5076","22de4147":"5240","6101b3fc":"5248","97615df2":"5375",bebbf51e:"5376",b9bde34b:"5468",df1d8f19:"5478",c9181a9f:"5591","657ac0bc":"5625",f0057c03:"5708",f0e3a130:"5776",ff8f5ed0:"5803",f20fb67e:"5974","51dec273":"6026",c9c860ee:"6038",f213dd13:"6049",a233b66e:"6082","88efc5aa":"6088",ccc49370:"6103",d4840880:"6120",e8dc4d98:"6308",c0d19596:"6328","3ed6e2e9":"6536","5099f3e0":"6608",b104dd1e:"6623","4816649b":"6690","2ae2e7fe":"6692","2e0c1e3c":"6719",e5638e51:"6766","9f97f9d1":"6843","8593ff01":"7007","3e03f778":"7034","0b40a488":"7134","38a042e4":"7138",b5abacaa:"7141","822c343e":"7149","7591d420":"7220",d9e85037:"7239",ba5b9f11:"7251",be315de3:"7274","8bedf5f0":"7350","583db3ef":"7363","652d909c":"7365",dba48714:"7370","708d858d":"7377","9c021584":"7438",eb17771c:"7480","016d7603":"7526",f6e0e63c:"7536","48b6ff5f":"7573",dbbb982f:"7622","31de1779":"7653","83245ae6":"7679",cd23aec9:"7698","7bdcd7a7":"7714","3ede2625":"7739","7d88b63f":"7741",ff38b1ce:"7759","43b416ef":"7847","2658ced2":"7881","1a4e3797":"7920","53f302bb":"8065","006e489c":"8145","1cfced13":"8215","6af14956":"8221",cbe6e75d:"8242","059d1c6a":"8262","3fe48f60":"8290",b4657d81:"8502",d651e2ee:"8514",f3d54061:"8533","9dce5486":"8566","6875c492":"8610",e6fb1369:"8800","3289a752":"8811","0d040286":"8860",ba1dc56d:"8893","68b843fc":"8970",d4bf7e47:"8989","771d7520":"9019","473de3ed":"9043","72dd8f7e":"9106","02e265ea":"9133",d2117a98:"9209",a35cf155:"9341","07f59c2a":"9372",b0f1c099:"9387","415c4e0e":"9395","3b85f227":"9469","1be78505":"9514","0e384e19":"9671","4f561e31":"9817",df203c0f:"9924","08570680":"9944"}[e]||e,r.p+r.u(e)},(()=>{var e={1303:0,532:0};r.f.j=(f,a)=>{var c=r.o(e,f)?e[f]:void 0;if(0!==c)if(c)a.push(c[2]);else if(/^(1303|532)$/.test(f))e[f]=0;else{var b=new Promise(((a,b)=>c=e[f]=[a,b]));a.push(c[2]=b);var d=r.p+r.u(f),t=new Error;r.l(d,(a=>{if(r.o(e,f)&&(0!==(c=e[f])&&(e[f]=void 0),c)){var b=a&&("load"===a.type?"missing":a.type),d=a&&a.target&&a.target.src;t.message="Loading chunk "+f+" failed.\n("+b+": "+d+")",t.name="ChunkLoadError",t.type=b,t.request=d,c[1](t)}}),"chunk-"+f,f)}},r.O.j=f=>0===e[f];var f=(f,a)=>{var c,b,d=a[0],t=a[1],o=a[2],n=0;if(d.some((f=>0!==e[f]))){for(c in t)r.o(t,c)&&(r.m[c]=t[c]);if(o)var i=o(r)}for(f&&f(a);n{"use strict";var e,f,a,c,b,d={},t={};function r(e){var f=t[e];if(void 0!==f)return f.exports;var a=t[e]={exports:{}};return d[e].call(a.exports,a,a.exports,r),a.exports}r.m=d,e=[],r.O=(f,a,c,b)=>{if(!a){var d=1/0;for(i=0;i=b)&&Object.keys(r.O).every((e=>r.O[e](a[o])))?a.splice(o--,1):(t=!1,b0&&e[i-1][2]>b;i--)e[i]=e[i-1];e[i]=[a,c,b]},r.n=e=>{var f=e&&e.__esModule?()=>e.default:()=>e;return r.d(f,{a:f}),f},a=Object.getPrototypeOf?e=>Object.getPrototypeOf(e):e=>e.__proto__,r.t=function(e,c){if(1&c&&(e=this(e)),8&c)return e;if("object"==typeof e&&e){if(4&c&&e.__esModule)return e;if(16&c&&"function"==typeof e.then)return e}var b=Object.create(null);r.r(b);var d={};f=f||[null,a({}),a([]),a(a)];for(var t=2&c&&e;"object"==typeof t&&!~f.indexOf(t);t=a(t))Object.getOwnPropertyNames(t).forEach((f=>d[f]=()=>e[f]));return d.default=()=>e,r.d(b,d),b},r.d=(e,f)=>{for(var a in f)r.o(f,a)&&!r.o(e,a)&&Object.defineProperty(e,a,{enumerable:!0,get:f[a]})},r.f={},r.e=e=>Promise.all(Object.keys(r.f).reduce(((f,a)=>(r.f[a](e,f),f)),[])),r.u=e=>"assets/js/"+({10:"33942509",24:"902d9f40",53:"935f2afb",70:"86f2a982",114:"e665718d",138:"54590fd2",182:"c276ecb2",205:"83d480e9",397:"6194ac84",465:"f7b7f9b7",506:"9aa62c0e",522:"308aae28",533:"b2b675dd",563:"c685778b",592:"b39cdcf9",628:"2c93bfff",649:"512fbd77",692:"6b600968",743:"61d4c13a",759:"e5878f42",809:"840a98fb",873:"cabda5f8",899:"b985118d",921:"c37b4a03",944:"b2e1a0c8",945:"df322e14",1021:"1a0737b6",1032:"a67ca768",1074:"9e8f4e9c",1297:"34cf6fc7",1335:"7327116e",1342:"a766a857",1441:"382c5d2b",1476:"44f02f2c",1477:"b2f554cd",1625:"de311ed4",1676:"819ef483",1705:"94fb813f",1713:"a7023ddc",1724:"5087625a",1830:"b00bc883",1981:"b799648a",2079:"1a16e8bf",2082:"e85ba0e6",2173:"36eac8b2",2178:"ba322490",2217:"d7fbbe43",2284:"4117ac4b",2323:"6c80b6fe",2364:"8cdb21e1",2385:"8f92bc29",2472:"65a10ffa",2535:"814f3328",2549:"5c63ba15",2557:"28726be2",2609:"6269f1c0",2667:"368cce37",2778:"608238a8",2896:"abc85917",2938:"c95aa39f",2965:"4384f6ba",3010:"56c3a9b2",3089:"a6aa9e1f",3154:"c6346fcf",3163:"232c546d",3207:"6603ef13",3232:"1f35373c",3237:"1df93b7f",3259:"03ccf92d",3296:"181ef600",3317:"846a5e19",3324:"1ce91f4c",3414:"35a7a45c",3505:"72486833",3584:"ed75cfcb",3608:"9e4087bc",3636:"8b4dd820",3691:"7be672a3",3714:"894e67a6",3751:"3720c009",3820:"a5e1f61e",3870:"5df556a2",3879:"2d629ea6",3952:"1b710012",3973:"f523fb3f",4013:"01a85c17",4059:"9cb03f5d",4112:"9f02b2b5",4121:"55960ee5",4157:"83e10f72",4356:"a9a76bf7",4386:"ae79aff5",4551:"3b161fd7",4617:"95366386",4735:"0c1dc3b8",4781:"12f1535e",4929:"330dfcdb",5018:"cd509849",5076:"b4561fd7",5240:"22de4147",5248:"6101b3fc",5375:"97615df2",5376:"bebbf51e",5468:"b9bde34b",5478:"df1d8f19",5591:"c9181a9f",5625:"657ac0bc",5708:"f0057c03",5776:"f0e3a130",5803:"ff8f5ed0",5974:"f20fb67e",6026:"51dec273",6038:"c9c860ee",6049:"f213dd13",6082:"a233b66e",6088:"88efc5aa",6103:"ccc49370",6120:"d4840880",6308:"e8dc4d98",6328:"c0d19596",6536:"3ed6e2e9",6608:"5099f3e0",6623:"b104dd1e",6690:"4816649b",6692:"2ae2e7fe",6719:"2e0c1e3c",6766:"e5638e51",6843:"9f97f9d1",7007:"8593ff01",7034:"3e03f778",7134:"0b40a488",7138:"38a042e4",7141:"b5abacaa",7149:"822c343e",7220:"7591d420",7239:"d9e85037",7251:"ba5b9f11",7274:"be315de3",7350:"8bedf5f0",7363:"583db3ef",7365:"652d909c",7366:"75281220",7370:"dba48714",7377:"708d858d",7438:"9c021584",7480:"eb17771c",7526:"016d7603",7536:"f6e0e63c",7573:"48b6ff5f",7622:"dbbb982f",7653:"31de1779",7679:"83245ae6",7698:"cd23aec9",7714:"7bdcd7a7",7739:"3ede2625",7741:"7d88b63f",7759:"ff38b1ce",7847:"43b416ef",7881:"2658ced2",7918:"17896441",7920:"1a4e3797",8065:"53f302bb",8145:"006e489c",8215:"1cfced13",8221:"6af14956",8242:"cbe6e75d",8262:"059d1c6a",8290:"3fe48f60",8445:"99245987",8502:"b4657d81",8514:"d651e2ee",8533:"f3d54061",8566:"9dce5486",8610:"6875c492",8800:"e6fb1369",8811:"3289a752",8860:"0d040286",8893:"ba1dc56d",8970:"68b843fc",8989:"d4bf7e47",9019:"771d7520",9043:"473de3ed",9106:"72dd8f7e",9133:"02e265ea",9179:"79551407",9209:"d2117a98",9341:"a35cf155",9372:"07f59c2a",9387:"b0f1c099",9395:"415c4e0e",9469:"3b85f227",9514:"1be78505",9671:"0e384e19",9817:"4f561e31",9924:"df203c0f",9944:"08570680"}[e]||e)+"."+{10:"b3b53e4f",24:"c9c02d31",53:"3ed5b938",70:"6082feaf",114:"22a38c18",138:"01cf4745",182:"c229eebf",205:"7ed9f2aa",397:"727a973d",465:"1cbd3a08",506:"3f0bed63",522:"d7cd5912",533:"b092fb30",563:"4744a638",592:"20325692",628:"7140d154",649:"10a887e2",692:"99e3d625",743:"89c00deb",759:"721f9cf0",809:"06decfd8",873:"919ad21c",899:"7e8cb215",921:"f0615854",944:"a49ec1c2",945:"faae8bea",1021:"4ab01d95",1032:"22c424dc",1074:"ead1b706",1297:"dee27ee5",1335:"b2b0cf3e",1342:"478736f2",1441:"dfb53e35",1476:"3a468864",1477:"f9bb77ec",1625:"35d33fff",1676:"8a2bafc1",1705:"fa2462b2",1713:"e07968c5",1724:"2461c2e7",1830:"740a117d",1947:"bda1afcc",1981:"4e218966",2079:"e37eaeb3",2082:"bc14e954",2173:"10c12339",2178:"13069292",2217:"60800c25",2284:"21e267ca",2323:"f0b907ab",2364:"9cad35d4",2385:"07336b58",2472:"afc2f917",2535:"5cc4827f",2549:"f76e17c6",2557:"9fd5df8f",2609:"dbc29b18",2667:"88023070",2778:"04ce1efb",2896:"eab98cda",2938:"3c5797b2",2965:"a212fb0d",3010:"d11d7eb3",3089:"cf7d6632",3154:"a51fa70f",3163:"4913f1cb",3207:"a9afbcd8",3232:"9528760d",3237:"9b5882c1",3259:"d48e5470",3296:"b7616ae4",3317:"7ce74ef2",3324:"3cf78b95",3414:"f68026ae",3505:"6cbf58b2",3584:"4a5a7db3",3608:"6b194cc3",3636:"bac4874d",3691:"09a183f0",3714:"176b91ec",3751:"e6a1ff2c",3820:"75a6ed57",3866:"6f22f670",3870:"045cc138",3879:"b182e077",3893:"43838999",3952:"271e9a6e",3973:"9a8bb6e1",4013:"17c10467",4059:"2e148b4d",4112:"1b206455",4121:"47f9361b",4157:"b189e4c1",4178:"a197f856",4356:"982cf786",4386:"194fc2a2",4551:"b79d0bd2",4617:"61371bc1",4670:"c6602195",4735:"f27330d3",4781:"007e12d4",4929:"a0707feb",5018:"9d824327",5076:"9abee33b",5240:"641ec7fc",5248:"e7820b8e",5375:"f19ca62b",5376:"106682fc",5468:"f089dbbd",5478:"e9e824b5",5591:"9621308b",5625:"c4b6a5f2",5708:"9e67218b",5776:"9289db31",5803:"7724e22b",5974:"5ef63543",6026:"6c6a5338",6038:"f7180e21",6049:"2f6bc428",6082:"3694c963",6088:"0e41b8ce",6103:"0a9a510b",6120:"11c2c21b",6308:"326b3a51",6328:"0458dc90",6536:"e236509f",6608:"5cf78b44",6623:"3c07d980",6690:"0738083d",6692:"9034be99",6719:"56f34a53",6766:"90588983",6843:"efcf1441",7007:"e073c454",7034:"e478b99c",7134:"0d536e2b",7138:"66534a1a",7141:"aa741b27",7149:"663ec94f",7171:"ed520d1e",7220:"ab5b2baa",7239:"4f656480",7251:"75e3d1b3",7274:"c42d9b9e",7350:"9b125618",7363:"9fcc6d04",7365:"9acd3eb7",7366:"b9ad9349",7370:"f73e8663",7377:"b821d601",7438:"a0f3d6c3",7480:"d849bbc6",7526:"61e556ee",7536:"3a66b423",7573:"f26b658c",7622:"b17356bb",7653:"ee3ea3e0",7679:"f15da8d9",7698:"a0fbf744",7714:"2f0eeee5",7735:"b12007f7",7739:"9cc24e77",7741:"ff546f54",7759:"315bf772",7847:"2c70676d",7849:"bb1a7e66",7881:"de8f5c25",7918:"e15ec73f",7920:"a7306422",8065:"546ab956",8145:"16412c4f",8215:"bcf97e6c",8221:"82e37ffd",8242:"b4cf6364",8262:"c004698d",8290:"c415179d",8306:"5f30899d",8445:"4fc783d0",8502:"7b175b26",8514:"e4ec655c",8533:"9a7a6392",8566:"636842d6",8610:"51bd3ba5",8777:"e2ef1f93",8800:"a0bdbe06",8811:"f2b0882a",8860:"b24be5ae",8893:"3281bcfc",8970:"4c411332",8989:"17f0efbe",9019:"5add45ab",9043:"c48512f7",9106:"3d077178",9127:"02f87f8d",9133:"7057011c",9179:"b5281c34",9209:"e11404ca",9341:"dc82cf1a",9372:"7bc1a408",9387:"f0f7a6a7",9395:"aac52386",9469:"14c4eb5c",9514:"0e6e9a66",9671:"cab46598",9817:"5036f126",9924:"dc218f14",9944:"91801d8b"}[e]+".js",r.miniCssF=e=>{},r.g=function(){if("object"==typeof globalThis)return globalThis;try{return this||new Function("return this")()}catch(e){if("object"==typeof window)return window}}(),r.o=(e,f)=>Object.prototype.hasOwnProperty.call(e,f),c={},b="docs:",r.l=(e,f,a,d)=>{if(c[e])c[e].push(f);else{var t,o;if(void 0!==a)for(var n=document.getElementsByTagName("script"),i=0;i{t.onerror=t.onload=null,clearTimeout(s);var b=c[e];if(delete c[e],t.parentNode&&t.parentNode.removeChild(t),b&&b.forEach((e=>e(a))),f)return f(a)},s=setTimeout(l.bind(null,void 0,{type:"timeout",target:t}),12e4);t.onerror=l.bind(null,t.onerror),t.onload=l.bind(null,t.onload),o&&document.head.appendChild(t)}},r.r=e=>{"undefined"!=typeof Symbol&&Symbol.toStringTag&&Object.defineProperty(e,Symbol.toStringTag,{value:"Module"}),Object.defineProperty(e,"__esModule",{value:!0})},r.p="/",r.gca=function(e){return e={17896441:"7918",33942509:"10",72486833:"3505",75281220:"7366",79551407:"9179",95366386:"4617",99245987:"8445","902d9f40":"24","935f2afb":"53","86f2a982":"70",e665718d:"114","54590fd2":"138",c276ecb2:"182","83d480e9":"205","6194ac84":"397",f7b7f9b7:"465","9aa62c0e":"506","308aae28":"522",b2b675dd:"533",c685778b:"563",b39cdcf9:"592","2c93bfff":"628","512fbd77":"649","6b600968":"692","61d4c13a":"743",e5878f42:"759","840a98fb":"809",cabda5f8:"873",b985118d:"899",c37b4a03:"921",b2e1a0c8:"944",df322e14:"945","1a0737b6":"1021",a67ca768:"1032","9e8f4e9c":"1074","34cf6fc7":"1297","7327116e":"1335",a766a857:"1342","382c5d2b":"1441","44f02f2c":"1476",b2f554cd:"1477",de311ed4:"1625","819ef483":"1676","94fb813f":"1705",a7023ddc:"1713","5087625a":"1724",b00bc883:"1830",b799648a:"1981","1a16e8bf":"2079",e85ba0e6:"2082","36eac8b2":"2173",ba322490:"2178",d7fbbe43:"2217","4117ac4b":"2284","6c80b6fe":"2323","8cdb21e1":"2364","8f92bc29":"2385","65a10ffa":"2472","814f3328":"2535","5c63ba15":"2549","28726be2":"2557","6269f1c0":"2609","368cce37":"2667","608238a8":"2778",abc85917:"2896",c95aa39f:"2938","4384f6ba":"2965","56c3a9b2":"3010",a6aa9e1f:"3089",c6346fcf:"3154","232c546d":"3163","6603ef13":"3207","1f35373c":"3232","1df93b7f":"3237","03ccf92d":"3259","181ef600":"3296","846a5e19":"3317","1ce91f4c":"3324","35a7a45c":"3414",ed75cfcb:"3584","9e4087bc":"3608","8b4dd820":"3636","7be672a3":"3691","894e67a6":"3714","3720c009":"3751",a5e1f61e:"3820","5df556a2":"3870","2d629ea6":"3879","1b710012":"3952",f523fb3f:"3973","01a85c17":"4013","9cb03f5d":"4059","9f02b2b5":"4112","55960ee5":"4121","83e10f72":"4157",a9a76bf7:"4356",ae79aff5:"4386","3b161fd7":"4551","0c1dc3b8":"4735","12f1535e":"4781","330dfcdb":"4929",cd509849:"5018",b4561fd7:"5076","22de4147":"5240","6101b3fc":"5248","97615df2":"5375",bebbf51e:"5376",b9bde34b:"5468",df1d8f19:"5478",c9181a9f:"5591","657ac0bc":"5625",f0057c03:"5708",f0e3a130:"5776",ff8f5ed0:"5803",f20fb67e:"5974","51dec273":"6026",c9c860ee:"6038",f213dd13:"6049",a233b66e:"6082","88efc5aa":"6088",ccc49370:"6103",d4840880:"6120",e8dc4d98:"6308",c0d19596:"6328","3ed6e2e9":"6536","5099f3e0":"6608",b104dd1e:"6623","4816649b":"6690","2ae2e7fe":"6692","2e0c1e3c":"6719",e5638e51:"6766","9f97f9d1":"6843","8593ff01":"7007","3e03f778":"7034","0b40a488":"7134","38a042e4":"7138",b5abacaa:"7141","822c343e":"7149","7591d420":"7220",d9e85037:"7239",ba5b9f11:"7251",be315de3:"7274","8bedf5f0":"7350","583db3ef":"7363","652d909c":"7365",dba48714:"7370","708d858d":"7377","9c021584":"7438",eb17771c:"7480","016d7603":"7526",f6e0e63c:"7536","48b6ff5f":"7573",dbbb982f:"7622","31de1779":"7653","83245ae6":"7679",cd23aec9:"7698","7bdcd7a7":"7714","3ede2625":"7739","7d88b63f":"7741",ff38b1ce:"7759","43b416ef":"7847","2658ced2":"7881","1a4e3797":"7920","53f302bb":"8065","006e489c":"8145","1cfced13":"8215","6af14956":"8221",cbe6e75d:"8242","059d1c6a":"8262","3fe48f60":"8290",b4657d81:"8502",d651e2ee:"8514",f3d54061:"8533","9dce5486":"8566","6875c492":"8610",e6fb1369:"8800","3289a752":"8811","0d040286":"8860",ba1dc56d:"8893","68b843fc":"8970",d4bf7e47:"8989","771d7520":"9019","473de3ed":"9043","72dd8f7e":"9106","02e265ea":"9133",d2117a98:"9209",a35cf155:"9341","07f59c2a":"9372",b0f1c099:"9387","415c4e0e":"9395","3b85f227":"9469","1be78505":"9514","0e384e19":"9671","4f561e31":"9817",df203c0f:"9924","08570680":"9944"}[e]||e,r.p+r.u(e)},(()=>{var e={1303:0,532:0};r.f.j=(f,a)=>{var c=r.o(e,f)?e[f]:void 0;if(0!==c)if(c)a.push(c[2]);else if(/^(1303|532)$/.test(f))e[f]=0;else{var b=new Promise(((a,b)=>c=e[f]=[a,b]));a.push(c[2]=b);var d=r.p+r.u(f),t=new Error;r.l(d,(a=>{if(r.o(e,f)&&(0!==(c=e[f])&&(e[f]=void 0),c)){var b=a&&("load"===a.type?"missing":a.type),d=a&&a.target&&a.target.src;t.message="Loading chunk "+f+" failed.\n("+b+": "+d+")",t.name="ChunkLoadError",t.type=b,t.request=d,c[1](t)}}),"chunk-"+f,f)}},r.O.j=f=>0===e[f];var f=(f,a)=>{var c,b,d=a[0],t=a[1],o=a[2],n=0;if(d.some((f=>0!==e[f]))){for(c in t)r.o(t,c)&&(r.m[c]=t[c]);if(o)var i=o(r)}for(f&&f(a);n - + @@ -29,7 +29,7 @@ of Podman Desktop: not just local container engines, but Kubernetes too. More im providing tools that allow you to manage both environments and seamlessly move between them.

Some of these features were available in development mode over the last few releases, but since they are now in the release build, we will do a full roundup and talk about all the Kind features.

  • Kind Installation: Install Kind from the status bar
  • Manage Kind Clusters: Create and manage Kind clusters from Settings > Resources
  • Using Kind: Deploying YAML and sharing images to a cluster
  • Kind Ingress: Install a Contour ingress controller
  • UX and UI Improvements: Updated preferences and telemetry prompt

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

Podman-desktop-0-14-hero

· 4 min read
Tim deBoer

This release note covers Podman Desktop 0.13 release changes.

  • Podman Version: Podman 4.4.4 now included in Windows and Mac installers.
  • Compose: Support for installing Docker Compose.
  • Extensions: Improved extension support for Podman Desktop with additional capabilities.
  • UX and UI Improvements: Welcome page, task manager, resources, and update alerts.

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

Podman-desktop-0-13-hero

· 5 min read
Florent Benoit

The 5 things to know being a Docker user by using Podman Desktop:

  • Use a single UI: Podman Desktop works with several container engines, including Docker.
  • The compatibility mode: How to ensure tools are working with Podman instead of Docker.
  • Compose support: How to work with Compose files and Podman.
  • Kubernetes support: How to use Kubernetes with Podman.
  • Security: Use rootless mode or containers without root privileges.

5-things-to-know-for-a-docker-user-hero

· 5 min read
Stevan Le Meur

This release note covers Podman Desktop 0.12 release changes.

  • Podman Version: Podman 4.4.1 now included in Windows and Mac installers.
  • Containers Configuration: Configure port mappings for an image without exported ports.
  • Windows Home Support: Podman Desktop now supports Windows Home Edition.
  • Start minimized: Option to start Podman Desktop minimized to system tray.
  • UX and UI Improvements: Consistent actions, placeholder for logs, unified icons and others.

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

podman-desktop-0-12-hero

· 10 min read
Stevan Le Meur

This release note covers Podman Desktop 0.11 release changes.

  • Air-Gapped Installation: New all-in-one binaries for air-gapped installation.
  • Feedback: Submit feedback directly from Podman Desktop.
  • Docker Compatibility Mode: Information about the Docker compatibility mode.
  • Proxy Setting: Toggle on/off the proxy setting.
  • Deploy to Kubernetes: Select the namespace to deploy to Kubernetes.
  • Registry Configuration: Simplified registry configuration for well known registries.
  • UX/UI Improvements: View pod's container logs, better visual feedback, configurable editor font size, and more.

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

· 5 min read
Dev Kumar

This release note covers Podman Desktop 0.10 release changes.

  • Containers Configuration: Container creation wizzard allowing to define environment variables, networking and more configuration options.
  • Kubernetes Improvements: Play Kubernetes YAML, custom Kubeconfig path support, reload of kube context.
  • Registries Configuration: Revamped registries configuration UI.
  • Podman Version: Podman 4.3.1 now included in Windows and Mac installers.
  • UX/UI Improvements: Improved lists, better contrast, and more.

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

· 7 min read
Florent Benoit

GitHub announced last week that Codespaces is available for everyone and it includes free minutes.

Let see how we can use a Development Container having all the tools to build and run Podman Desktop. The Development Container works locally using Visual Studio Code but in this blog post we will see how it works directly with a simple click from GitHub.

The challenges are to run a desktop tool (Podman Desktop) and running a container engine (Podman) inside this Development Container without using too many memory !

- + \ No newline at end of file diff --git a/blog/5-things-to-know-for-a-docker-user.html b/blog/5-things-to-know-for-a-docker-user.html index 39be4f7d11c..6009c151fb2 100644 --- a/blog/5-things-to-know-for-a-docker-user.html +++ b/blog/5-things-to-know-for-a-docker-user.html @@ -13,13 +13,13 @@ - +

5 things to know about Podman Desktop for a Docker user

· 5 min read
Florent Benoit

The 5 things to know being a Docker user by using Podman Desktop:

  • Use a single UI: Podman Desktop works with several container engines, including Docker.
  • The compatibility mode: How to ensure tools are working with Podman instead of Docker.
  • Compose support: How to work with Compose files and Podman.
  • Kubernetes support: How to use Kubernetes with Podman.
  • Security: Use rootless mode or containers without root privileges.

5-things-to-know-for-a-docker-user-hero

Use Podman Desktop to interact with containers running in Docker​

Docker Desktop provides a UI to interact with containers and images. But the UI depends on Docker API and it is not possible to use the UI with Docker and Podman at the same time.

Podman Desktop is a multi-engine UI tool. The UI is compatible with the API of Docker and Podman. It means all containers and images from all the engines at the same time are visible in the UI.

When migrating from Docker to Podman, you can use Podman Desktop to interact with containers running in Docker. Explore all commands and features of Podman Desktop and see all the resources from Docker.

Many container engines at the same time

Docker compatibility mode​

Using Podman with Podman Desktop or with the Podman CLI is straightforward. But some tools expect to find docker CLI or docker.sock socket. In this case, you have to use the compatibility mode of Podman.

Socket file compatibility​

The socket compatibility mode is a feature of Podman that allows to bind the Podman socket under the Docker socket path.

On Windows the socket compatibility mode is always enabled by default. On macOS, by using the .pkg installer it is active by default. But when installing with brew, it will not be there because it requires some admin permissions.

That is not an issue because you can enable it by invoking a CLI tool that will setup the compatibility mode.

For example if you use TestContainers in your Java project, you can use the compatibility mode to ensure that the tool will use Podman instead of Docker.

CLI compatibility​

If you have scripts relying on docker CLI, you can use the compatibility mode to ensure that the tool is working with Podman instead of Docker.

If you have the docker CLI installed on your computer, you can use the socket file compatibility of docker to ensure that the tool is working with Podman engine instead of Docker.

If you do not have the docker CLI installed on your computer, you can Create a script called docker that will call the podman CLI

NOTE: creating a shell prompt alias, for example alias docker=podman, will not work inside scripts that you call.

Compose​

As a user of Docker, you might use docker compose (or docker-compose) to run some of your applications.

For now Podman does not include a Compose support directly in the CLI with a command podman compose.

Compose can work with the Podman socket.

Based on the compatibility mode (see section about Docker compatibility mode):

You can now use the compose binary to run your applications and it will use Podman engine.

Podman Desktop has a compose extension that can fetch compose binary if not already available on the filesystem.

Podman Desktop UI displays the containers created by Compose are in the same group.

Compose support in the UI

Kubernetes​

It is possible to start a Kubernetes cluster with Docker.

Podman supports directly a subset of Kubernetes resources that you can use with .yaml files.

For example if you only want to create a Pod resource, you can use the Play Kubernetes YAML button from the Containers list screen with your .yaml file. No need to install or start a Kubernetes cluster.

Play Kubernetes YAML

It is possible to do the counter-part. Export the definition of a container or pod to a Kubernetes resource. You can use the Generate kube button from the kebab menu of a given container or pod.

Kubernetes generate

Podman handles pods and in the Podman Desktop UI, you can see all the pods inside a Pod section. All containers inside the pod are in the same group.

Pods in the UI

Containers from pod

An experimental kind extension is bringing the creation of full-blown Kubernetes cluster with Podman.

Rootless mode​

One of the difference of Docker and Podman is the way they handle containers. Docker requires root privileges to run containers by default. Podman can run containers without root privileges by default.

It means that for example, starting a container with a port < 1024 will not work. You need to use a port > 1024.

If you still need to create containers with a port < 1024, you can change the Podman machine configuration of the Podman Machine if you are on Windows or macOS.

The command is podman machine --rootful to enable the execution with root privileges or podman machine --rootful=false to switch back to rootless mode.

- + \ No newline at end of file diff --git a/blog/archive.html b/blog/archive.html index 90e9a74f16c..fd79281c7d0 100644 --- a/blog/archive.html +++ b/blog/archive.html @@ -13,13 +13,13 @@ - +

Archive

Archive

2022

2023

- + \ No newline at end of file diff --git a/blog/develop-using-devcontainer.html b/blog/develop-using-devcontainer.html index d2fb7d1b3d0..9b709becec8 100644 --- a/blog/develop-using-devcontainer.html +++ b/blog/develop-using-devcontainer.html @@ -13,7 +13,7 @@ - + @@ -23,7 +23,7 @@ Using --privileged we don't really know what are the privilege that are required while specifying all of them, people are aware of what is granted/denied.

"runArgs": [
    "--cap-add=sys_admin",
    "--security-opt",
    "seccomp=unconfined",
    "--device",
    "/dev/fuse",
    "--security-opt",
    "label=disable",
    "--security-opt",
    "apparmor=unconfined"
  ],

Source code of Podman Desktop needs to be editable within the DevContainer so it needs to be mounted.

"workspaceMount": "source=${localWorkspaceFolder},target=/workspace,type=bind",
"workspaceFolder": "/workspace",

Then we need a command to build Podman Desktop.

For that, we use onCreateCommand hook with a custom command

"onCreateCommand": "${containerWorkspaceFolder}/.devcontainer/onCreateCommand.sh",

and in the .devcontainer folder the onCreateCommand.sh script is the following

#!/bin/sh
yarn

MODE=production yarn run build && yarn run electron-builder build --linux --dir --config .electron-builder.config.cjs

Two instructions:

  1. Fetch all Node.js dependencies.
  2. build Podman Desktop in the dist folder using Linux as target Operating System.

After the start of the container, how to launch Podman Desktop, the website and VNC, etc ?

Just use postStartCommand hook.

"postStartCommand": "${containerWorkspaceFolder}/.devcontainer/postStartCommand.sh",

and in the .devcontainer folder the postStartCommand.sh script is the following:

#!/bin/sh

# Start all services
/usr/bin/supervisord -c /etc/supervisord.conf &

# wait X server to be ready or after 2mn exit
echo "Waiting for X server to be ready"
timeout 120 bash -c 'until xdpyinfo -display :0 &> /dev/null; do printf "."; sleep 1; done'

# launch podman desktop
echo "Launching Podman Desktop"
cd dist/linux-unpacked/&& ./podman-desktop &

# Launch the 9000 redirect after 20 seconds
sleep 20
websockify --web=/usr/share/novnc localhost:9000 localhost:5900 &

# launch the website rendering
echo "Launching Website"
cd website && yarn start

It starts VNC and noVNC, start precompiled Podman Desktop and start the documentation rendering.

It is not launching the Watch mode/development mode of Podman Desktop as it requires a container having more than 8GB of memory.

Picking up a larger instace with for example 16GB, it's possible to use development mode.

Of course, to make VNC happy, we need to specify the DISPLAY environment variable.

"remoteEnv": {
  "DISPLAY": ":0"
}

When the DevContainer is fully available, we want to have a way to quickly open the Website rendering URL and noVNC

Let's tweak the devcontainer.json file by adding the portsAttributes section

"portsAttributes": {
  "9000": {
    "label": "vnc",
    "onAutoForward": "openPreview"
  },
  "3000": {
    "label": "website"
  }
}

After all post-creation steps, the Preview browser inside the VS Code editor will open a window to VNC. And another port (3000) is flagged for the website.

Using the DevContainer.json on Github Codespace​

As a user, opening a workspace with all what we configured is done using a single click.

Go to https://github.com/containers/podman-desktop then click on the < > Code dropdown and click on Create codespace on main button.

Open Codespace

Once you click on the button, the codespace is setting up:

Preparing Codepace

After few minutes, as there is not yet prebuilt codespaces, the codespace is opening.

The simple Browser displays the noVNC window: Opening Codespace

Click on the connect button. Then on the terminal you can enter podman run quay.io/podman/hello and the container is detected in Podman Desktop. Testing Codespace

It's also possible using the port widget to get on 3000 port by clicking on the world icon a preview of the website in another tab. Changing source code of the website will refresh the content of the window.

Depending on the usecase, it's also possible to open documentation in the preview browser.

Edit website Codespace

Conclusion​

The DevContainer image for Podman Desktop is recent so it'll probably evolve over time by adding new capabilities but it allows you to easily build/run/experiment and contribute to the tool or the website.

- + \ No newline at end of file diff --git a/blog/podman-desktop-release-0.10.html b/blog/podman-desktop-release-0.10.html index e201325a676..269fbe28348 100644 --- a/blog/podman-desktop-release-0.10.html +++ b/blog/podman-desktop-release-0.10.html @@ -13,13 +13,13 @@ - +

Release Notes - Podman Desktop 0.10

· 5 min read
Dev Kumar

This release note covers Podman Desktop 0.10 release changes.

  • Containers Configuration: Container creation wizzard allowing to define environment variables, networking and more configuration options.
  • Kubernetes Improvements: Play Kubernetes YAML, custom Kubeconfig path support, reload of kube context.
  • Registries Configuration: Revamped registries configuration UI.
  • Podman Version: Podman 4.3.1 now included in Windows and Mac installers.
  • UX/UI Improvements: Improved lists, better contrast, and more.

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

Release Details​

New configuration wizzard to create containers (#773)​

Until now, we could only specify port binding when building images to start containers. The create container wizzard now includes several options enabling configuring volumes, environment variables, restart policy and settings on networking and security. It is also possible to reuse an existing (and already configured) a network when creating containers.

new container creation wizard

Kubernetes Capabilities Improvements​

Custom Kubeconfig file path (#780)

Kubeconfig path location is now configurable from Settings > Preferences > Kubernetes: Kubeconfig and can be set to a custom path. By default, Podman Desktop use the path $HOME/.kube/config for the Kubeconfig file.

custom kubeconfig file path

Play Kubernetes YAML from the Pods list (#739)

Podman Desktop enables to play existing Kubernetes YAML files. This is now available from Play Kubernetes YAML button added to the Pods list, in addition to the Containers list.

play k8s yaml

Kube context automatically reloaded when updated (#813)

Any change to the kube context will now be detected by Podman Desktop in its running state. The system tray, allowing to select which Kubernetes environment to work with, will now reload the kube context without restarting Podman Desktop.

Revamped Container Registries UI (#446)​

The registries configuration UI has been revamped. Instead of using tiles for displaying the registries, now it uses a list where each registry can be added or edited directly in the list. The kebab menu provides options to edit or remove a registry from the list.

registries

Update to Podman 4.3.1 (#913)​

Podman Desktop 0.10 is now embedding Podman 4.3.1 in Windows and macOS installers.

UI/UX Improvements​

Improved lists UX (#877)

To reduce the width used in the lists when displaying all the icons, main actions icons are now always displayed (before it was on hover) and the secondary actions are displayed in a kebab menu. For example Start/Stop and delete are primary actions while open the browser, inspect, generate kube yaml, etc. are secondary options.

kebab menu

Delay appearance of text in navbar (#767)

When minimizing or expanding the navbar, the text was overlapping for a few second the page. Now it's displayed with a fading animation.

Selected state: better text color contrast (#802)

In the Images page, on hover for both the image and the name column, the text contrast has been increased for better visibility: violet indicates that you have selected it.

text color when hover

On Linux and Windows, the menu bar is now hidden by default (#668)

With this change, the menu bar looks more integrated to the Operating System. The menu can appear if you hit the Alt key. Thanks to Dylan M. Taylor for contributing to fix this.

Exit when clicking on the close icon of the dashboard on Linux (#671)

For most users on Linux, there is no tray icon support. In this situation, when closed, Podman Desktop continues to run in background. Dylan M. Taylor added a property to exit the app by default when clicking on the close icon. For people having tray icon support or with the desire of a different behavior, it is possible to disable it from the Settings.

Other Notable Enhancements​

  • Rename Started into Age in Containers list.(#878)
  • Added domain validation when adding a registry. (#838)
  • Provided a consistent behavior with Podman CLI, podman-machine-default is now the default name when creating a Podman machine from Podman Desktop. (#775)

Notable bug fixes​

  • Fixed error handling when pulling images of Desktop Extensions. (#782)
  • Fixed use of the full height of the screen when displaying log in the details of a container. (#946)
  • Fixed First start of Podman Desktop on flatpak was not seeing the podman engine (#860)

Community Thank You​

🎉 We’d like to say a big thank you to everyone who helped to make Podman Desktop 0.10 even better:

Final Notes​

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

Get the latest release from the Downloads section of the website and boost your development journey with Podman Desktop. Additionally, visit the GitHub repository and see how you can help us make Podman Desktop better.

- + \ No newline at end of file diff --git a/blog/podman-desktop-release-0.11.html b/blog/podman-desktop-release-0.11.html index 3a988dd88be..fddf5bef520 100644 --- a/blog/podman-desktop-release-0.11.html +++ b/blog/podman-desktop-release-0.11.html @@ -13,7 +13,7 @@ - + @@ -24,7 +24,7 @@ Please note, that those binaries are available only on releases and not the pre- mac-docker-compatibility

Allow to toggle on/off the proxy setting #983​

In some context, users need the ability to disable and re-enable the proxy configuration very quickly, without having to entirely reconfigure it. This is now possible from the Podman Desktop settings page, where a toggle to enable/disable the proxy configuration has been added.

Note: extensions can read this information and then update the proxy configuration.

Namespace selection for deploy to Kubernetes #1008​

A new dropdown menu has been added to the deploy to Kubernetes screen to allow selecting the namespace to deploy to. Defaults to defaultnamespace, if unable to get any from kube_client module.

If the user have set kubectl config set-context --current --namespace=NAMESPACE it honors that as the chosen value.

deploy-kubernetes-namespace

Configure Podman binary path #941​

Users may use a custom path to the podman binary. An option within settings (Settings -> Preferences) to allow providing an additional path to Podman binary has been added. This is useful for users who have installed Podman using a package manager and want to use the binary provided by the package manager. Additional information is available in the documentation for Mac users: http://podman-desktop.io/docs/troubleshooting#unable-to-set-custom-binary-path-for-podman-on-macos

custom-path

Provide pre-defined registries #1201​

The experience of configuring a registry is getting simplified for the most popular ones. The user will be able to select a registry from a pre-defined list and will only have to provide the username and password. The following registries will be pre-defined:

  • Dockerhub
  • Red Hat Quay
  • GitHub
  • IBM Container Registry
  • Google Container Registry

UI/UX Improvements​

View Pods logs #1122​

The pods details view provides the ability to view the logs of each containers that might be running in a pod. Moreover, as it can also be hard to scan and identify which container is producing which output, we appended the container name at the beginning of each output and differentiate each container with a different color.

pods-logs

Improved feedback when clicking on container list action icons #1150 #1161​

When starting/stopping or deleting a container, a spinner is now displayed. In case of error, a message indicating that the action failed will also be better indicated.

For containers that exit immediately or short-lived containers, the feedback is also improved and include report of error now provide a better feedback to the user #1161.

Allows to change the default font size for the editor #1160​

An editor is used in several screens of Podman Desktop, from the inspect screen to container's outputs and Kubernetes YAML. The default font size is 10 pixels. It's now possible to adjust the font size to the one the one you prefer. This setting is persisted and will be used for all the editors of Podman Desktop and available from the preferences page (Settings -> Preferences).

Keep expanded state of pods when refreshing containers #1042​

When switching from different screens of the application or simply refreshing the list of containers, the expanded state of each item in the list is now persisted and will be properly restored.

Click on the Pod name redirects to the Pod details page #1159​

The list of containers also displays pods, now clicking on the pod name directly redirects to the Pod details page.

Improved styles of buttons for actions #984​

The style of the buttons for actions on item in the list of in details pages have been improved. The background has been removed, but to make the hover state more visible, the "hover" circle is visble and the icon's color is also changing.

On lists: list-actions

On details pages: details-actions

Improved alignments in pages with lists #1182​

The alignment of the items in the list of containers and pods have been improved. The header of each columns are now aligned with the text. and the actions icons are now aligned with the top of the text.

list-actions

Other Notable Enhancements​

  • Statistics area in container details are always shown. (#1131)
  • Add more descriptive wording and more information to extensions. (#985)
  • Allow to install on-the fly Podman Desktop extensions using an OCI image. (#1187)
  • Display correctly non-multiplexed stream in logs (when using non interactive mode). (#1197)
  • Font changed from white to gray for non-name sections (creation date, size). (#1206)
  • Add Help/about menu for macOS/Windows/Linux. (#1207)

Documentation​

Coming with this new version of Podman Desktop, the documentation has been getting attention (with number of editorial reviews) and new content have been added.

Content for helping users to migrate from Docker to Podman has been added:

Several of other improvements have been made to the documentation and the website:

Notable bug fixes​

  • Update to v0.3.2 Docker Desktop API for extensions - #1070
  • Updated link to the Matrix room - #1076
  • Report error when container name already exists - #1142
  • Fixed connectivity to the Podman machine when the generated socket length is greater than 104 characters in MacOS - #1145
  • Do not use long calls for external clients - #1151
  • Invalid name/tag for images with registries using a different port - #1127
  • Invalid badge count for images when two images have the same tag - #1124
  • Fixed detection of WSL2 - #981
  • Handle invalid kubeconfig files instead of crashing - #953
  • Removed redundant actions from details pages - #1200
  • Fixed registry URL not aligned with header - #1205
  • Moved SVGs to reusable components - #1211

Extensions API has also been improved in this new release:

  • (extension-api): Allows to register a factory for kubernetes connection objects (like for container connections) - #1040
  • (extension-api): List or inspect containers, be notified on events - #1041
  • (extension-api): Allows to get provider notification - #1045
  • (dd-extension-api): Implement toast API - #1154
  • (extension-api): Moved extension properties to preferences - #948
  • (dd-extension-api): Added open dev console on dd webview in development mode - #1071
  • (extension-api): Added notes on extension and frameworks/tooling of Podman Desktop - #1166
  • (extension-api): Documentation on how to write an extension and use the api - #1172
  • (dd-extension-api): DD extensions should see only minimal information on containers - #1191

Community Thank You​

🎉 We’d like to say a big thank you to everyone who helped to make Podman Desktop 0.11 even better:

Final Notes​

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

Get the latest release from the Downloads section of the website and boost your development journey with Podman Desktop. Additionally, visit the GitHub repository and see how you can help us make Podman Desktop better.

- + \ No newline at end of file diff --git a/blog/podman-desktop-release-0.12.html b/blog/podman-desktop-release-0.12.html index d0b33097c5d..90f263c1a30 100644 --- a/blog/podman-desktop-release-0.12.html +++ b/blog/podman-desktop-release-0.12.html @@ -13,14 +13,14 @@ - +

Release Notes - Podman Desktop 0.12

· 5 min read
Stevan Le Meur

This release note covers Podman Desktop 0.12 release changes.

  • Podman Version: Podman 4.4.1 now included in Windows and Mac installers.
  • Containers Configuration: Configure port mappings for an image without exported ports.
  • Windows Home Support: Podman Desktop now supports Windows Home Edition.
  • Start minimized: Option to start Podman Desktop minimized to system tray.
  • UX and UI Improvements: Consistent actions, placeholder for logs, unified icons and others.

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

podman-desktop-0-12-hero

Release Details​

Update to Podman v4.4.1 #1456​

Podman Desktop 0.12 embeds Podman 4.4.1 in Windows and macOS installers. Make sure to upgrade to benefit from the latest Podman features and bug fixes.

Configuring port mappings when an image has no exported port #1265​

With the latest update, users can now add multiple local-to-remote port mappings when starting a container from an image that has no exported ports. This feature provides users with the flexibility to specify which ports on their local machine should map to which ports on the container, even if the container does not have any exported ports by default.

port-mapping

Installing Podman Dekstop on Windows Home Edition #1268​

Podman Desktop 0.12 offers the ability to be installed on Windows Home Edition. The mechanism uses Virtual Machine Platform detection, instead of hyper-v. WSL2 is still requires but can be installed along with the installation process.

install-windows-home-edition-2

Option to automatically minimize Podman Desktop on login #1374​

Podman Desktop now provides a "start minimized" option when users log in onto the laptop. This option, available from the application's settings, can be useful if users want to automatically launch Podman Desktop at log in, but prefer not to have the window visible on the screen. With this feature, you can ensure that Podman Desktop is up and running in the background without any interruption to your workflows.

  • Go to Settings > Preferences > Login: Minimize to activate the option.

minimize-on-login

UI and UX Improvements​

Improved actions consistency #1225​

Actions displayed in the list pages for Images and Containers have been reviewed and made consistent between other pages.

action-consistency-1

Actions displayed in the header of the container's details page have been improved so that the actions are always displayed in the same order.

action-consistency-2

Consistent status icons for Pods, Containers, Images and Volumes #1326, #1377, #1459 and #1245​

The status icons for Pods, Containers, Images, and Volumes have been unified and use consistent states.

pods-status-icon

Icons in empty screens have been updated to use the same consistent SVG icon as the status icons.

empty-screen-2

Placeholder when logs for containers are being fetched #1353​

A placeholder is now displayed when logs are being fetched. placeholder-loading-logs

Fixed alignement in badges from the navigation sidebar #1357​

Badges in the sidebar are now aligned with the title of the section.

alignement-badges

Enable/disable open browser action based on container state #1395 and #1397​

The action to open the browser if a port is opened in a container, is now disabled when the container is stopped. It is also hidden in the kebab menu.

enable-disable-container-actions

Other Notable Enhancements​

  • Display extension icons #1058
  • Solid Icons #1267
  • Differentiate icons compared to status icons #1268
  • Refactors window initializing #1309
  • Change window creation background color to dark #1310
  • Use Podman machine inspect to read the address to connect to the Podman machine #1364
  • Update the editor content when the pod name changes, and disable the deploy button when empty #1403
  • Ability to manually set color of tray icon for Windows and Linux #1243
  • Better UI feedback when starting pods #1242

Documentation​

The documentation had many editorial reviews, and new content.

Notable bug fixes​

  • Fixed handling path with spaces on Windows when installing Podman #1270
  • Removed padding from SVG icons #1253
  • Website: fixed download links for Windows and macOS binaries #1255
  • Fixed prettier commands on Windows #1266
  • Fixed new xterm instance spawn when clicking the logs route #1344
  • Fixed need to wait that telemetry has been initilized before proceeding #1373
  • Fixed new xterm instance spawn when clicking the logs route in pod details#1393
  • Fixed stop spinner if image cannot be retrieved #1394
  • Fixed escape command with quotes only for Windows #1462
  • Fixed random CRC status change #1420

Community Thank You​

🎉 We’d like to say a big thank you to everyone who helped to make Podman Desktop 0.12 even better:

Final Notes​

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

Get the latest release from the Downloads section of the website and boost your development journey with Podman Desktop. Additionally, visit the GitHub repository and see how you can help us make Podman Desktop better.

- + \ No newline at end of file diff --git a/blog/podman-desktop-release-0.13.html b/blog/podman-desktop-release-0.13.html index 12933a78e1f..473d894b715 100644 --- a/blog/podman-desktop-release-0.13.html +++ b/blog/podman-desktop-release-0.13.html @@ -13,7 +13,7 @@ - + @@ -21,7 +21,7 @@

Release Notes - Podman Desktop 0.13

· 4 min read
Tim deBoer

This release note covers Podman Desktop 0.13 release changes.

  • Podman Version: Podman 4.4.4 now included in Windows and Mac installers.
  • Compose: Support for installing Docker Compose.
  • Extensions: Improved extension support for Podman Desktop with additional capabilities.
  • UX and UI Improvements: Welcome page, task manager, resources, and update alerts.

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

Podman-desktop-0-13-hero

Release details​

Update to Podman v4.4.4​

Podman Desktop 0.13 embeds Podman 4.4.4 in Windows and macOS installers #1456.

Compose support​

You can install Docker Compose from the Podman Desktop UI #1578. This will allow you use Compose workflows using Podman.

Extensions​

To make it easier to extend Podman Desktop we have:

UI and UX improvements​

Welcome page #1726​

The first time every user starts Podman Desktop, they will see a welcome page:

welcome-page

Note that the Welcome page will only appear the first time you run Podman Desktop 0.13.0, and none of your settings or assets in Podman Desktop will be affected by it. Over time, this page will be expanded to help with initial setup and configuration.

New Task Manager #1724​

A new Task Manager has been added to the status bar to see the progress (or return to) long running tasks. To start with, building images #1725 and Podman machine #1742 are using the task manager.

task-manager

Updated Resources Settings #1582​

The Settings > Resources page has been updated with a new design, making it easier to see and control your providers from a single place.

resources

The other settings pages have been updated for consistency with this new design.

Update Alerts #1827​

A new alert button will appear in the status bar when future updates are available.

Prune buttons #1481, #1482, #1484​

We've added buttons to prune unused volumes #1481, images #1482 and pods #1484.

prune-image

Other notable enhancements​

  • Kubernetes pods are now shown in the Pods view #1312
  • Easy button to fix Docker compatibility mode on macOS #1697
  • Display extension icons #1058
  • API to cancel long running tasks #1777

Documentation​

The documentation has new content:

Notable bug fixes​

  • Periodically check and refresh Podman connection on Windows and Mac #1662
  • Fix inconsistent Log view behaviour #1710
  • Don't create route for regular Kubernetes clusters #1707
  • Fix copy button on empty screen #1804
  • Register extension tray items correctly #1778 and handle updates #1800

Community thank you​

🎉 We’d like to say a big thank you to everyone who helped to make Podman Desktop 0.13 even better:

Final notes​

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

Get the latest release from the Downloads section of the website and boost your development journey with Podman Desktop. Additionally, visit the GitHub repository and see how you can help us make Podman Desktop better.

- + \ No newline at end of file diff --git a/blog/podman-desktop-release-0.14.html b/blog/podman-desktop-release-0.14.html index e95865b1f73..e57e38ec97f 100644 --- a/blog/podman-desktop-release-0.14.html +++ b/blog/podman-desktop-release-0.14.html @@ -13,7 +13,7 @@ - + @@ -46,7 +46,7 @@ making it easier to see and change preferences. Changes are live, no more Update 1927 This is more usable, one less prompt, and solves a window-layering issue for some users!

telemetry prompt

Other notable enhancements​

  • Extension support for opening an external URL 2028 and accessing the clipboard 2023

Documentation​

Naturally, we have a section in the documentation just for Kind.

Notable bug fixes​

  • Avoid a dialog box if unable to check for updates 2062
  • Unable to get to the Dashboard if Kind (or Kubernetes) cluster was not running 2052

Final notes​

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

Get the latest release from the Downloads section of the website and boost your development journey with Podman Desktop. Additionally, visit the GitHub repository and see how you can help us make Podman Desktop better.

- + \ No newline at end of file diff --git a/blog/podman-desktop-release-0.15.html b/blog/podman-desktop-release-0.15.html index ebf4534d064..1c0069f1660 100644 --- a/blog/podman-desktop-release-0.15.html +++ b/blog/podman-desktop-release-0.15.html @@ -13,7 +13,7 @@ - + @@ -41,7 +41,7 @@ provider properties/creation pages

Other Notable Enhancements​

  • We know which Settings page is used the most often, so now it's the default: Settings > Resources #2105.

  • Extensions can now use the Tasks API to let long running tasks continue in the background #2019 and the existing withProgress API also uses the task manager now #2187.

Task API

  • Images are now sorted by age #2311.

  • When you start/stop a container or pod, the button is now animated instead of having an separate spinner #2101.

  • The Settings > Preferences page now has a search bar #2128.

Search preferences

  • The Help page has been updated #431.

Updated Help

Notable Bug Fixes​

  • There was no way to see log or outcome if you leave the Kind cluster creation page #2079.
  • Kind image load doesn't show a notification #2225.
  • Fix odd selection in Settings > Extensions #2130.
  • Menus are now cleaned up properly when extensions are stopped #2188.
  • Kind clusters are now cleaned up when Podman machine is stopped #2306.

Final notes​

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

Get the latest release from the Downloads section of the website and boost your development journey with Podman Desktop. Additionally, visit the GitHub repository and see how you can help us make Podman Desktop better.

- + \ No newline at end of file diff --git a/blog/podman-desktop-release-1.0.html b/blog/podman-desktop-release-1.0.html index e544459c5cd..9d27cf47bc3 100644 --- a/blog/podman-desktop-release-1.0.html +++ b/blog/podman-desktop-release-1.0.html @@ -13,7 +13,7 @@ - + @@ -94,7 +94,7 @@ to get us here:

ucomesdag, xbabalov, zezo2019.

Final notes​

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

Get the latest release from the Downloads section of the website and boost your development journey with Podman Desktop. Additionally, visit the GitHub repository and see how you can help us make Podman Desktop better.

- + \ No newline at end of file diff --git a/blog/podman-desktop-release-1.1.html b/blog/podman-desktop-release-1.1.html index 4b865ecdaf4..6c01d148b84 100644 --- a/blog/podman-desktop-release-1.1.html +++ b/blog/podman-desktop-release-1.1.html @@ -13,7 +13,7 @@ - + @@ -26,7 +26,7 @@ automatically check for and install extension updates.

- + \ No newline at end of file diff --git a/blog/podman-desktop-release-1.2.html b/blog/podman-desktop-release-1.2.html index cb72629b683..ff431e42915 100644 --- a/blog/podman-desktop-release-1.2.html +++ b/blog/podman-desktop-release-1.2.html @@ -13,13 +13,13 @@ - +

Release Notes - Podman Desktop 1.2

· 7 min read
Charlie Drage

Podman Desktop 1.2 Release! 🎉

We're excited to announce the release of Podman Desktop version 1.2.0! This release includes many new features (Kubernetes, Compose and extension support!), bug fixes, and improvements to enhance your container management experience. Here's a summary of the key changes in this release:

  • Added start/stop/delete/restart buttons for Compose: You can now make changes to an entire Compose group of containers
  • Kubernetes context on the status bar: Choose from multiple Kubernetes contexts more easily all from the status bar
  • Rename images: Rename an image with a click of a button
  • Protocol handler support: Added support for protocol handlers such as open podman-desktop:extension/redhat.openshift-local
  • Troubleshooting page: A troubleshooting page for helping diagnose Podman Desktop related development issues

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

Podman-desktop-1-2-hero

Release Details​

Added start/stop/delete/restart buttons for Compose​

In the last month we've been addind support for more Compose features. Before you were only able to control a group of containers if they were in a Pod. Now we have added the ability to control a group of Compose containers. You can now start, stop, delete and restart a group of containers launched by either docker-compose or podman-compose.

Stay tuned as we add even more features to Compose! If you have any feedback or feature requests, feel free to open an issue or start a discussion on GitHub.

Kubernetes context on the status bar​

With Kubernetes context on the status bar, you can switch from one context to another in just a couple of clicks. Easily switch to a different cluster all together. If there are multiple contexts available, you can now click and pick which one to use.

Rename images​

Deployed an image but now you need to rename it / add a new tag? Podman Desktop allows you to edit an image now. Thanks to an awesome contributor @tuckerrc who added the new feature.

Troubleshooting page​

Developing an extension for Podman Desktop? Want to view the logs of Podman Desktop as well as ping your container connection? We now have a troubleshooting page!

Click on the lightbulb button on the bottom right to access the page.

Protocol handler support​

Podman Desktop now supports protocol handling when using the terminal! Want to access your favourite extension directly from a script or the terminal? If you type in open podman-desktop:extension/redhat.openshift-local in the terminal, Podman Desktop will automatically load up to the correct extension.

Other Notable Features​

  • Background colors and FormPage (PR #2977)
  • Add ability to add insecure registry / skipping cert verify (PR #2896)
  • Add support for icon contribution (PR #2984)
  • Add warning dialog message that virtual machine has low memory limit (PR #2822)
  • Propose indexed name for new pod (PR #3028)
  • Add restart button after enabling / disabling mac os compatibility (PR #2841)
  • Add environment related helper constants (PR #3079)
  • Allow entrypoint and cmd when starting container (PR #3031)
  • Add a way to debug stores in troubleshooting page (PR #3121)
  • Add custompick component (#2855) (PR #3012)
  • Dynamic breadcrumbs (PR #3119)
  • Icons on form pages (PR #3155)
  • Switch more pages to formpage (PR #3162)
  • Add rename image button (PR #2588)
  • Fixed headers, improved scrollbars (PR #2863)
  • Reports warnings on failed kube deploy, fixes error out (PR #3050)
  • Kube context on statusbar (PR #2755)
  • Install provider if not installed when clicking on create new button (#2706) (PR #2817)
  • Add tag and authenticated push capacity to the extension API (PR #2876)
  • Add navigation bar e2e tests (PR #2950)

Documentation Updates​

  • Fix documentation for building image of extensions (PR #2873)
  • Add Minikube install docs (PR #2824)
  • Add Minikube documentation (PR #2694)
  • Updated Building an image procedure (PR #2964)
  • Starting a container (PR #2958)
  • Pulling an image (PR #2956)
  • Updated selecting containers to run in a pod (PR #2970)
  • Pushing an image to a registry (PR #2969)
  • How to add an insecure registry (PR #2953)
  • Add documentation for lima (PR #2995)
  • Replace broken link to podman.io (PR #2994)
  • Authenticating to a pre-configured registry (PR #2965)
  • Lima is not a container engine (PR #3051)
  • Using the Troubleshooting page (PR #3083)
  • View and select your current Kubernetes context in the status bar (PR #3090)

Notable Bug Fixes​

  • Deleting a running pod generates an error (PR #2827)
  • If kubeconfig is empty, does not try to do things, cancel (PR #2874)
  • Async telemetry startup (PR #2885)
  • Do not block startup while waiting for kube resource refresh (PR #2884)
  • Images list too wide (PR #2918)
  • Compose deactivate function never called (PR #2922)
  • Auto-scrolling on form pages, layout issues (PR #2927)
  • Show current context in quick pick (PR #2920)
  • Remove sticky position of loader in dashboard UI (#2535) (PR #2959)
  • Undo change that broke the website (PR #2992)
  • Detailspage, resizing & consistency (PR #2987)
  • Quick pick click to close and over nav bar (PR #2758)
  • Only show empty screen when no pods (PR #2929)
  • Do not redirect to /pods when deleting pod in containerlist (PR #2963)
  • Bulk delete on pods should call the pod deletion (PR #2979)
  • Update nodejs version to 18 in .nvmrc to fix yarn install failure (PR #2989)
  • Website check targets (PR #2996)
  • Don't show exception to user (PR #3034)
  • Interpret arguments given to info command for example (PR #3015)
  • Change defaults for Podman machine (PR #3061)
  • Normalize development/production folders path (PR #3113)
  • Calculate machine socket path for linux (PR #3070)
  • Replace backslash with slash so to support rendering on Windows (#3120) (PR #3122)
  • Keep stdout and stderr in the error object for Docker Desktop extensions (PR #3014)
  • Mark task completed if there's a failure (PR #3016)
  • Handle invalid kubeconfig file (PR #3129)
  • Do not remove registries when podman extension is stopping (PR #3136)
  • Warning should be amber (PR #3153)
  • Load user extensions from plugins as removable (PR #3152)
  • Images with spaces in entrypoints or commands fail to start (PR #3161)
  • Scrolling offscreen when clicking checkbox (PR #3178)
  • Avoid messagebox expanding offscreen (PR #2778)
  • Release-notes-generator run failure (PR #2752)
  • Unable to do a new build if the previous one failed (PR #2721)

Community Thank You​

🎉 We’d like to say a big thank you to everyone who helped to make Podman Desktop even better.

A big shoutout to @afbjorklund, @tuckerrc and @evanshortiss who contributed to this release!

Final notes​

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

Get the latest release from the Downloads section of the website and boost your development journey with Podman Desktop. Additionally, visit the GitHub repository and see how you can help us make Podman Desktop better.

- + \ No newline at end of file diff --git a/blog/podman-desktop-release-1.3.html b/blog/podman-desktop-release-1.3.html index 327fe272962..5e5b5f30d27 100644 --- a/blog/podman-desktop-release-1.3.html +++ b/blog/podman-desktop-release-1.3.html @@ -13,14 +13,14 @@ - +

Release Notes - Podman Desktop 1.3

· 6 min read
Denis Golovin

Podman Desktop 1.3 Release! 🎉

This is essentially a bug-fix release to fix various issues in UI, extension engine and featured extensions, but as usual we also added a few new features.

  • Podman 4.6.1: Podman 4.6.1 included in Windows and Mac installers
  • Podman user-mode networking support to Windows/WSL: A new switch `User mode networking' is available when creating Podman machine on Windows for Podman 4.6.0+ to configure podman to work in certain VPN setups and other specialized networking configurations
  • Compose group new UI elements: You can now see summary, inspect, deploy to kubernetes, generate kube yaml and view logs
  • Extension packs and extension dependencies: Install group of extensions in one click
  • Resource details page update: See summary and log for resource
  • Create Kind cluster form update: A new Node's container image field can be used to specify the Kubernetes version used for the control-planed
  • Support Docker Desktop extensions using a backend: When loading Docker Desktop extension the containers are created in the backend as described in the vm section of extension's descriptor
  • Podman Initial Onboarding (preview): Install and configure podman using included installer

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

Podman-desktop-1-3-bug-swatting

Release Details​

Compose group Logs tab #3176​

When clicking on the group of containers, you can now view the logs of the entire group of compose containers and don't need to open log for every component individually.

Screenshot 2023-07-11 at 12 48 47 PM

Podman user-mode networking support to Windows/WSL #3251​

Certain VPN setups or other specialized networking configs will block traffic from the virtual WSL networking device, resulting in the podman WSL backend from being unable to contact systems on the VPN, and potentially losing internet access altogether. The new switch allows you to create a podman VM machine configured to work correctly in mentioned above networking environments.

user

Compose group Summary tab #3317,​

Compose group Summary tab shows all containers in the group and let you navigate to Details page for specific container.

Compose group Inspect tab #3316​

Compose group Inspect tab shows an array of "container inspect" from docker / podman.

Deploy to kubernetes in compose actions #3299​

A button to deploy to kubernetes added to Compose group.

Generate Kube in Compose actions and Kube tab in compose details #3253​

Generate Kube item added to Compose actions and "Kube" tab is now available in Compose details view.

Install multiple extensions using extension pack #3150​

An Extension pack introduced in Extension engine is a way to declare set of extensions to install them all at once.

Customize icons from extension #3131​

Extensions now can customize icons for list elements using when clause.

image

Resource details page update #1923​

If you click on the arrow icon next to a resource name it will open up a details page (similarly to how clicking on a container in the container list opens up a details page).

image

Node's container image field added to Create a Kind cluster form #3508​

The new Node's container image field can be used to specify the Kubernetes version used for the control-planed.

image

Support Docker Desktop extensions using a backend #3435​

Podman Desktop now loads the containers in the backend as described in the vm section of extension descriptor the same way as Docker Desktop does.

Initial onboarding implementation for podman (experimental) #3308​

This is the initial implementation for the onboarding feature. It only covers a simple onboarding for podman. Check system requirements -> install podman -> yay! Done!

Notable Bug Fixes​

  • Updating videos to be adaptive for mobile by @mairin #3229
  • Consistent max width and padding in settings by @deboer-tim #3232
  • Settings navigation bar resizing by @deboer-tim in #3231
  • Move new registry button to header by @deboer-tim #3245
  • Bigger lima logo by @afbjorklund #3248
  • Horizontal docker logo by @afbjorklund #3236
  • Respect LIMA_HOME environment variable by @afbjorklund #3254
  • Add check before writing to terminal by @lstocchi #3263
  • Wait until remote side has fully initialized the extensions by @benoitf #3257
  • Fix loader not centered horizontally by @benoitf #3270
  • Troubleshooting still waiting after failure by @deboer-tim #3354
  • Store error for build by @cdrage #3365
  • Missing checkbox tooltips by @deboer-tim #3380
  • Load compose logs async not await by @cdrage #3377
  • Set rootful connection when starting rootful machine by @lstocchi #3364
  • Default last page by @deboer-tim #3388
  • Avoid dashboard displaying providers starting while they don't by @benoitf #3451
  • Do not use extensionInfo until it is defined by @benoitf #V
  • Allow BASIC authentication (all caps) by @cdrage #3471
  • Allow single domain registry such as localhost:5000 by @cdrage #3468
  • Create /usr/local/bin directory if it does not exist on binary install by @cdrage #3425
  • Only delete selected pods by @deboer-tim #
  • Add back 'Done' text on the button by @benoitf #3487
  • Do not wait for more than 5s when checking for podman ping by @benoitf #3497
  • Add proxy support for extension using patching get and request approach by @dgolovin #2825
  • Refresh component when field is updated by @benoitf #3525
  • Higher-res icons for featured extensions list by @mairin #3511
  • Main nav selection by @deboer-tim #3510
  • kube event error when switching context by @jeffmaury #3494
  • Reset error message each time we pull image by @benoitf #3550

Community Thank You​

🎉 We’d like to say a big thank you to everyone who helped to make Podman Desktop even better.

A warm welcome to @rostalan and @axel7083 who made their first contribution to the project in this release.

Final Notes​

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

Get the latest release from the Downloads section of the website and boost your development journey with Podman Desktop. Additionally, visit the GitHub repository and see how you can help us make Podman Desktop better.

- + \ No newline at end of file diff --git a/blog/podman-desktop-release-1.4.html b/blog/podman-desktop-release-1.4.html index 4b8aa5c0538..870eb3467cd 100644 --- a/blog/podman-desktop-release-1.4.html +++ b/blog/podman-desktop-release-1.4.html @@ -13,13 +13,13 @@ - +

Release Notes - Podman Desktop 1.4

· 4 min read
Jeff Maury

Podman Desktop 1.4 Release! 🎉

This is essentially a bug-fix release to fix various issues in UI, but as usual we also added a few new features.

  • Podman 4.6.2: Podman 4.6.2 included with Podman Desktop 1.4
  • Windows Arm64: Native Windows on Arm64 installers and binaries
  • Port range mapping: Start containers and map a range of ports
  • Terminal UX Improvement: Persistent terminal sessions when SSH'ing in a container
  • Volume Creation: Create volume from the Volumes page
  • Bash support: Terminals are now using bash if available.

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

Podman-desktop-1-4-juggling

Release Details​

Port range mapping #3654​

When starting a new container, you can now map a port range between host and container. If the range is not valid between host and container, an error is raised.

Range mapping

Terminal lifetime #3725​

When a terminal is opened for a container, it can now be reused after you switched to another part of the Podman Desktop UI.

terminal lifetime

Create volume #3742​

The Volumes tab now has a Create volume button. The Create volume UI has a single field for the volume name.

create volume

bash support #3750​

When a terminal is opened for a container, if bash is available within the container, it will be used. Otherwise, sh will be used.

bash sh

Notable Bug Fixes​

  • Reduce API calls when listing containers by @benoitf #3489
  • Removing a connection(podman machine) should redirect to previous page by @benoitf #3576
  • Enhance error message when image is not there by @benoitf #3587
  • Dispose kind install button when extension is deactivated (#3586) by @lstocchi #3610
  • Replace backslash/slash on windows when building image (#3465) by @lstocchi #3618
  • Handle null value in container command (#3620) by @lstocchi #3625
  • Add maximum activation time for extensions by @benoitf #3446
  • Handle single non-spread arguments by @benoitf #3641
  • Grab usage data of volumes only on-demand by @benoitf #3635
  • Add arm64 binaries for Windows by @benoitf #3643
  • Include right airgap file for Windows and arm64 by @benoitf #3651
  • Redirect to previous page when removing a kubernetes connection by @benoitf #3650
  • Support port ranges when starting a container (#3204) by @lstocchi #3654
  • Add a strict undefined check to messagebox result (#3692) by @lstocchi #3699
  • Only restart if a machine is running by @cdrage #3491
  • Session to the terminal is reused by @benoitf #3725
  • Disable next button and show try again when onboarding failed (#3616) by @lstocchi #3711
  • Add podman in PATH after updating process environment PATH (#3729) by @lstocchi #3730
  • Allow to create a volume by @benoitf #3742
  • Using bash if available otherwise sh in terminal by @axel7083 #3750
  • Allow to embed existing component to onboarding (#3755) by @lstocchi #3763
  • Some containers never return logs, do not wait for them by @dgolovin #3784
  • Remove cancel button when on final onboarding step (#3771) by @lstocchi #3802
  • Onboarding add link micromark for commands by @cdrage #3747
  • Mounts can be null when using older podman by @afbjorklund #3806
  • Remove redundant step completion check when onboarding gets started by @lstocchi #3798
  • Ability to click enter in pull image name input by @deboer-tim #3850
  • Set proxy environment variable when launching process by @jeffmaury #3838
  • The socket location was moved for new podman by @afbjorklund #3853
  • Don't log console errors when activating lima extension by @afbjorklund #3852

Community Thank You​

🎉 We’d like to say a big thank you to everyone who helped to make Podman Desktop even better.

A warm welcome to @tomgoren, @Julian, @Gelob and @cedricclyburn who made their first contribution to the project in this release.

Final Notes​

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

Get the latest release from the Downloads section of the website and boost your development journey with Podman Desktop. Additionally, visit the GitHub repository and see how you can help us make Podman Desktop better.

- + \ No newline at end of file diff --git a/blog/running-a-local-kubernetes-cluster-with-podman-desktop.html b/blog/running-a-local-kubernetes-cluster-with-podman-desktop.html index a188129aa7f..c6c791b26b0 100644 --- a/blog/running-a-local-kubernetes-cluster-with-podman-desktop.html +++ b/blog/running-a-local-kubernetes-cluster-with-podman-desktop.html @@ -13,7 +13,7 @@ - + @@ -31,7 +31,7 @@ It is configured to communicate with either the Redis follower or leader Service The frontend exposes a JSON interface, and serves a jQuery-Ajax-based UX.

With Podman Desktop, you can prepare the Guestbook frontend image and container on your local container engine, and deploy the results to Kubernetes pods and services. This is functionally equal to the frontend deployment that the Kubernetes example propose.

Procedure​

  1. Open Images > Pull an image.
    1. Image to Pull: enter gcr.io/google_samples/gb-frontend:v5
    2. Click Pull image to pull the image to your container engine local image registry.
    3. Wait for the pull to complete.
    4. Click Done to get back to the images list.
  2. Search images: enter gb-frontend:v5 to find the image.
  3. Click to open the Create a container from image dialog.
    1. Container name: enter frontend,
    2. Local port for 80/tcp: 9000.
    3. Click Start Container to start the container in your container engine.
  4. Search containers: enter frontend to find the running container.
  5. Click to stop the container: you do not need it to run in the container engine.
  6. Click > Deploy to Kubernetes to open the Deploy generated pod to Kubernetes screen.
    1. Pod Name: enter frontend.
    2. Use Kubernetes Services: select Replace hostPort exposure on containers by Services. It is the recommended way to expose ports, as a cluster policy might prevent to use hostPort.
    3. Expose service locally using Kubernetes Ingress: select Create a Kubernetes ingress to get access to the ports that this pod exposes, at the default ingress controller location. Example: on a default Kind cluster created with Podman Desktop: http://localhost:9090. Requirements: your cluster has an ingress controller`.
    4. Kubernetes namespaces: select default.
    5. Click Deploy. Deploy generated frontend pod to Kubernetes screen
    6. Wait for the pod to reach the state: Phase: Running.
    7. Click Done.

Verification​

  1. The Pods screen lists the running frontend pod.

    `frontend` pod is running

  2. Go to http://localhost:9090: the Guestbook application is running.

- + \ No newline at end of file diff --git a/blog/tags.html b/blog/tags.html index 4db5e95aa22..6590b654e7f 100644 --- a/blog/tags.html +++ b/blog/tags.html @@ -13,13 +13,13 @@ - +

Tags

- + \ No newline at end of file diff --git a/blog/tags/codespaces.html b/blog/tags/codespaces.html index 6105b55dc96..05c0a925c14 100644 --- a/blog/tags/codespaces.html +++ b/blog/tags/codespaces.html @@ -13,13 +13,13 @@ - +

One post tagged with "codespaces"

View All Tags

· 7 min read
Florent Benoit

GitHub announced last week that Codespaces is available for everyone and it includes free minutes.

Let see how we can use a Development Container having all the tools to build and run Podman Desktop. The Development Container works locally using Visual Studio Code but in this blog post we will see how it works directly with a simple click from GitHub.

The challenges are to run a desktop tool (Podman Desktop) and running a container engine (Podman) inside this Development Container without using too many memory !

- + \ No newline at end of file diff --git a/blog/tags/compose.html b/blog/tags/compose.html index f775df44727..6971f373579 100644 --- a/blog/tags/compose.html +++ b/blog/tags/compose.html @@ -13,13 +13,13 @@ - +

One post tagged with "compose"

View All Tags

· 4 min read
Tim deBoer

This release note covers Podman Desktop 0.13 release changes.

  • Podman Version: Podman 4.4.4 now included in Windows and Mac installers.
  • Compose: Support for installing Docker Compose.
  • Extensions: Improved extension support for Podman Desktop with additional capabilities.
  • UX and UI Improvements: Welcome page, task manager, resources, and update alerts.

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

Podman-desktop-0-13-hero

- + \ No newline at end of file diff --git a/blog/tags/devcontainer.html b/blog/tags/devcontainer.html index 39811b29d60..7cd8d69a741 100644 --- a/blog/tags/devcontainer.html +++ b/blog/tags/devcontainer.html @@ -13,13 +13,13 @@ - +

One post tagged with "devcontainer"

View All Tags

· 7 min read
Florent Benoit

GitHub announced last week that Codespaces is available for everyone and it includes free minutes.

Let see how we can use a Development Container having all the tools to build and run Podman Desktop. The Development Container works locally using Visual Studio Code but in this blog post we will see how it works directly with a simple click from GitHub.

The challenges are to run a desktop tool (Podman Desktop) and running a container engine (Podman) inside this Development Container without using too many memory !

- + \ No newline at end of file diff --git a/blog/tags/docker.html b/blog/tags/docker.html index da83958f58b..6c17e36b6db 100644 --- a/blog/tags/docker.html +++ b/blog/tags/docker.html @@ -13,13 +13,13 @@ - +

One post tagged with "docker"

View All Tags

· 5 min read
Florent Benoit

The 5 things to know being a Docker user by using Podman Desktop:

  • Use a single UI: Podman Desktop works with several container engines, including Docker.
  • The compatibility mode: How to ensure tools are working with Podman instead of Docker.
  • Compose support: How to work with Compose files and Podman.
  • Kubernetes support: How to use Kubernetes with Podman.
  • Security: Use rootless mode or containers without root privileges.

5-things-to-know-for-a-docker-user-hero

- + \ No newline at end of file diff --git a/blog/tags/kind.html b/blog/tags/kind.html index f8fa49407a0..87d6cce2cf3 100644 --- a/blog/tags/kind.html +++ b/blog/tags/kind.html @@ -13,7 +13,7 @@ - + @@ -27,7 +27,7 @@ of Podman Desktop: not just local container engines, but Kubernetes too. More im providing tools that allow you to manage both environments and seamlessly move between them.

Some of these features were available in development mode over the last few releases, but since they are now in the release build, we will do a full roundup and talk about all the Kind features.

  • Kind Installation: Install Kind from the status bar
  • Manage Kind Clusters: Create and manage Kind clusters from Settings > Resources
  • Using Kind: Deploying YAML and sharing images to a cluster
  • Kind Ingress: Install a Contour ingress controller
  • UX and UI Improvements: Updated preferences and telemetry prompt

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

Podman-desktop-0-14-hero

- + \ No newline at end of file diff --git a/blog/tags/kubernetes.html b/blog/tags/kubernetes.html index 6d4a0a85959..539414c8865 100644 --- a/blog/tags/kubernetes.html +++ b/blog/tags/kubernetes.html @@ -13,7 +13,7 @@ - + @@ -29,7 +29,7 @@ of Podman Desktop: not just local container engines, but Kubernetes too. More im providing tools that allow you to manage both environments and seamlessly move between them.

Some of these features were available in development mode over the last few releases, but since they are now in the release build, we will do a full roundup and talk about all the Kind features.

  • Kind Installation: Install Kind from the status bar
  • Manage Kind Clusters: Create and manage Kind clusters from Settings > Resources
  • Using Kind: Deploying YAML and sharing images to a cluster
  • Kind Ingress: Install a Contour ingress controller
  • UX and UI Improvements: Updated preferences and telemetry prompt

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

Podman-desktop-0-14-hero

· 4 min read
Tim deBoer

This release note covers Podman Desktop 0.13 release changes.

  • Podman Version: Podman 4.4.4 now included in Windows and Mac installers.
  • Compose: Support for installing Docker Compose.
  • Extensions: Improved extension support for Podman Desktop with additional capabilities.
  • UX and UI Improvements: Welcome page, task manager, resources, and update alerts.

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

Podman-desktop-0-13-hero

· 5 min read
Stevan Le Meur

This release note covers Podman Desktop 0.12 release changes.

  • Podman Version: Podman 4.4.1 now included in Windows and Mac installers.
  • Containers Configuration: Configure port mappings for an image without exported ports.
  • Windows Home Support: Podman Desktop now supports Windows Home Edition.
  • Start minimized: Option to start Podman Desktop minimized to system tray.
  • UX and UI Improvements: Consistent actions, placeholder for logs, unified icons and others.

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

podman-desktop-0-12-hero

· 10 min read
Stevan Le Meur

This release note covers Podman Desktop 0.11 release changes.

  • Air-Gapped Installation: New all-in-one binaries for air-gapped installation.
  • Feedback: Submit feedback directly from Podman Desktop.
  • Docker Compatibility Mode: Information about the Docker compatibility mode.
  • Proxy Setting: Toggle on/off the proxy setting.
  • Deploy to Kubernetes: Select the namespace to deploy to Kubernetes.
  • Registry Configuration: Simplified registry configuration for well known registries.
  • UX/UI Improvements: View pod's container logs, better visual feedback, configurable editor font size, and more.

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

· 5 min read
Dev Kumar

This release note covers Podman Desktop 0.10 release changes.

  • Containers Configuration: Container creation wizzard allowing to define environment variables, networking and more configuration options.
  • Kubernetes Improvements: Play Kubernetes YAML, custom Kubeconfig path support, reload of kube context.
  • Registries Configuration: Revamped registries configuration UI.
  • Podman Version: Podman 4.3.1 now included in Windows and Mac installers.
  • UX/UI Improvements: Improved lists, better contrast, and more.

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

- + \ No newline at end of file diff --git a/blog/tags/migrating.html b/blog/tags/migrating.html index b34e46f327b..5525a1a00b2 100644 --- a/blog/tags/migrating.html +++ b/blog/tags/migrating.html @@ -13,13 +13,13 @@ - +

One post tagged with "migrating"

View All Tags

· 5 min read
Florent Benoit

The 5 things to know being a Docker user by using Podman Desktop:

  • Use a single UI: Podman Desktop works with several container engines, including Docker.
  • The compatibility mode: How to ensure tools are working with Podman instead of Docker.
  • Compose support: How to work with Compose files and Podman.
  • Kubernetes support: How to use Kubernetes with Podman.
  • Security: Use rootless mode or containers without root privileges.

5-things-to-know-for-a-docker-user-hero

- + \ No newline at end of file diff --git a/blog/tags/openshift.html b/blog/tags/openshift.html index 4396127fb51..6115f3cb335 100644 --- a/blog/tags/openshift.html +++ b/blog/tags/openshift.html @@ -13,7 +13,7 @@ - + @@ -23,7 +23,7 @@ log for every component individually.

Click here to download it!

Podman-desktop-1-1-hero

· 5 min read
Tim deBoer

Podman Desktop 1.0 Release! 🎉

We still have many things planned, but with a little polish and a few more bug fixes we felt we've reached a level of maturity and it is now time to declare our 1.0 release.

Thank you to everyone who has been with us on this journey so far! Please keep the feedback coming!

  • Highlighting Featured Extensions: Easily find and install new extensions.
  • Featured Extensions: Two new extensions supporting OpenShift.
  • Podman Machine as Root: Ability to run a Podman machine as root.
  • UX and UI Improvements: Opening external websites, editing numbers, and tooltips.

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

Podman-desktop-1-0-hero

- + \ No newline at end of file diff --git a/blog/tags/podman-desktop.html b/blog/tags/podman-desktop.html index bba23c45146..bccfd9f5e11 100644 --- a/blog/tags/podman-desktop.html +++ b/blog/tags/podman-desktop.html @@ -13,7 +13,7 @@ - + @@ -29,7 +29,7 @@ of Podman Desktop: not just local container engines, but Kubernetes too. More im providing tools that allow you to manage both environments and seamlessly move between them.

Some of these features were available in development mode over the last few releases, but since they are now in the release build, we will do a full roundup and talk about all the Kind features.

  • Kind Installation: Install Kind from the status bar
  • Manage Kind Clusters: Create and manage Kind clusters from Settings > Resources
  • Using Kind: Deploying YAML and sharing images to a cluster
  • Kind Ingress: Install a Contour ingress controller
  • UX and UI Improvements: Updated preferences and telemetry prompt

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

Podman-desktop-0-14-hero

· 4 min read
Tim deBoer

This release note covers Podman Desktop 0.13 release changes.

  • Podman Version: Podman 4.4.4 now included in Windows and Mac installers.
  • Compose: Support for installing Docker Compose.
  • Extensions: Improved extension support for Podman Desktop with additional capabilities.
  • UX and UI Improvements: Welcome page, task manager, resources, and update alerts.

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

Podman-desktop-0-13-hero

· 5 min read
Florent Benoit

The 5 things to know being a Docker user by using Podman Desktop:

  • Use a single UI: Podman Desktop works with several container engines, including Docker.
  • The compatibility mode: How to ensure tools are working with Podman instead of Docker.
  • Compose support: How to work with Compose files and Podman.
  • Kubernetes support: How to use Kubernetes with Podman.
  • Security: Use rootless mode or containers without root privileges.

5-things-to-know-for-a-docker-user-hero

· 5 min read
Stevan Le Meur

This release note covers Podman Desktop 0.12 release changes.

  • Podman Version: Podman 4.4.1 now included in Windows and Mac installers.
  • Containers Configuration: Configure port mappings for an image without exported ports.
  • Windows Home Support: Podman Desktop now supports Windows Home Edition.
  • Start minimized: Option to start Podman Desktop minimized to system tray.
  • UX and UI Improvements: Consistent actions, placeholder for logs, unified icons and others.

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

podman-desktop-0-12-hero

· 10 min read
Stevan Le Meur

This release note covers Podman Desktop 0.11 release changes.

  • Air-Gapped Installation: New all-in-one binaries for air-gapped installation.
  • Feedback: Submit feedback directly from Podman Desktop.
  • Docker Compatibility Mode: Information about the Docker compatibility mode.
  • Proxy Setting: Toggle on/off the proxy setting.
  • Deploy to Kubernetes: Select the namespace to deploy to Kubernetes.
  • Registry Configuration: Simplified registry configuration for well known registries.
  • UX/UI Improvements: View pod's container logs, better visual feedback, configurable editor font size, and more.

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

· 5 min read
Dev Kumar

This release note covers Podman Desktop 0.10 release changes.

  • Containers Configuration: Container creation wizzard allowing to define environment variables, networking and more configuration options.
  • Kubernetes Improvements: Play Kubernetes YAML, custom Kubeconfig path support, reload of kube context.
  • Registries Configuration: Revamped registries configuration UI.
  • Podman Version: Podman 4.3.1 now included in Windows and Mac installers.
  • UX/UI Improvements: Improved lists, better contrast, and more.

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

· 7 min read
Florent Benoit

GitHub announced last week that Codespaces is available for everyone and it includes free minutes.

Let see how we can use a Development Container having all the tools to build and run Podman Desktop. The Development Container works locally using Visual Studio Code but in this blog post we will see how it works directly with a simple click from GitHub.

The challenges are to run a desktop tool (Podman Desktop) and running a container engine (Podman) inside this Development Container without using too many memory !

- + \ No newline at end of file diff --git a/blog/tags/release.html b/blog/tags/release.html index 5a65679e042..64893ae3797 100644 --- a/blog/tags/release.html +++ b/blog/tags/release.html @@ -13,7 +13,7 @@ - + @@ -29,7 +29,7 @@ of Podman Desktop: not just local container engines, but Kubernetes too. More im providing tools that allow you to manage both environments and seamlessly move between them.

Some of these features were available in development mode over the last few releases, but since they are now in the release build, we will do a full roundup and talk about all the Kind features.

  • Kind Installation: Install Kind from the status bar
  • Manage Kind Clusters: Create and manage Kind clusters from Settings > Resources
  • Using Kind: Deploying YAML and sharing images to a cluster
  • Kind Ingress: Install a Contour ingress controller
  • UX and UI Improvements: Updated preferences and telemetry prompt

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

Podman-desktop-0-14-hero

· 4 min read
Tim deBoer

This release note covers Podman Desktop 0.13 release changes.

  • Podman Version: Podman 4.4.4 now included in Windows and Mac installers.
  • Compose: Support for installing Docker Compose.
  • Extensions: Improved extension support for Podman Desktop with additional capabilities.
  • UX and UI Improvements: Welcome page, task manager, resources, and update alerts.

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

Podman-desktop-0-13-hero

· 5 min read
Stevan Le Meur

This release note covers Podman Desktop 0.12 release changes.

  • Podman Version: Podman 4.4.1 now included in Windows and Mac installers.
  • Containers Configuration: Configure port mappings for an image without exported ports.
  • Windows Home Support: Podman Desktop now supports Windows Home Edition.
  • Start minimized: Option to start Podman Desktop minimized to system tray.
  • UX and UI Improvements: Consistent actions, placeholder for logs, unified icons and others.

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

podman-desktop-0-12-hero

· 10 min read
Stevan Le Meur

This release note covers Podman Desktop 0.11 release changes.

  • Air-Gapped Installation: New all-in-one binaries for air-gapped installation.
  • Feedback: Submit feedback directly from Podman Desktop.
  • Docker Compatibility Mode: Information about the Docker compatibility mode.
  • Proxy Setting: Toggle on/off the proxy setting.
  • Deploy to Kubernetes: Select the namespace to deploy to Kubernetes.
  • Registry Configuration: Simplified registry configuration for well known registries.
  • UX/UI Improvements: View pod's container logs, better visual feedback, configurable editor font size, and more.

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

· 5 min read
Dev Kumar

This release note covers Podman Desktop 0.10 release changes.

  • Containers Configuration: Container creation wizzard allowing to define environment variables, networking and more configuration options.
  • Kubernetes Improvements: Play Kubernetes YAML, custom Kubeconfig path support, reload of kube context.
  • Registries Configuration: Revamped registries configuration UI.
  • Podman Version: Podman 4.3.1 now included in Windows and Mac installers.
  • UX/UI Improvements: Improved lists, better contrast, and more.

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

- + \ No newline at end of file diff --git a/blog/tags/story.html b/blog/tags/story.html index bd2bcdd8eeb..bb815abe43b 100644 --- a/blog/tags/story.html +++ b/blog/tags/story.html @@ -13,13 +13,13 @@ - +

One post tagged with "story"

View All Tags

· 9 min read
Fabrice Flore-Thebault

In this blog post you will learn to use Podman Desktop to run the Kubernetes documentation example: Deploying PHP Guestbook application with Redis.

On the agenda:

  1. Installing Podman Desktop.
  2. Installing and initializing your container engine: Podman.
  3. Installing and starting your local Kubernetes provider: Kind.
  4. Starting the Redis leader.
  5. Starting and scaling the Redis followers.
  6. Starting and exposing the Guestbook frontend.
- + \ No newline at end of file diff --git a/core-values.html b/core-values.html index dde3e15c779..edc1c469d0b 100644 --- a/core-values.html +++ b/core-values.html @@ -13,13 +13,13 @@ - +

Podman Desktop: Core Values

Podman Desktop is designed and built with the following core values in mind.

Fast and Light

Daemon-less and using the fastest technologies to make Podman Desktop fast to use.

Reactive and light on resources utilized from your environment.

Open

While focusing on Podman as a container engine packaged by default, Podman Desktop also enables other container engines.

This gives the end-user a single tool to manage all their containers independently from the engine used.

Simple

Managing a container engine locally can be hard.

Running Kubernetes in a local environment requires knowledge.

Podman Desktop takes care of this complexity and enables developers to focus on their code.

Extensible Workflow

Podman Desktop provides extensions points to enable the community to build more features.

This allows more in-deep integrations with other tools and technologies to extend workflows and capabilities of the tool.

Thus giving the developer a single tool to manage all their containers independently from the engine used.

- + \ No newline at end of file diff --git a/docs/compose.html b/docs/compose.html index 1dddb8305d7..17a53b74855 100644 --- a/docs/compose.html +++ b/docs/compose.html @@ -13,13 +13,13 @@ - +

Working with Compose

Podman Desktop supports the Compose specification, and can:

  • Set up a Compose engine.
  • Manage multi-container applications defined in Compose files.

Procedure​

  1. You set up Compose.

  2. You have a Compose file.

  3. You run a Compose engine on the Compose file.

  4. The Compose engine starts the containers and services, and adds a label to each resource:

    • Container label: com.docker.compose.project
    • Service label: com.docker.compose.service

  5. Podman Desktop detects the Compose labels, and displays the container group as a group of containers.

    img2

- + \ No newline at end of file diff --git a/docs/compose/running-compose.html b/docs/compose/running-compose.html index 0a4b3e8ee0e..f86498760f8 100644 --- a/docs/compose/running-compose.html +++ b/docs/compose/running-compose.html @@ -13,13 +13,13 @@ - +

Running Compose files

With Podman Desktop, you can manage multi-container applications defined in a Compose file.

Prerequisites​

Procedure​

  • Run the command in a terminal:

    $ docker-compose --file compose.yaml up --detach

Verification​

  • The Podman Desktop Containers list displays the containers created by Compose grouped in a container group with a (compose) suffix, such as flask-redis (compose).

    img2

Additional resources​

- + \ No newline at end of file diff --git a/docs/compose/setting-up-compose.html b/docs/compose/setting-up-compose.html index 41fc00233fe..a94fea4b430 100644 --- a/docs/compose/setting-up-compose.html +++ b/docs/compose/setting-up-compose.html @@ -13,13 +13,13 @@ - +

Setting up Compose

Podman Desktop can install the Compose engine.

Procedure​

  1. Install the Compose engine: in the Podman Desktop status bar, click Compose, and follow the prompts.
  2. To use the Compose engine from your terminal, set the DOCKER_HOST variable.

Verification​

  1. Open a terminal.

  2. The Compose reference implementation is in your PATH, therefore, you can display the Compose engine version:

    $ docker-compose version

  3. The DOCKER_HOST variable is set:

    $ env | grep DOCKER_HOST

Additional resources​

- + \ No newline at end of file diff --git a/docs/extensions.html b/docs/extensions.html index 822a622e6a3..fc6e28e68b2 100644 --- a/docs/extensions.html +++ b/docs/extensions.html @@ -13,13 +13,13 @@ - +

Podman Desktop extensions

Podman Desktop extensions contribute to:

  • Container engine support, such as Podman, Docker.
  • Virtual machine support, such as Lima.
  • Podman Desktop extension points such as tray icon menu, status bar items, icons, menus, and commands.
  • Integration with third parties tools, such as Kind or Compose.

Next steps​

- + \ No newline at end of file diff --git a/docs/extensions/install.html b/docs/extensions/install.html index 5c0a84b9049..b407a73e969 100644 --- a/docs/extensions/install.html +++ b/docs/extensions/install.html @@ -13,13 +13,13 @@ - +

Installing a Podman Desktop extension

Consider installing Podman Desktop extensions to enrich the default capabilities of Podman Desktop.

Prerequisites​

Procedure​

  1. Go to the Settings > Extensions.

  2. In the Name of the Image field, write the extension OCI image name.

  3. Click the Install extension from the OCI image button.

Verification​

  • If Podman Desktop satisfies the minimum required version of the extension, the extension activates.

  • Depending on the extension, items can appear in the status bar, tray menu, or other contributions.

- + \ No newline at end of file diff --git a/docs/extensions/publish.html b/docs/extensions/publish.html index b83c4bdf52d..79c93ea52c4 100644 --- a/docs/extensions/publish.html +++ b/docs/extensions/publish.html @@ -13,7 +13,7 @@ - + @@ -21,7 +21,7 @@

Packaging and publishing a Podman Desktop extension

To enable users to install your extension, consider publishing your extension to an Open Container Initiative (OCI) image registry.

Prerequisites​

  • The extension builds successfully. See Writing a Podman Desktop extension.

  • All runtime dependencies are inside the final binary.

  • An OCI image registry to publish to, such as quay.io/fbenoit/my-first-extension.

  • (Optional) The OCI image registry is public to enable anybody to fetch the image.

Procedure​

  1. Create and edit a Containerfile file.

  2. Use a scratch image. The extension requires no runtime:

    FROM scratch

  3. Apply mandatory Podman Desktop metadata on the OCI image:

    LABEL org.opencontainers.image.title="My first extension" \
          org.opencontainers.image.description="Example of extension" \
          org.opencontainers.image.vendor="podman-desktop" \
          io.podman-desktop.api.version=">= 0.12.0"

    io.podman-desktop.api.version=">= 0.12.0" sets the minimal Podman Desktop version that the extension requires to run.

  4. Copy the extension assembly, including the metadata, icon, and production binary, to the /extension folder inside the image:

    COPY package.json /extension/
    COPY icon.png /extension/
    COPY dist /extension/dist

  5. Build an image:

    $ podman build -t quay.io/fbenoit/my-first-extension .

  6. Push the image and manifest to the OCI image registry:

    $ podman push quay.io/fbenoit/my-first-extension

Next steps​

- + \ No newline at end of file diff --git a/docs/extensions/write.html b/docs/extensions/write.html index 17fbac57a28..791925c324e 100644 --- a/docs/extensions/write.html +++ b/docs/extensions/write.html @@ -13,13 +13,13 @@ - +

Writing a Podman Desktop extension

To write a Podman Desktop extension, start a Node.js or TypeScript project calling the Podman Desktop API, and ensure all runtime dependencies are inside the final binary.

Initializing a Podman Desktop extension​

Write the Podman Desktop extension Node.js package metadata.

Prerequisites​

  • JavaScript or TypeScript

Procedure​

  1. Create and edit a package.json file.

    {}

  2. Add TypeScript and Podman Desktop API to the development dependencies:

     "devDependencies": {
       "@podman-desktop/api": "latest",
       "typescript": "latest"
     },

  3. Add the required metadata:

      "name": "my-extension",
      "displayName": "My Hello World extension",
      "description": "How to write my first extension",
      "version": "0.0.1",
      "icon": "icon.png",
      "publisher": "benoitf",

  4. Add the Podman Desktop version that might run this extension:

      "engines": {
        "podman-desktop": "latest"
      },

  5. Add the main entry point:

     "main": "./dist/extension.js"

  6. Add a Hello World command contribution

      "contributes": {
        "commands": [
         {
           "command": "my.first.command",
           "title": "My First Extension: Hello World"
         }
       ]
      }

  7. Add an icon.png file to the project.

Verification​

  • Full package.json example:

    {
      "devDependencies": {
        "@podman-desktop/api": "latest",
        "typescript": "latest"
      },
      "name": "my-extension",
      "displayName": "My Hello World extension",
      "description": "How to write my first extension",
      "version": "0.0.1",
      "icon": "icon.png",
      "publisher": "benoitf",
      "engines": {
        "podman-desktop": "latest"
      },
      "main": "./dist/extension.js",
      "contributes": {
        "commands": [
          {
            "command": "my.first.command",
            "title": "My First Extension: Hello World"
          }
        ]
      }
    }

Writing a Podman Desktop extension entry point​

Write the extension features.

Prerequisites​

  • JavaScript or TypeScript

Procedure​

  1. Create and edit a dist/extension.js file.

  2. Import the Podman Desktop API

    import * as podmanDesktopAPI from '@podman-desktop/api';

  3. Expose the activate function to call on activation.

    The signature of the function can be:

    • Synchronous

      export function activate(): void;

    • Asynchronous

      export async function activate(): Promise<void>;

  4. (Optional) Add an extension context to the activate function enabling the extension to register disposable resources:

    export async function activate(extensionContext: podmanDesktopAPI.ExtensionContext): Promise<void> {}

  5. Register the command and the callback

    import * as podmanDesktopAPI from '@podman-desktop/api';
    export async function activate(extensionContext: podmanDesktopAPI.ExtensionContext): Promise<void> {
      // register the command referenced in package.json file
      const myFirstCommand = podmanDesktopAPI.commands.registerCommand('my.first.command', async () => {
        // display a choice to the user for selecting some values
        const result = await podmanDesktopAPI.window.showQuickPick(['un', 'deux', 'trois'], {
          canPickMany: true, // user can select more than one choice
        });

        // display an information message with the user choice
        await podmanDesktopAPI.window.showInformationMessage(`The choice was: ${result}`);
      });

      // create an item in the status bar to run our command
      // it will stick on the left of the status bar
      const item = podmanDesktopAPI.window.createStatusBarItem(podmanDesktopAPI.StatusBarAlignLeft, 100);
      item.text = 'My first command';
      item.command = 'my.first.command';
      item.show();

      // register disposable resources to it's removed when we deactivte the extension
      extensionContext.subscriptions.push(myFirstCommand);
      extensionContext.subscriptions.push(item);
    }

  6. (Optional) Expose the deactivate function to call on deactivation.

    The signature of the function can be:

    • Synchronous

      export function deactivate(): void;

    • Asynchronous

      export async function deactivate(): Promise<void>;

Verification​

  • The extension compiles and produces the output in the dist folder.

  • All runtime dependencies are inside the final binary.

Additional resources​

  • Consider a packer such as Rollup or Webpack to shrink the size of the artifact.

Next steps​

- + \ No newline at end of file diff --git a/docs/extensions/write/when-clause-context.html b/docs/extensions/write/when-clause-context.html index 5fd1c3fa8ca..bc995cf6862 100644 --- a/docs/extensions/write/when-clause-context.html +++ b/docs/extensions/write/when-clause-context.html @@ -13,13 +13,13 @@ - +

When clause contexts

Podman Desktop uses when clauses to enable or disable extensions command and UI customizations, such as views.

For example, the Kind extension adds a custom icon to a container that has a label equals to io.x-k8s.kind.cluster by using the following instruction.

"views": {
   "icons/containersList": [
     {
       "when": "io.x-k8s.kind.cluster in containerLabelKeys",
       "icon": "${kind-icon}"
     }
   ]
 }

A when clause can consist of a context key (such as isLinux) or complex expressions to define a specific state.

Available context keys​

Podman Desktop has a set of context keys that are evaluated to Boolean true/false.

Context keyTrue when
Operating system contexts
isLinuxTrue when the OS is Linux.
isWindowsTrue when the OS is Windows.
isMacTrue when the OS is macOS.

Podman Desktop also provides context keys that return values that can be used to create meaningful expressions

Context keyValue in it
containerLabelKeysA list of all labels belonging to the current container. Example: "value in containerLabelKeys"

Add a custom when clause context​

If you are creating your own extension and none of the existing keys suit your needs, you can set your own context key by calling the function setValue(key: string, value: any, scope?: 'onboarding') provided by the context namespace in the Podman Desktop API.

The scope, if specified, triggers a custom behavior to avoid any type of collisions between different extensions for that specific scope. Podman Desktop is responsible for handling its state and cleans it accordingly when necessary.

If omitted, the key/value is set globally. For this reason it is recommended to use the extension id as part of the key to avoid unexpected collisions with other extensions.

The first example below sets the key "podmanIsInstalled" to true globally while the second example sets the key "toolInstalled" to oc.exe using the onboarding scope.

   extensionsAPI.context.setValue('podmanIsInstalled', true);

   extensionsAPI.context.setValue('toolInstalled', 'oc.exe', 'onboarding');

After setting the toolInstalled to oc.exe, you could use this information in the when clause to enable something

{
  "when": "onboardingContext:toolInstalled == oc.exe"
}

Conditional operators​

To create when clauses a bit more complex Podman Desktop offers a set of operators that can be combined with each other.

Logical operators​

Logical operators allow combining simple context keys or when-clause expressions that include other operators

OperatorSymbolExample
Not!!podmanIsInstalled or !(podmanIsInstalled && isWindows)
And&&podmanIsInstalled && isWindows
Or\|\|isLinux \|\| isWindows

Equality operators​

Equality operators allow checking for equality of a context key's value againt a specified value.

Note: the right side is a value and not considered as a context key, so no value is searched in the context. If it contains whitespaces, it must be wrapped in single-quotes (for example 'my tool.exe')

OperatorSymbolExample
Equality==onboardingContext:toolInstalled == oc.exe
Inequality!=onboardingContext:toolInstalled != oc.exe

Comparison operators​

Comparison operator allow comparing a context key's value against a number.

Note: the left and right side of the operator must be separated by whitespace - bar < 2, but not bar<2

OperatorSymbolExample
Greater than>, >=onboardingContext:toolInstalled > 2
Less than<, <=onboardingContext:toolInstalled <= 3

In and not in​

The in/not in operators allow checking if a value exists/not exists within the other. The right should be a context key, which value is retrieved in the context. The left can be a value or a context key.

OperatorSymbolExample
Ininlabel in containerLabelKeys
Notnot inlabel not in containerLabelKeys

Match operator​

The match operator allow treating the right side item as a regular expression literal to match against the left side.

OperatorSymbolExample
Matches=~label =~ /podman$/
- + \ No newline at end of file diff --git a/docs/installation.html b/docs/installation.html index 1ddd88762c2..0af3358f022 100644 --- a/docs/installation.html +++ b/docs/installation.html @@ -13,13 +13,13 @@ - +
- + \ No newline at end of file diff --git a/docs/installation/linux-install.html b/docs/installation/linux-install.html index 0e67fc8c136..78a8b431e89 100644 --- a/docs/installation/linux-install.html +++ b/docs/installation/linux-install.html @@ -13,13 +13,13 @@ - +

Installing Podman Desktop on Linux

Consider installing the Podman Desktop from Flathub to have:

  • One command installation
  • Package updates

Alternatively, you can install Podman Desktop from:

Prerequisites​

Procedure​

  1. Verify the Flathub repository is enabled, and add it if required:

    $ flatpak remote-add --if-not-exists --user flathub https://flathub.org/repo/flathub.flatpakrepo

  2. Install Podman Desktop from Flathub:

    $ flatpak install --user flathub io.podman_desktop.PodmanDesktop

Verification​

  • Open Podman Desktop from a terminal:

    $ flatpak run io.podman_desktop.PodmanDesktop

Update​

  • Update Podman Desktop from Flathub:

    $ flatpak update --user io.podman_desktop.PodmanDesktop

Additional resources​

Next steps​

- + \ No newline at end of file diff --git a/docs/installation/linux-install/installing-podman-desktop-from-a-compressed-tar-file.html b/docs/installation/linux-install/installing-podman-desktop-from-a-compressed-tar-file.html index dd92659b2b7..4f3e7e99112 100644 --- a/docs/installation/linux-install/installing-podman-desktop-from-a-compressed-tar-file.html +++ b/docs/installation/linux-install/installing-podman-desktop-from-a-compressed-tar-file.html @@ -13,14 +13,14 @@ - +

Installing Podman Desktop from a compressed tar file

Consider installing from an archive rather than from Flathub, or from a Flatpak bundle when:

  • You cannot use Flatpak.
  • You install in a restricted environment.

Prerequisites​

Procedure​

  1. Download the podman-desktop-<version>.tar.gz archive from the Git repository release assets.
  2. Extract the content.
  3. Go to the extracted directory.
  4. Double-click on the podman-desktop executable file.

Next steps​

- + \ No newline at end of file diff --git a/docs/installation/linux-install/installing-podman-desktop-from-a-flatpak-bundle.html b/docs/installation/linux-install/installing-podman-desktop-from-a-flatpak-bundle.html index 97a36f8598b..42ae84e6be0 100644 --- a/docs/installation/linux-install/installing-podman-desktop-from-a-flatpak-bundle.html +++ b/docs/installation/linux-install/installing-podman-desktop-from-a-flatpak-bundle.html @@ -13,13 +13,13 @@ - +

Installing Podman Desktop from a Flatpak bundle

Consider installing a Flatpak bundle rather than from Flathub when:

  • You cannot use Flathub.
  • You want to install an unreleased version.

Prerequisites​

Procedure​

  1. Download the Flatpak bundle to a $HOME/Downloads/podman-desktop-<version>.flatpak file from:

  2. Install Podman Desktop from the downloaded Flatpak bundle:

    $ flatpak install --user $HOME/Downloads/podman-desktop-<version>.flatpak

Verification​

  • Open Podman Desktop from a terminal:

    $ flatpak run io.podman_desktop.PodmanDesktop

Additional resources​

Next steps​

- + \ No newline at end of file diff --git a/docs/installation/macos-install.html b/docs/installation/macos-install.html index 3569f50bd21..c0df6714fa9 100644 --- a/docs/installation/macos-install.html +++ b/docs/installation/macos-install.html @@ -13,14 +13,14 @@ - +

MacOS

This page contains information regarding installation of Podman Desktop on MacOS.

You can install Podman Desktop on Mac:

  1. Using the .dmg file
  2. Using Brew
Prerequisite

Podman Desktop requires Podman Engine. If you don't have Podman Engine installed, Podman Desktop will prompt you to do so at a later stage.

Installing Podman Desktop on MacOS using .dmg file​

  1. Download the .dmg file from the Downloads section of this website.

    While we recommend getting the "universal" binary file which will work irrespective of the chip architecture your Mac possesses, you also have the option to get the applicable .dmg file depending on your Mac Hardware Architecture (that is Intel or Apple M1).

  2. Locate the downloaded file, and double-click on it. (Usually, you will find the downloaded file in the Downloads folder)

    img0

  3. Drag Podman Desktop icon to the Applications folder.

    img1

  4. Start Podman Desktop from the 'Launchpad' or Mac's Applications directory.

    img2

  5. Install Podman from Podman Desktop, if not yet installed.

    When you open Podman Desktop for the first time, click on the "View detection checks" button to scan if all the prerequisites to use Podman Desktop are met. If it says ❌ podman cli was not found in the PATH, then you need to install the Podman CLI/Engine which can be done within the application.

    img3

  6. Click on the "Install" button next to the "View detection checks" button, and follow the instructions on screen.

  7. You will be redirected to the Podman Installer. Follow the instructions on screen and enter your system password when asked.

    img4

  8. After the installation is complete, close the installation program. Podman Engine has been installed and you are now ready to use Podman Desktop.

Installing Podman Desktop on MacOS using brew​

Prerequisite

Installation steps​

  1. Open a terminal on your Mac.

  2. Run the command mentioned below.

    brew install podman-desktop

    Brew will also install the Podman Engine along with the Podman Desktop application, in case you don't have it installed yet.

    After the command is executed, you can find the Podman Desktop Application within the Applications directory of the MacOS.

Getting Started​

Learn more on how to get started with Podman Desktop by clicking here.

- + \ No newline at end of file diff --git a/docs/installation/windows-install.html b/docs/installation/windows-install.html index 6fa89c3ebc0..75f4403a488 100644 --- a/docs/installation/windows-install.html +++ b/docs/installation/windows-install.html @@ -13,13 +13,13 @@ - +

Installing Podman Desktop using the Windows installer

Consider using this installation method if you don't require another method such as:

Procedure​

  1. Download the Windows installer.

  2. Open the downloaded file to start the Podman Desktop installer.

Next steps​

- + \ No newline at end of file diff --git a/docs/installation/windows-install/installing-podman-desktop-and-podman-in-a-restricted-environment.html b/docs/installation/windows-install/installing-podman-desktop-and-podman-in-a-restricted-environment.html index 64079e22286..05b5262887d 100644 --- a/docs/installation/windows-install/installing-podman-desktop-and-podman-in-a-restricted-environment.html +++ b/docs/installation/windows-install/installing-podman-desktop-and-podman-in-a-restricted-environment.html @@ -13,13 +13,13 @@ - +

Installing Podman Desktop and Podman in a restricted environment

Consider using the Windows installer for restricted environments to install the Podman Desktop and Podman in a restricted environment.

The Windows installer for restricted environments:

  • Has all artifacts required to install Podman Desktop and Podman.
  • Does not require Internet access to download resources during installation.
  • Does not contain additional utilities such as Compose or Kind.

Prerequisites​

Procedure​

  1. Download the Windows installer for restricted environments, and copy the downloaded file to the Windows host in a restricted environment.
  2. Run the Windows installer for restricted environments to install Podman Desktop.
  3. Open Podman Desktop and click the Install button to install Podman.
  4. (Optionally) Configure Podman Desktop to run behind your proxy.
  5. (Optionally) Configure Podman to run behind your VPN.
  6. Create and start a Podman machine

Next steps​

- + \ No newline at end of file diff --git a/docs/installation/windows-install/installing-podman-desktop-silently-with-the-windows-installer.html b/docs/installation/windows-install/installing-podman-desktop-silently-with-the-windows-installer.html index 5eab19f465b..e0dc3c1c19f 100644 --- a/docs/installation/windows-install/installing-podman-desktop-silently-with-the-windows-installer.html +++ b/docs/installation/windows-install/installing-podman-desktop-silently-with-the-windows-installer.html @@ -13,13 +13,13 @@ - +
- + \ No newline at end of file diff --git a/docs/installation/windows-install/installing-podman-desktop-with-chocolatey.html b/docs/installation/windows-install/installing-podman-desktop-with-chocolatey.html index 0a885b0cc61..d61ce9b9b8d 100644 --- a/docs/installation/windows-install/installing-podman-desktop-with-chocolatey.html +++ b/docs/installation/windows-install/installing-podman-desktop-with-chocolatey.html @@ -13,13 +13,13 @@ - +
- + \ No newline at end of file diff --git a/docs/installation/windows-install/installing-podman-desktop-with-scoop.html b/docs/installation/windows-install/installing-podman-desktop-with-scoop.html index 06e195b4542..b68784a10f5 100644 --- a/docs/installation/windows-install/installing-podman-desktop-with-scoop.html +++ b/docs/installation/windows-install/installing-podman-desktop-with-scoop.html @@ -13,13 +13,13 @@ - +
- + \ No newline at end of file diff --git a/docs/installation/windows-install/installing-podman-desktop-with-winget.html b/docs/installation/windows-install/installing-podman-desktop-with-winget.html index f71059988ee..40a651ae031 100644 --- a/docs/installation/windows-install/installing-podman-desktop-with-winget.html +++ b/docs/installation/windows-install/installing-podman-desktop-with-winget.html @@ -13,13 +13,13 @@ - +
- + \ No newline at end of file diff --git a/docs/intro.html b/docs/intro.html index cbb5c0b03d1..bd0abbf7f17 100644 --- a/docs/intro.html +++ b/docs/intro.html @@ -13,13 +13,13 @@ - +
- + \ No newline at end of file diff --git a/docs/kubernetes.html b/docs/kubernetes.html index e5b6a910a9b..2cbe0834e8b 100644 --- a/docs/kubernetes.html +++ b/docs/kubernetes.html @@ -13,13 +13,13 @@ - +
- + \ No newline at end of file diff --git a/docs/kubernetes/configuring-access-to-a-kubernetes-cluster.html b/docs/kubernetes/configuring-access-to-a-kubernetes-cluster.html index 33b2adceef5..57f5ad01b7e 100644 --- a/docs/kubernetes/configuring-access-to-a-kubernetes-cluster.html +++ b/docs/kubernetes/configuring-access-to-a-kubernetes-cluster.html @@ -13,13 +13,13 @@ - +

Configuring access to a Kubernetes cluster

Podman Desktop configures the access to Kubernetes clusters automatically when:

You can also use the Kubernetes CLI to configure access to your Kubernetes cluster:

Prerequisites​

  • You have credentials for your Kubernetes cluster.

Procedure​

  1. (Optionally) Go to Settings > Preferences > Path to the kubeconfig file to adapt your kubeconfig file location, when different from the default $HOME/.kube/config.

  2. Register your <my_kubernetes> Kubernetes cluster:

    $ kubectl config set-cluster <my_kubernetes> --server=<my_kubernetes_url>

Verification​

Additional resopurces​

- + \ No newline at end of file diff --git a/docs/kubernetes/deploying-a-container-to-kubernetes.html b/docs/kubernetes/deploying-a-container-to-kubernetes.html index b43cf31b82a..aa6be69b2b9 100644 --- a/docs/kubernetes/deploying-a-container-to-kubernetes.html +++ b/docs/kubernetes/deploying-a-container-to-kubernetes.html @@ -13,13 +13,13 @@ - +

Deploying a container to Kubernetes

With Podman Desktop, you can deploy a container to your Kubernetes cluster.

Prerequisites​

  • Your are using the Podman container engine.
  • Your container, running or stopped, is available on the Containers page: <your_container>.
  • You registered the Kubernetes cluster in your kubeconfig file: <your_kubernetes_cluster>. For example, Creating a kind cluster.
  • The Kubernetes namespace to deploy to already exists.

Procedure​

  1. Click Podman Desktop tray > Kubernetes > Context > <your_kubernetes_cluster> to set your Kubernetes context.
  2. Open Podman Desktop dashboard > Containers > <your_container> to see the Container Details page.
  3. Click to generate a Kubernetes pod.
  4. On the Deploy generated pod to Kubernetes screen, choose your options:
    1. Pod Name: edit the proposed name.
    2. Use Kubernetes Services: enable or disable Replace hostPort exposure on containers by Services. It is the recommended way to expose ports, as a cluster policy might prevent to use hostPort.
    3. Kubernetes namespace: select in the list the namespace to deploy the pod to.
  5. Click the Deploy button.

Verification​

  • On the Deploy generated pod to Kubernetes screen, the created pod status is Phase: Running

    Deploying a container

  • Go to Containers: your pod is in the list.

- + \ No newline at end of file diff --git a/docs/kubernetes/deploying-a-pod-to-kubernetes.html b/docs/kubernetes/deploying-a-pod-to-kubernetes.html index 82defcbc2f4..3e4e49c400c 100644 --- a/docs/kubernetes/deploying-a-pod-to-kubernetes.html +++ b/docs/kubernetes/deploying-a-pod-to-kubernetes.html @@ -13,13 +13,13 @@ - +

Deploying a pod to Kubernetes

With Podman Desktop, you can deploy a pod to your Kubernetes cluster.

Prerequisites​

  • Your are using the Podman container engine.
  • Your pod, running or stopped, is available on the Pods page: <your_pod>.
  • You registered the Kubernetes cluster in your kubeconfig file: <your_kubernetes_cluster>. For example, Creating a kind cluster.
  • The Kubernetes namespace to deploy to already exists.

Procedure​

  1. Click Podman Desktop tray > Kubernetes > Context > <your_kubernetes_cluster> to set your Kubernetes context.
  2. Open Podman Desktop dashboard > Pods > <your_pod> to see the Pod Details page.
  3. Click to generate a Kubernetes pod.
  4. On the Deploy generated pod to Kubernetes screen, choose your options:
    1. Pod Name: edit the proposed name.
    2. Use Kubernetes Services: enable or disable Replace hostPort exposure on containers by Services. It is the recommended way to expose ports, as a cluster policy might prevent to use hostPort.
    3. Kubernetes namespace: select in the list the namespace to deploy the pod to.
  5. Click the Deploy button.

Verification​

  • On the Deploy generated pod to Kubernetes screen, the created pod status is Phase: Running

    Deplying a pod

  • Go to Pods: your pod is in the list.

- + \ No newline at end of file diff --git a/docs/kubernetes/kind.html b/docs/kubernetes/kind.html index 3864c6abf7b..3c7e31157a2 100644 --- a/docs/kubernetes/kind.html +++ b/docs/kubernetes/kind.html @@ -13,13 +13,13 @@ - +
- + \ No newline at end of file diff --git a/docs/kubernetes/kind/building-an-image-and-testing-it-in-kind.html b/docs/kubernetes/kind/building-an-image-and-testing-it-in-kind.html index 28262f2f9e8..ad78214e1d0 100644 --- a/docs/kubernetes/kind/building-an-image-and-testing-it-in-kind.html +++ b/docs/kubernetes/kind/building-an-image-and-testing-it-in-kind.html @@ -13,13 +13,13 @@ - +

Building an image and testing it in Kind

With Podman Desktop, you can build an image with your container engine, and test it in your local Kind-powered Kubernetes cluster.

Prerequisites​

Procedure​

  1. Build your image:

    1. Open Images > Build an image.
    2. Containerfile path: select your Containerfile or Dockerfile.
    3. Build context directory: optionally, select a directory different from the directory containing your Containerfile or Dockerfile.
    4. Image Name: enter your image name my-custom-image.
    5. Click Build.
    6. Wait for the image build to finish.
    7. Click Done to get back to the images list.

  2. Push your image to your Kind cluster:

    1. Search images: enter your image name my-custom-image to find the image.
    2. Click > Push image to Kind cluster.

  3. Test your image by creating a container:

    1. Click to open the Create a container from image dialog.
    2. Container name: enter my-custom-image-container.
    3. Review the parameters that Podman Desktop has detected from your image definition.
    4. Click Start Container to start the container in your container engine.

  4. Test your image and container on your Kind cluster:

    1. Search containers: enter my-custom-image-container to find the running container.
    2. Click > Deploy to Kubernetes to open the Deploy generated pod to Kubernetes screen.
    3. Pod Name: keep the proposed value my-custom-image-container-pod.
    4. Use Kubernetes Services: select Replace hostPort exposure on containers by Services. It is the recommended way to expose ports, as a cluster policy might prevent to use hostPort.
    5. Expose service locally using Kubernetes Ingress: if your container is exposing at a port, select Create a Kubernetes ingress to get access to the ports that this pod exposes, at the default ingress controller location. Example: on a default Kind cluster created with Podman Desktop: http://localhost:9090. Requirements: your cluster has an ingress controller`.
    6. Optionally, if your container is exposing more than one port, select the port to expose.
    7. Kubernetes namespaces: select default.
    8. Click Deploy.
    9. Wait for the pod to reach the state: Phase: Running.
    10. Click Done.

Verification​

  1. The Pods screen lists the running my-image-container-pod pod.
  2. Click on the pod name to view details and logs.
  3. Optionally, if your container is exposing a port, go to http://localhost:9090: your application is running.
- + \ No newline at end of file diff --git a/docs/kubernetes/kind/pushing-an-image-to-kind.html b/docs/kubernetes/kind/pushing-an-image-to-kind.html index 3dcdb453f8a..9d19b553e3c 100644 --- a/docs/kubernetes/kind/pushing-an-image-to-kind.html +++ b/docs/kubernetes/kind/pushing-an-image-to-kind.html @@ -13,7 +13,7 @@ - + @@ -21,7 +21,7 @@

Pushing an image to your local Kind-powered Kubernetes cluster

With Podman Desktop, you can push an image to your local Kind-powered Kubernetes cluster.

Prerequisites​

Procedure​

  1. Open Podman Desktop dashboard > Images.
  2. Search images: <your_image>:<your_tag>.
  3. Click > Push image to Kind cluster.
  4. If you created many Kind clusters, select your Kind cluster from the list.

Verification​

Kind does not enable you to list loaded images. Therefore, create a Pod that uses the loaded image.

  1. Create a verify_my_image.yaml Kubernetes YAML file on your workstation. Replace the placeholders:

    • Pod name and container name value must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character.
    • Container image value is the image you pushed.
    apiVersion: v1
    kind: Pod
    metadata:
      name: <verify-my-image>
    spec:
      containers:
        - name: <my-image>
          image: <my_image>:<my_tag>
          imagePullPolicy: Never

  2. Open Pods > Play Kubernetes YAML.

    1. Kubernetes YAML file: select your verify_my_image.yaml file.
    2. Select Runtime: Using a Kubernetes cluster.
    3. Click Play.
    4. Clik Done

  3. Open Pods.

  4. Search pods: <verify-my-image>.

  5. The pod Status is Running.

- + \ No newline at end of file diff --git a/docs/kubernetes/kind/working-with-your-local-kind-cluster.html b/docs/kubernetes/kind/working-with-your-local-kind-cluster.html index 385603f5a65..1bb77e422c7 100644 --- a/docs/kubernetes/kind/working-with-your-local-kind-cluster.html +++ b/docs/kubernetes/kind/working-with-your-local-kind-cluster.html @@ -13,13 +13,13 @@ - +

Working with your local Kind-powered Kubernetes cluster

Set your Kubernetes context to your local Kind-powered Kubernetes cluster.

Prerequisites​

Procedure​

  1. Open the Podman Desktop tray.
  2. Go to Kubernetes.
  3. Click on the Kubernetes context with the kind prefix.

Verification​

  • The Kubernetes CLI reports that the current context is your cluster with the kind suffix:

    $ kubectl config current-context
- + \ No newline at end of file diff --git a/docs/kubernetes/lima.html b/docs/kubernetes/lima.html index c9a8ee7e01a..d0d6d354b17 100644 --- a/docs/kubernetes/lima.html +++ b/docs/kubernetes/lima.html @@ -13,13 +13,13 @@ - +
- + \ No newline at end of file diff --git a/docs/kubernetes/minikube.html b/docs/kubernetes/minikube.html index ac462f5494e..c14a8df0e6f 100644 --- a/docs/kubernetes/minikube.html +++ b/docs/kubernetes/minikube.html @@ -13,13 +13,13 @@ - +

Running Kubernetes on your workstation with Minikube and Podman

Podman Desktop can help you run Minikube-powered local Kubernetes clusters on a container engine, such as Podman.

Procedure​

  1. Go to Settings > Extensions.
  2. Install the Minikube extension:
    1. Go to Install a new extension from OCI Image
    2. Enter the Name of the Image: ghcr.io/containers/podman-desktop-extension-minikube
    3. Click Install extension from the OCI image
- + \ No newline at end of file diff --git a/docs/kubernetes/minikube/building-an-image-and-testing-it-in-minikube.html b/docs/kubernetes/minikube/building-an-image-and-testing-it-in-minikube.html index 90fa6e9caba..4fdbd36cce2 100644 --- a/docs/kubernetes/minikube/building-an-image-and-testing-it-in-minikube.html +++ b/docs/kubernetes/minikube/building-an-image-and-testing-it-in-minikube.html @@ -13,13 +13,13 @@ - +

Building an image and testing it in Minikube

With Podman Desktop, you can build an image with your container engine, and test it in your local Minikube-powered Kubernetes cluster.

Prerequisites​

  • Podman Desktop has access to:
    • A running container engine.
    • A running Minikube cluster.
  • A container definition file: Containerfile or Dockerfile.

Procedure​

  1. Build your image:

    1. Open Images > Build an image.
    2. Containerfile path: select your Containerfile or Dockerfile.
    3. Build context directory: optionally, select a directory different from the directory containing your Containerfile or Dockerfile.
    4. Image Name: enter your image name my-custom-image.
    5. Click Build.
    6. Wait for the image build to finish.
    7. Click Done to get back to the images list.

  2. Push your image to your Minikube cluster:

    1. Search images: enter your image name my-custom-image to find the image.
    2. Click > Push image to Minikube cluster.

  3. Test your image by creating a container:

    1. Click to open the Create a container from image dialog.
    2. Container name: enter my-custom-image-container.
    3. Review the parameters that Podman Desktop has detected from your image definition.
    4. Click Start Container to start the container in your container engine.

  4. Test your image and container on your Minikube cluster:

    1. Search containers: enter my-custom-image-container to find the running container.
    2. Click > Deploy to Kubernetes to open the Deploy generated pod to Kubernetes screen.
    3. Pod Name: keep the proposed value my-custom-image-container-pod.
    4. Use Kubernetes Services: select Replace hostPort exposure on containers by Services. It is the recommended way to expose ports, as a cluster policy might prevent to use hostPort.
    5. Expose service locally using Kubernetes LoadBalancer: if your container is exposing a service, you can use minikube service to get a web browser or an URL to use.
    6. Optionally, if your container is exposing more than one port, select the port to expose.
    7. Kubernetes namespaces: select default.
    8. Click Deploy.
    9. Wait for the pod to reach the state: Phase: Running.
    10. Click Done.

Verification​

  1. The Pods screen lists the running my-image-container-pod pod.
  2. Click on the pod name to view details and logs.
  3. Optionally, if your container is exposing a service, go to the server URL: your application is running.
- + \ No newline at end of file diff --git a/docs/kubernetes/minikube/configuring-podman-for-minikube-on-windows.html b/docs/kubernetes/minikube/configuring-podman-for-minikube-on-windows.html index b94e096c4b1..56c795cc85b 100644 --- a/docs/kubernetes/minikube/configuring-podman-for-minikube-on-windows.html +++ b/docs/kubernetes/minikube/configuring-podman-for-minikube-on-windows.html @@ -13,13 +13,13 @@ - +

Configuring Podman for Minikube on Windows Subsystem for Linux (WSL)

When you create a Podman machine, Podman creates the machine in rootless mode.

With a Podman machine running on WSL, Minikube:

  • Requires a rootful machine.

Therefore, set the Podman machine to rootful mode.

Procedure​

  1. Stop the Podman machine:

    $ podman machine stop

  2. Set the Podman machine in rooful mode:

    $ podman machine set --rootful

  3. Start the Podman machine:

    $ podman machine start
- + \ No newline at end of file diff --git a/docs/kubernetes/minikube/creating-a-minikube-cluster.html b/docs/kubernetes/minikube/creating-a-minikube-cluster.html index 35a53c3767c..827e9be49d7 100644 --- a/docs/kubernetes/minikube/creating-a-minikube-cluster.html +++ b/docs/kubernetes/minikube/creating-a-minikube-cluster.html @@ -13,13 +13,13 @@ - +

Creating a local Minikube-powered Kubernetes cluster

You can create multiple local Minikube-powered Kubernetes clusters.

Prerequisites​

Procedure​

  1. Go to Settings > Resources

  2. In the Minikube tile, click on the Create new ... button.

  3. Choose your options, and click the Create button.

    The defaults are:

    • Name: minikube
    • Driver: podman
    • Container runtime: cri-o

  4. (Optionally) Click the Show logs button to display the logs.

  5. After successful creation, click on the Go back to resources button

Verification​

  1. In Settings > Resources, in the Minikube tile, your <minikube> instance is running.
  2. In the Podman Desktop tray, open the Kubernetes menu, you can set the context to your Minikube cluster: minikube.
- + \ No newline at end of file diff --git a/docs/kubernetes/minikube/deleting-your-minikube-cluster.html b/docs/kubernetes/minikube/deleting-your-minikube-cluster.html index 6421bf4847a..efc962f4fee 100644 --- a/docs/kubernetes/minikube/deleting-your-minikube-cluster.html +++ b/docs/kubernetes/minikube/deleting-your-minikube-cluster.html @@ -13,13 +13,13 @@ - +
- + \ No newline at end of file diff --git a/docs/kubernetes/minikube/installing-minikube.html b/docs/kubernetes/minikube/installing-minikube.html index 69cc078d064..b6ebdfb3ce0 100644 --- a/docs/kubernetes/minikube/installing-minikube.html +++ b/docs/kubernetes/minikube/installing-minikube.html @@ -13,7 +13,7 @@ - + @@ -21,7 +21,7 @@
- + \ No newline at end of file diff --git a/docs/kubernetes/minikube/pushing-an-image-to-minikube.html b/docs/kubernetes/minikube/pushing-an-image-to-minikube.html index 8dc170e2f3d..2e661e29a10 100644 --- a/docs/kubernetes/minikube/pushing-an-image-to-minikube.html +++ b/docs/kubernetes/minikube/pushing-an-image-to-minikube.html @@ -13,14 +13,14 @@ - +

Pushing an image to your local Minikube-powered Kubernetes cluster

With Podman Desktop, you can push an image to your local Minikube-powered Kubernetes cluster.

Prerequisites​

Procedure​

  1. Open Podman Desktop dashboard > Images.
  2. Search images: <your_image>:<your_tag>.
  3. Click > Push image to Minikube cluster.
  4. If you created many Minikube clusters, select your Minikube cluster from the list.

Verification​

Minikube enables you to list loaded images, using:

$ minikube image list

You can also create a Pod that uses the loaded image:

  1. Create a verify_my_image.yaml Kubernetes YAML file on your workstation. Replace the placeholders:

    • Pod name and container name value must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character.
    • Container image value is the image you pushed.
    apiVersion: v1
    kind: Pod
    metadata:
      name: <verify-my-image>
    spec:
      containers:
        - name: <my-image>
          image: <my_image>:<my_tag>
          imagePullPolicy: Never

  2. Open Pods > Play Kubernetes YAML.

    1. Kubernetes YAML file: select your verify_my_image.yaml file.
    2. Select Runtime: Using a Kubernetes cluster.
    3. Click Play.
    4. Clik Done

  3. Open Pods.

  4. Search pods: <verify-my-image>.

  5. The pod Status is Running.

- + \ No newline at end of file diff --git a/docs/kubernetes/minikube/restarting-your-minikube-cluster.html b/docs/kubernetes/minikube/restarting-your-minikube-cluster.html index 40859f5eca9..f5aff6bc4bb 100644 --- a/docs/kubernetes/minikube/restarting-your-minikube-cluster.html +++ b/docs/kubernetes/minikube/restarting-your-minikube-cluster.html @@ -13,7 +13,7 @@ - + @@ -22,7 +22,7 @@ Therefore, Podman Desktop stops the Minikube cluster, and starts it again. The Minikube cluster might not restart successfully. In that case:

- + \ No newline at end of file diff --git a/docs/kubernetes/minikube/working-with-your-local-minikube-cluster.html b/docs/kubernetes/minikube/working-with-your-local-minikube-cluster.html index b7ba4c1c917..609032a9b73 100644 --- a/docs/kubernetes/minikube/working-with-your-local-minikube-cluster.html +++ b/docs/kubernetes/minikube/working-with-your-local-minikube-cluster.html @@ -13,13 +13,13 @@ - +

Working with your local Minikube-powered Kubernetes cluster

Set your Kubernetes context to your local Minikube-powered Kubernetes cluster.

Procedure​

  1. Open the Podman Desktop tray.
  2. Go to Kubernetes.
  3. Click on the Kubernetes context with the minikube name.

Verification​

  • The Kubernetes CLI reports that the current context is your cluster with the minikube name:

    $ kubectl config current-context
- + \ No newline at end of file diff --git a/docs/kubernetes/openshift.html b/docs/kubernetes/openshift.html index 709f7b8a228..5b463682f0c 100644 --- a/docs/kubernetes/openshift.html +++ b/docs/kubernetes/openshift.html @@ -13,13 +13,13 @@ - +
- + \ No newline at end of file diff --git a/docs/kubernetes/openshift/configuring-access-to-a-developer-sandbox.html b/docs/kubernetes/openshift/configuring-access-to-a-developer-sandbox.html index 96e307a6a05..2b19488a268 100644 --- a/docs/kubernetes/openshift/configuring-access-to-a-developer-sandbox.html +++ b/docs/kubernetes/openshift/configuring-access-to-a-developer-sandbox.html @@ -13,14 +13,14 @@ - +

Configuring access to a Developer Sandbox

The Developer Sandbox is a free, private OpenShift environment including one project and a resource quota of 14 GB RAM, and 40 GB storage. It lasts 30 days.

With Podman Desktop, you can configure access to your Developer Sandbox instances.

Prerequisites​

Procedure​

  1. Install the Developer Sandbox extension: go to Dashboard, and click Developer Sandbox .
  2. Go to Settings > Resources.
  3. In the Developer Sandbox tile, click Create new.
  4. In the Create a Developer Sandbox screen, click Log into Developer Sandbox.
  5. In the Open external website dialog, click Yes.
  6. In the Developer Sandbox website:
    1. Click Start your sandbox for free
    2. If you never used this service, you might get through a verification workflow.
    3. In the Login with... screen, click DevSandbox.
    4. In your Developer Sandbox Console, click on your login name > Copy login command from the menu.
    5. In the Login with... screen, click DevSandbox.
    6. Click Display Token.
    7. Copy the Log in with this token full login command, similar to: oc login --token=sha256~<token> --server=https://api.sandbox-m2.<sandbox_id>.openshiftapps.com:6443.
  7. Get back to Podman Desktop Create a Developer Sandbox screen.
    1. Context name: Enter a name such as Developer Sandbox.
    2. Login command: Paste the oc login command that you copied previously.
  8. The Creation screen displays Successful operation. Click Go back to Resources.

Verification​

  1. On the Settings > Resources screen, your Developer Sandbox is running.

    Developer Sandbox is running

  2. Select your Developer Sandbox in the Podman Desktop tray

  3. Run basic tasks such as:

- + \ No newline at end of file diff --git a/docs/kubernetes/openshift/creating-an-openshift-local-cluster.html b/docs/kubernetes/openshift/creating-an-openshift-local-cluster.html index 5dc00a9104b..37c12295f91 100644 --- a/docs/kubernetes/openshift/creating-an-openshift-local-cluster.html +++ b/docs/kubernetes/openshift/creating-an-openshift-local-cluster.html @@ -13,13 +13,13 @@ - +

Creating an OpenShift Local instance

Red Hat OpenShift Local manages a minimal OpenShift or MicroShift cluster on your workstation for local development and testing.

With Podman Desktop and the OpenShift Local extension, you can manage your OpenShift Local instances.

Prerequisites​

Procedure​

  1. Install the OpenShift Local extension: on to Dashboard, click OpenShift Local .

  2. Install the OpenShift Local binaries, when on the Dashboard, you see Podman Desktop was not able to find an installation of OpenShift Local.

    1. In the OpenShift Local tile, click Install.
    2. When prerequisites are missing, follow the instructions.
    3. In the Red Hat OpenShift Local screen, click Yes to start the installation.
    4. Follow the installation program instructions.
    5. Reboot to finalize system changes.

  3. (Optionally) Review the extension settings in Settings > Preferences > Extension: Red Hat OpenShift Local.

  4. On the Dashboard, click Initialize and start.

    1. Select your OpenShift Local Virtual machine preset, if not set in Settings > Preferences > Extension: Red Hat OpenShift Local > Preset.

      • MicroShift (experimental): provides a lightweight and optimized environment with a limited set of services.
      • OpenShift: provides a single node OpenShift cluster with a fuller set of services, including a web console (requires more resources).

    2. Provide a pull secret, required to pull container images from the registry:

      1. Open the Red Hat OpenShift Local download page.
      2. Click Copy pull secret.
      3. Get back to Podman Desktop.
      4. Paste the pull secret, and press Enter.

Verification​

  1. On the Dashboard screen, OpenShift Local is running.

  2. On the Settings > Resources screen, your OpenShift Local instance is running.

    Developer Sandbox is running

  3. Select your OpenShift Local instance the Podman Desktop tray.

  4. Run basic tasks such as:

Additional resources​

- + \ No newline at end of file diff --git a/docs/kubernetes/viewing-and-selecting-current-kubernete-context-in-the-status-bar.html b/docs/kubernetes/viewing-and-selecting-current-kubernete-context-in-the-status-bar.html index 2e4681307ca..8d627bc70de 100644 --- a/docs/kubernetes/viewing-and-selecting-current-kubernete-context-in-the-status-bar.html +++ b/docs/kubernetes/viewing-and-selecting-current-kubernete-context-in-the-status-bar.html @@ -13,14 +13,14 @@ - +

Viewing and selecting the current Kubernetes context

With Podman Desktop, you can view and select your current Kubernetes context in the status bar.

Prerequisites​

  • You have a Kubernetes context in your kubeconfig file: <your_kubernetes_cluster>. For example, Creating a kind cluster.

Procedure​

  1. To view your current Kubernetes context, in the Podman Desktop main window status bar, see the name next to the icon.

  2. (Optionally) To change your Kubernetes context:

    1. Click .
    2. In the drop-down menu, click the context name to activate.
- + \ No newline at end of file diff --git a/docs/kubernetes/viewing-and-selecting-current-kubernete-context.html b/docs/kubernetes/viewing-and-selecting-current-kubernete-context.html index c07ebee1878..81344c5acf0 100644 --- a/docs/kubernetes/viewing-and-selecting-current-kubernete-context.html +++ b/docs/kubernetes/viewing-and-selecting-current-kubernete-context.html @@ -13,14 +13,14 @@ - +

Viewing and selecting the current Kubernetes context

With Podman Desktop, you can view and select your current Kubernetes context.

Prerequisites​

  • You have a Kubernetes context in your kubeconfig file: <your_kubernetes_cluster>. For example, Creating a kind cluster.

Procedure​

  1. Open the Podman Desktop tray menu.

    In the task bar, click Show hidden icons.

    Podman Desktop tray

    Right-click the Podman Desktop tray icon to open the menu.

    Podman Desktop tray

  2. Click Kubernetes to see your current Kubernetes context.

    Podman Desktop tray

  3. (Optionally) To change your Kubernetes context, click on the context name to activate.

- + \ No newline at end of file diff --git a/docs/migrating-from-docker.html b/docs/migrating-from-docker.html index f61d642f6d0..d2a2b0af100 100644 --- a/docs/migrating-from-docker.html +++ b/docs/migrating-from-docker.html @@ -13,13 +13,13 @@ - +

Migration from Docker to Podman Desktop

When you have used Docker in the past, you can continue using familiar workflows with Podman Desktop:

- + \ No newline at end of file diff --git a/docs/migrating-from-docker/emulating-docker-cli-with-podman.html b/docs/migrating-from-docker/emulating-docker-cli-with-podman.html index 35c0b24fd00..1d9d5d9b09f 100644 --- a/docs/migrating-from-docker/emulating-docker-cli-with-podman.html +++ b/docs/migrating-from-docker/emulating-docker-cli-with-podman.html @@ -13,14 +13,14 @@ - +

Emulating Docker CLI with Podman

Consider emulating Docker CLI with Podman to migrate transparently to Podman.

  • Continue using familiar Docker commands.
  • Take advantage of the benefits of Podman on macOS.
  • Your tools, such as Maven or Testcontainers, communicate with Podman without reconfiguration.

Prerequisites​

  • Podman

Procedure​

  1. Create a /usr/local/bin/docker script:

    #!/usr/bin/sh
    [ -e /etc/containers/nodocker ] || \
    echo "Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg." >&2
    exec podman "$@"

  2. (Optional) Create an empty /etc/containers/nodocker file to avoid the Emulate Docker CLI using podman. message when running the script.

    # touch /etc/containers/nodocker

  3. Make the script executable:

    # chmod +x /usr/local/bin/docker

Verification​

  • Use the docker script to run commands. Example:

    $ docker run -it docker.io/hello-world
- + \ No newline at end of file diff --git a/docs/migrating-from-docker/importing-saved-containers.html b/docs/migrating-from-docker/importing-saved-containers.html index 07a3404e7e5..e5fac60e692 100644 --- a/docs/migrating-from-docker/importing-saved-containers.html +++ b/docs/migrating-from-docker/importing-saved-containers.html @@ -13,14 +13,14 @@ - +

Importing saved containers to Podman

Consider importing saved containers to continue using familiar containers.

Prerequisites​

  • Podman

  • You saved your existing containers by running the command:

    $ podman save <your_container> > <your_container_archive>.tar

Procedure​

  • Import your existing containers into Podman. Run the command for each container archive:

    $ podman import <your_container_archive>.tar

Verification​

  • Your imported containers appear in the Podman Desktop Images section.

Additional resources​

- + \ No newline at end of file diff --git a/docs/migrating-from-docker/using-podman-mac-helper.html b/docs/migrating-from-docker/using-podman-mac-helper.html index fc55d355a82..7168eafc792 100644 --- a/docs/migrating-from-docker/using-podman-mac-helper.html +++ b/docs/migrating-from-docker/using-podman-mac-helper.html @@ -13,14 +13,14 @@ - +

Using the podman-mac-helper tool to migrate from Docker to Podman on macOS

Consider using podman-mac-help to migrate transparently to Podman on macOS.

  • Continue using familiar Docker commands.
  • Take advantage of the benefits of Podman on macOS.
  • Your tools, such as Maven or Testcontainers, communicate with Podman without reconfiguration.

The podman-mac-helper tool provides a compatibility layer that allows you to use most Docker commands with Podman on macOS. The service redirects /var/run/docker to the fixed user-assigned UNIX socket location.

Prerequisites​

Procedure​

  1. Set up the podman-mac-helper service: run the command in a terminal:

    sudo podman-mac-helper install

  2. Restart your Podman machine: go to Settings > Resources, and in the Podman tile, click .

Verification​

  1. The Docker socket is a symbolic link for the Podman socket:

    $ ls -la /var/run/docker.sock

    The output points to a podman.sock file such as:

    /var/run/docker.sock -> /Users/username/.local/share/containers/podman/machine/podman.sock

  2. When you query the Docker socket, you receive replies from Podman rather than Docker.

    For instance, this command outputs Podman version rather that Docker version:

    $ curl -s --unix-socket /var/run/docker.sock "http://v1.41/info"  | jq -r .ServerVersion

  3. Your tools communicating to the Docker socket, such as Maven or Testcontainers, communicate with Podman without reconfiguration.

  4. (Optionally, if the docker CLI is installed) The docker CLI context is set to the default value unix:///var/run/docker.sock:

    $ docker context list
    NAME       TYPE  DESCRIPTION                              DOCKER ENDPOINT             KUBERNETES ENDPOINT  ORCHESTRATOR
    default *  moby  Current DOCKER_HOST based configuration  unix:///var/run/docker.sock

  5. (Optionally, if the docker CLI is installed) The docker CLI communicates with the Podman socket.

    Therefore this command outputs Podman version rather that Docker version:

    $ docker info --format=json | jq -r .ServerVersion

Additional resources​

- + \ No newline at end of file diff --git a/docs/migrating-from-docker/using-the-docker_host-environment-variable.html b/docs/migrating-from-docker/using-the-docker_host-environment-variable.html index e61b3fb23b8..e583c5b25d4 100644 --- a/docs/migrating-from-docker/using-the-docker_host-environment-variable.html +++ b/docs/migrating-from-docker/using-the-docker_host-environment-variable.html @@ -13,13 +13,13 @@ - +

Using the DOCKER_HOST environment variable

Consider using the DOCKER_HOST environment variable to migrate transparently from Docker to Podman Desktop on all platforms.

  • Continue using familiar Docker commands.
  • Take advantage of the benefits of Podman.
  • Your tools, such as Gradle or Testcontainers, communicate with Podman without reconfiguration.

Prerequisites​

  • Podman

Procedure​

  1. Identify the location of your Podman socket

    $ podman machine inspect --format '{{.ConnectionInfo.PodmanSocket.Path}}'

  2. Set the DOCKER_HOST environment variable to your Podman socket location. Be sure to add the unix:// scheme to the path retrieved previously:

    $ export DOCKER_HOST=unix://<your_podman_socket_location>

Verification​

  • Your tools using the DOCKER_HOST environment variable, such as Gradle or Testcontainers, communicate with Podman without reconfiguration.
- + \ No newline at end of file diff --git a/docs/migrating-from-docker/verifying-your-tools-are-using-podman.html b/docs/migrating-from-docker/verifying-your-tools-are-using-podman.html index 6a9e9768412..de341165da4 100644 --- a/docs/migrating-from-docker/verifying-your-tools-are-using-podman.html +++ b/docs/migrating-from-docker/verifying-your-tools-are-using-podman.html @@ -13,13 +13,13 @@ - +

Verifying that your tools are using Podman

When you have configured your host to use Podman rather then Docker, consider verifying your setup works as intended.

Prerequisites​

Procedure​

  1. The Docker socket replies successfully for listing all containers:

    $ curl --unix-socket npipe:////./pipe/docker_engine "http:/v1.41/containers/json?all=true"

  2. Podman commands run successfully when redirected to the Docker socket:

    $ CONTAINER_HOST=npipe:////./pipe/docker_engine podman ps
- + \ No newline at end of file diff --git a/docs/onboarding.html b/docs/onboarding.html index 72e31f986d9..2d171e9cd65 100644 --- a/docs/onboarding.html +++ b/docs/onboarding.html @@ -13,13 +13,13 @@ - +
- + \ No newline at end of file diff --git a/docs/onboarding/containers.html b/docs/onboarding/containers.html index 886a7506116..85796daafd7 100644 --- a/docs/onboarding/containers.html +++ b/docs/onboarding/containers.html @@ -13,13 +13,13 @@ - +

Onboarding for container workloads

To run container workloads, set up at least one container engine.

Podman Desktop does not automatically set up container engine resources that you might not need.

Procedure​

  1. Select a container engine supporting your workload.

    WorkloadPodmanNative DockerDocker Desktop
    Rootless containers✅ yes✅ yes❌ no
    Rootful containers✅ yes✅ yes✅ yes
    Compose✅ yes✅ yes✅ yes
    Pods✅ yes❌ no❌ no

    Podman supports rootless container and pods, in addition to rootful containers and Compose.

  2. Select an execution environment supporting your container engine and your operating system.

    • Select a Podman execution environment:

      Host operating systemNative containersPodman machineLima machine
      Windows❌ no✅ yes❌ experimental
      macOS❌ no✅ yes✅ yes
      Linux✅ yes❌ disabled in Podman Desktop✅ yes

    • Select a Docker execution environment:

      Host operating systemNative containersLima machineDocker Desktop
      Windows❌ no❌ no✅ yes
      macOS❌ no✅ yes✅ yes
      Linux✅ yes❌ no✅ yes

  3. Setup your container engine.

- + \ No newline at end of file diff --git a/docs/onboarding/containers/creating-a-lima-instance-with-podman-desktop.html b/docs/onboarding/containers/creating-a-lima-instance-with-podman-desktop.html index 9211d9b7733..e0e3989fe3b 100644 --- a/docs/onboarding/containers/creating-a-lima-instance-with-podman-desktop.html +++ b/docs/onboarding/containers/creating-a-lima-instance-with-podman-desktop.html @@ -13,13 +13,13 @@ - +

Creating a Lima instance with Podman Desktop

To use the Lima provider you need a Lima instance running a Linux virtual machine.

In the future, Podman Desktop might be able to create Lima instances.

Consider creating a custom Lima instance to:

  • Control the assigned resources: CPUs, memory, and disk size.
  • Use the rootful connection by default, for example to run Kind.

Prerequisites​

  • The limactl executable is installed.
brew install lima

See https://lima-vm.io

Procedure​

Currently you need to use the console, to create a new Lima instance.

After the instance is started, you need to restart the Lima extension.

Examples:

To create an instance "podman" from a template "podman":

$ limactl start --name=podman template://podman

To create an instance "docker" from a template "docker":

$ limactl start --name=docker template://docker

To select the number of CPUs and the memory or disk size:

$ limactl start --set='.cpus = 2 | .memory = "2GiB" | .disk = "50GiB"' ...

To create a rootful instance, use the rootful template:

$ limactl start --name=podman template://podman-rootful

Verification​

To verify the connection to a running "podman" instance:

$ podman.lima version

To verify the connection to a running "docker" instance:

$ docker.lima version

Kubernetes​

To create a single-node Kubernetes cluster running k3s:

$ limactl start template://k3s

To create a single-node Kubernetes cluster running k8s:

$ limactl start template://k8s

When the installation is done, the location of the KUBECONFIG file is printed:

You can also use the kubectl.lima wrapper script, to connect to the cluster:

$ kubectl.lima version
- + \ No newline at end of file diff --git a/docs/onboarding/containers/creating-a-podman-machine-with-podman-desktop.html b/docs/onboarding/containers/creating-a-podman-machine-with-podman-desktop.html index e5f3edbece1..2330fd868fb 100644 --- a/docs/onboarding/containers/creating-a-podman-machine-with-podman-desktop.html +++ b/docs/onboarding/containers/creating-a-podman-machine-with-podman-desktop.html @@ -13,7 +13,7 @@ - + @@ -28,7 +28,7 @@ Enable to use the rootful connection by default. Required to use Kind on Windows.
  • (On Windows) User mode networking (traffic relayed by a user process): Enable to route the traffic through the network connection from your Windows session. Required to access resources behind your VPN connection.
  • Click Create

    • Create a Podman machine

    - + \ No newline at end of file diff --git a/docs/onboarding/containers/installing-podman-with-openshift-local-on-windows.html b/docs/onboarding/containers/installing-podman-with-openshift-local-on-windows.html index 1174ca0b7de..c100399132b 100644 --- a/docs/onboarding/containers/installing-podman-with-openshift-local-on-windows.html +++ b/docs/onboarding/containers/installing-podman-with-openshift-local-on-windows.html @@ -13,13 +13,13 @@ - +

    Installing the Podman Preset with OpenShift Local on Windows

    On Windows, running the Podman container engine requires running a Linux distribution on a virtual machine.

    Consider installing the Podman Preset in OpenShift Local rather than installing Podman with Podman Desktop when you require one of following:

    • No WSL 2
    • Full control on the HyperV virtual machine
    • User without administrator privileges
    • VPN
    • Windows 10

    Prerequisites​

    • The user is a member of the Hyper-V Administrators group. The user can add a virtual machine, start or stop this virtual machine, and access the resources related to this virtual machine.
    • Windows 10 version 1709 or later, Enterprise or Professional edition, or Windows 11, Enterprise or Professional edition

    Procedure​

    1. Install the OpenShift Local extension.

    2. Install OpenShift Local.

    3. Select the Podman container runtime preset:

      $ crc config set preset podman

    4. Set up your host machine for Red Hat OpenShift Local:

      $ crc setup

    5. Start the Red Hat OpenShift instance:

      $ crc start

    Additional resources​

    Next steps​

    - + \ No newline at end of file diff --git a/docs/onboarding/containers/installing-podman-with-podman-desktop-on-windows.html b/docs/onboarding/containers/installing-podman-with-podman-desktop-on-windows.html index 46210d7e1c4..4381eac8a61 100644 --- a/docs/onboarding/containers/installing-podman-with-podman-desktop-on-windows.html +++ b/docs/onboarding/containers/installing-podman-with-podman-desktop-on-windows.html @@ -13,14 +13,14 @@ - +

    Installing Podman on Windows with Podman Desktop

    On Windows, running the Podman container engine requires running a Linux distribution on a virtual machine.

    Podman Desktop can assist you to install the Podman container engine in a Fedora distribution of Linux, on the Windows Subsystem for Linux version 2 (WSL 2). Main benefits are:

    • Ease of use
    • Windows native virtualization performance

    Consider rather installing Podman with OpenShift Local if:

    • You prefer working with a RHEL distribution of Linux
    • Your environment doesn't allow you to meet the prerequisites

    Prerequisites​

    • 6 GB RAM
    • No VPN
    • WSL prerequisites
      • User with administrator privileges
      • Windows 64bit
      • Windows 10 Build 18362 or greater, or Windows 11
      • On a virtual machine: Nested Virtualization enabled
    • Podman is not installed
    • No WSL 2 Linux virtual machine is running

    Procedure​

    1. Enable the WSL feature without installing the default Ubuntu distribution of Linux. See Enabling WSL 2 and WSL basic commands:

      wsl --install --no-distribution

    2. The Home screen displays Podman Desktop was not able to find an installation of Podman. Click on Install.

      img1

    3. Podman Desktop checks the prerequites to install Podman Engine. When necessary, follow the instructions to install prerequisites.

    4. Podman displays the dialog: Podman is not installed on this system, would you like to install Podman?. Click on Yes to install Podman.

    5. Click on Initialize Podman.

    Additional resources​

    Next steps​

    - + \ No newline at end of file diff --git a/docs/onboarding/kubernetes.html b/docs/onboarding/kubernetes.html index 3d6ef37a829..5922f5e83da 100644 --- a/docs/onboarding/kubernetes.html +++ b/docs/onboarding/kubernetes.html @@ -13,13 +13,13 @@ - +

    Onboarding for Kubernetes workloads

    To run Kubernetes workloads, set up at least one Kubernetes context.

    Podman Desktop does not automatically set up Kubernetes resources that you might not need.

    Procedure​

    To connect to a remote Kubernetes, you can:

    To setup Kubernetes on your workstation, you can:

    - + \ No newline at end of file diff --git a/docs/onboarding/kubernetes/kind.html b/docs/onboarding/kubernetes/kind.html index f40a85ff799..4692fcc7f34 100644 --- a/docs/onboarding/kubernetes/kind.html +++ b/docs/onboarding/kubernetes/kind.html @@ -13,13 +13,13 @@ - +
    - + \ No newline at end of file diff --git a/docs/onboarding/kubernetes/kind/configuring-podman-for-kind-on-windows.html b/docs/onboarding/kubernetes/kind/configuring-podman-for-kind-on-windows.html index 72e52f60960..f25d9a7ac5a 100644 --- a/docs/onboarding/kubernetes/kind/configuring-podman-for-kind-on-windows.html +++ b/docs/onboarding/kubernetes/kind/configuring-podman-for-kind-on-windows.html @@ -13,13 +13,13 @@ - +

    Configuring Podman for Kind on Windows Subsystem for Linux (WSL)

    When you create a Podman machine, Podman creates the machine in rootless mode.

    With a Podman machine running on WSL, Kind:

    • Requires the rootful machine.

    Therefore, set the Podman machine to rootful mode.

    Procedure​

    1. Stop the Podman machine:

      $ podman machine stop

    2. Set the Podman machine in rootful mode:

      $ podman machine set --rootful

    3. Start the Podman machine:

      $ podman machine start
    - + \ No newline at end of file diff --git a/docs/onboarding/kubernetes/kind/creating-a-kind-cluster.html b/docs/onboarding/kubernetes/kind/creating-a-kind-cluster.html index 8bb147a6d0b..b3ac3ec8e8a 100644 --- a/docs/onboarding/kubernetes/kind/creating-a-kind-cluster.html +++ b/docs/onboarding/kubernetes/kind/creating-a-kind-cluster.html @@ -13,13 +13,13 @@ - +

    Creating a local Kind-powered Kubernetes cluster

    You can create multiple local Kind-powered Kubernetes clusters.

    Prerequisites​

    Procedure​

    1. Go to Settings > Resources

    2. In the Kind tile, click on the Create new ... button.

    3. Choose your options, and click the Create button.

      The defaults are:

      • Name: kind-cluster
      • Provider type: podman
      • HTTP port: 9090
      • HTTPS port: 9443

    4. (Optionally) Click the Show logs button to display the logs.

    5. After successful creation, click on the Go back to resources button

    Verification​

    1. In Settings > Resources, in the Kind tile, your <kind-cluster> instance is running.
    2. In the Podman Desktop tray, open the Kubernetes menu, you can set the context to your Kind cluster: kind-<kind-cluster>.
    - + \ No newline at end of file diff --git a/docs/onboarding/kubernetes/kind/deleting-your-kind-cluster.html b/docs/onboarding/kubernetes/kind/deleting-your-kind-cluster.html index 24de2a87949..feabe19ff0a 100644 --- a/docs/onboarding/kubernetes/kind/deleting-your-kind-cluster.html +++ b/docs/onboarding/kubernetes/kind/deleting-your-kind-cluster.html @@ -13,13 +13,13 @@ - +
    - + \ No newline at end of file diff --git a/docs/onboarding/kubernetes/kind/installing-kind.html b/docs/onboarding/kubernetes/kind/installing-kind.html index 8b4f8e0a7e6..9ad6a5df7c4 100644 --- a/docs/onboarding/kubernetes/kind/installing-kind.html +++ b/docs/onboarding/kubernetes/kind/installing-kind.html @@ -13,7 +13,7 @@ - + @@ -21,7 +21,7 @@
    - + \ No newline at end of file diff --git a/docs/onboarding/kubernetes/kind/restarting-your-kind-cluster.html b/docs/onboarding/kubernetes/kind/restarting-your-kind-cluster.html index 422ba403c5d..76e195dfbbe 100644 --- a/docs/onboarding/kubernetes/kind/restarting-your-kind-cluster.html +++ b/docs/onboarding/kubernetes/kind/restarting-your-kind-cluster.html @@ -13,7 +13,7 @@ - + @@ -22,7 +22,7 @@ Therefore, Podman Desktop stops the Kind cluster, starts it again, and hopes for the best. The Kind cluster might not restart successfully. In that case:

    - + \ No newline at end of file diff --git a/docs/proxy.html b/docs/proxy.html index c190642454b..6df67f8459c 100644 --- a/docs/proxy.html +++ b/docs/proxy.html @@ -13,13 +13,13 @@ - +
    - + \ No newline at end of file diff --git a/docs/proxy/using-a-proxy-in-your-containers.html b/docs/proxy/using-a-proxy-in-your-containers.html index 933cad3c157..68cb9413c7e 100644 --- a/docs/proxy/using-a-proxy-in-your-containers.html +++ b/docs/proxy/using-a-proxy-in-your-containers.html @@ -13,13 +13,13 @@ - +

    Using a proxy in your containers on macOS and Windows

    You can configure your Podman machine to use a proxy for your containers.

    Prerequisites​

    • <your.proxy.tld:port>: Your proxy URL.

    Procedure​

    1. Open a shell prompt on the Podman machine:

      $ podman machine ssh

    2. Edit the containers.conf file to pass the proxy environment variables to Podman CLI.

      The file location depends on your connection mode:

      • rootless: $HOME/.config/containers/containers.conf

      • rootful: /etc/containers/containers.conf

    3. Set the proxy environment variables to pass into the containers:

      [containers]
      http_proxy = true
      env = ["http_proxy=<your.proxy.tld:port>", "https_proxy=<your.proxy.tld:port>"]

    4. Go to Settings > Resources and restart the Podman machine.

    - + \ No newline at end of file diff --git a/docs/proxy/using-a-proxy-on-linux.html b/docs/proxy/using-a-proxy-on-linux.html index 4dddcb18ff2..cfa1e1800d1 100644 --- a/docs/proxy/using-a-proxy-on-linux.html +++ b/docs/proxy/using-a-proxy-on-linux.html @@ -13,13 +13,13 @@ - +

    Using Podman Desktop behind a proxy on Linux

    You can configure Podman to run behind a proxy.

    Prerequisites​

    • <proxy_ca.pem>: Your proxy Certificate Authorities (CA), in Privacy-Enhanced Mail (PEM) format.
    • <your.proxy.tld:port>: Your proxy URL.

    Procedure​

    1. Edit the containers.conf file to pass the proxy environment variables to Podman CLI.

      The file location depends on your connection mode:

      • rootless: $HOME/.config/containers/containers.conf

      • rootful: /etc/containers/containers.conf

    2. Set the proxy environment variables to pass into the containers:

      [containers]
      http_proxy = true
      env = ["http_proxy=<your.proxy.tld:port>", "https_proxy=<your.proxy.tld:port>"]

    3. Set the proxy environment variables to pass into the Podman engine:

      [engine]
      env = ["http_proxy=<your.proxy.tld:port>", "https_proxy=<your.proxy.tld:port>"]

    4. Add the custom Certificate Authorities (CA) for your proxy:

      $ sudo cp <proxy_ca.pem> /etc/pki/ca-trust/source/anchors/
      $ sudo update-ca-trust

    5. Restart all podman processes.

      $ pkill podman

    6. Restart Podman Desktop: Ctrl + q.

    Verification​

    1. Go to Images.
    2. Click Pull an image.
    3. Image to Pull: bash
    4. Click Pull image.
    5. Podman Desktop reports Download complete.
    - + \ No newline at end of file diff --git a/docs/proxy/using-a-proxy-requiring-a-custom-ca.html b/docs/proxy/using-a-proxy-requiring-a-custom-ca.html index adf1f207a82..19113d6e811 100644 --- a/docs/proxy/using-a-proxy-requiring-a-custom-ca.html +++ b/docs/proxy/using-a-proxy-requiring-a-custom-ca.html @@ -13,14 +13,14 @@ - +

    Using Podman Desktop behind a proxy requiring custom Certificate Authorities (CA) on macOS and Windows

    You can configure Podman Desktop to run behind a proxy requiring custom Certificate Authorities (CA), such as self-signed certificates. The configuration applies to the Podman engine, but not to your containers.

    Prerequisites​

    • Your proxy URL: <your.proxy.tld:port>
    • Your proxy Certificate Authorities (CA) is stored in your home directory, in the proxy_ca.pem file, in Privacy-Enhanced Mail (PEM) format.

    Procedure​

    1. Go to Settings > Proxy, and set your proxy URL:

      1. Proxy configuration enabled: yes
      2. Web Proxy (HTTP): <your.proxy.tld:port>
      3. Secure Web Proxy (HTTPS): <your.proxy.tld:port>
      4. Click the Update button

    2. Copy the certificate to the Podman machine:

      $ cat proxy_ca.pem | podman machine ssh podman-machine-default "cat > proxy_ca.pem"

    3. Open a shell prompt on the Podman machine:

      $ podman machine ssh podman-machine-default

    4. Add the custom Certificate Authorities (CA) for your proxy:

      $ sudo cp proxy_ca.pem /etc/pki/ca-trust/source/anchors/
      $ sudo update-ca-trust

    5. Go to Settings > Resources and restart the Podman machine.

    Verification​

    1. Go to Images.
    2. Click Pull an image.
    3. Image to Pull: bash
    4. Click Pull image.
    5. Podman Desktop reports Download complete.
    - + \ No newline at end of file diff --git a/docs/proxy/using-a-proxy.html b/docs/proxy/using-a-proxy.html index 997add6ea30..06205e9837d 100644 --- a/docs/proxy/using-a-proxy.html +++ b/docs/proxy/using-a-proxy.html @@ -13,13 +13,13 @@ - +

    Using Podman Desktop behind a proxy on macOS and Windows

    You can configure Podman Desktop to run behind a proxy.

    The configuration applies to:

    • Processes that Podman Desktop started, such as downloading Podman, Compose, or Kind installers.
    • Podman engine.

    The configuration does not apply to:

    • Your Podman containers.
    • Command line tools that Podman Desktop did not start.

    Prerequisites​

    Procedure​

    1. Go to Settings > Proxy, and set your proxy URL:

      1. Proxy configuration enabled: yes
      2. Web Proxy (HTTP): <your.proxy.tld:port>
      3. Secure Web Proxy (HTTPS): <your.proxy.tld:port>
      4. Click the Update button

    2. Go to Settings > Resources and restart the Podman machine.

    Verification​

    1. You can install extensions such as:

    2. Podman can pull images.

      1. Go to Images.
      2. Click Pull an image.
      3. Image to Pull: bash
      4. Click Pull image.
      5. Podman Desktop reports Download complete.

    Additional resources​

    - + \ No newline at end of file diff --git a/docs/proxy/using-a-vpn-on-windows.html b/docs/proxy/using-a-vpn-on-windows.html index 097f5232124..a8672e9508d 100644 --- a/docs/proxy/using-a-vpn-on-windows.html +++ b/docs/proxy/using-a-vpn-on-windows.html @@ -13,13 +13,13 @@ - +

    Accessing resources behind a VPN with Podman on Windows

    On Windows, if Podman needs to access resources behind a user-controlled VPN, enable user mode networking in your Podman machine.

    Prerequisites​

    • Windows host with updated WSL2.
    • Podman 4.6.0 or greater.

    Procedure​

    Verification​

    • You can now access resources that are behind the VPN.
    - + \ No newline at end of file diff --git a/docs/tags.html b/docs/tags.html index 96a824f54a8..6d548ad282f 100644 --- a/docs/tags.html +++ b/docs/tags.html @@ -13,13 +13,13 @@ - +

    Tags

    - + \ No newline at end of file diff --git a/docs/tags/chocolatey.html b/docs/tags/chocolatey.html index 7f5ecf8ac13..ab7a6456e56 100644 --- a/docs/tags/chocolatey.html +++ b/docs/tags/chocolatey.html @@ -13,13 +13,13 @@ - +

    One doc tagged with "chocolatey"

    View All Tags
    - + \ No newline at end of file diff --git a/docs/tags/compose.html b/docs/tags/compose.html index 1ca9552bf28..fa2eeb98871 100644 --- a/docs/tags/compose.html +++ b/docs/tags/compose.html @@ -13,13 +13,13 @@ - +

    3 docs tagged with "compose"

    View All Tags

    Running Compose files

    With Podman Desktop, you can manage multi-container applications defined in Compose files.

    Working with Compose

    With Podman Desktop, you can install a Compose engine and manage multi-container applications defined in Compose files.

    - + \ No newline at end of file diff --git a/docs/tags/containers.html b/docs/tags/containers.html index 0c121e02ebf..0655082c27a 100644 --- a/docs/tags/containers.html +++ b/docs/tags/containers.html @@ -13,13 +13,13 @@ - +

    3 docs tagged with "containers"

    View All Tags

    Images

    Working with container images

    - + \ No newline at end of file diff --git a/docs/tags/extension.html b/docs/tags/extension.html index e98401c302c..ae4c5c0b166 100644 --- a/docs/tags/extension.html +++ b/docs/tags/extension.html @@ -13,13 +13,13 @@ - +

    4 docs tagged with "extension"

    View All Tags

    Writing

    Writing a Podman Desktop extension

    - + \ No newline at end of file diff --git a/docs/tags/flathub.html b/docs/tags/flathub.html index 9de1bb54222..79ebda4544e 100644 --- a/docs/tags/flathub.html +++ b/docs/tags/flathub.html @@ -13,13 +13,13 @@ - +

    2 docs tagged with "flathub"

    View All Tags

    Linux

    You can install Podman Desktop on Linux from Flathub, a Flatpak bundle, or a ZIP archive.

    - + \ No newline at end of file diff --git a/docs/tags/flatpak.html b/docs/tags/flatpak.html index a04a3097533..748d4560429 100644 --- a/docs/tags/flatpak.html +++ b/docs/tags/flatpak.html @@ -13,13 +13,13 @@ - +

    2 docs tagged with "flatpak"

    View All Tags

    Linux

    You can install Podman Desktop on Linux from Flathub, a Flatpak bundle, or a ZIP archive.

    - + \ No newline at end of file diff --git a/docs/tags/images.html b/docs/tags/images.html index 4ac25033617..54f0f49699b 100644 --- a/docs/tags/images.html +++ b/docs/tags/images.html @@ -13,13 +13,13 @@ - +

    8 docs tagged with "images"

    View All Tags

    Containers

    Starting a container on your container engine.

    Images

    Working with container images

    - + \ No newline at end of file diff --git a/docs/tags/installing.html b/docs/tags/installing.html index da91a309718..10727823f80 100644 --- a/docs/tags/installing.html +++ b/docs/tags/installing.html @@ -13,13 +13,13 @@ - +

    17 docs tagged with "installing"

    View All Tags

    Custom Lima instance

    Podman Desktop can assist you to create custom Lima instance on Linux and macOS.

    In your containers

    Using Podman Desktop behind a proxy requiring custom Certificate Authorities (CA).

    Linux

    You can install Podman Desktop on Linux from Flathub, a Flatpak bundle, or a ZIP archive.

    Using behind a proxy

    Using Podman Desktop behind a proxy requiring custom Certificate Authorities (CA).

    Windows

    How to install Podman on Windows.

    - + \ No newline at end of file diff --git a/docs/tags/kind.html b/docs/tags/kind.html index 42c7f0ba663..0d8a7946143 100644 --- a/docs/tags/kind.html +++ b/docs/tags/kind.html @@ -13,13 +13,13 @@ - +

    8 docs tagged with "kind"

    View All Tags

    Onboarding Kind

    Kind is one way to get Kubernetes running on your workstation.

    - + \ No newline at end of file diff --git a/docs/tags/lima.html b/docs/tags/lima.html index 53248fc71db..33009ef3798 100644 --- a/docs/tags/lima.html +++ b/docs/tags/lima.html @@ -13,13 +13,13 @@ - +

    One doc tagged with "lima"

    View All Tags
    - + \ No newline at end of file diff --git a/docs/tags/linux.html b/docs/tags/linux.html index 4974b362174..f576a47cc13 100644 --- a/docs/tags/linux.html +++ b/docs/tags/linux.html @@ -13,13 +13,13 @@ - +

    8 docs tagged with "linux"

    View All Tags

    Custom Lima instance

    Podman Desktop can assist you to create custom Lima instance on Linux and macOS.

    In your containers

    Using Podman Desktop behind a proxy requiring custom Certificate Authorities (CA).

    Linux

    You can install Podman Desktop on Linux from Flathub, a Flatpak bundle, or a ZIP archive.

    Linux

    Using Podman Desktop behind a proxy on Linux.

    Using behind a proxy

    Using Podman Desktop behind a proxy requiring custom Certificate Authorities (CA).

    - + \ No newline at end of file diff --git a/docs/tags/mac-0-s.html b/docs/tags/mac-0-s.html index 36f4167bd85..941f012d084 100644 --- a/docs/tags/mac-0-s.html +++ b/docs/tags/mac-0-s.html @@ -13,13 +13,13 @@ - +

    One doc tagged with "mac0S"

    View All Tags

    Using `podman-mac-helper` on macOS

    Using the `podman-mac-helper` tool can make it easier to migrate from Docker to Podman on macOS, as it allows you to continue using familiar Docker commands while taking advantage of the benefits of Podman.

    - + \ No newline at end of file diff --git a/docs/tags/mac-os.html b/docs/tags/mac-os.html index 2c13019602c..478955e8ec9 100644 --- a/docs/tags/mac-os.html +++ b/docs/tags/mac-os.html @@ -13,13 +13,13 @@ - +

    2 docs tagged with "macOS"

    View All Tags

    Custom Lima instance

    Podman Desktop can assist you to create custom Lima instance on Linux and macOS.

    - + \ No newline at end of file diff --git a/docs/tags/macos.html b/docs/tags/macos.html index 0a915d204e8..71e459d9abc 100644 --- a/docs/tags/macos.html +++ b/docs/tags/macos.html @@ -13,13 +13,13 @@ - +

    4 docs tagged with "macos"

    View All Tags

    In your containers

    Using Podman Desktop behind a proxy requiring custom Certificate Authorities (CA).

    Using behind a proxy

    Using Podman Desktop behind a proxy requiring custom Certificate Authorities (CA).

    - + \ No newline at end of file diff --git a/docs/tags/migrating-from-docker.html b/docs/tags/migrating-from-docker.html index 601f076447a..cec665f4fca 100644 --- a/docs/tags/migrating-from-docker.html +++ b/docs/tags/migrating-from-docker.html @@ -13,13 +13,13 @@ - +

    6 docs tagged with "migrating-from-docker"

    View All Tags

    Emulating Docker CLI with Podman

    Emulation Docker CLI with Podman can make it easier to migrate from Docker to Podman, as it allows you to continue using familiar Docker commands while taking advantage of the benefits of Podman.

    Using `podman-mac-helper` on macOS

    Using the `podman-mac-helper` tool can make it easier to migrate from Docker to Podman on macOS, as it allows you to continue using familiar Docker commands while taking advantage of the benefits of Podman.

    Using the `DOCKER_HOST` environment variable

    Using the `DOCKER_HOST` environment variable can make it easier to migrate from Docker to Podman Desktop, as it allows you to continue using familiar Docker commands while taking advantage of the benefits of Podman.

    - + \ No newline at end of file diff --git a/docs/tags/migrating-to-kubernetes.html b/docs/tags/migrating-to-kubernetes.html index f54f8abab1c..1035a701a20 100644 --- a/docs/tags/migrating-to-kubernetes.html +++ b/docs/tags/migrating-to-kubernetes.html @@ -13,13 +13,13 @@ - +

    30 docs tagged with "migrating-to-kubernetes"

    View All Tags

    Kubernetes

    Migrate transparently from Podman to Kubernetes, and continue using familiar workflows.

    Onboarding Kind

    Kind is one way to get Kubernetes running on your workstation.

    - + \ No newline at end of file diff --git a/docs/tags/minikube.html b/docs/tags/minikube.html index 1976ad34895..25e023ec581 100644 --- a/docs/tags/minikube.html +++ b/docs/tags/minikube.html @@ -13,13 +13,13 @@ - +

    7 docs tagged with "minikube"

    View All Tags
    - + \ No newline at end of file diff --git a/docs/tags/onboarding.html b/docs/tags/onboarding.html index bb9daf965c2..7bee95ecfe2 100644 --- a/docs/tags/onboarding.html +++ b/docs/tags/onboarding.html @@ -13,13 +13,13 @@ - +

    3 docs tagged with "onboarding"

    View All Tags

    Containers

    To run container workloads with Podman Desktop, set up at least one container engine.

    Onboarding

    You can install Podman Desktop on Windows, macOS, and Linux.

    - + \ No newline at end of file diff --git a/docs/tags/openshift-local.html b/docs/tags/openshift-local.html index 167823c53bf..69c50a7876b 100644 --- a/docs/tags/openshift-local.html +++ b/docs/tags/openshift-local.html @@ -13,13 +13,13 @@ - +

    One doc tagged with "openshift-local"

    View All Tags
    - + \ No newline at end of file diff --git a/docs/tags/openshift.html b/docs/tags/openshift.html index 78d9c30075d..75d29147852 100644 --- a/docs/tags/openshift.html +++ b/docs/tags/openshift.html @@ -13,13 +13,13 @@ - +

    3 docs tagged with "openshift"

    View All Tags
    - + \ No newline at end of file diff --git a/docs/tags/podman-desktop.html b/docs/tags/podman-desktop.html index bf1899392ef..d6d65d900fc 100644 --- a/docs/tags/podman-desktop.html +++ b/docs/tags/podman-desktop.html @@ -13,13 +13,13 @@ - +

    28 docs tagged with "podman-desktop"

    View All Tags

    Containers

    To run container workloads with Podman Desktop, set up at least one container engine.

    Custom Lima instance

    Podman Desktop can assist you to create custom Lima instance on Linux and macOS.

    Images

    Working with container images

    In your containers

    Using Podman Desktop behind a proxy requiring custom Certificate Authorities (CA).

    Linux

    You can install Podman Desktop on Linux from Flathub, a Flatpak bundle, or a ZIP archive.

    Linux

    Using Podman Desktop behind a proxy on Linux.

    Onboarding

    You can install Podman Desktop on Windows, macOS, and Linux.

    Using behind a proxy

    Using Podman Desktop behind a proxy requiring custom Certificate Authorities (CA).

    Windows

    How to install Podman on Windows.

    Writing

    Writing a Podman Desktop extension

    - + \ No newline at end of file diff --git a/docs/tags/podman.html b/docs/tags/podman.html index 14aed7fe036..56638dbe663 100644 --- a/docs/tags/podman.html +++ b/docs/tags/podman.html @@ -13,13 +13,13 @@ - +

    5 docs tagged with "podman"

    View All Tags

    Custom Lima instance

    Podman Desktop can assist you to create custom Lima instance on Linux and macOS.

    - + \ No newline at end of file diff --git a/docs/tags/pods.html b/docs/tags/pods.html index 57f64f52567..4c28ab5379a 100644 --- a/docs/tags/pods.html +++ b/docs/tags/pods.html @@ -13,13 +13,13 @@ - +

    2 docs tagged with "pods"

    View All Tags

    Pods

    Creating a pod from selected containers.

    - + \ No newline at end of file diff --git a/docs/tags/proxy.html b/docs/tags/proxy.html index b7ab077c254..a1661383a47 100644 --- a/docs/tags/proxy.html +++ b/docs/tags/proxy.html @@ -13,13 +13,13 @@ - +

    2 docs tagged with "proxy"

    View All Tags

    Linux

    Using Podman Desktop behind a proxy on Linux.

    - + \ No newline at end of file diff --git a/docs/tags/publishing.html b/docs/tags/publishing.html index 171abdd5665..4779c8f97d4 100644 --- a/docs/tags/publishing.html +++ b/docs/tags/publishing.html @@ -13,13 +13,13 @@ - +

    2 docs tagged with "publishing"

    View All Tags
    - + \ No newline at end of file diff --git a/docs/tags/registries.html b/docs/tags/registries.html index 59d634a4c74..94a96a27d31 100644 --- a/docs/tags/registries.html +++ b/docs/tags/registries.html @@ -13,13 +13,13 @@ - +

    One doc tagged with "registries"

    View All Tags
    - + \ No newline at end of file diff --git a/docs/tags/restricted-environment.html b/docs/tags/restricted-environment.html index 991c94e3e19..5807c4cb337 100644 --- a/docs/tags/restricted-environment.html +++ b/docs/tags/restricted-environment.html @@ -13,13 +13,13 @@ - +

    2 docs tagged with "restricted-environment"

    View All Tags
    - + \ No newline at end of file diff --git a/docs/tags/scoop.html b/docs/tags/scoop.html index d913302a89e..08c275a2dd9 100644 --- a/docs/tags/scoop.html +++ b/docs/tags/scoop.html @@ -13,13 +13,13 @@ - +

    One doc tagged with "scoop"

    View All Tags
    - + \ No newline at end of file diff --git a/docs/tags/vpn.html b/docs/tags/vpn.html index bfa50a4e0d1..6c287f32af3 100644 --- a/docs/tags/vpn.html +++ b/docs/tags/vpn.html @@ -13,13 +13,13 @@ - +

    One doc tagged with "vpn"

    View All Tags
    - + \ No newline at end of file diff --git a/docs/tags/when-clause.html b/docs/tags/when-clause.html index 990ff93b21d..9b6ca00dfe4 100644 --- a/docs/tags/when-clause.html +++ b/docs/tags/when-clause.html @@ -13,13 +13,13 @@ - +

    One doc tagged with "when clause"

    View All Tags
    - + \ No newline at end of file diff --git a/docs/tags/windows.html b/docs/tags/windows.html index 867bad1b580..8c1e746bcb5 100644 --- a/docs/tags/windows.html +++ b/docs/tags/windows.html @@ -13,13 +13,13 @@ - +

    14 docs tagged with "windows"

    View All Tags

    In your containers

    Using Podman Desktop behind a proxy requiring custom Certificate Authorities (CA).

    Using behind a proxy

    Using Podman Desktop behind a proxy requiring custom Certificate Authorities (CA).

    Windows

    How to install Podman on Windows.

    - + \ No newline at end of file diff --git a/docs/tags/winget.html b/docs/tags/winget.html index 6005fed7d16..41c3ca28f27 100644 --- a/docs/tags/winget.html +++ b/docs/tags/winget.html @@ -13,13 +13,13 @@ - +

    One doc tagged with "winget"

    View All Tags
    - + \ No newline at end of file diff --git a/docs/tags/writing.html b/docs/tags/writing.html index 9282446db14..a0f9ca9f81f 100644 --- a/docs/tags/writing.html +++ b/docs/tags/writing.html @@ -13,13 +13,13 @@ - +

    2 docs tagged with "writing"

    View All Tags

    Writing

    Writing a Podman Desktop extension

    - + \ No newline at end of file diff --git a/docs/troubleshooting.html b/docs/troubleshooting.html index 9eab03f4c55..4a57a578baa 100644 --- a/docs/troubleshooting.html +++ b/docs/troubleshooting.html @@ -13,13 +13,13 @@ - +

    Troubleshooting

    If you cannot find your issue here or in the documentation, please fill an issue on our repository. You can also explore the discussions and do a search on similar issues on the repository.

    Using the Troubleshooting page​

    Podman Desktop has a Troubleshooting page to help identify and fix most common errors.

    Procedure​

    1. To open the Troubleshooting page, click the icon.

    2. To test the connection to the container engine, click the Ping button.

      Expect a reply such as: Responded: 79,75 (9.10ms).

    3. To test Click the Check containers button.

      Expect a reply such as: Responded: 16 containers (108.70ms).

    4. When connection to the container engine failed, to recreate connections to the sockets, click the Reconnect providers button.

      Expect a reply such as: Done in (5.00ms).

    5. Search for errors in the Logs section.

    Additional resources​

    - + \ No newline at end of file diff --git a/docs/troubleshooting/troubleshooting-openshift-local.html b/docs/troubleshooting/troubleshooting-openshift-local.html index f999b5c2629..84d5df78662 100644 --- a/docs/troubleshooting/troubleshooting-openshift-local.html +++ b/docs/troubleshooting/troubleshooting-openshift-local.html @@ -13,13 +13,13 @@ - +

    Troubleshooting OpenShift Local

    You can find here troubleshooting help for issues specific to OpenShift Local.

    1. To verify that your user can run crc, verify that the crc binary is available in the user PATH (/usr/local/bin/crc on macOS and Linux).

    2. To verify that the host is ready to run OpenShift Local, in a terminal, run this command and verify the output has no errors:

      $ crc setup --check-only

      Sample output:

      INFO Using bundle path <bundle_path>
      INFO Checking if running as non-root
      INFO Checking if running inside WSL2
      INFO Checking if crc-admin-helper executable is cached
      crc-admin-helper executable is not cached

    3. To verify the configured preset, in a terminal, run:

      $ crc config get preset
    - + \ No newline at end of file diff --git a/docs/troubleshooting/troubleshooting-podman-on-linux.html b/docs/troubleshooting/troubleshooting-podman-on-linux.html index aeb62468d61..81f20a4ba81 100644 --- a/docs/troubleshooting/troubleshooting-podman-on-linux.html +++ b/docs/troubleshooting/troubleshooting-podman-on-linux.html @@ -13,14 +13,14 @@ - +

    Troubleshooting Podman on Linux

    Podman Desktop does not manage native Podman​

    On Linux, Podman usually runs natively on the host. Podman might also run in a virtual machine.

    Podman Desktop does only connect to the native rootless podman connection.

    Podman Desktop does not manage podman native configuration or podman machine (create, configure, start, stop, delete).

    Podman Desktop might manage configuration relative to connections to registries and proxies.

    - + \ No newline at end of file diff --git a/docs/troubleshooting/troubleshooting-podman-on-macos.html b/docs/troubleshooting/troubleshooting-podman-on-macos.html index d0146e94f11..e5051af5bac 100644 --- a/docs/troubleshooting/troubleshooting-podman-on-macos.html +++ b/docs/troubleshooting/troubleshooting-podman-on-macos.html @@ -13,7 +13,7 @@ - + @@ -23,7 +23,7 @@ or any similar error denoting that Podman Engine does not exist.

    Explanation​

    The Podman Installer and Homebrew use different locations to store the Podman Engine files in the file system. For example, Podman Installer installs Podman Engine in the path /opt/podman whereas Homebrew uses the path /usr/local for macOS Intel, /opt/homebrew for Apple Silicon and /home/linuxbrew/.linuxbrew for Linux.

    Solution​

    To check where exactly is your Podman Engine installed, run the command-

    which podman

    This returns the path where the Podman Engine would be installed. This would help determine further action.

    For example, if you’re looking to completely uninstall Podman Engine from your system for a fresh installation, running which podman returns the exact path where Podman still exists. This could be the path where Podman Installer stores Podman Engine, such as /opt/podman. Once you know the path, run:

    sudo rm -rf /opt/podman

    Or

    sudo rm -rf path-where-podman-exists

    Here, you would replace path-where-podman-exists with the output of which podman.

    You can now proceed for a fresh installation of Podman Desktop

    Podman machine on Apple Silicon​

    Issue​

    If you are using an Apple Silicon and brew, you might encounter the following error when starting Podman from Podman Desktop

    Error: qemu exited unexpectedly with exit code 1, stderr: qemu-system-x86_64: invalid accelerator hvf
    qemu-system-x86_64: falling back to tcg
    qemu-system-x86_64: unable to find CPU model 'host'

    Explanation​

    Podman machine is running as a x86_64 process and it could be due to a dual install of homebrew: one for x86_64 and one for arm64.

    Solution​

    You can

    1. Uninstall Podman machine on your x86_64 brew install (for example from a terminal running under rosetta) brew uninstall podman
    2. or uninstall brew x86_64 as most brew receipe have now arm64 support: follow these instructions from a terminal running under rosetta

    Then run a terminal in native mode (default) and install Podman machine brew install podman

    Finally clean the Podman machine VMs that had been previously created, and create new ones.

    $ podman machine rm podman-machine-default
    $ podman machine init

    You should be a happy camper from here.

    Recovering from a failed start​

    After a failed start, the Podman machine might be unable to start because a QEMU process is still running and the PID file is in use.

    Workaround​

    1. Kill the remaining QEMU process and stop the Podman machine:

      $ ps -edf | grep qemu-system | grep -v grep | awk '{print $2}' | xargs -I{} kill -9 {}; podman machine stop

    2. Start the Podman machine.

    Solution​

    Use Podman 4.6.1 or greater.

    Podman machine not starting with QEMU 8.1.0 from brew​

    When you installed Podman and QEMU with brew, and QEMU version is 8.1.0, Podman machine might fail to start with an error such as: Error: qemu exited unexpectedly with exit code -1, stderr: qemu-system-x86_64: Error: HV_DENIED

    Solution​

    Workaround​

    Keep your brew-based installation and apply one of these workarounds:

    • Rollback the QEMU brew package to v8.0.3.

      $ brew uninstall qemu
      $ curl -OSL https://raw.githubusercontent.com/Homebrew/homebrew-core/dc0669eca9479e9eeb495397ba3a7480aaa45c2e/Formula/qemu.rb
      $ brew install ./qemu.rb

    • Alternatively, sign the QEMU brew binary locally:

      $ cat >entitlements.xml <<EOF
      <?xml version="1.0" encoding="UTF-8"?>
      <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
      <plist version="1.0">
      <dict>
        <key>com.apple.security.hypervisor</key>
        <true/>
      </dict>
      </plist>
      EOF
      $ codesign --sign - --entitlements entitlements.xml --force /usr/local/bin/qemu-system-$(uname -m | sed -e s/arm64/aarch64/)

    Additional resources​

    - + \ No newline at end of file diff --git a/docs/troubleshooting/troubleshooting-podman-on-windows.html b/docs/troubleshooting/troubleshooting-podman-on-windows.html index fd98fb705f8..5c46b5239ae 100644 --- a/docs/troubleshooting/troubleshooting-podman-on-windows.html +++ b/docs/troubleshooting/troubleshooting-podman-on-windows.html @@ -13,14 +13,14 @@ - +

    Troubleshooting Podman on Windows

    You can find here troubleshooting help for issues specific to Windows.

    Deleting a corrupted Podman Machine​

    Issue​

    1. You are not able to stop your Podman Machine.

      $podman machine stop

    2. The Logs contain this error:

      Error: Error stopping sysd: exit status 1

    Workaround​

    1. To display the active Windows Subsystem for Linux (WSL) distribution list: in the terminal, run:

      $ wsl --list

    2. The command returns the list of active WSL distributions. Identify your Podman Machine in the list, such as podman-machine-default.

    3. To stop, and uninstall your Podman Machine: in the terminal, replace podman-machine-default by your Podman machine name, and run:

      $ wsl --unregister podman-machine-default

    Additional resources​

    The terminal session attaches to Podman Desktop when launching it from the command line​

    Issue​

    1. When you start Podman Desktop from the command line in Windows the terminal session attaches to it.
    2. When you quit the terminal, it kills Podman Desktop.

    Workaround​

    • Set the environment variable ELECTRON_NO_ATTACH_CONSOLE to true before launching Podman Desktop.

    When the host is behind a VPN, Podman cannot access network resources​

    When the host is behind a VPN, Podman might fail to access network resources, and display errors such as Temporary failure in name resolution.

    Solution​

    See Accessing resources behind a VPN with Podman on Windows.

    Older WSL versions might lead to networking issues​

    Older versions of WSL might cause networking issues, such as the Get-NetTCPConnection error, indicating that the WSL loopback forwarding facility is not functioning correctly. Recent versions of WSL do not have this issue Recent WSL versions do not have the issue.

    Solution​

    1. Update Windows to either the 21H1, 21H2, or 22H2 version of Windows 10, or to the 21H1 version of Windows 11, or greater.

    2. Update WSL:

      wsl --update

    3. Optionally, delete your Podman machine, and create a new one.

    - + \ No newline at end of file diff --git a/docs/troubleshooting/troubleshooting-podman.html b/docs/troubleshooting/troubleshooting-podman.html index c1a4b1da068..443956a791c 100644 --- a/docs/troubleshooting/troubleshooting-podman.html +++ b/docs/troubleshooting/troubleshooting-podman.html @@ -13,7 +13,7 @@ - + @@ -23,7 +23,7 @@ After each step, quit and restart Podman Desktop to ensure that it can detect yo img

    Solution​

    1. Stop and restart Podman Desktop.

    2. In Podman Desktop, restart the Podman machine.

    3. In a terminal, restart the Podman machine:

      $ podman machine stop
      $ podman machine start

    4. If the previous step did not work for you, delete your Podman machine, and create a new one:

      $ podman machine rm
      $ podman machine init

    5. If the previous steps did not work for you, delete your Podman configuration files, and create a new Podman machine:

      $ rm -rf ~/.local/share/containers/podman
      $ rm -rf ~/.config/containers/
      $ podman machine init

    Podman Desktop is failing to display the images or containers from a rootful Podman machine​

    The rootful configuration for a Podman machine depends on the Podman machine default connection. The default connection can be modified by external events, or when creating a new Podman machine. Podman Desktop might then reconnect in rootless mode, and fail to display the images or containers.

    Workaround​

    1. Verify that the Podman default connection is the rootful connection to your Podman machine:

      $ podman system connection ls

      The default connection has true at the end of the line.

      The rootful connection has a -root name suffix, and a ssh://root@ URI prefix.

      Example default rootful connection:

      Name                        URI                                                         Identity                                      Default
      podman-machine-default      ssh://user@127.0.0.1:54826/run/user/1000/podman/podman.sock c:\Users\username\.ssh\podman-machine-default false
      podman-machine-default-root ssh://root@127.0.0.1:54826/run/podman/podman.sock           c:\Users\username\.ssh\podman-machine-default true

      Example default rootless connection:

      Name                        URI                                                         Identity                                      Default
      podman-machine-default      ssh://user@127.0.0.1:54826/run/user/1000/podman/podman.sock c:\Users\username\.ssh\podman-machine-default true
      podman-machine-default-root ssh://root@127.0.0.1:54826/run/podman/podman.sock           c:\Users\username\.ssh\podman-machine-default false

      Continue with the next steps only if the default connection is not the rootful connection to your Podman machine.

    2. Set the Podman machine in rootful mode:

      $ podman machine set --rootful

    3. Restart the Podman machine:

      $ podman machine stop
      $ podman machine start

    4. Verify that Podman default connection points to the rootful connection:

      $ podman system connection ls

      Continue with the next steps only if the default connection is not the rootful connection to your Podman machine.

    5. Set the Podman machine, such as podman-machine-default in rootful mode:

      $ podman system connection default podman-machine-default-root

    6. Restart the Podman machine:

      $ podman machine stop
      $ podman machine start

    Verification​

    1. The Podman default connection is the rootful connection to your Podman machine:

      $ podman system connection ls

    Warning about Docker compatibility mode​

    Issue​

    When running the Podman provider, a warning shows regarding Docker compatibility mode on the dashboard:

    ⚠️ Docker Socket Compatibility: Podman is not emulating the default Docker socket path: '/var/run/docker.sock'. Docker-specific tools may not work. See troubleshooting page on podman-desktop.io for more information.

    This might appear when either:

    • The Docker socket is not mounted correctly.
    • Docker Desktop is also being ran at the same time.

    Solution​

    1. Stop Docker Desktop (if installed).

    2. On macOS, Run the podman-mac-helper binary:

      $ sudo podman-mac-helper install

    3. Restart the Podman machine to recreate and activate the default Docker socket path.

    Note: If Docker Desktop is started again, it will automatically re-alias the default Docker socket location and the Podman compatibilty warning will re-appear.

    - + \ No newline at end of file diff --git a/docs/working-with-containers.html b/docs/working-with-containers.html index c8d6b4b21bc..2f8b37d7f19 100644 --- a/docs/working-with-containers.html +++ b/docs/working-with-containers.html @@ -13,13 +13,13 @@ - +
    - + \ No newline at end of file diff --git a/docs/working-with-containers/creating-a-pod.html b/docs/working-with-containers/creating-a-pod.html index 76d81f8d143..43334d996e7 100644 --- a/docs/working-with-containers/creating-a-pod.html +++ b/docs/working-with-containers/creating-a-pod.html @@ -13,13 +13,13 @@ - +

    Creating a pod from selected containers

    With Podman Desktop, you can create a pod from your selected containers, and run the pod on the Podman container engine.

    Consider running containers in a pod to:

    1. Expose your frontend application to the public network.
    2. Protect your database container in a private network.

    Prerequisites​

    • You are using the Podman container engine.
    • Your containers, such as database and frontend, running or stopped, are available on the Containers page.
    • The frontend container is configured to access the service exposed by the database container on localhost, such as localhost:6379.

    Procedure​

    1. Go to Containers.
    2. Click the checkbox in the container line for your containers, such as database and frontend.
    3. Click .
    4. In the Copy containers to a pod screen:
      1. Name of the pod: enter your pod name, such as my-pod.
      2. All selected ports will be exposed:
        1. Select frontend.
        2. Clear database.
    5. Click Create Pod.

    Verification​

    1. Go to Pods.
    2. Click your pod, such as my-pod.
    3. Go to Logs: see the combined logs from the two containers.
    4. Go to Summary: see the containers.
    5. Click frontend-podified.
    6. Click .
    7. Your browser opens the service exposed by your frontend-podified container.
    8. Go to Containers: see the running containers.
    - + \ No newline at end of file diff --git a/docs/working-with-containers/images.html b/docs/working-with-containers/images.html index b03010c497b..af746bae0fd 100644 --- a/docs/working-with-containers/images.html +++ b/docs/working-with-containers/images.html @@ -13,13 +13,13 @@ - +
    - + \ No newline at end of file diff --git a/docs/working-with-containers/images/building-an-image.html b/docs/working-with-containers/images/building-an-image.html index 150f78d7178..4331c12cdb9 100644 --- a/docs/working-with-containers/images/building-an-image.html +++ b/docs/working-with-containers/images/building-an-image.html @@ -13,13 +13,13 @@ - +

    Building an image on your container engine

    With Podman Desktop, you can build an image from a Containerfile on your container engine.

    Prerequisites​

    • Your Containerfile: Containerfile or Dockerfile.

    Procedure​

    1. Go to Images.
    2. Click Build an image.
    3. On the Build Image from Containerfile screen
      1. Containerfile path: select the Containerfile or Dockerfile to build.
      2. Image Name: enter your image name, such as my-image. If you want to push the image to a registry, use the fully qualified image name that your registry requires, such as quay.io/my-repository/my-image, ghcr.io/my-repository/my-image, or docker.io/my-repository/my-image.
      3. Click Build.
      4. Click Done.

    Verification​

    1. Go to Images.
    2. : Enter your image name, such as quay.io/my-repository/my-image, ghcr.io/my-repository/my-image, or docker.io/my-repository/my-image.
    3. Click the line with your image name.
    4. Go to History.
      1. Click the content area to activate it.
      2. Enter Ctrl + F on Windows and Linux, or ⌘ + F on macOS to start searching in the content.
    5. Go to Inspect.
      1. Click the content area to activate it.
      2. Enter Ctrl + F on Windows and Linux, or ⌘ + F on macOS to start searching in the content.
    6. Click ..
      1. You see the Create a container screen.
    - + \ No newline at end of file diff --git a/docs/working-with-containers/images/pulling-an-image.html b/docs/working-with-containers/images/pulling-an-image.html index a678bc929e6..5aac64d5a5e 100644 --- a/docs/working-with-containers/images/pulling-an-image.html +++ b/docs/working-with-containers/images/pulling-an-image.html @@ -13,13 +13,13 @@ - +

    Pulling an image to your container engine

    With Podman Desktop, you can pull an image from a registry, to your container engine.

    Prerequisites​

    • The image is available in a registry.
    • If the registry or the image are not publicly available, you configured access to the registry on Podman Desktop in Settings > Registries.

    Procedure​

    1. Go to Images.
    2. Click Pull an image.
    3. On the Image to Pull screen:
      1. Image to pull: enter the image name, such as quay.io/podman/hello. Prefer the fully qualified image name that specifies the registry, to the short name that might lead to registry resolution mistakes.
      2. Click Pull image.
    4. Click Done.

    Verification​

    1. Go to Images.
    2. Click the image name you pulled, such as quay.io/podman/hello. Podman Desktop always displays the fully qualified image name.
    3. Go to Summary.
    4. Go to History.
      1. Click the output area.
      2. Enter Ctrl + F on Windows and Linux, or ⌘ + F on macOS to start searching in the content.
    5. Go to Inspect.
      1. Click the output area.
      2. Enter Ctrl + F on Windows and Linux, or ⌘ + F on macOS to start searching in the content.
    - + \ No newline at end of file diff --git a/docs/working-with-containers/images/pushing-an-image-to-a-registry.html b/docs/working-with-containers/images/pushing-an-image-to-a-registry.html index 51a314b8369..a8160916247 100644 --- a/docs/working-with-containers/images/pushing-an-image-to-a-registry.html +++ b/docs/working-with-containers/images/pushing-an-image-to-a-registry.html @@ -13,14 +13,14 @@ - +

    Pushing an image to a registry

    With Podman Desktop, you can push an image to registries.

    Prerequisites​

    • You have configured your registry Settings > Registries.
    • You have built an image, which name is the fully qualified name required for your registry, such as quay.io/my-repository/my-image, ghcr.io/my-repository/my-image, or docker.io/my-repository/my-image. Ensure that the image name includes the registry where to publish the image. To publish on quay.io/repository the image my-image, the FQN image name should be quay.io/repository/my-image.

    Procedure​

    1. Go to Images.
    2. On your image line, click > Push Image.
    3. Select the Image tag for your registry.
    4. Click Push Image.
    5. Click Done.

    Verification​

    1. Go to your container registry.
    2. Find your image.
    - + \ No newline at end of file diff --git a/docs/working-with-containers/registries.html b/docs/working-with-containers/registries.html index 81e38619e4f..32ac77472be 100644 --- a/docs/working-with-containers/registries.html +++ b/docs/working-with-containers/registries.html @@ -13,13 +13,13 @@ - +
    - + \ No newline at end of file diff --git a/docs/working-with-containers/registries/authenticating-to-a-preconfigured-registry.html b/docs/working-with-containers/registries/authenticating-to-a-preconfigured-registry.html index e3f29febf5d..3109c3987f2 100644 --- a/docs/working-with-containers/registries/authenticating-to-a-preconfigured-registry.html +++ b/docs/working-with-containers/registries/authenticating-to-a-preconfigured-registry.html @@ -13,13 +13,13 @@ - +

    Authenticating to a pre-configured registry

    With Podman Desktop, you can authenticate to a set of pre-configured registries:

    • Red Hat Quay
    • Docker Hub
    • GitHub
    • Google Container registry

    Prerequisites​

    • You have credentials on a pre-configured image registry.

    Procedure​

    1. Go to Settings > Registries.

    2. On your registry line, click Configure.

      1. User name: Enter your user name.
      2. Password: Enter your password or OAuth secret.

    Verification​

    1. Go to Images.
    2. You can pull a private image from the registry.
    3. You can push an image to the registry:
      1. Build an image the fully qualified name required for your registry, such as quay.io/my-repository/my-image, ghcr.io/my-repository/my-image, or docker.io/my-repository/my-image.
      2. On your image line, click .
      3. The contextual menu has a Push Image entry.
    - + \ No newline at end of file diff --git a/docs/working-with-containers/registries/insecure-registry.html b/docs/working-with-containers/registries/insecure-registry.html index d27845707bf..3ea8b3a4d32 100644 --- a/docs/working-with-containers/registries/insecure-registry.html +++ b/docs/working-with-containers/registries/insecure-registry.html @@ -13,13 +13,13 @@ - +

    Adding an Insecure Registry to Podman Desktop

    In this guide, you will learn how to add an insecure registry to Podman Desktop. An insecure registry allows you to pull and push container images either over an unencrypted HTTP connection, or a HTTPS connection with a self-signed unverified certificate. Please note that using an insecure registry can expose your data to security risks, so it's recommended to use secure connections with a verifiable certificate whenever possible.

    Prerequisites​

    • Podman installed and running (VM if on macOS or Windows).

    Procedure​

    1. Add your insecure registry within Settings > Registries.

    2. Click "Yes" to the insecure registry warning.

    Podman Desktop Registry Warning

    1. SSH into the Podman Machine to edit registries.conf.
    $ podman machine ssh [optional-machine-name]
    1. Open registries.conf.
    $ sudo vi /etc/containers/registries.conf
    1. Add the insecure registry: Add a new [[registry]] section for the URL of the insecure registry you want to use. For example, if your insecure registry is located at http://registry.example.com, add the following lines:
    [[registry]]
    location = registry.example.com
    insecure = true

    If you have multiple registries, you can add one [[registry]] block per registry.

    1. Save and exit the file.

    2. Restart Podman by the CLI or through Podman Desktop.

    $ podman machine stop
    $ podman machine start
    1. Pull or push container images: You can now use Podman Desktop to pull or push container images from/to the insecure registry you added.
    - + \ No newline at end of file diff --git a/docs/working-with-containers/starting-a-container.html b/docs/working-with-containers/starting-a-container.html index 026ba881f88..1c57e146054 100644 --- a/docs/working-with-containers/starting-a-container.html +++ b/docs/working-with-containers/starting-a-container.html @@ -13,14 +13,14 @@ - +

    Starting a container on your container engine

    With Podman Desktop, you can start a container from an image on your container engine. You can interact with the running container by using the terminal in Podman Desktop, or by opening your browser to the exposed ports.

    Prerequisites​

    • The Images list has your image, such as quay.io/podman/hello.

    Procedure​

    1. Go to Images.
    2. On the line with your image name, such as quay.io/podman/hello, click .
    3. On the Create a container screen, review the configuration.
    4. Click Start Container.

    Verification​

    1. Go to Containers.
    2. : Enter your image name, such as quay.io/podman/hello, to find your running container.
    3. Click your running container name.
    4. To view logs:
      1. Go to Logs.
      2. Browse the content.
    5. To inspect the container:
      1. Go to Inspect.
      2. Click the content area to activate it.
      3. Enter Ctrl + F on Windows and Linux, or ⌘ + F on macOS to start searching in the content.
    6. To generate Kubernetes YAML, when your container engine is Podman:
      1. Go to Kube.
      2. Click the content area to activate it.
      3. Enter Ctrl + F on Windows and Linux, or ⌘ + F on macOS to start searching in the content.
      4. Copy the content to a YAML file.
      5. Later, you can reuse this file to start a container in Podman from Kubernetes YAML, or to start a pod in Kubernetes.
    7. To interact with the container terminal:
      1. Go to Terminal.
      2. Click the content area to activate the terminal.
      3. Enter your commands.
    8. To interact with the exposed ports:
      1. Click .
      2. Your browser opens a page to the first exposed port on localhost.
    9. To deploy to your current Kubernetes context, when you container engine is Podman:
      1. Click .
      2. Review the Deploy generated pod to Kubernetes screen.
      3. Click .
    10. To stop the container:
    11. Click .
    12. To delete the container:
    13. Click .
    - + \ No newline at end of file diff --git a/docs/working-with-containers/switching-podman-machine-default-connection.html b/docs/working-with-containers/switching-podman-machine-default-connection.html index 056e49d5a40..15d65775d8c 100644 --- a/docs/working-with-containers/switching-podman-machine-default-connection.html +++ b/docs/working-with-containers/switching-podman-machine-default-connection.html @@ -13,13 +13,13 @@ - +

    Setting Podman machine default connection

    Each Podman machine exposes two connections:

    • rootless
    • rootful

    Podman has one default connection.

    Podman Desktop, and other tools, such as Kind, connect to the default connection.

    After an event that might have changed the default Podman machine connection, such as creating another Podman machine, consider verifying and setting the default connection.

    Procedure​

    1. List Podman machine connections, in a terminal:

      $ podman system connection ls

    2. Set the Podman machine default connection to your desired connection, such as podman-machine-default-root, in a terminal:

      $ podman system connection default podman-machine-default-root

    3. List Podman machine connections, to verify which is the default, in a terminal:

      $ podman system connection ls

    4. Restart the Podman machine that has the default connection:

      $ podman mahine stop
      $ podman machine start

    5. Refresh Podman Desktop connection to Podman: click the icon to open the Troubleshooting page, and click the Reconnect providers button.

    Verification​

    • Podman Desktop lists images, containers, and pods that are accessible via the desired Podman machine connection.
    - + \ No newline at end of file diff --git a/downloads.html b/downloads.html index 789ec704d53..896669d5af5 100644 --- a/downloads.html +++ b/downloads.html @@ -13,13 +13,13 @@ - +

    Downloads

    Windows

    Podman Desktop for Windows

    Download NowWindows installer x64, version
    Other Windows downloads:
    Installer:
    x64arm64
    Portable binary:
    x64arm64
    Installer for restricted environments:
    x64arm64
    Package Managers Guide

    Using winget? Install in one command:

    winget install -e --id RedHat.Podman-Desktop

    macOS

    Podman Desktop for macOS

    Download NowUniversal *.dmg, version
    Other macOS downloads:
    IntelArmDisk Image for restricted environments

    Using Brew? Install in one command:

    brew install podman-desktop

    Linux

    Podman Desktop for Linux

    Download NowLinux *.flatpak, version
    Other Linux downloads:
    AMD64 binary (tar.gz)

    Using Flathub ? Install in one command:

    flatpak install flathub io.podman_desktop.PodmanDesktop
    - + \ No newline at end of file diff --git a/downloads/linux.html b/downloads/linux.html index 9e52f464df6..1f281f77f8d 100644 --- a/downloads/linux.html +++ b/downloads/linux.html @@ -13,13 +13,13 @@ - +

    Linux Downloads

    Linux

    Podman Desktop for Linux

    Download NowLinux *.flatpak, version
    Other Linux downloads:
    AMD64 binary (tar.gz)

    Using Flathub ? Install in one command:

    flatpak install flathub io.podman_desktop.PodmanDesktop
    - + \ No newline at end of file diff --git a/downloads/macos.html b/downloads/macos.html index 32829c98d17..8e5aa8b8df5 100644 --- a/downloads/macos.html +++ b/downloads/macos.html @@ -13,13 +13,13 @@ - +

    macOS Downloads

    macOS

    Podman Desktop for macOS

    Download NowUniversal *.dmg, version
    Other macOS downloads:
    IntelArmDisk Image for restricted environments

    Using Brew? Install in one command:

    brew install podman-desktop

    - + \ No newline at end of file diff --git a/downloads/windows.html b/downloads/windows.html index 71b9554d0a2..3bf80dbad47 100644 --- a/downloads/windows.html +++ b/downloads/windows.html @@ -13,13 +13,13 @@ - +

    Windows Downloads

    Windows

    Podman Desktop for Windows

    Download NowWindows installer x64, version
    Other Windows downloads:
    Installer:
    x64arm64
    Portable binary:
    x64arm64
    Installer for restricted environments:
    x64arm64
    Package Managers Guide

    Using winget? Install in one command:

    winget install -e --id RedHat.Podman-Desktop
    - + \ No newline at end of file diff --git a/extend.html b/extend.html index fd4c9cf2ddc..02f8536557b 100644 --- a/extend.html +++ b/extend.html @@ -13,13 +13,13 @@ - +

    Extend capabilities with Docker Desktop extensions.

    Podman Desktop is able to use Docker Desktop UI plug-ins by adding a wrapper to intercept the API calls.

    By adding a Docker Desktop extension, you can extend the capabilities of Podman Desktop.

    Extend with Docker Desktop extensionsExtend with Docker Desktop extensionsReuse Docker Desktop extensionsReuse Docker Desktop extensions

    Extend capabilities with Podman Desktop plug-ins.

    Podman Desktop is using plug-ins under the hood to manage the different container engine.

    By adding a new plugin, you can extend the capabilities of Podman Desktop.

    For example plug a new container engine like Podman, Docker, or use Lima.

    Extensibility diagramExtensibility diagram

    Extensions are written in JavaScript/Typescript
    It consumes a TypeScript definition of the extension model.

    More extension points

    Several extension points exists in addition to adding a Provider connection.

    User interaction, dialogs, launching commands are among the possible ways to extend Podman Desktop

    - + \ No newline at end of file diff --git a/features.html b/features.html index 5add2728d2e..93fec7e75ee 100644 --- a/features.html +++ b/features.html @@ -13,13 +13,13 @@ - +

    Manage containers

    List, Search, Inspect, Connect, Run and Stop containers.

    Manage containersManage containers
    Pull image and manage registriesPull image and manage registries

    Build, Pull and Push images

    Build images from the tool.

    Pull and push images by managing registries.

    Run containers from these images

    Management from the tray icon

    Check status and start/stop container engines.

    Create new machine if needed as well as start or stop Podman machines directly from the tray icon.

    Quickly check activity status and stay updated without losing focus from other tasks.

    Manage Podman MachineManage Podman Machine
    Manage Podman MachineManage Podman Machine

    Manage Podman resources

    View allocated memory, CPU and storage.

    Create new machine if needed

    Create and start Pods with Podman

    Select containers to run as a Pod.

    Play Kubernetes YAML locally without Kubernetes.

    Generate Kubernetes YAML from Pods.

    Manage PodsManage Pods
    Pull image and manage registriesPull image and manage registries

    Import Docker Desktop extensions

    Specify OCI image of a Docker Desktop extension to import it.

    For example: security scanner or deploy to OpenShift extensions.

    - + \ No newline at end of file diff --git a/index.html b/index.html index 0ce1be9ee6b..e23e2c632ff 100644 --- a/index.html +++ b/index.html @@ -13,13 +13,13 @@ - +

    Containers and Kubernetes for application developers

    Podman Desktop is an open source graphical tool enabling you to seamlessly work with containers and Kubernetes from your local environment.

    Download Page
    Podman Desktop home page

    Available on Windows, Mac and Linux

    Use the same UI across different operating systems

    Windows

    exe or setup.exe

    macOS

    arm64, x64 or unified dmg

    Linux

    Flatpak or AMD64 binary (tar.gz)

    features

    Build, run and manage containers.

    Build

    Build images from Containerfile or Dockerfile

    Run

    Pull images from remote registries

    Start / Stop / Restart containers

    Inspect

    Get a terminal in your container

    Inspect logs

    Push

    Push images to OCI registries

    Deploy & Test images on Kubernetes

    Discover More

    features

    Work with Pods and Kubernetes

    Working with pods

    Create Pods from existing containers

    Create, start, inspect and manage pods

    Working with Kubernetes

    Play Kubernetes YAML directly with Podman Engine

    Generate Kubernetes YAML from pods

    Deploy to existing Kubernetes environments

    Running Kubernetes on your workstation with Kind and Podman

    Discover More

    Configure

    Multiple configuration options

    Registries

    Manage OCI registries. Add/edit/delete registries.

    Proxy

    Configure your proxy settings.

    Resources Utilization

    Configure CPU/Memory/Disk of Podman machines.

    Container Engines

    Handle multiple container engines at the same time: Podman, Docker.

    extensibility

    Bring new features with Podman Desktop plug-ins or Docker Desktop Extensions.

    • Container engines are plugged through extension points
    • JavaScript extensions can contribute new behaviour
    • Reuse existing extensions such as Trivy and OpenShift directly in Podman Desktop

    Current Podman Desktop plugins: Podman, Docker, Lima, Kubernetes, and OpenShift Local with the Podman preset.

    Reuse Docker Desktop extensionsReuse Docker Desktop extensions
    Learn More

    update

    Install and keep up to date Podman

    Install Podman and other dependencies directly from Podman Desktop if not yet installed.

    Check for updates and get notified about new changes.

    Available on Windows and macOS!

    enterprise

    Enterprise ready

    Match configuration options.

    Code signing

    Signed binaries for both macOS and Windows

    Proxy

    Configure proxy within the tool. Avoid any painful files to edit.

    Registries

    Manage OCI registries. Add/edit/delete registries.

    - + \ No newline at end of file diff --git a/search.html b/search.html index 2ca6bf73582..0b738aac54c 100644 --- a/search.html +++ b/search.html @@ -13,13 +13,13 @@ - +

    Search the documentation

    - + \ No newline at end of file