diff --git a/404.html b/404.html index ad0181b06f4..ec91674b1ae 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/d4bf7e47.8f46b4ce.js b/assets/js/d4bf7e47.8f46b4ce.js deleted file mode 100644 index d16d7d261a1..00000000000 --- a/assets/js/d4bf7e47.8f46b4ce.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkdocs=self.webpackChunkdocs||[]).push([[8989],{5318:(e,n,o)=>{o.d(n,{Zo:()=>m,kt:()=>c});var t=o(7378);function a(e,n,o){return n in e?Object.defineProperty(e,n,{value:o,enumerable:!0,configurable:!0,writable:!0}):e[n]=o,e}function r(e,n){var o=Object.keys(e);if(Object.getOwnPropertySymbols){var t=Object.getOwnPropertySymbols(e);n&&(t=t.filter((function(n){return Object.getOwnPropertyDescriptor(e,n).enumerable}))),o.push.apply(o,t)}return o}function i(e){for(var n=1;n=0||(a[o]=e[o]);return a}(e,n);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);for(t=0;t=0||Object.prototype.propertyIsEnumerable.call(e,o)&&(a[o]=e[o])}return a}var s=t.createContext({}),p=function(e){var n=t.useContext(s),o=n;return e&&(o="function"==typeof e?e(n):i(i({},n),e)),o},m=function(e){var n=p(e.components);return t.createElement(s.Provider,{value:n},e.children)},u={inlineCode:"code",wrapper:function(e){var n=e.children;return t.createElement(t.Fragment,{},n)}},d=t.forwardRef((function(e,n){var o=e.components,a=e.mdxType,r=e.originalType,s=e.parentName,m=l(e,["components","mdxType","originalType","parentName"]),d=p(o),c=a,h=d["".concat(s,".").concat(c)]||d[c]||u[c]||r;return o?t.createElement(h,i(i({ref:n},m),{},{components:o})):t.createElement(h,i({ref:n},m))}));function c(e,n){var o=arguments,a=n&&n.mdxType;if("string"==typeof e||a){var r=o.length,i=new Array(r);i[0]=d;var l={};for(var s in n)hasOwnProperty.call(n,s)&&(l[s]=n[s]);l.originalType=e,l.mdxType="string"==typeof e?e:a,i[1]=l;for(var p=2;p{o.r(n),o.d(n,{assets:()=>s,contentTitle:()=>i,default:()=>u,frontMatter:()=>r,metadata:()=>l,toc:()=>p});var t=o(5773),a=(o(7378),o(5318));const r={sidebar_position:30},i="Troubleshooting Podman on macOS",l={unversionedId:"troubleshooting/troubleshooting-podman-on-macos",id:"troubleshooting/troubleshooting-podman-on-macos",title:"Troubleshooting Podman on macOS",description:"Unable to set custom binary path for Podman on macOS",source:"@site/docs/troubleshooting/troubleshooting-podman-on-macos.md",sourceDirName:"troubleshooting",slug:"/troubleshooting/troubleshooting-podman-on-macos",permalink:"/docs/troubleshooting/troubleshooting-podman-on-macos",draft:!1,editUrl:"https://github.com/containers/podman-desktop/tree/main/website/docs/troubleshooting/troubleshooting-podman-on-macos.md",tags:[],version:"current",sidebarPosition:30,frontMatter:{sidebar_position:30},sidebar:"mySidebar",previous:{title:"Troubleshooting Podman on Windows",permalink:"/docs/troubleshooting/troubleshooting-podman-on-windows"},next:{title:"Troubleshooting Podman on Linux",permalink:"/docs/troubleshooting/troubleshooting-podman-on-linux"}},s={},p=[{value:"Unable to set custom binary path for Podman on macOS",id:"unable-to-set-custom-binary-path-for-podman-on-macos",level:2},{value:"Issue",id:"issue",level:4},{value:"Solution",id:"solution",level:4},{value:"Unable to locate Podman Engine",id:"unable-to-locate-podman-engine",level:2},{value:"Issue",id:"issue-1",level:4},{value:"Explanation",id:"explanation",level:4},{value:"Solution",id:"solution-1",level:4},{value:"Podman machine on Apple Silicon",id:"podman-machine-on-apple-silicon",level:2},{value:"Issue",id:"issue-2",level:4},{value:"Explanation",id:"explanation-1",level:4},{value:"Solution",id:"solution-2",level:4}],m={toc:p};function u(e){let{components:n,...o}=e;return(0,a.kt)("wrapper",(0,t.Z)({},m,o,{components:n,mdxType:"MDXLayout"}),(0,a.kt)("h1",{id:"troubleshooting-podman-on-macos"},"Troubleshooting Podman on macOS"),(0,a.kt)("h2",{id:"unable-to-set-custom-binary-path-for-podman-on-macos"},"Unable to set custom binary path for Podman on macOS"),(0,a.kt)("h4",{id:"issue"},"Issue"),(0,a.kt)("p",null,"When setting a custom binary path (under Preferences -> Custom binary path), Podman is unable to find ",(0,a.kt)("inlineCode",{parentName:"p"},"gvproxy")," and ",(0,a.kt)("inlineCode",{parentName:"p"},"podman-mac-helper"),":"),(0,a.kt)("pre",null,(0,a.kt)("code",{parentName:"pre",className:"language-sh"},'Error: unable to start host networking: "could not find \\"gvproxy\\" in one of [/usr/local/opt/podman/libexec /opt/homebrew/bin /opt/homebrew/opt/podman/libexec /usr/local/bin /usr/local/libexec/podman /usr/local/lib/podman /usr/libexec/podman /usr/lib/podman $BINDIR/../libexec/podman]. To resolve this error, set the helper_binaries_dir key in the `[engine]` section of containers.conf to the directory containing your helper binaries."\n')),(0,a.kt)("h4",{id:"solution"},"Solution"),(0,a.kt)("ol",null,(0,a.kt)("li",{parentName:"ol"},"Download ",(0,a.kt)("inlineCode",{parentName:"li"},"gvproxy")," from the ",(0,a.kt)("a",{parentName:"li",href:"https://github.com/containers/gvisor-tap-vsock/releases"},"gvisor-tap-vsock release page"),"."),(0,a.kt)("li",{parentName:"ol"},"Build the ",(0,a.kt)("inlineCode",{parentName:"li"},"podman-mac-helper")," from the source code on the ",(0,a.kt)("a",{parentName:"li",href:"https://github.com/containers/podman/tree/main/cmd/podman-mac-helper"},"Podman GitHub page"),"."),(0,a.kt)("li",{parentName:"ol"},"Add the ",(0,a.kt)("inlineCode",{parentName:"li"},"helpers_binaries_dir")," entry to ",(0,a.kt)("inlineCode",{parentName:"li"},"~/.config/containers/conf"),":")),(0,a.kt)("pre",null,(0,a.kt)("code",{parentName:"pre",className:"language-sh"},'[containers]\n\nhelper_binaries_dir=["/Users/user/example_directory"]\n')),(0,a.kt)("p",null,(0,a.kt)("strong",{parentName:"p"},"NOTE"),": A pre-built binary will be added to the Podman release page so you do not have to build ",(0,a.kt)("inlineCode",{parentName:"p"},"podman-mac-helper"),". An ",(0,a.kt)("a",{parentName:"p",href:"https://github.com/containers/podman/issues/16746"},"issue is open for this"),"."),(0,a.kt)("h2",{id:"unable-to-locate-podman-engine"},"Unable to locate Podman Engine"),(0,a.kt)("h4",{id:"issue-1"},"Issue"),(0,a.kt)("p",null,"Despite having Podman Engine installed, you might receive an error as follows -\n",(0,a.kt)("inlineCode",{parentName:"p"},"Error: No such keg: /usr/local/Cellar/podman"),"\nor any similar error denoting that Podman Engine does not exist."),(0,a.kt)("h4",{id:"explanation"},"Explanation"),(0,a.kt)("p",null,"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 ",(0,a.kt)("inlineCode",{parentName:"p"},"/opt/podman")," whereas Homebrew uses the path ",(0,a.kt)("inlineCode",{parentName:"p"},"/usr/local")," for macOS Intel, ",(0,a.kt)("inlineCode",{parentName:"p"},"/opt/homebrew")," for Apple Silicon and ",(0,a.kt)("inlineCode",{parentName:"p"},"/home/linuxbrew/.linuxbrew")," for Linux."),(0,a.kt)("h4",{id:"solution-1"},"Solution"),(0,a.kt)("p",null,"To check where exactly is your Podman Engine installed, run the command-"),(0,a.kt)("pre",null,(0,a.kt)("code",{parentName:"pre",className:"language-sh"},"which podman\n")),(0,a.kt)("p",null,"This returns the path where the Podman Engine would be installed. This would help determine further action."),(0,a.kt)("p",null,"For example, if you\u2019re looking to completely uninstall Podman Engine from your system for a fresh installation, running ",(0,a.kt)("inlineCode",{parentName:"p"},"which podman")," returns the exact path where Podman still exists. This could be the path where Podman Installer stores Podman Engine, such as ",(0,a.kt)("inlineCode",{parentName:"p"},"/opt/podman"),". Once you know the path, run:"),(0,a.kt)("pre",null,(0,a.kt)("code",{parentName:"pre",className:"language-sh"},"sudo rm -rf /opt/podman\n")),(0,a.kt)("p",null,"Or"),(0,a.kt)("pre",null,(0,a.kt)("code",{parentName:"pre",className:"language-sh"},"sudo rm -rf path-where-podman-exists\n")),(0,a.kt)("p",null,"Here, you would replace ",(0,a.kt)("inlineCode",{parentName:"p"},"path-where-podman-exists")," with the output of ",(0,a.kt)("inlineCode",{parentName:"p"},"which podman"),"."),(0,a.kt)("p",null,"You can now proceed for a fresh installation of Podman Desktop"),(0,a.kt)("h2",{id:"podman-machine-on-apple-silicon"},"Podman machine on Apple Silicon"),(0,a.kt)("h4",{id:"issue-2"},"Issue"),(0,a.kt)("p",null,"If you are using an Apple Silicon and brew, you might encounter the following error when starting Podman from Podman Desktop"),(0,a.kt)("pre",null,(0,a.kt)("code",{parentName:"pre",className:"language-shell-session"},"Error: qemu exited unexpectedly with exit code 1, stderr: qemu-system-x86_64: invalid accelerator hvf\nqemu-system-x86_64: falling back to tcg\nqemu-system-x86_64: unable to find CPU model 'host'\n")),(0,a.kt)("h4",{id:"explanation-1"},"Explanation"),(0,a.kt)("p",null,"Podman machine is running as a ",(0,a.kt)("inlineCode",{parentName:"p"},"x86_64")," process and it could be due to a dual install of homebrew: one for ",(0,a.kt)("inlineCode",{parentName:"p"},"x86_64")," and one for ",(0,a.kt)("inlineCode",{parentName:"p"},"arm64"),"."),(0,a.kt)("h4",{id:"solution-2"},"Solution"),(0,a.kt)("p",null,"You can"),(0,a.kt)("ol",null,(0,a.kt)("li",{parentName:"ol"},"Uninstall Podman machine on your ",(0,a.kt)("inlineCode",{parentName:"li"},"x86_64")," brew install (for example from a terminal running under rosetta) ",(0,a.kt)("inlineCode",{parentName:"li"},"brew uninstall podman-machine")),(0,a.kt)("li",{parentName:"ol"},"or uninstall brew ",(0,a.kt)("inlineCode",{parentName:"li"},"x86_64")," as most brew receipe have now arm64 support: follow ",(0,a.kt)("a",{parentName:"li",href:"https://github.com/homebrew/install#uninstall-homebrew"},"these instructions")," from a terminal running under rosetta")),(0,a.kt)("p",null,"Then run a terminal in native mode (default) and install Podman machine ",(0,a.kt)("inlineCode",{parentName:"p"},"brew install podman-machine")),(0,a.kt)("p",null,"Finally clean the Podman machine VMs that had been previously created, and create new ones."),(0,a.kt)("pre",null,(0,a.kt)("code",{parentName:"pre",className:"language-shell-session"},"$ podman machine rm podman-machine-default\n$ podman machine init\n")),(0,a.kt)("p",null,"You should be a happy camper from here."))}u.isMDXComponent=!0}}]); \ No newline at end of file diff --git a/assets/js/d4bf7e47.eb3d4296.js b/assets/js/d4bf7e47.eb3d4296.js new file mode 100644 index 00000000000..b50ca994070 --- /dev/null +++ b/assets/js/d4bf7e47.eb3d4296.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkdocs=self.webpackChunkdocs||[]).push([[8989],{5318:(e,n,o)=>{o.d(n,{Zo:()=>m,kt:()=>c});var t=o(7378);function a(e,n,o){return n in e?Object.defineProperty(e,n,{value:o,enumerable:!0,configurable:!0,writable:!0}):e[n]=o,e}function r(e,n){var o=Object.keys(e);if(Object.getOwnPropertySymbols){var t=Object.getOwnPropertySymbols(e);n&&(t=t.filter((function(n){return Object.getOwnPropertyDescriptor(e,n).enumerable}))),o.push.apply(o,t)}return o}function l(e){for(var n=1;n=0||(a[o]=e[o]);return a}(e,n);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);for(t=0;t=0||Object.prototype.propertyIsEnumerable.call(e,o)&&(a[o]=e[o])}return a}var s=t.createContext({}),p=function(e){var n=t.useContext(s),o=n;return e&&(o="function"==typeof e?e(n):l(l({},n),e)),o},m=function(e){var n=p(e.components);return t.createElement(s.Provider,{value:n},e.children)},u={inlineCode:"code",wrapper:function(e){var n=e.children;return t.createElement(t.Fragment,{},n)}},d=t.forwardRef((function(e,n){var o=e.components,a=e.mdxType,r=e.originalType,s=e.parentName,m=i(e,["components","mdxType","originalType","parentName"]),d=p(o),c=a,h=d["".concat(s,".").concat(c)]||d[c]||u[c]||r;return o?t.createElement(h,l(l({ref:n},m),{},{components:o})):t.createElement(h,l({ref:n},m))}));function c(e,n){var o=arguments,a=n&&n.mdxType;if("string"==typeof e||a){var r=o.length,l=new Array(r);l[0]=d;var i={};for(var s in n)hasOwnProperty.call(n,s)&&(i[s]=n[s]);i.originalType=e,i.mdxType="string"==typeof e?e:a,l[1]=i;for(var p=2;p{o.r(n),o.d(n,{assets:()=>s,contentTitle:()=>l,default:()=>u,frontMatter:()=>r,metadata:()=>i,toc:()=>p});var t=o(5773),a=(o(7378),o(5318));const r={sidebar_position:30},l="Troubleshooting Podman on macOS",i={unversionedId:"troubleshooting/troubleshooting-podman-on-macos",id:"troubleshooting/troubleshooting-podman-on-macos",title:"Troubleshooting Podman on macOS",description:"Unable to set custom binary path for Podman on macOS",source:"@site/docs/troubleshooting/troubleshooting-podman-on-macos.md",sourceDirName:"troubleshooting",slug:"/troubleshooting/troubleshooting-podman-on-macos",permalink:"/docs/troubleshooting/troubleshooting-podman-on-macos",draft:!1,editUrl:"https://github.com/containers/podman-desktop/tree/main/website/docs/troubleshooting/troubleshooting-podman-on-macos.md",tags:[],version:"current",sidebarPosition:30,frontMatter:{sidebar_position:30},sidebar:"mySidebar",previous:{title:"Troubleshooting Podman on Windows",permalink:"/docs/troubleshooting/troubleshooting-podman-on-windows"},next:{title:"Troubleshooting Podman on Linux",permalink:"/docs/troubleshooting/troubleshooting-podman-on-linux"}},s={},p=[{value:"Unable to set custom binary path for Podman on macOS",id:"unable-to-set-custom-binary-path-for-podman-on-macos",level:2},{value:"Issue",id:"issue",level:4},{value:"Solution",id:"solution",level:4},{value:"Unable to locate Podman Engine",id:"unable-to-locate-podman-engine",level:2},{value:"Issue",id:"issue-1",level:4},{value:"Explanation",id:"explanation",level:4},{value:"Solution",id:"solution-1",level:4},{value:"Podman machine on Apple Silicon",id:"podman-machine-on-apple-silicon",level:2},{value:"Issue",id:"issue-2",level:4},{value:"Explanation",id:"explanation-1",level:4},{value:"Solution",id:"solution-2",level:4},{value:"Recovering from a failed start",id:"recovering-from-a-failed-start",level:2},{value:"Workaround",id:"workaround",level:4},{value:"Solution",id:"solution-3",level:4}],m={toc:p};function u(e){let{components:n,...o}=e;return(0,a.kt)("wrapper",(0,t.Z)({},m,o,{components:n,mdxType:"MDXLayout"}),(0,a.kt)("h1",{id:"troubleshooting-podman-on-macos"},"Troubleshooting Podman on macOS"),(0,a.kt)("h2",{id:"unable-to-set-custom-binary-path-for-podman-on-macos"},"Unable to set custom binary path for Podman on macOS"),(0,a.kt)("h4",{id:"issue"},"Issue"),(0,a.kt)("p",null,"When setting a custom binary path (under Preferences -> Custom binary path), Podman is unable to find ",(0,a.kt)("inlineCode",{parentName:"p"},"gvproxy")," and ",(0,a.kt)("inlineCode",{parentName:"p"},"podman-mac-helper"),":"),(0,a.kt)("pre",null,(0,a.kt)("code",{parentName:"pre",className:"language-sh"},'Error: unable to start host networking: "could not find \\"gvproxy\\" in one of [/usr/local/opt/podman/libexec /opt/homebrew/bin /opt/homebrew/opt/podman/libexec /usr/local/bin /usr/local/libexec/podman /usr/local/lib/podman /usr/libexec/podman /usr/lib/podman $BINDIR/../libexec/podman]. To resolve this error, set the helper_binaries_dir key in the `[engine]` section of containers.conf to the directory containing your helper binaries."\n')),(0,a.kt)("h4",{id:"solution"},"Solution"),(0,a.kt)("ol",null,(0,a.kt)("li",{parentName:"ol"},"Download ",(0,a.kt)("inlineCode",{parentName:"li"},"gvproxy")," from the ",(0,a.kt)("a",{parentName:"li",href:"https://github.com/containers/gvisor-tap-vsock/releases"},"gvisor-tap-vsock release page"),"."),(0,a.kt)("li",{parentName:"ol"},"Build the ",(0,a.kt)("inlineCode",{parentName:"li"},"podman-mac-helper")," from the source code on the ",(0,a.kt)("a",{parentName:"li",href:"https://github.com/containers/podman/tree/main/cmd/podman-mac-helper"},"Podman GitHub page"),"."),(0,a.kt)("li",{parentName:"ol"},"Add the ",(0,a.kt)("inlineCode",{parentName:"li"},"helpers_binaries_dir")," entry to ",(0,a.kt)("inlineCode",{parentName:"li"},"~/.config/containers/conf"),":")),(0,a.kt)("pre",null,(0,a.kt)("code",{parentName:"pre",className:"language-sh"},'[containers]\n\nhelper_binaries_dir=["/Users/user/example_directory"]\n')),(0,a.kt)("p",null,(0,a.kt)("strong",{parentName:"p"},"NOTE"),": A pre-built binary will be added to the Podman release page so you do not have to build ",(0,a.kt)("inlineCode",{parentName:"p"},"podman-mac-helper"),". An ",(0,a.kt)("a",{parentName:"p",href:"https://github.com/containers/podman/issues/16746"},"issue is open for this"),"."),(0,a.kt)("h2",{id:"unable-to-locate-podman-engine"},"Unable to locate Podman Engine"),(0,a.kt)("h4",{id:"issue-1"},"Issue"),(0,a.kt)("p",null,"Despite having Podman Engine installed, you might receive an error as follows -\n",(0,a.kt)("inlineCode",{parentName:"p"},"Error: No such keg: /usr/local/Cellar/podman"),"\nor any similar error denoting that Podman Engine does not exist."),(0,a.kt)("h4",{id:"explanation"},"Explanation"),(0,a.kt)("p",null,"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 ",(0,a.kt)("inlineCode",{parentName:"p"},"/opt/podman")," whereas Homebrew uses the path ",(0,a.kt)("inlineCode",{parentName:"p"},"/usr/local")," for macOS Intel, ",(0,a.kt)("inlineCode",{parentName:"p"},"/opt/homebrew")," for Apple Silicon and ",(0,a.kt)("inlineCode",{parentName:"p"},"/home/linuxbrew/.linuxbrew")," for Linux."),(0,a.kt)("h4",{id:"solution-1"},"Solution"),(0,a.kt)("p",null,"To check where exactly is your Podman Engine installed, run the command-"),(0,a.kt)("pre",null,(0,a.kt)("code",{parentName:"pre",className:"language-sh"},"which podman\n")),(0,a.kt)("p",null,"This returns the path where the Podman Engine would be installed. This would help determine further action."),(0,a.kt)("p",null,"For example, if you\u2019re looking to completely uninstall Podman Engine from your system for a fresh installation, running ",(0,a.kt)("inlineCode",{parentName:"p"},"which podman")," returns the exact path where Podman still exists. This could be the path where Podman Installer stores Podman Engine, such as ",(0,a.kt)("inlineCode",{parentName:"p"},"/opt/podman"),". Once you know the path, run:"),(0,a.kt)("pre",null,(0,a.kt)("code",{parentName:"pre",className:"language-sh"},"sudo rm -rf /opt/podman\n")),(0,a.kt)("p",null,"Or"),(0,a.kt)("pre",null,(0,a.kt)("code",{parentName:"pre",className:"language-sh"},"sudo rm -rf path-where-podman-exists\n")),(0,a.kt)("p",null,"Here, you would replace ",(0,a.kt)("inlineCode",{parentName:"p"},"path-where-podman-exists")," with the output of ",(0,a.kt)("inlineCode",{parentName:"p"},"which podman"),"."),(0,a.kt)("p",null,"You can now proceed for a fresh installation of Podman Desktop"),(0,a.kt)("h2",{id:"podman-machine-on-apple-silicon"},"Podman machine on Apple Silicon"),(0,a.kt)("h4",{id:"issue-2"},"Issue"),(0,a.kt)("p",null,"If you are using an Apple Silicon and brew, you might encounter the following error when starting Podman from Podman Desktop"),(0,a.kt)("pre",null,(0,a.kt)("code",{parentName:"pre",className:"language-shell-session"},"Error: qemu exited unexpectedly with exit code 1, stderr: qemu-system-x86_64: invalid accelerator hvf\nqemu-system-x86_64: falling back to tcg\nqemu-system-x86_64: unable to find CPU model 'host'\n")),(0,a.kt)("h4",{id:"explanation-1"},"Explanation"),(0,a.kt)("p",null,"Podman machine is running as a ",(0,a.kt)("inlineCode",{parentName:"p"},"x86_64")," process and it could be due to a dual install of homebrew: one for ",(0,a.kt)("inlineCode",{parentName:"p"},"x86_64")," and one for ",(0,a.kt)("inlineCode",{parentName:"p"},"arm64"),"."),(0,a.kt)("h4",{id:"solution-2"},"Solution"),(0,a.kt)("p",null,"You can"),(0,a.kt)("ol",null,(0,a.kt)("li",{parentName:"ol"},"Uninstall Podman machine on your ",(0,a.kt)("inlineCode",{parentName:"li"},"x86_64")," brew install (for example from a terminal running under rosetta) ",(0,a.kt)("inlineCode",{parentName:"li"},"brew uninstall podman-machine")),(0,a.kt)("li",{parentName:"ol"},"or uninstall brew ",(0,a.kt)("inlineCode",{parentName:"li"},"x86_64")," as most brew receipe have now arm64 support: follow ",(0,a.kt)("a",{parentName:"li",href:"https://github.com/homebrew/install#uninstall-homebrew"},"these instructions")," from a terminal running under rosetta")),(0,a.kt)("p",null,"Then run a terminal in native mode (default) and install Podman machine ",(0,a.kt)("inlineCode",{parentName:"p"},"brew install podman-machine")),(0,a.kt)("p",null,"Finally clean the Podman machine VMs that had been previously created, and create new ones."),(0,a.kt)("pre",null,(0,a.kt)("code",{parentName:"pre",className:"language-shell-session"},"$ podman machine rm podman-machine-default\n$ podman machine init\n")),(0,a.kt)("p",null,"You should be a happy camper from here."),(0,a.kt)("h2",{id:"recovering-from-a-failed-start"},"Recovering from a failed start"),(0,a.kt)("p",null,"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."),(0,a.kt)("h4",{id:"workaround"},"Workaround"),(0,a.kt)("ol",null,(0,a.kt)("li",{parentName:"ol"},(0,a.kt)("p",{parentName:"li"},"Kill the remaining QEMU process and stop the Podman machine:"),(0,a.kt)("pre",{parentName:"li"},(0,a.kt)("code",{parentName:"pre",className:"language-shell-session"},"$ ps -edf | grep qemu-system | grep -v grep | awk '{print $2}' | xargs -I{} kill -9 {}; podman machine stop\n"))),(0,a.kt)("li",{parentName:"ol"},(0,a.kt)("p",{parentName:"li"},"Start the Podman machine."))),(0,a.kt)("h4",{id:"solution-3"},"Solution"),(0,a.kt)("p",null,"Use Podman 4.6.1 or greater."))}u.isMDXComponent=!0}}]); \ No newline at end of file diff --git a/assets/js/runtime~main.79b9a7fa.js b/assets/js/runtime~main.880382e9.js similarity index 99% rename from assets/js/runtime~main.79b9a7fa.js rename to assets/js/runtime~main.880382e9.js index 153e319681c..7042e7b1b39 100644 --- a/assets/js/runtime~main.79b9a7fa.js +++ b/assets/js/runtime~main.880382e9.js @@ -1 +1 @@ -(()=>{"use strict";var e,a,f,c,d,b={},t={};function r(e){var a=t[e];if(void 0!==a)return a.exports;var f=t[e]={exports:{}};return b[e].call(f.exports,f,f.exports,r),f.exports}r.m=b,e=[],r.O=(a,f,c,d)=>{if(!f){var b=1/0;for(i=0;i=d)&&Object.keys(r.O).every((e=>r.O[e](f[o])))?f.splice(o--,1):(t=!1,d0&&e[i-1][2]>d;i--)e[i]=e[i-1];e[i]=[f,c,d]},r.n=e=>{var a=e&&e.__esModule?()=>e.default:()=>e;return r.d(a,{a:a}),a},f=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 d=Object.create(null);r.r(d);var b={};a=a||[null,f({}),f([]),f(f)];for(var t=2&c&&e;"object"==typeof t&&!~a.indexOf(t);t=f(t))Object.getOwnPropertyNames(t).forEach((a=>b[a]=()=>e[a]));return b.default=()=>e,r.d(d,b),d},r.d=(e,a)=>{for(var f in a)r.o(a,f)&&!r.o(e,f)&&Object.defineProperty(e,f,{enumerable:!0,get:a[f]})},r.f={},r.e=e=>Promise.all(Object.keys(r.f).reduce(((a,f)=>(r.f[f](e,a),a)),[])),r.u=e=>"assets/js/"+({10:"33942509",53:"935f2afb",70:"86f2a982",83:"09905e74",93:"4305e853",114:"e665718d",138:"54590fd2",182:"c276ecb2",205:"83d480e9",210:"3c6cc7c6",397:"6194ac84",465:"f7b7f9b7",506:"9aa62c0e",522:"308aae28",533:"b2b675dd",563:"c685778b",592:"b39cdcf9",649:"512fbd77",692:"6b600968",743:"61d4c13a",809:"840a98fb",873:"cabda5f8",902:"e5ba977d",921:"c37b4a03",945:"df322e14",1021:"1a0737b6",1032:"a67ca768",1074:"9e8f4e9c",1089:"e561c556",1297:"34cf6fc7",1335:"7327116e",1342:"a766a857",1441:"382c5d2b",1476:"53f302bb",1477:"b2f554cd",1591:"2d81b9d5",1625:"de311ed4",1676:"819ef483",1705:"94fb813f",1713:"a7023ddc",1724:"5087625a",1981:"b799648a",2030:"103db5ac",2051:"da78859a",2079:"1a16e8bf",2082:"e85ba0e6",2173:"36eac8b2",2178:"ba322490",2217:"d7fbbe43",2284:"4117ac4b",2323:"6c80b6fe",2472:"65a10ffa",2535:"814f3328",2557:"28726be2",2609:"6269f1c0",2667:"368cce37",2778:"608238a8",2938:"c95aa39f",2965:"4384f6ba",3010:"56c3a9b2",3089:"a6aa9e1f",3237:"1df93b7f",3259:"03ccf92d",3317:"846a5e19",3324:"1ce91f4c",3505:"72486833",3584:"ed75cfcb",3608:"9e4087bc",3636:"8b4dd820",3691:"7be672a3",3751:"3720c009",3820:"a5e1f61e",3870:"5df556a2",3879:"2d629ea6",3973:"f523fb3f",4013:"01a85c17",4059:"9cb03f5d",4121:"55960ee5",4207:"beebaad6",4386:"ae79aff5",4531:"5a8fbd01",4617:"95366386",4685:"d194414f",4758:"c1fad867",4770:"538510a2",4781:"12f1535e",4929:"330dfcdb",5018:"cd509849",5068:"d83d689a",5240:"22de4147",5248:"6101b3fc",5375:"97615df2",5406:"eed60bcf",5468:"b9bde34b",5625:"657ac0bc",5708:"f0057c03",5723:"5d67f40a",5776:"f0e3a130",5803:"ff8f5ed0",5908:"eabf5d51",5974:"f20fb67e",6026:"51dec273",6038:"c9c860ee",6049:"f213dd13",6082:"a233b66e",6088:"88efc5aa",6103:"ccc49370",6120:"d4840880",6134:"3fed3fa8",6181:"4e8ec325",6308:"e8dc4d98",6536:"3ed6e2e9",6690:"4816649b",6692:"2ae2e7fe",6766:"e5638e51",6843:"9f97f9d1",6855:"9061acb9",6870:"dd8511d3",7007:"8593ff01",7034:"3e03f778",7134:"0b40a488",7138:"38a042e4",7141:"b5abacaa",7149:"822c343e",7155:"76cfb1f4",7220:"7591d420",7251:"ba5b9f11",7350:"8bedf5f0",7363:"583db3ef",7366:"75281220",7377:"708d858d",7438:"9c021584",7480:"eb17771c",7505:"8894e90f",7536:"f6e0e63c",7622:"dbbb982f",7673:"499ddca7",7679:"83245ae6",7698:"cd23aec9",7705:"ea2f3e28",7714:"7bdcd7a7",7739:"3ede2625",7741:"7d88b63f",7813:"933a69d3",7847:"43b416ef",7918:"17896441",7920:"1a4e3797",8065:"5ac0e5f4",8145:"006e489c",8215:"1cfced13",8221:"6af14956",8262:"059d1c6a",8290:"3fe48f60",8445:"99245987",8492:"7856861d",8502:"b4657d81",8514:"d651e2ee",8566:"9dce5486",8610:"6875c492",8698:"59c97daa",8800:"e6fb1369",8811:"3289a752",8860:"0d040286",8893:"ba1dc56d",8940:"b6cf724b",8970:"68b843fc",8989:"d4bf7e47",9019:"771d7520",9043:"473de3ed",9106:"72dd8f7e",9133:"02e265ea",9179:"79551407",9184:"b443212b",9214:"a2e79257",9372:"07f59c2a",9387:"b0f1c099",9514:"1be78505",9671:"0e384e19",9817:"4f561e31",9924:"df203c0f",9944:"08570680"}[e]||e)+"."+{10:"34eb91cf",53:"fd6dfec8",70:"3a2b8814",83:"d159b680",93:"fa5c0b9e",114:"1d49c845",138:"eda42b47",182:"90a09a09",205:"844b4921",210:"ba14e6b5",397:"7e08ca10",465:"87b0e77c",506:"10261cc8",522:"500d2126",533:"5401d6bb",563:"72c3d41a",592:"1610e5a1",649:"1a2b3596",692:"9214cbb0",743:"a0769e61",809:"2d892519",873:"46ea42de",902:"445dc0a6",921:"e50247ae",945:"fabffd12",1021:"16a452eb",1032:"7c09c93f",1074:"795fd324",1089:"cfe07000",1297:"923f27fc",1335:"1cf0af2b",1342:"f912ab6a",1441:"f689182f",1476:"1d05c108",1477:"4e447142",1591:"0bc95205",1625:"ced7e14f",1676:"0cba73e6",1705:"62bf5a08",1713:"ed4a16ba",1724:"ed643cc2",1947:"ff7c17e0",1981:"8fdcf563",2030:"dbab4671",2051:"5cf39931",2079:"0a2720f4",2082:"384ae0e3",2173:"5b762612",2178:"13069292",2217:"7e4b1420",2284:"4a5eede5",2323:"a00a3f7f",2472:"f0def9e9",2535:"f7be2bf5",2557:"b6b3e65e",2609:"3ea06f13",2667:"cbc12bfd",2778:"e6f57c14",2938:"234f359a",2965:"1587ea51",3010:"20b15fc9",3089:"3f265d65",3237:"2acfacc0",3259:"f1abd038",3317:"913de95f",3324:"a680ef72",3337:"82efefd4",3505:"49f4afb7",3584:"31de0eeb",3608:"c3805a81",3636:"0e5e6b35",3691:"a4937e8e",3751:"c483e5b5",3820:"24b9186d",3870:"c356cb95",3879:"55981757",3893:"dcd3a11c",3973:"756df355",4013:"e401bc08",4059:"2e148b4d",4121:"4cbea8c2",4207:"cc409e22",4386:"51fd5acd",4531:"389bac49",4617:"a77b39c9",4670:"1a86ede8",4685:"c4794482",4758:"be68be2a",4770:"0771beeb",4781:"04789d76",4929:"3a152928",5018:"14423442",5068:"771af886",5240:"1cc01bd9",5248:"ee07cc61",5375:"95dd6a7a",5406:"6951a3ef",5468:"b24353de",5625:"727df06d",5708:"fdb3f855",5723:"7b09b04e",5776:"9305c8ca",5803:"fab3d5f9",5908:"57562d84",5974:"81815ccd",6026:"2b35ac89",6038:"5089699f",6049:"6cfe5f17",6082:"a0753f0b",6088:"8e2f5865",6103:"a8d429fe",6120:"df5aa334",6134:"c26c79e4",6181:"5c0b2193",6308:"abf1c905",6536:"4e80f52b",6690:"5ce0540d",6692:"cdd7459f",6766:"e6fc3d86",6843:"93279953",6855:"1c8adf02",6870:"c65f0cb2",7007:"928d6401",7034:"66548c3f",7134:"a5670b1e",7138:"415295c7",7141:"a509d41c",7149:"8d1aa85a",7155:"ffe94aa2",7220:"36877b11",7251:"ca3ca0fa",7350:"95dbb769",7363:"8c5a45a9",7366:"e3dd8efe",7377:"cb23f392",7438:"87d8f101",7480:"43b7e388",7505:"41db4959",7536:"1688c2d8",7622:"07d3e0ee",7673:"e6b0543d",7679:"5ead1eee",7698:"c6b6a540",7705:"833c6f97",7714:"67afb974",7739:"b0ed878a",7741:"8564aa5f",7813:"8a96939a",7847:"da52cc1e",7849:"335e2c80",7918:"7183501d",7920:"41536f7b",8065:"210315e8",8145:"57e59b10",8215:"4c17dca9",8221:"a30a6aba",8262:"e7d625ae",8290:"a275a64b",8306:"32d20a44",8445:"3c50af99",8492:"b1390de3",8502:"82de7bfb",8514:"52311247",8566:"346f0a6f",8610:"e64867fe",8698:"c0cc2f45",8777:"10f7b1e7",8800:"40ac3960",8811:"6dfd0211",8860:"eea3323e",8893:"e79ddd86",8940:"5ffd10e1",8970:"e7b7dbf5",8989:"8f46b4ce",9019:"b249609b",9043:"49ebd957",9106:"b51c032f",9127:"24e80eea",9133:"d67cc2b3",9179:"fb2b6aab",9184:"397983fc",9214:"3e1e1dbb",9372:"8b1fcf0d",9387:"c68f7606",9514:"d688c44c",9671:"7a5b19a3",9817:"2921319c",9924:"a7bd29c2",9944:"986cf0d2"}[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,a)=>Object.prototype.hasOwnProperty.call(e,a),c={},d="docs:",r.l=(e,a,f,b)=>{if(c[e])c[e].push(a);else{var t,o;if(void 0!==f)for(var n=document.getElementsByTagName("script"),i=0;i{t.onerror=t.onload=null,clearTimeout(s);var d=c[e];if(delete c[e],t.parentNode&&t.parentNode.removeChild(t),d&&d.forEach((e=>e(f))),a)return a(f)},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","935f2afb":"53","86f2a982":"70","09905e74":"83","4305e853":"93",e665718d:"114","54590fd2":"138",c276ecb2:"182","83d480e9":"205","3c6cc7c6":"210","6194ac84":"397",f7b7f9b7:"465","9aa62c0e":"506","308aae28":"522",b2b675dd:"533",c685778b:"563",b39cdcf9:"592","512fbd77":"649","6b600968":"692","61d4c13a":"743","840a98fb":"809",cabda5f8:"873",e5ba977d:"902",c37b4a03:"921",df322e14:"945","1a0737b6":"1021",a67ca768:"1032","9e8f4e9c":"1074",e561c556:"1089","34cf6fc7":"1297","7327116e":"1335",a766a857:"1342","382c5d2b":"1441","53f302bb":"1476",b2f554cd:"1477","2d81b9d5":"1591",de311ed4:"1625","819ef483":"1676","94fb813f":"1705",a7023ddc:"1713","5087625a":"1724",b799648a:"1981","103db5ac":"2030",da78859a:"2051","1a16e8bf":"2079",e85ba0e6:"2082","36eac8b2":"2173",ba322490:"2178",d7fbbe43:"2217","4117ac4b":"2284","6c80b6fe":"2323","65a10ffa":"2472","814f3328":"2535","28726be2":"2557","6269f1c0":"2609","368cce37":"2667","608238a8":"2778",c95aa39f:"2938","4384f6ba":"2965","56c3a9b2":"3010",a6aa9e1f:"3089","1df93b7f":"3237","03ccf92d":"3259","846a5e19":"3317","1ce91f4c":"3324",ed75cfcb:"3584","9e4087bc":"3608","8b4dd820":"3636","7be672a3":"3691","3720c009":"3751",a5e1f61e:"3820","5df556a2":"3870","2d629ea6":"3879",f523fb3f:"3973","01a85c17":"4013","9cb03f5d":"4059","55960ee5":"4121",beebaad6:"4207",ae79aff5:"4386","5a8fbd01":"4531",d194414f:"4685",c1fad867:"4758","538510a2":"4770","12f1535e":"4781","330dfcdb":"4929",cd509849:"5018",d83d689a:"5068","22de4147":"5240","6101b3fc":"5248","97615df2":"5375",eed60bcf:"5406",b9bde34b:"5468","657ac0bc":"5625",f0057c03:"5708","5d67f40a":"5723",f0e3a130:"5776",ff8f5ed0:"5803",eabf5d51:"5908",f20fb67e:"5974","51dec273":"6026",c9c860ee:"6038",f213dd13:"6049",a233b66e:"6082","88efc5aa":"6088",ccc49370:"6103",d4840880:"6120","3fed3fa8":"6134","4e8ec325":"6181",e8dc4d98:"6308","3ed6e2e9":"6536","4816649b":"6690","2ae2e7fe":"6692",e5638e51:"6766","9f97f9d1":"6843","9061acb9":"6855",dd8511d3:"6870","8593ff01":"7007","3e03f778":"7034","0b40a488":"7134","38a042e4":"7138",b5abacaa:"7141","822c343e":"7149","76cfb1f4":"7155","7591d420":"7220",ba5b9f11:"7251","8bedf5f0":"7350","583db3ef":"7363","708d858d":"7377","9c021584":"7438",eb17771c:"7480","8894e90f":"7505",f6e0e63c:"7536",dbbb982f:"7622","499ddca7":"7673","83245ae6":"7679",cd23aec9:"7698",ea2f3e28:"7705","7bdcd7a7":"7714","3ede2625":"7739","7d88b63f":"7741","933a69d3":"7813","43b416ef":"7847","1a4e3797":"7920","5ac0e5f4":"8065","006e489c":"8145","1cfced13":"8215","6af14956":"8221","059d1c6a":"8262","3fe48f60":"8290","7856861d":"8492",b4657d81:"8502",d651e2ee:"8514","9dce5486":"8566","6875c492":"8610","59c97daa":"8698",e6fb1369:"8800","3289a752":"8811","0d040286":"8860",ba1dc56d:"8893",b6cf724b:"8940","68b843fc":"8970",d4bf7e47:"8989","771d7520":"9019","473de3ed":"9043","72dd8f7e":"9106","02e265ea":"9133",b443212b:"9184",a2e79257:"9214","07f59c2a":"9372",b0f1c099:"9387","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=(a,f)=>{var c=r.o(e,a)?e[a]:void 0;if(0!==c)if(c)f.push(c[2]);else if(/^(1303|532)$/.test(a))e[a]=0;else{var d=new Promise(((f,d)=>c=e[a]=[f,d]));f.push(c[2]=d);var b=r.p+r.u(a),t=new Error;r.l(b,(f=>{if(r.o(e,a)&&(0!==(c=e[a])&&(e[a]=void 0),c)){var d=f&&("load"===f.type?"missing":f.type),b=f&&f.target&&f.target.src;t.message="Loading chunk "+a+" failed.\n("+d+": "+b+")",t.name="ChunkLoadError",t.type=d,t.request=b,c[1](t)}}),"chunk-"+a,a)}},r.O.j=a=>0===e[a];var a=(a,f)=>{var c,d,b=f[0],t=f[1],o=f[2],n=0;if(b.some((a=>0!==e[a]))){for(c in t)r.o(t,c)&&(r.m[c]=t[c]);if(o)var i=o(r)}for(a&&a(f);n{"use strict";var e,a,f,c,d,b={},t={};function r(e){var a=t[e];if(void 0!==a)return a.exports;var f=t[e]={exports:{}};return b[e].call(f.exports,f,f.exports,r),f.exports}r.m=b,e=[],r.O=(a,f,c,d)=>{if(!f){var b=1/0;for(i=0;i=d)&&Object.keys(r.O).every((e=>r.O[e](f[o])))?f.splice(o--,1):(t=!1,d0&&e[i-1][2]>d;i--)e[i]=e[i-1];e[i]=[f,c,d]},r.n=e=>{var a=e&&e.__esModule?()=>e.default:()=>e;return r.d(a,{a:a}),a},f=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 d=Object.create(null);r.r(d);var b={};a=a||[null,f({}),f([]),f(f)];for(var t=2&c&&e;"object"==typeof t&&!~a.indexOf(t);t=f(t))Object.getOwnPropertyNames(t).forEach((a=>b[a]=()=>e[a]));return b.default=()=>e,r.d(d,b),d},r.d=(e,a)=>{for(var f in a)r.o(a,f)&&!r.o(e,f)&&Object.defineProperty(e,f,{enumerable:!0,get:a[f]})},r.f={},r.e=e=>Promise.all(Object.keys(r.f).reduce(((a,f)=>(r.f[f](e,a),a)),[])),r.u=e=>"assets/js/"+({10:"33942509",53:"935f2afb",70:"86f2a982",83:"09905e74",93:"4305e853",114:"e665718d",138:"54590fd2",182:"c276ecb2",205:"83d480e9",210:"3c6cc7c6",397:"6194ac84",465:"f7b7f9b7",506:"9aa62c0e",522:"308aae28",533:"b2b675dd",563:"c685778b",592:"b39cdcf9",649:"512fbd77",692:"6b600968",743:"61d4c13a",809:"840a98fb",873:"cabda5f8",902:"e5ba977d",921:"c37b4a03",945:"df322e14",1021:"1a0737b6",1032:"a67ca768",1074:"9e8f4e9c",1089:"e561c556",1297:"34cf6fc7",1335:"7327116e",1342:"a766a857",1441:"382c5d2b",1476:"53f302bb",1477:"b2f554cd",1591:"2d81b9d5",1625:"de311ed4",1676:"819ef483",1705:"94fb813f",1713:"a7023ddc",1724:"5087625a",1981:"b799648a",2030:"103db5ac",2051:"da78859a",2079:"1a16e8bf",2082:"e85ba0e6",2173:"36eac8b2",2178:"ba322490",2217:"d7fbbe43",2284:"4117ac4b",2323:"6c80b6fe",2472:"65a10ffa",2535:"814f3328",2557:"28726be2",2609:"6269f1c0",2667:"368cce37",2778:"608238a8",2938:"c95aa39f",2965:"4384f6ba",3010:"56c3a9b2",3089:"a6aa9e1f",3237:"1df93b7f",3259:"03ccf92d",3317:"846a5e19",3324:"1ce91f4c",3505:"72486833",3584:"ed75cfcb",3608:"9e4087bc",3636:"8b4dd820",3691:"7be672a3",3751:"3720c009",3820:"a5e1f61e",3870:"5df556a2",3879:"2d629ea6",3973:"f523fb3f",4013:"01a85c17",4059:"9cb03f5d",4121:"55960ee5",4207:"beebaad6",4386:"ae79aff5",4531:"5a8fbd01",4617:"95366386",4685:"d194414f",4758:"c1fad867",4770:"538510a2",4781:"12f1535e",4929:"330dfcdb",5018:"cd509849",5068:"d83d689a",5240:"22de4147",5248:"6101b3fc",5375:"97615df2",5406:"eed60bcf",5468:"b9bde34b",5625:"657ac0bc",5708:"f0057c03",5723:"5d67f40a",5776:"f0e3a130",5803:"ff8f5ed0",5908:"eabf5d51",5974:"f20fb67e",6026:"51dec273",6038:"c9c860ee",6049:"f213dd13",6082:"a233b66e",6088:"88efc5aa",6103:"ccc49370",6120:"d4840880",6134:"3fed3fa8",6181:"4e8ec325",6308:"e8dc4d98",6536:"3ed6e2e9",6690:"4816649b",6692:"2ae2e7fe",6766:"e5638e51",6843:"9f97f9d1",6855:"9061acb9",6870:"dd8511d3",7007:"8593ff01",7034:"3e03f778",7134:"0b40a488",7138:"38a042e4",7141:"b5abacaa",7149:"822c343e",7155:"76cfb1f4",7220:"7591d420",7251:"ba5b9f11",7350:"8bedf5f0",7363:"583db3ef",7366:"75281220",7377:"708d858d",7438:"9c021584",7480:"eb17771c",7505:"8894e90f",7536:"f6e0e63c",7622:"dbbb982f",7673:"499ddca7",7679:"83245ae6",7698:"cd23aec9",7705:"ea2f3e28",7714:"7bdcd7a7",7739:"3ede2625",7741:"7d88b63f",7813:"933a69d3",7847:"43b416ef",7918:"17896441",7920:"1a4e3797",8065:"5ac0e5f4",8145:"006e489c",8215:"1cfced13",8221:"6af14956",8262:"059d1c6a",8290:"3fe48f60",8445:"99245987",8492:"7856861d",8502:"b4657d81",8514:"d651e2ee",8566:"9dce5486",8610:"6875c492",8698:"59c97daa",8800:"e6fb1369",8811:"3289a752",8860:"0d040286",8893:"ba1dc56d",8940:"b6cf724b",8970:"68b843fc",8989:"d4bf7e47",9019:"771d7520",9043:"473de3ed",9106:"72dd8f7e",9133:"02e265ea",9179:"79551407",9184:"b443212b",9214:"a2e79257",9372:"07f59c2a",9387:"b0f1c099",9514:"1be78505",9671:"0e384e19",9817:"4f561e31",9924:"df203c0f",9944:"08570680"}[e]||e)+"."+{10:"34eb91cf",53:"fd6dfec8",70:"3a2b8814",83:"d159b680",93:"fa5c0b9e",114:"1d49c845",138:"eda42b47",182:"90a09a09",205:"844b4921",210:"ba14e6b5",397:"7e08ca10",465:"87b0e77c",506:"10261cc8",522:"500d2126",533:"5401d6bb",563:"72c3d41a",592:"1610e5a1",649:"1a2b3596",692:"9214cbb0",743:"a0769e61",809:"2d892519",873:"46ea42de",902:"445dc0a6",921:"e50247ae",945:"fabffd12",1021:"16a452eb",1032:"7c09c93f",1074:"795fd324",1089:"cfe07000",1297:"923f27fc",1335:"1cf0af2b",1342:"f912ab6a",1441:"f689182f",1476:"1d05c108",1477:"4e447142",1591:"0bc95205",1625:"ced7e14f",1676:"0cba73e6",1705:"62bf5a08",1713:"ed4a16ba",1724:"ed643cc2",1947:"ff7c17e0",1981:"8fdcf563",2030:"dbab4671",2051:"5cf39931",2079:"0a2720f4",2082:"384ae0e3",2173:"5b762612",2178:"13069292",2217:"7e4b1420",2284:"4a5eede5",2323:"a00a3f7f",2472:"f0def9e9",2535:"f7be2bf5",2557:"b6b3e65e",2609:"3ea06f13",2667:"cbc12bfd",2778:"e6f57c14",2938:"234f359a",2965:"1587ea51",3010:"20b15fc9",3089:"3f265d65",3237:"2acfacc0",3259:"f1abd038",3317:"913de95f",3324:"a680ef72",3337:"82efefd4",3505:"49f4afb7",3584:"31de0eeb",3608:"c3805a81",3636:"0e5e6b35",3691:"a4937e8e",3751:"c483e5b5",3820:"24b9186d",3870:"c356cb95",3879:"55981757",3893:"dcd3a11c",3973:"756df355",4013:"e401bc08",4059:"2e148b4d",4121:"4cbea8c2",4207:"cc409e22",4386:"51fd5acd",4531:"389bac49",4617:"a77b39c9",4670:"1a86ede8",4685:"c4794482",4758:"be68be2a",4770:"0771beeb",4781:"04789d76",4929:"3a152928",5018:"14423442",5068:"771af886",5240:"1cc01bd9",5248:"ee07cc61",5375:"95dd6a7a",5406:"6951a3ef",5468:"b24353de",5625:"727df06d",5708:"fdb3f855",5723:"7b09b04e",5776:"9305c8ca",5803:"fab3d5f9",5908:"57562d84",5974:"81815ccd",6026:"2b35ac89",6038:"5089699f",6049:"6cfe5f17",6082:"a0753f0b",6088:"8e2f5865",6103:"a8d429fe",6120:"df5aa334",6134:"c26c79e4",6181:"5c0b2193",6308:"abf1c905",6536:"4e80f52b",6690:"5ce0540d",6692:"cdd7459f",6766:"e6fc3d86",6843:"93279953",6855:"1c8adf02",6870:"c65f0cb2",7007:"928d6401",7034:"66548c3f",7134:"a5670b1e",7138:"415295c7",7141:"a509d41c",7149:"8d1aa85a",7155:"ffe94aa2",7220:"36877b11",7251:"ca3ca0fa",7350:"95dbb769",7363:"8c5a45a9",7366:"e3dd8efe",7377:"cb23f392",7438:"87d8f101",7480:"43b7e388",7505:"41db4959",7536:"1688c2d8",7622:"07d3e0ee",7673:"e6b0543d",7679:"5ead1eee",7698:"c6b6a540",7705:"833c6f97",7714:"67afb974",7739:"b0ed878a",7741:"8564aa5f",7813:"8a96939a",7847:"da52cc1e",7849:"335e2c80",7918:"7183501d",7920:"41536f7b",8065:"210315e8",8145:"57e59b10",8215:"4c17dca9",8221:"a30a6aba",8262:"e7d625ae",8290:"a275a64b",8306:"32d20a44",8445:"3c50af99",8492:"b1390de3",8502:"82de7bfb",8514:"52311247",8566:"346f0a6f",8610:"e64867fe",8698:"c0cc2f45",8777:"10f7b1e7",8800:"40ac3960",8811:"6dfd0211",8860:"eea3323e",8893:"e79ddd86",8940:"5ffd10e1",8970:"e7b7dbf5",8989:"eb3d4296",9019:"b249609b",9043:"49ebd957",9106:"b51c032f",9127:"24e80eea",9133:"d67cc2b3",9179:"fb2b6aab",9184:"397983fc",9214:"3e1e1dbb",9372:"8b1fcf0d",9387:"c68f7606",9514:"d688c44c",9671:"7a5b19a3",9817:"2921319c",9924:"a7bd29c2",9944:"986cf0d2"}[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,a)=>Object.prototype.hasOwnProperty.call(e,a),c={},d="docs:",r.l=(e,a,f,b)=>{if(c[e])c[e].push(a);else{var t,o;if(void 0!==f)for(var n=document.getElementsByTagName("script"),i=0;i{t.onerror=t.onload=null,clearTimeout(s);var d=c[e];if(delete c[e],t.parentNode&&t.parentNode.removeChild(t),d&&d.forEach((e=>e(f))),a)return a(f)},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","935f2afb":"53","86f2a982":"70","09905e74":"83","4305e853":"93",e665718d:"114","54590fd2":"138",c276ecb2:"182","83d480e9":"205","3c6cc7c6":"210","6194ac84":"397",f7b7f9b7:"465","9aa62c0e":"506","308aae28":"522",b2b675dd:"533",c685778b:"563",b39cdcf9:"592","512fbd77":"649","6b600968":"692","61d4c13a":"743","840a98fb":"809",cabda5f8:"873",e5ba977d:"902",c37b4a03:"921",df322e14:"945","1a0737b6":"1021",a67ca768:"1032","9e8f4e9c":"1074",e561c556:"1089","34cf6fc7":"1297","7327116e":"1335",a766a857:"1342","382c5d2b":"1441","53f302bb":"1476",b2f554cd:"1477","2d81b9d5":"1591",de311ed4:"1625","819ef483":"1676","94fb813f":"1705",a7023ddc:"1713","5087625a":"1724",b799648a:"1981","103db5ac":"2030",da78859a:"2051","1a16e8bf":"2079",e85ba0e6:"2082","36eac8b2":"2173",ba322490:"2178",d7fbbe43:"2217","4117ac4b":"2284","6c80b6fe":"2323","65a10ffa":"2472","814f3328":"2535","28726be2":"2557","6269f1c0":"2609","368cce37":"2667","608238a8":"2778",c95aa39f:"2938","4384f6ba":"2965","56c3a9b2":"3010",a6aa9e1f:"3089","1df93b7f":"3237","03ccf92d":"3259","846a5e19":"3317","1ce91f4c":"3324",ed75cfcb:"3584","9e4087bc":"3608","8b4dd820":"3636","7be672a3":"3691","3720c009":"3751",a5e1f61e:"3820","5df556a2":"3870","2d629ea6":"3879",f523fb3f:"3973","01a85c17":"4013","9cb03f5d":"4059","55960ee5":"4121",beebaad6:"4207",ae79aff5:"4386","5a8fbd01":"4531",d194414f:"4685",c1fad867:"4758","538510a2":"4770","12f1535e":"4781","330dfcdb":"4929",cd509849:"5018",d83d689a:"5068","22de4147":"5240","6101b3fc":"5248","97615df2":"5375",eed60bcf:"5406",b9bde34b:"5468","657ac0bc":"5625",f0057c03:"5708","5d67f40a":"5723",f0e3a130:"5776",ff8f5ed0:"5803",eabf5d51:"5908",f20fb67e:"5974","51dec273":"6026",c9c860ee:"6038",f213dd13:"6049",a233b66e:"6082","88efc5aa":"6088",ccc49370:"6103",d4840880:"6120","3fed3fa8":"6134","4e8ec325":"6181",e8dc4d98:"6308","3ed6e2e9":"6536","4816649b":"6690","2ae2e7fe":"6692",e5638e51:"6766","9f97f9d1":"6843","9061acb9":"6855",dd8511d3:"6870","8593ff01":"7007","3e03f778":"7034","0b40a488":"7134","38a042e4":"7138",b5abacaa:"7141","822c343e":"7149","76cfb1f4":"7155","7591d420":"7220",ba5b9f11:"7251","8bedf5f0":"7350","583db3ef":"7363","708d858d":"7377","9c021584":"7438",eb17771c:"7480","8894e90f":"7505",f6e0e63c:"7536",dbbb982f:"7622","499ddca7":"7673","83245ae6":"7679",cd23aec9:"7698",ea2f3e28:"7705","7bdcd7a7":"7714","3ede2625":"7739","7d88b63f":"7741","933a69d3":"7813","43b416ef":"7847","1a4e3797":"7920","5ac0e5f4":"8065","006e489c":"8145","1cfced13":"8215","6af14956":"8221","059d1c6a":"8262","3fe48f60":"8290","7856861d":"8492",b4657d81:"8502",d651e2ee:"8514","9dce5486":"8566","6875c492":"8610","59c97daa":"8698",e6fb1369:"8800","3289a752":"8811","0d040286":"8860",ba1dc56d:"8893",b6cf724b:"8940","68b843fc":"8970",d4bf7e47:"8989","771d7520":"9019","473de3ed":"9043","72dd8f7e":"9106","02e265ea":"9133",b443212b:"9184",a2e79257:"9214","07f59c2a":"9372",b0f1c099:"9387","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=(a,f)=>{var c=r.o(e,a)?e[a]:void 0;if(0!==c)if(c)f.push(c[2]);else if(/^(1303|532)$/.test(a))e[a]=0;else{var d=new Promise(((f,d)=>c=e[a]=[f,d]));f.push(c[2]=d);var b=r.p+r.u(a),t=new Error;r.l(b,(f=>{if(r.o(e,a)&&(0!==(c=e[a])&&(e[a]=void 0),c)){var d=f&&("load"===f.type?"missing":f.type),b=f&&f.target&&f.target.src;t.message="Loading chunk "+a+" failed.\n("+d+": "+b+")",t.name="ChunkLoadError",t.type=d,t.request=b,c[1](t)}}),"chunk-"+a,a)}},r.O.j=a=>0===e[a];var a=(a,f)=>{var c,d,b=f[0],t=f[1],o=f[2],n=0;if(b.some((a=>0!==e[a]))){for(c in t)r.o(t,c)&&(r.m[c]=t[c]);if(o)var i=o(r)}for(a&&a(f);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 a27f6905450..51c0316a11e 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 fd07a9933a9..d35e4e9c362 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 8963b24b4c5..7313e011960 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 50c0ed4f39d..19276f062d0 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 7ed514600b7..63d9cf05de4 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 9b3e73791e8..0cd1eb685d7 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 ee086d7e3e4..f489b894f6a 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 f0936af634b..497bfc08c2f 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 28ba6958426..133e2482526 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 4e699d9e588..234c656ac5e 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 b3258fedc5b..861ce3a3f06 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 65a5ca2a4f1..2c7cfefd50e 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 d641b39d034..888717e9cb9 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/running-a-local-kubernetes-cluster-with-podman-desktop.html b/blog/running-a-local-kubernetes-cluster-with-podman-desktop.html index 6bfd5d1f943..6c07124f439 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 1e45cc22ad5..cbca3de58ad 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 5ce5e97c5bc..a117d220deb 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 0e70df21f84..579ab66ad52 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 e42dfb31a50..06290fee842 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 8cebeff2334..aa65e6c2929 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 bfff9d14c33..832e7a59766 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 5e238a0f7eb..23cbe16140f 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 e3ea5aa0c43..d40f4076eae 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 9a27c914c48..612a3149cdf 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 45227430c73..604292063b3 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 7b8b7b2df60..ba3312e719f 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 c355ec97cfb..60b79addcf0 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 35bcb5075a8..4a1742865f5 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/Installation.html b/docs/Installation.html index a7cf88bf981..d5fbb2cc862 100644 --- a/docs/Installation.html +++ b/docs/Installation.html @@ -13,13 +13,13 @@ - +

Installing Podman Desktop

You can install Podman Desktop on:

Podman Desktop requires you to install at least one container engine.

Podman Desktop does not install any container engine automatically.

Podman Desktop can use different virtual machines, such as:

  • Lima
  • Podman Machine

Podman Desktop can control various container engines, such as:

  • Docker
  • Podman

Consider installing the Podman container engine for:

  • Added security
  • No daemon
  • Open source
  • Rootless
- + \ No newline at end of file diff --git a/docs/Installation/creating-a-lima-instance-with-podman-desktop.html b/docs/Installation/creating-a-lima-instance-with-podman-desktop.html index ba3828d1978..247b2e309e9 100644 --- a/docs/Installation/creating-a-lima-instance-with-podman-desktop.html +++ b/docs/Installation/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/Installation/creating-a-podman-machine-with-podman-desktop.html b/docs/Installation/creating-a-podman-machine-with-podman-desktop.html index cb77b463478..aeaa27ea6cd 100644 --- a/docs/Installation/creating-a-podman-machine-with-podman-desktop.html +++ b/docs/Installation/creating-a-podman-machine-with-podman-desktop.html @@ -13,7 +13,7 @@ - + @@ -26,7 +26,7 @@ Select the disk size.
  • Image path (Optional): Select a bootable image containing a virtual machine with Podman.
  • Machine with root privileges: Enable to use the rootful connection by default. Required to use Kind on Windows.
  • Click Create

    • Create a Podman machine

    - + \ No newline at end of file diff --git a/docs/Installation/linux-install.html b/docs/Installation/linux-install.html index 3c0bcc8dbc3..232f82af38d 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 1317ae4672f..8a2ec8f1b83 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 666df1ed256..b20ef468c43 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 76129a86154..4cc4076d9a8 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 87c9e85e82e..cd8d3305c2f 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 fd77a2bb3e9..bc9285f7b58 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 for installation
    • Does not require Internet access to download resources during installation

    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 on the Install button to install Podman.
    4. Click on Initialize Podman.

    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 61ee75c83fe..e073db446de 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 @@ - +

    Installing Podman Desktop silently with the Windows installer

    Consider using this method to install the Podman Desktop Windows installer without user interaction.

    Procedure​

    1. Download the Windows installer.

    2. Run the PowerShell command:

      Start-Process -FilePath '.\podman-desktop-0.10.0-setup.exe' -ArgumentList "\S" -Wait

    Next steps​

    - + \ 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 2f31e9b762e..4c1a9aba769 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 @@ - +

    Installing Podman Desktop with Chocolatey

    Installing Podman Desktop on Windows with Chocolatey​

    Prerequisites​

    Procedure​

    • Run the command from the command line or from PowerShell:

      choco install podman-desktop

    Additional resources​

    Next steps​

    - + \ 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 159e6c9dec6..6b8a8d5f3bd 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 @@ - +

    Installing Podman Desktop with Scoop package manager for Windows

    Prerequisites​

    Procedure​

    • Run the commands from the command line or from PowerShell:

      scoop bucket add extras
      scoop install podman-desktop

    Additional resources​

    Next steps​

    - + \ 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 80e25d40b55..4a3ccd4551c 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/Installation/windows-install/installing-podman-with-openshift-local.html b/docs/Installation/windows-install/installing-podman-with-openshift-local.html index 9b7fd569577..8acc0f3ad46 100644 --- a/docs/Installation/windows-install/installing-podman-with-openshift-local.html +++ b/docs/Installation/windows-install/installing-podman-with-openshift-local.html @@ -13,13 +13,13 @@ - +

    Installing the Podman Preset with OpenShift Local

    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 OpenShift Local

    2. Select the Podman container runtime preset:

      $ crc config set preset podman

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

      $ crc setup

    4. Start the Red Hat OpenShift instance:

      $ crc start

    Additional resources​

    Next steps​

    - + \ No newline at end of file diff --git a/docs/Installation/windows-install/installing-podman-with-podman-desktop.html b/docs/Installation/windows-install/installing-podman-with-podman-desktop.html index 4eef88e52a9..ea6c46ba46b 100644 --- a/docs/Installation/windows-install/installing-podman-with-podman-desktop.html +++ b/docs/Installation/windows-install/installing-podman-with-podman-desktop.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/compose/compose-spec.html b/docs/compose/compose-spec.html index 242778bd9d3..1739ea93792 100644 --- a/docs/compose/compose-spec.html +++ b/docs/compose/compose-spec.html @@ -13,14 +13,14 @@ - +

    Compose spec with Podman Desktop

    Introduction​

    Podman Desktop supports the Compose spec. With Podman Desktop, users can easily create and manage multi-container applications by using Compose files.

    How does it work​

    Each time you run a Compose file by using Podman Compose or Docker Compose a label is assigned to each container. Podman Desktop detects that label and shows it appropriately within the management console.

    img2

    What do you need to enable​

    Containers deployed by the Compose specification are automatically detected by Podman Desktop.

    What if you already have Docker Compose or Podman Compose installed​

    Any containers already deployed by Docker Compose / Podman Compose will be automatically shown within Podman Desktop. You do not need to do anything!

    - + \ No newline at end of file diff --git a/docs/compose/podman-compose.html b/docs/compose/podman-compose.html index dc400580410..07d328673ae 100644 --- a/docs/compose/podman-compose.html +++ b/docs/compose/podman-compose.html @@ -13,13 +13,13 @@ - +

    Podman Compose with Podman Desktop

    Introduction​

    Podman Compose is a community-driven tool that allows developers to use the Compose spec to run many containers at the same time. Podman Compose requires a Compose YAML file with definitions about the containers that need to communicate.

    If you have not used a Compose file or the Compose spec, visit this guide for more information.

    Requirements​

    Getting started​

    Spin up your compose.yaml with the podman-compose binary and Podman Desktop will automatically detect it!

    Use the Flask Redis project from the awesome-compose repository as an example project.

    1. Git clone the project and cd into the directory:

      $ git clone https://github.com/docker/awesome-compose
      $ cd awesome-compose/redis-flask

    2. Run the podman-compose command:

      $ podman-compose -f compose.yaml up -d

      img1

    3. Manage Compose with Podman Desktop

      To confirm if the containers are running, open Podman Desktop and click on the ‘Containers’ option on the left side of the application. You will have the containers bundled together under a Pod named flask-redis (compose) in this case. Here, the compose within the bracket indicates it has been generated from a Compose YAML file.

      img2

    4. You can further configure or work with these containers within the Podman Desktop application now that they are visible. Here, clicking on the ‘Open Browser’ button allows us to confirm if the application is running expectedly.

      img3

    5. You can do much more such as checking logs, opening the terminal or inspecting the files for more details.

      img4

    - + \ No newline at end of file diff --git a/docs/extensions.html b/docs/extensions.html index 274c7caf6d3..6b81d759e21 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 edf84a91e01..b21f814ac87 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 22fd3186246..f14b6b7838d 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 56b61230761..478cd0e29d0 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 4165c7dbadc..d3e181aa5ee 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/getting-started/authenticating-to-a-preconfigured-registry.html b/docs/getting-started/authenticating-to-a-preconfigured-registry.html index e9c5c9ae70e..93abfc45635 100644 --- a/docs/getting-started/authenticating-to-a-preconfigured-registry.html +++ b/docs/getting-started/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/getting-started/building-an-image.html b/docs/getting-started/building-an-image.html index cd9a4aa7d6a..4319b896c85 100644 --- a/docs/getting-started/building-an-image.html +++ b/docs/getting-started/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/getting-started/creating-a-pod.html b/docs/getting-started/creating-a-pod.html index 639d57dfb3e..11f5aa585bc 100644 --- a/docs/getting-started/creating-a-pod.html +++ b/docs/getting-started/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/getting-started/getting-started.html b/docs/getting-started/getting-started.html index 0f79baa99ae..7d03e3a615d 100644 --- a/docs/getting-started/getting-started.html +++ b/docs/getting-started/getting-started.html @@ -13,13 +13,13 @@ - +

    Getting Started with Podman Desktop

    Introduction​

    Podman Desktop leverages Podman Engine to provide a lightweight and daemon-less container management tool. It enables you to easily work with containers from your local environment without running container management commands.

    Podman Desktop brings all the capabilities of Podman with the added advantage of a GUI which is becoming increasingly powerful and user-friendly. It is super easy to adapt to. With this tutorial, you will be ready to roll and work with your containerized applications in no time.

    In this tutorial, I am working with Podman Desktop v0.0.5.

    Requirements​

    To work with Podman Desktop, you firstly require the latest version of Podman Desktop. Depending on your operating system, you can download it from this page.

    Next, you need the latest version of Podman Engine installed on your computer. When started, Podman Desktop looks for the Podman Engine in the system and will prompt you to install the same if it is not present. You can read more about how to set up the Podman Desktop and Podman Engine in the Installation guide here.

    Once everything is set up, you are ready to go!

    Get Started​

    When you open the Podman Desktop application, you will be greeted with the home screen. It will show you a toggle button that says ‘Initialize Podman’. And as mentioned, it initializes the Podman Engine and creates a Podman Machine for you. Click on it to create a Podman Machine. Within no time, your Podman Machine will be created. This is equivalent to running the command podman machine init. You can read more about it here.

    Next, you need to start the Podman Machine by toggling the button that says ‘Run Podman’. This is equivalent to running podman machine start. You can read more about it here.

    Once it says “Podman is running”, you are ready to build images and run containers!

    Our first step will be to build an image for our application followed by running the image to create the container.

    1. Build Image​

    For this section of the tutorial, I have created my Containerfile using the Red Hat Universal Base Image. You can also write your own Containerfiles and build images from it using the Red Hat Universal Base Image (UBI). Read more about it in this blog. Once you have your Containerfile ready, follow the steps below to build your own image.

    1. To load the Containerfile to Podman Desktop and build the Image, we browse to the “Images” section and click on the “Build Image” button. This opens a tab within which you can select the path where your Containerfile is present.

      img1.1

    2. Click on the placeholder “Select Containerfile to build”, browse to the folder where the Containerfile is present and select the file.

      img1.2

    3. Go ahead and type in any name for your image below but Podman Desktop will have something generated by default in case you want to skip it.

      img1.3

    4. Click on ‘Build’ and that’s it. You will see each instruction from your Containerfile being executed to build the image.

      img1.4

    5. Once completed, Click on “Done” above to continue. You will see that your image has been added to the Images section of Podman Desktop.

      img1.5

    2. Create and Run the Container​

    Following are the steps to create and start a container from the image.

    1. Once the image is built, you can see its name (in our case, ‘my-custom-image’) and other details in the Images section.

      img2.1

    2. Simply hover over the name of the image and you will see a list of buttons to the right. In case you are confused about the action of each button, just take the cursor over each button and wait for it to tell the action it does.

      img2.2

    3. Upon clicking the ‘Run Image’ button, a window will appear and it will ask you to Create the container by giving it a name and mapping the desired port number.

      img2.3

    4. Once you click on “Start Container”, you will see some changes in the Containers section. Upon hovering your cursor over the newly created container, you will see a set of buttons allowing you to work with it.

      img2.4

    5. To check if it is running our application as desired, open the URL in the browser (in this case, localhost:8080 because that’s where we mapped our port). This can be done by clicking on the ‘Open Browser’ button.

      img2.5

    6. As we can see, it returns {“Hello”:”World”} as intended.

      img2.6

    Conclusion​

    So that’s it! It is that simple to get started with Podman Desktop for building and running your first container image!

    - + \ No newline at end of file diff --git a/docs/getting-started/insecure-registry.html b/docs/getting-started/insecure-registry.html index d76536fbf57..8c440ba6969 100644 --- a/docs/getting-started/insecure-registry.html +++ b/docs/getting-started/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/getting-started/pulling-an-image.html b/docs/getting-started/pulling-an-image.html index 6194a24c372..1793ef6c3ff 100644 --- a/docs/getting-started/pulling-an-image.html +++ b/docs/getting-started/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/getting-started/pushing-an-image-to-a-registry.html b/docs/getting-started/pushing-an-image-to-a-registry.html index 886dc4e142c..ad03bb640a4 100644 --- a/docs/getting-started/pushing-an-image-to-a-registry.html +++ b/docs/getting-started/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/getting-started/starting-a-container.html b/docs/getting-started/starting-a-container.html index 0b9ee7b7434..03bb050fc24 100644 --- a/docs/getting-started/starting-a-container.html +++ b/docs/getting-started/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/intro.html b/docs/intro.html index b0887708c91..0875a81da0b 100644 --- a/docs/intro.html +++ b/docs/intro.html @@ -13,13 +13,13 @@ - +

    Introduction

    Let's discover Podman Desktop in less than 5 minutes.

    Getting Started​

    Get started by Downloading the product for your operating system.

    What you'll need​

    • Podman 4.x
      • Check there is a Podman machine running

    Check Podman CLI is working​

    Run the development server:

    $ podman run quay.io/podman/hello
    !... Hello Podman World ...!

             .--"--.
           / -     - \
          / (O)   (O) \
       ~~~| -=(,Y,)=- |
        .---. /`  \   |~~
     ~/  o  o \~~~~.----. ~~
      | =(X)= |~  / (O (O) \
       ~~~~~~~  ~| =(Y_)=-  |
      ~~~~    ~~~|   U      |~~

    Project:   https://github.com/containers/podman
    Website:   https://podman.io
    Documents: https://docs.podman.io
    Twitter:   @Podman_io
    - + \ No newline at end of file diff --git a/docs/kubernetes.html b/docs/kubernetes.html index 6b4689e6974..9f7c20d1fcc 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 240a0b0b1cc..cdd0812a377 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 add7a080389..6304d24e5c6 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 b9c3d7a1554..c3e64bb03d4 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 24c18c9a384..3e58bdd2343 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 7a18d5ea2ea..57426858bf0 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​

    • Podman Desktop has access to:
      • A running container engine.
      • A running Kind 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 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/configuring-podman-for-kind-on-windows.html b/docs/kubernetes/kind/configuring-podman-for-kind-on-windows.html index e495a0c3682..d9703305594 100644 --- a/docs/kubernetes/kind/configuring-podman-for-kind-on-windows.html +++ b/docs/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/kubernetes/kind/creating-a-kind-cluster.html b/docs/kubernetes/kind/creating-a-kind-cluster.html index 1afdc4045e6..2095060cd67 100644 --- a/docs/kubernetes/kind/creating-a-kind-cluster.html +++ b/docs/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/kubernetes/kind/deleting-your-kind-cluster.html b/docs/kubernetes/kind/deleting-your-kind-cluster.html index 16c8692ff1e..a4a9f0f2032 100644 --- a/docs/kubernetes/kind/deleting-your-kind-cluster.html +++ b/docs/kubernetes/kind/deleting-your-kind-cluster.html @@ -13,13 +13,13 @@ - +
    - + \ No newline at end of file diff --git a/docs/kubernetes/kind/installing-kind.html b/docs/kubernetes/kind/installing-kind.html index 3460ae6c10d..66660405157 100644 --- a/docs/kubernetes/kind/installing-kind.html +++ b/docs/kubernetes/kind/installing-kind.html @@ -13,7 +13,7 @@ - + @@ -21,7 +21,7 @@
    - + \ 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 49d7ad3d20a..bae694299a6 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/restarting-your-kind-cluster.html b/docs/kubernetes/kind/restarting-your-kind-cluster.html index dcb49044ad4..d88486e759e 100644 --- a/docs/kubernetes/kind/restarting-your-kind-cluster.html +++ b/docs/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/kubernetes/kind/working-with-your-local-kind-cluster.html b/docs/kubernetes/kind/working-with-your-local-kind-cluster.html index 5489e90c3ec..f380e510793 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.

    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 ecf74dd89c8..f8e1b7dea27 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 ed91273efe6..2cf43a661fc 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 5ad1ab2d288..6fb7ac29e12 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 8fad8f813e7..03da30279d5 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 65dba5003b9..898b2fcffc9 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 70ff346559f..91f05fcd541 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 45e2ae98fc6..decbe193ce5 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 eb123fa6437..cdd2c804904 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 6bc22fdb43d..87f094ad783 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 947984e1d5d..7ed1e213eac 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 f16af92fcd5..1ed44651ea0 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 8f6d746ad94..9f2c388f658 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 bce0d1ec9f1..2487167e5be 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 65b544e3f36..5a2e699ed8b 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 abe69f03a28..03c02ccab5b 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 701e427abeb..69b6a8dd881 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 eef4ae9f133..779a5f5a7b8 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 d6644c0d59b..92cf0565e6c 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 c40774cd3d5..f6715494738 100644 --- a/docs/migrating-from-docker/using-podman-mac-helper.html +++ b/docs/migrating-from-docker/using-podman-mac-helper.html @@ -13,7 +13,7 @@ - + @@ -22,7 +22,7 @@ The service redirects /var/run/docker to the fixed user-assigned UNIX socket location.

    Prerequisites​

    Procedure​

    • Set up the podman-mac-helper service for each user. Run the command:

      sudo podman-mac-helper install

      For additional install options please run the command:

      sudo podman-mac-helper install --help

    Verification​

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

    2. Use the podman-mac-helper tool to run commands. To run a command with Podman by using the podman-mac-helper tool, prefix the command with podman-mac-helper.

      Example:

      $ podman-mac-helper run -it <your_container> bash

    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 e2cec695d52..651f9dc2ef0 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:

      $ export DOCKER_HOST=<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 eb365b062d6..574d6d39969 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/proxy.html b/docs/proxy.html index 9955a337cf7..de5e3df0991 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 ac320b0ee51..409d998a35f 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 417e58d7692..e94c18f541b 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 df9b62d97dc..47095892394 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 3779dc13ae6..ac275a962ed 100644 --- a/docs/proxy/using-a-proxy.html +++ b/docs/proxy/using-a-proxy.html @@ -13,14 +13,14 @@ - +

    Using Podman Desktop behind a proxy on macOS and Windows

    You can configure Podman Desktop to run behind a proxy. The configuration applies to the Podman engine, but not to your containers.

    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. 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/tags.html b/docs/tags.html index b1734c57b79..0ddd7ba6cc4 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 4584fecae99..f443a0b0e24 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/extension.html b/docs/tags/extension.html index 288238da12b..84712e1d771 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 e1a1594c553..ec151e522ed 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 ec3fc155a6a..26aeffe54a0 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/getting-started.html b/docs/tags/getting-started.html index 68968c644e4..714fd93e9f4 100644 --- a/docs/tags/getting-started.html +++ b/docs/tags/getting-started.html @@ -13,13 +13,13 @@ - +

    One doc tagged with "getting-started"

    View All Tags
    - + \ No newline at end of file diff --git a/docs/tags/images.html b/docs/tags/images.html index 3c2b8577689..80b638996bc 100644 --- a/docs/tags/images.html +++ b/docs/tags/images.html @@ -13,13 +13,13 @@ - +

    7 docs tagged with "images"

    View All Tags
    - + \ No newline at end of file diff --git a/docs/tags/installing.html b/docs/tags/installing.html index ff1757c62cd..7cb8f669861 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).

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

    7 docs tagged with "kind"

    View All Tags
    - + \ No newline at end of file diff --git a/docs/tags/lima.html b/docs/tags/lima.html index 85c3e0ca7a3..75fd6cc6d82 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 7dee7df9d96..ca7835cb693 100644 --- a/docs/tags/linux.html +++ b/docs/tags/linux.html @@ -13,13 +13,13 @@ - +

    9 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 288326183ef..95b41a4ee88 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 0bd0c4a3e80..def9d0d993e 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 e68504a9bae..1dcb27de19b 100644 --- a/docs/tags/macos.html +++ b/docs/tags/macos.html @@ -13,13 +13,13 @@ - +

    5 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 044931f5dbc..93fcde83c84 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 9c2a352c972..53d00213ab6 100644 --- a/docs/tags/migrating-to-kubernetes.html +++ b/docs/tags/migrating-to-kubernetes.html @@ -13,13 +13,13 @@ - +

    29 docs tagged with "migrating-to-kubernetes"

    View All Tags

    Kubernetes

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

    - + \ No newline at end of file diff --git a/docs/tags/minikube.html b/docs/tags/minikube.html index 3323e00a5c5..a2223703cf6 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/openshift-local.html b/docs/tags/openshift-local.html index e51e5ced3fa..836b9f8e402 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 8ffd1a999ae..da6b0654f8d 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 182f4f21334..2b75198b472 100644 --- a/docs/tags/podman-desktop.html +++ b/docs/tags/podman-desktop.html @@ -13,13 +13,13 @@ - +

    23 docs tagged with "podman-desktop"

    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).

    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 8fade333c8f..d65424327f2 100644 --- a/docs/tags/podman.html +++ b/docs/tags/podman.html @@ -13,13 +13,13 @@ - +

    4 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 990b59e87a8..ab2a9e8726c 100644 --- a/docs/tags/pods.html +++ b/docs/tags/pods.html @@ -13,13 +13,13 @@ - +

    2 docs tagged with "pods"

    View All Tags
    - + \ No newline at end of file diff --git a/docs/tags/proxy.html b/docs/tags/proxy.html index c00168a1177..4ededee44f4 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 6839d922868..e9cf8dce643 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/restricted-environment.html b/docs/tags/restricted-environment.html index 945e00fd29f..b1db4adf5c6 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 89a794aeb0e..57f1f56f702 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/when-clause.html b/docs/tags/when-clause.html index 0de678518f3..c8d3733ae2a 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 d306f26dae8..6c6eda0dab4 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).

    - + \ No newline at end of file diff --git a/docs/tags/winget.html b/docs/tags/winget.html index 5a91380fce6..43d8103dbc8 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 41d8e46b4f9..673f6dedd6a 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 d04c703c58f..89329ccbbc1 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 3274a8a8f81..11834dc2632 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 30b1ae3c17d..3f478947f9e 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 6dba96f6f1b..238386b659d 100644 --- a/docs/troubleshooting/troubleshooting-podman-on-macos.html +++ b/docs/troubleshooting/troubleshooting-podman-on-macos.html @@ -13,15 +13,15 @@ - +

    Troubleshooting Podman on macOS

    Unable to set custom binary path for Podman on macOS​

    Issue​

    When setting a custom binary path (under Preferences -> Custom binary path), Podman is unable to find gvproxy and podman-mac-helper:

    Error: unable to start host networking: "could not find \"gvproxy\" in one of [/usr/local/opt/podman/libexec /opt/homebrew/bin /opt/homebrew/opt/podman/libexec /usr/local/bin /usr/local/libexec/podman /usr/local/lib/podman /usr/libexec/podman /usr/lib/podman $BINDIR/../libexec/podman].  To resolve this error, set the helper_binaries_dir key in the `[engine]` section of containers.conf to the directory containing your helper binaries."

    Solution​

    1. Download gvproxy from the gvisor-tap-vsock release page.
    2. Build the podman-mac-helper from the source code on the Podman GitHub page.
    3. Add the helpers_binaries_dir entry to ~/.config/containers/conf:
    [containers]

    helper_binaries_dir=["/Users/user/example_directory"]

    NOTE: A pre-built binary will be added to the Podman release page so you do not have to build podman-mac-helper. An issue is open for this.

    Unable to locate Podman Engine​

    Issue​

    Despite having Podman Engine installed, you might receive an error as follows - Error: No such keg: /usr/local/Cellar/podman -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-machine
    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-machine

    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.

    - +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-machine
    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-machine

    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.

    + \ 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 397d07bed07..19bb55ed4b3 100644 --- a/docs/troubleshooting/troubleshooting-podman-on-windows.html +++ b/docs/troubleshooting/troubleshooting-podman-on-windows.html @@ -13,13 +13,13 @@ - +

    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.
    - + \ No newline at end of file diff --git a/docs/troubleshooting/troubleshooting-podman.html b/docs/troubleshooting/troubleshooting-podman.html index 42090611562..b6f862ee8c6 100644 --- a/docs/troubleshooting/troubleshooting-podman.html +++ b/docs/troubleshooting/troubleshooting-podman.html @@ -13,7 +13,7 @@ - + @@ -22,7 +22,7 @@ This is available only on Podman 4.0.2+ So, please check your version and update.

    On Windows, the named pipe is //./pipe/docker_engine when Docker Desktop is not installed. It will be solved by https://github.com/containers/podman/issues/13502 / https://github.com/containers/podman/pull/13655. During that time, you might start Docker Desktop so the named pipe is the one expected.

    Check connection​

    Check at least a Podman machine is running on Windows & macOS:

    podman machine list

    And check a connection can be made with the CLI

    $ podman run quay.io/podman/hello
    !... Hello Podman World ...!

             .--"--.
           / -     - \
          / (O)   (O) \
       ~~~| -=(,Y,)=- |
        .---. /`  \   |~~
     ~/  o  o \~~~~.----. ~~
      | =(X)= |~  / (O (O) \
       ~~~~~~~  ~| =(Y_)=-  |
      ~~~~    ~~~|   U      |~~

    Project:   https://github.com/containers/podman
    Website:   https://podman.io
    Documents: https://docs.podman.io
    Twitter:   @Podman_io

    Unable to see information about active containers​

    Issue​

    In this scenario, the screen might be displaying "No Containers" as shown below despite active containers runnning in the background. img

    Solution​

    There are three ways to work this out.

    1. To solve this issue, open the Terminal and run the following commands-

      podman machine stop
      podman machine start

    2. If this does not work for you, you might proceed with the following commands-

      $ podman machine rm
      $ podman machine init

    3. If both of the abovementioned steps don't work for you, run the following commands-

      $ rm -rf ~/.local/share/containers/podman
      $ rm -rf ~/.config/containers/

      After this, you can start off again by initializing a new Podman Machine and loading up the containers.

    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​

    On macOS:

    1. Stop Docker Desktop (if install)

    2. Run the podman-mac-helper binary:

      sudo podman-mac-helper install

      for additional options please run the command:

      sudo podman-mac-helper install --help

    3. Restart the Podman machine (the default Docker socket path will be recreated and Podman will emulate it)

    On Linux / Windows:

    1. Stop Docker Desktop (if installed)
    2. Restart the Podman machine (the default Docker socket path will be recreated and Podman will emulate it)

    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/downloads.html b/downloads.html index 0e77887906a..f427b944d35 100644 --- a/downloads.html +++ b/downloads.html @@ -13,13 +13,13 @@ - +

    Downloads

    Windows

    Podman Desktop for Windows

    Download NowWindows installer, version
    Other downloads for Windows:
    Windows portable executableWindows installer for restricted environmentsPackage 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 7f9c199ed36..e7c50335413 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 3a0790ff118..f7c49a22653 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 8ec71d63471..2cde0bb6e23 100644 --- a/downloads/windows.html +++ b/downloads/windows.html @@ -13,13 +13,13 @@ - +

    Windows Downloads

    Windows

    Podman Desktop for Windows

    Download NowWindows installer, version
    Other downloads for Windows:
    Windows portable executableWindows installer for restricted environmentsPackage 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 494b495257d..d876824b886 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 63a61b401ea..d914fc54178 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 965d3f1a2e7..fc0a03db998 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

    brew install podman-desktop

    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 8c804cb485e..9c0ee08b41c 100644 --- a/search.html +++ b/search.html @@ -13,13 +13,13 @@ - +

    Search the documentation

    - + \ No newline at end of file