diff --git a/404.html b/404.html index 96bb850ca6f..821cefe11f0 100644 --- a/404.html +++ b/404.html @@ -13,7 +13,7 @@ - + diff --git a/assets/js/4d71dffe.42f65190.js b/assets/js/4d71dffe.42f65190.js deleted file mode 100644 index ff9b405e879..00000000000 --- a/assets/js/4d71dffe.42f65190.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkdocs=self.webpackChunkdocs||[]).push([[816],{66360:(e,n,o)=>{o.r(n),o.d(n,{assets:()=>d,contentTitle:()=>t,default:()=>p,frontMatter:()=>a,metadata:()=>r,toc:()=>c});var i=o(24246),s=o(71670);const a={title:"Getting started with Compose on Podman Desktop",description:"Getting started with Compose on Podman Desktop",slug:"getting-started-with-compose",authors:["cdrage"],tags:["podman-desktop","story","compose","containers","containerfile","docker-compose","dockerfile","multi-container"],hide_table_of_contents:!1},t=void 0,r={permalink:"/blog/getting-started-with-compose",source:"@site/blog/2024-01-02-getting-started-with-compose.md",title:"Getting started with Compose on Podman Desktop",description:"Getting started with Compose on Podman Desktop",date:"2024-01-02T00:00:00.000Z",formattedDate:"January 2, 2024",tags:[{label:"podman-desktop",permalink:"/blog/tags/podman-desktop"},{label:"story",permalink:"/blog/tags/story"},{label:"compose",permalink:"/blog/tags/compose"},{label:"containers",permalink:"/blog/tags/containers"},{label:"containerfile",permalink:"/blog/tags/containerfile"},{label:"docker-compose",permalink:"/blog/tags/docker-compose"},{label:"dockerfile",permalink:"/blog/tags/dockerfile"},{label:"multi-container",permalink:"/blog/tags/multi-container"}],readingTime:4.475,hasTruncateMarker:!1,authors:[{name:"Charlie Drage",title:"Software Engineer",url:"https://github.com/cdrage",imageURL:"https://github.com/cdrage.png",key:"cdrage"}],frontMatter:{title:"Getting started with Compose on Podman Desktop",description:"Getting started with Compose on Podman Desktop",slug:"getting-started-with-compose",authors:["cdrage"],tags:["podman-desktop","story","compose","containers","containerfile","docker-compose","dockerfile","multi-container"],hide_table_of_contents:!1},unlisted:!1,nextItem:{title:"Release Notes - Podman Desktop 1.6",permalink:"/blog/podman-desktop-release-1.6"}},d={authorsImageUrls:[void 0]},c=[{value:"Objectives",id:"objectives",level:2},{value:"What is Compose",id:"what-is-compose",level:2},{value:"Before we begin",id:"before-we-begin",level:2},{value:"Download and run the example application",id:"download-and-run-the-example-application",level:2},{value:"Viewing the guestbook application",id:"viewing-the-guestbook-application",level:2},{value:"Viewing and modifying the database",id:"viewing-and-modifying-the-database",level:2},{value:"How does it work?",id:"how-does-it-work",level:2},{value:"Scaling more replicas",id:"scaling-more-replicas",level:2}];function l(e){const n={a:"a",code:"code",h2:"h2",img:"img",li:"li",ol:"ol",p:"p",pre:"pre",strong:"strong",ul:"ul",...(0,s.a)(),...e.components},{Icon:a}=n;return a||function(e,n){throw new Error("Expected "+(n?"component":"object")+" `"+e+"` to be defined: you likely forgot to import, pass, or provide it.")}("Icon",!0),(0,i.jsxs)(i.Fragment,{children:[(0,i.jsx)(n.p,{children:"In this blog post we will learn how take a multi-container Compose application and use it within Podman Desktop."}),"\n",(0,i.jsx)(n.h2,{id:"objectives",children:"Objectives"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["Start the Compose YAML through ",(0,i.jsx)(n.code,{children:"podman compose up"}),"."]}),"\n",(0,i.jsx)(n.li,{children:"View the guestbook web application."}),"\n",(0,i.jsx)(n.li,{children:"Confirm the web application is being synchronized and running correctly with the database."}),"\n",(0,i.jsx)(n.li,{children:"Use Podman Desktop to view, inspect and access the terminal of the Redis cluster."}),"\n"]}),"\n",(0,i.jsx)(n.h2,{id:"what-is-compose",children:"What is Compose"}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.a,{href:"https://www.compose-spec.io/",children:"Compose is a specification"})," for defining and running multi-container Docker applications. With pose, you use a YAML file to configure your application\u2019s services, networks, and volumes. This allows you to capture in a single file the entire configuration necessary to run a set of interconnected containers as an application. For example, if you have an application that requires a web server, a database, and a caching service, you can define these components and their relationships in your Compose file."]}),"\n",(0,i.jsxs)(n.p,{children:["To use the Compose YAML, you can use a specification implementation such as ",(0,i.jsx)(n.a,{href:"https://docs.podman.io/en/latest/markdown/podman-compose.1.html",children:(0,i.jsx)(n.code,{children:"podman compose"})})," and ",(0,i.jsx)(n.a,{href:"https://github.com/docker/compose",children:(0,i.jsx)(n.code,{children:"docker compose"})}),"."]}),"\n",(0,i.jsx)(n.h2,{id:"before-we-begin",children:"Before we begin"}),"\n",(0,i.jsx)(n.p,{children:"If you do not have Compose installed, let's go through the onboarding process to install the Compose implementation binary:"}),"\n",(0,i.jsxs)(n.ol,{children:["\n",(0,i.jsxs)(n.li,{children:["Get to Resources under ",(0,i.jsxs)(n.strong,{children:[(0,i.jsx)(a,{icon:"fa-solid fa-cog",size:"lg"})," Settings > Resources"]}),"."]}),"\n",(0,i.jsxs)(n.li,{children:["Click ",(0,i.jsx)(n.strong,{children:"Setup"})," under Compose (it will appear if it has not been installed yet)."]}),"\n",(0,i.jsx)(n.li,{children:"Go through the onboarding process."}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.img,{alt:"Onboarding process",src:o(29856).Z+"",width:"1222",height:"946"})}),"\n",(0,i.jsxs)(n.p,{children:["Confirm that you are able to run ",(0,i.jsx)(n.code,{children:"podman compose"}),":"]}),"\n",(0,i.jsx)(n.pre,{children:(0,i.jsx)(n.code,{className:"language-sh",children:"podman compose\nRun compose workloads via an external provider such as docker-compose or podman-compose\n\nDescription:\n This command is a thin wrapper around an external compose provider such as docker-compose or podman-compose. This means that podman compose is executing another tool that implements the compose functionality but sets up the environment in a way to let the compose provider communicate transparently with the local Podman socket. The specified options as well the command and argument are passed directly to the compose provider.\n...\n"})}),"\n",(0,i.jsx)(n.h2,{id:"download-and-run-the-example-application",children:"Download and run the example application"}),"\n",(0,i.jsxs)(n.p,{children:["Our example application is located at ",(0,i.jsx)(n.a,{href:"https://github.com/redhat-developer/podman-desktop-compose-example",children:"github.com/redhat-developer/podman-desktop-compose-example"}),"."]}),"\n",(0,i.jsxs)(n.p,{children:["We will use ",(0,i.jsx)(n.code,{children:"git clone"})," so we can build the Go binary web application:"]}),"\n",(0,i.jsx)(n.pre,{children:(0,i.jsx)(n.code,{className:"language-sh",children:"git clone https://github.com/redhat-developer/podman-desktop-compose-example\ncd podman-desktop-compose-example\n"})}),"\n",(0,i.jsxs)(n.p,{children:["Run ",(0,i.jsx)(n.code,{children:"podman compose up -d"})," to start the application:"]}),"\n",(0,i.jsx)(n.pre,{children:(0,i.jsx)(n.code,{className:"language-sh",children:'podman compose up -d\n>>>> Executing external compose provider "/usr/local/bin/docker-compose". Please refer to the documentation for details. <<<<\n\n[+] Running 3/3\n \u2714 Container redis-replica Started 0.0s\n \u2714 Container web Started 0.0s\n \u2714 Container redis-leader Started 0.0s\n'})}),"\n",(0,i.jsx)(n.h2,{id:"viewing-the-guestbook-application",children:"Viewing the guestbook application"}),"\n",(0,i.jsx)(n.p,{children:"Within Podman Desktop, you can now see that all three containers are up and operational."}),"\n",(0,i.jsx)(n.p,{children:'Click the "Open Browser" button to view the web application:'}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.img,{alt:"Open browser",src:o(10517).Z+"",width:"1098",height:"812"})}),"\n",(0,i.jsx)(n.p,{children:"Within the Guestbook web application, you can:"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:'"Sign" the guestbook, which will write to the Redis leader and synchronize to the replicas.'}),"\n",(0,i.jsx)(n.li,{children:'"Read" from the guestbook, which will read from the pool of Redis replicas. This allows for readability even if the Redis leader is unavailable.'}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.code,{children:"/env"}),": View the container's environment variables."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.code,{children:"/info"}),": View information about the Redis cluster."]}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.img,{alt:"Guestbook application",src:o(23698).Z+"",width:"949",height:"653"})}),"\n",(0,i.jsx)(n.h2,{id:"viewing-and-modifying-the-database",children:"Viewing and modifying the database"}),"\n",(0,i.jsx)(n.p,{children:"Using Podman Desktop, you can also access the container's terminal directly from the GUI and modify the database."}),"\n",(0,i.jsxs)(n.p,{children:['Click "Open Terminal" to access the ',(0,i.jsx)(n.code,{children:"redis-leader"})," terminal:"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.img,{alt:"Open terminal",src:o(70256).Z+"",width:"1353",height:"1003"})}),"\n",(0,i.jsx)(n.p,{children:"Modify the database as if you are doing database administration:"}),"\n",(0,i.jsxs)(n.ol,{children:["\n",(0,i.jsxs)(n.li,{children:["Run ",(0,i.jsx)(n.code,{children:"redis-cli"})," within the container to access the Redis database."]}),"\n",(0,i.jsxs)(n.li,{children:["Type ",(0,i.jsx)(n.code,{children:'LPUSH guestbook "Hello World!"'})," and you will see your web application update in real-time."]}),"\n",(0,i.jsxs)(n.li,{children:["Type ",(0,i.jsx)(n.code,{children:"DEL guestbook"})," and you will see that your database drops the ",(0,i.jsx)(n.code,{children:"guestbook"})," key and clears the database."]}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.img,{alt:"Redis CLI",src:o(24207).Z+"",width:"1353",height:"1003"})}),"\n",(0,i.jsx)(n.p,{children:"Changes will reflect in real-time on the guestbook."}),"\n",(0,i.jsx)(n.p,{children:"You can further modify the database and see the changes propagate to the Redis replicas."}),"\n",(0,i.jsxs)(n.p,{children:["For example, view the logs of the ",(0,i.jsx)(n.code,{children:"redis-replica"}),", and you will notice that there are periodic database synchronizations as well as reads to the database:"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.img,{alt:"Redis replica logs",src:o(58645).Z+"",width:"1353",height:"1003"})}),"\n",(0,i.jsx)(n.h2,{id:"how-does-it-work",children:"How does it work?"}),"\n",(0,i.jsx)(n.p,{children:"A quick overview of how the architecture works in this multi-container scenario:"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["Within the Guestbook application, it looks for a database with the names ",(0,i.jsx)(n.code,{children:"redis-leader"})," and ",(0,i.jsx)(n.code,{children:"redis-replica"})," on port 6379."]}),"\n",(0,i.jsx)(n.li,{children:"Because it is a Compose application, the containers are connected on the same network. This means that a neighboring container can be network-accessible simply by its container name."}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:"There is a set of environment variables that the web application can modify in the Compose application:"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.code,{children:"REDIS_LEADER"}),": The default is ",(0,i.jsx)(n.code,{children:"redis-leader"}),"."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.code,{children:"REDIS_REPLICAS"}),": The default is ",(0,i.jsx)(n.code,{children:"redis-replica"}),". Can be comma-separated, such as ",(0,i.jsx)(n.code,{children:"redis-replica-1,redis-replica-2"}),"."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.code,{children:"REDIS_PORT"}),": The default is ",(0,i.jsx)(n.code,{children:"6379"}),"."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.code,{children:"SERVER_PORT"}),": The default is ",(0,i.jsx)(n.code,{children:"8080"}),"."]}),"\n"]}),"\n",(0,i.jsx)(n.h2,{id:"scaling-more-replicas",children:"Scaling more replicas"}),"\n",(0,i.jsxs)(n.p,{children:["Want to scale more replicas? This can be achieved by adding an environment variable to your ",(0,i.jsx)(n.code,{children:"compose.yaml"})," and duplicating your ",(0,i.jsx)(n.code,{children:"redis-replica"})," entry."]}),"\n",(0,i.jsxs)(n.p,{children:["Modify your ",(0,i.jsx)(n.code,{children:"compose.yaml"})," as follows:"]}),"\n",(0,i.jsx)(n.pre,{children:(0,i.jsx)(n.code,{className:"language-yaml",children:"services:\n redis-leader:\n container_name: redis-leader\n image: redis:latest\n ports:\n - '6379'\n\n redis-replica:\n container_name: redis-replica\n image: redis:latest\n ports:\n - '6379'\n command: redis-server --replicaof redis-leader 6379\n\n redis-replica-2:\n container_name: redis-replica-2\n image: redis:latest\n ports:\n - '6379'\n command: redis-server --replicaof redis-leader 6379\n\n web:\n container_name: web\n build: ./web\n environment:\n - REDIS_REPLICAS=redis-replica1,redis-replica2\n ports:\n - '8080:8080'\n"})}),"\n",(0,i.jsxs)(n.p,{children:["Run ",(0,i.jsx)(n.code,{children:"podman compose up -d"})," again to ensure the new container has been added and the new environment variable has propagated:"]}),"\n",(0,i.jsx)(n.pre,{children:(0,i.jsx)(n.code,{className:"language-sh",children:'podman compose up -d\n>>>> Executing external compose provider "/usr/local/bin/docker-compose". Please refer to the documentation for details. <<<<\n\n[+] Running 4/4\n \u2714 Container redis-replica-2 Started 0.0s\n \u2714 Container redis-leader Running 0.0s\n \u2714 Container web Started 0.0s\n \u2714 Container redis-replica Running 0.0s\n'})})]})}function p(e={}){const{wrapper:n}={...(0,s.a)(),...e.components};return n?(0,i.jsx)(n,{...e,children:(0,i.jsx)(l,{...e})}):l(e)}},23698:(e,n,o)=>{o.d(n,{Z:()=>i});const i=o.p+"assets/images/helloworld-516adc89ef8a509fb5ce998d3b0ea94b.png"},29856:(e,n,o)=>{o.d(n,{Z:()=>i});const i=o.p+"assets/images/onboarding-9b66ae02eaf2ebbec75dd092f78f26a3.png"},10517:(e,n,o)=>{o.d(n,{Z:()=>i});const i=o.p+"assets/images/openbrowser-9e28829878b62d868b2194a5a341fa1e.png"},70256:(e,n,o)=>{o.d(n,{Z:()=>i});const i=o.p+"assets/images/openterminal-648b30f8ad2add37bf4d5bafc37bfd46.png"},24207:(e,n,o)=>{o.d(n,{Z:()=>i});const i=o.p+"assets/images/redis-cli-d4648788bc57c0d57e0a7cdae4475d1d.png"},58645:(e,n,o)=>{o.d(n,{Z:()=>i});const i=o.p+"assets/images/redisreplica-31a441bbbe1383b80fb79a2f4dd52c56.png"},71670:(e,n,o)=>{o.d(n,{Z:()=>r,a:()=>t});var i=o(27378);const s={},a=i.createContext(s);function t(e){const n=i.useContext(a);return i.useMemo((function(){return"function"==typeof e?e(n):{...n,...e}}),[n,e])}function r(e){let n;return n=e.disableParentContext?"function"==typeof e.components?e.components(s):e.components||s:t(e.components),i.createElement(a.Provider,{value:n},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/4d71dffe.793f696b.js b/assets/js/4d71dffe.793f696b.js new file mode 100644 index 00000000000..d9fea1c29eb --- /dev/null +++ b/assets/js/4d71dffe.793f696b.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkdocs=self.webpackChunkdocs||[]).push([[816],{66360:(e,n,o)=>{o.r(n),o.d(n,{assets:()=>d,contentTitle:()=>t,default:()=>p,frontMatter:()=>a,metadata:()=>r,toc:()=>c});var i=o(24246),s=o(71670);const a={title:"Getting started with Compose on Podman Desktop",description:"Getting started with Compose on Podman Desktop",slug:"getting-started-with-compose",authors:["cdrage"],tags:["podman-desktop","story","compose","containers","containerfile","docker-compose","dockerfile","multi-container"],hide_table_of_contents:!1},t=void 0,r={permalink:"/blog/getting-started-with-compose",source:"@site/blog/2024-01-02-getting-started-with-compose.md",title:"Getting started with Compose on Podman Desktop",description:"Getting started with Compose on Podman Desktop",date:"2024-01-02T00:00:00.000Z",formattedDate:"January 2, 2024",tags:[{label:"podman-desktop",permalink:"/blog/tags/podman-desktop"},{label:"story",permalink:"/blog/tags/story"},{label:"compose",permalink:"/blog/tags/compose"},{label:"containers",permalink:"/blog/tags/containers"},{label:"containerfile",permalink:"/blog/tags/containerfile"},{label:"docker-compose",permalink:"/blog/tags/docker-compose"},{label:"dockerfile",permalink:"/blog/tags/dockerfile"},{label:"multi-container",permalink:"/blog/tags/multi-container"}],readingTime:4.475,hasTruncateMarker:!1,authors:[{name:"Charlie Drage",title:"Software Engineer",url:"https://github.com/cdrage",imageURL:"https://github.com/cdrage.png",key:"cdrage"}],frontMatter:{title:"Getting started with Compose on Podman Desktop",description:"Getting started with Compose on Podman Desktop",slug:"getting-started-with-compose",authors:["cdrage"],tags:["podman-desktop","story","compose","containers","containerfile","docker-compose","dockerfile","multi-container"],hide_table_of_contents:!1},unlisted:!1,nextItem:{title:"Release Notes - Podman Desktop 1.6",permalink:"/blog/podman-desktop-release-1.6"}},d={authorsImageUrls:[void 0]},c=[{value:"Objectives",id:"objectives",level:2},{value:"What is Compose",id:"what-is-compose",level:2},{value:"Before we begin",id:"before-we-begin",level:2},{value:"Download and run the example application",id:"download-and-run-the-example-application",level:2},{value:"Viewing the guestbook application",id:"viewing-the-guestbook-application",level:2},{value:"Viewing and modifying the database",id:"viewing-and-modifying-the-database",level:2},{value:"How does it work?",id:"how-does-it-work",level:2},{value:"Scaling more replicas",id:"scaling-more-replicas",level:2}];function l(e){const n={a:"a",code:"code",h2:"h2",img:"img",li:"li",ol:"ol",p:"p",pre:"pre",strong:"strong",ul:"ul",...(0,s.a)(),...e.components},{Icon:a}=n;return a||function(e,n){throw new Error("Expected "+(n?"component":"object")+" `"+e+"` to be defined: you likely forgot to import, pass, or provide it.")}("Icon",!0),(0,i.jsxs)(i.Fragment,{children:[(0,i.jsx)(n.p,{children:"In this blog post we will learn how take a multi-container Compose application and use it within Podman Desktop."}),"\n",(0,i.jsx)(n.h2,{id:"objectives",children:"Objectives"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["Start the Compose YAML through ",(0,i.jsx)(n.code,{children:"podman compose up"}),"."]}),"\n",(0,i.jsx)(n.li,{children:"View the guestbook web application."}),"\n",(0,i.jsx)(n.li,{children:"Confirm the web application is being synchronized and running correctly with the database."}),"\n",(0,i.jsx)(n.li,{children:"Use Podman Desktop to view, inspect and access the terminal of the Redis cluster."}),"\n"]}),"\n",(0,i.jsx)(n.h2,{id:"what-is-compose",children:"What is Compose"}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.a,{href:"https://www.compose-spec.io/",children:"Compose is a specification"})," for defining and running multi-container Docker applications. With pose, you use a YAML file to configure your application\u2019s services, networks, and volumes. This allows you to capture in a single file the entire configuration necessary to run a set of interconnected containers as an application. For example, if you have an application that requires a web server, a database, and a caching service, you can define these components and their relationships in your Compose file."]}),"\n",(0,i.jsxs)(n.p,{children:["To use the Compose YAML, you can use a specification implementation such as ",(0,i.jsx)(n.a,{href:"https://docs.podman.io/en/latest/markdown/podman-compose.1.html",children:(0,i.jsx)(n.code,{children:"podman compose"})})," and ",(0,i.jsx)(n.a,{href:"https://github.com/docker/compose",children:(0,i.jsx)(n.code,{children:"docker compose"})}),"."]}),"\n",(0,i.jsx)(n.h2,{id:"before-we-begin",children:"Before we begin"}),"\n",(0,i.jsx)(n.p,{children:"If you do not have Compose installed, let's go through the onboarding process to install the Compose implementation binary:"}),"\n",(0,i.jsxs)(n.ol,{children:["\n",(0,i.jsxs)(n.li,{children:["Get to Resources under ",(0,i.jsxs)(n.strong,{children:[(0,i.jsx)(a,{icon:"fa-solid fa-cog",size:"lg"})," Settings > Resources"]}),"."]}),"\n",(0,i.jsxs)(n.li,{children:["Click ",(0,i.jsx)(n.strong,{children:"Setup"})," under Compose (it will appear if it has not been installed yet)."]}),"\n",(0,i.jsx)(n.li,{children:"Go through the onboarding process."}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.img,{alt:"Onboarding process",src:o(29856).Z+"",width:"1222",height:"946"})}),"\n",(0,i.jsxs)(n.p,{children:["Confirm that you are able to run ",(0,i.jsx)(n.code,{children:"podman compose"}),":"]}),"\n",(0,i.jsx)(n.pre,{children:(0,i.jsx)(n.code,{className:"language-sh",children:"podman compose\nRun compose workloads via an external provider such as docker-compose or podman-compose\n\nDescription:\n This command is a thin wrapper around an external compose provider such as docker-compose or podman-compose. This means that podman compose is executing another tool that implements the compose functionality but sets up the environment in a way to let the compose provider communicate transparently with the local Podman socket. The specified options as well the command and argument are passed directly to the compose provider.\n...\n"})}),"\n",(0,i.jsx)(n.h2,{id:"download-and-run-the-example-application",children:"Download and run the example application"}),"\n",(0,i.jsxs)(n.p,{children:["Our example application is located at ",(0,i.jsx)(n.a,{href:"https://github.com/redhat-developer/podman-desktop-demo",children:"github.com/redhat-developer/podman-desktop-demo"}),"."]}),"\n",(0,i.jsxs)(n.p,{children:["We will use ",(0,i.jsx)(n.code,{children:"git clone"})," so we can build the Go binary web application:"]}),"\n",(0,i.jsx)(n.pre,{children:(0,i.jsx)(n.code,{className:"language-sh",children:"git clone https://github.com/redhat-developer/podman-desktop-demo\ncd podman-desktop-demo/guestbook-compose\n"})}),"\n",(0,i.jsxs)(n.p,{children:["Run ",(0,i.jsx)(n.code,{children:"podman compose up -d"})," to start the application:"]}),"\n",(0,i.jsx)(n.pre,{children:(0,i.jsx)(n.code,{className:"language-sh",children:'podman compose up -d\n>>>> Executing external compose provider "/usr/local/bin/docker-compose". Please refer to the documentation for details. <<<<\n\n[+] Running 3/3\n \u2714 Container redis-replica Started 0.0s\n \u2714 Container web Started 0.0s\n \u2714 Container redis-leader Started 0.0s\n'})}),"\n",(0,i.jsx)(n.h2,{id:"viewing-the-guestbook-application",children:"Viewing the guestbook application"}),"\n",(0,i.jsx)(n.p,{children:"Within Podman Desktop, you can now see that all three containers are up and operational."}),"\n",(0,i.jsx)(n.p,{children:'Click the "Open Browser" button to view the web application:'}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.img,{alt:"Open browser",src:o(10517).Z+"",width:"1098",height:"812"})}),"\n",(0,i.jsx)(n.p,{children:"Within the Guestbook web application, you can:"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:'"Sign" the guestbook, which will write to the Redis leader and synchronize to the replicas.'}),"\n",(0,i.jsx)(n.li,{children:'"Read" from the guestbook, which will read from the pool of Redis replicas. This allows for readability even if the Redis leader is unavailable.'}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.code,{children:"/env"}),": View the container's environment variables."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.code,{children:"/info"}),": View information about the Redis cluster."]}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.img,{alt:"Guestbook application",src:o(23698).Z+"",width:"949",height:"653"})}),"\n",(0,i.jsx)(n.h2,{id:"viewing-and-modifying-the-database",children:"Viewing and modifying the database"}),"\n",(0,i.jsx)(n.p,{children:"Using Podman Desktop, you can also access the container's terminal directly from the GUI and modify the database."}),"\n",(0,i.jsxs)(n.p,{children:['Click "Open Terminal" to access the ',(0,i.jsx)(n.code,{children:"redis-leader"})," terminal:"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.img,{alt:"Open terminal",src:o(70256).Z+"",width:"1353",height:"1003"})}),"\n",(0,i.jsx)(n.p,{children:"Modify the database as if you are doing database administration:"}),"\n",(0,i.jsxs)(n.ol,{children:["\n",(0,i.jsxs)(n.li,{children:["Run ",(0,i.jsx)(n.code,{children:"redis-cli"})," within the container to access the Redis database."]}),"\n",(0,i.jsxs)(n.li,{children:["Type ",(0,i.jsx)(n.code,{children:'LPUSH guestbook "Hello World!"'})," and you will see your web application update in real-time."]}),"\n",(0,i.jsxs)(n.li,{children:["Type ",(0,i.jsx)(n.code,{children:"DEL guestbook"})," and you will see that your database drops the ",(0,i.jsx)(n.code,{children:"guestbook"})," key and clears the database."]}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.img,{alt:"Redis CLI",src:o(24207).Z+"",width:"1353",height:"1003"})}),"\n",(0,i.jsx)(n.p,{children:"Changes will reflect in real-time on the guestbook."}),"\n",(0,i.jsx)(n.p,{children:"You can further modify the database and see the changes propagate to the Redis replicas."}),"\n",(0,i.jsxs)(n.p,{children:["For example, view the logs of the ",(0,i.jsx)(n.code,{children:"redis-replica"}),", and you will notice that there are periodic database synchronizations as well as reads to the database:"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.img,{alt:"Redis replica logs",src:o(58645).Z+"",width:"1353",height:"1003"})}),"\n",(0,i.jsx)(n.h2,{id:"how-does-it-work",children:"How does it work?"}),"\n",(0,i.jsx)(n.p,{children:"A quick overview of how the architecture works in this multi-container scenario:"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["Within the Guestbook application, it looks for a database with the names ",(0,i.jsx)(n.code,{children:"redis-leader"})," and ",(0,i.jsx)(n.code,{children:"redis-replica"})," on port 6379."]}),"\n",(0,i.jsx)(n.li,{children:"Because it is a Compose application, the containers are connected on the same network. This means that a neighboring container can be network-accessible simply by its container name."}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:"There is a set of environment variables that the web application can modify in the Compose application:"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.code,{children:"REDIS_LEADER"}),": The default is ",(0,i.jsx)(n.code,{children:"redis-leader"}),"."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.code,{children:"REDIS_REPLICAS"}),": The default is ",(0,i.jsx)(n.code,{children:"redis-replica"}),". Can be comma-separated, such as ",(0,i.jsx)(n.code,{children:"redis-replica-1,redis-replica-2"}),"."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.code,{children:"REDIS_PORT"}),": The default is ",(0,i.jsx)(n.code,{children:"6379"}),"."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.code,{children:"SERVER_PORT"}),": The default is ",(0,i.jsx)(n.code,{children:"8080"}),"."]}),"\n"]}),"\n",(0,i.jsx)(n.h2,{id:"scaling-more-replicas",children:"Scaling more replicas"}),"\n",(0,i.jsxs)(n.p,{children:["Want to scale more replicas? This can be achieved by adding an environment variable to your ",(0,i.jsx)(n.code,{children:"compose.yaml"})," and duplicating your ",(0,i.jsx)(n.code,{children:"redis-replica"})," entry."]}),"\n",(0,i.jsxs)(n.p,{children:["Modify your ",(0,i.jsx)(n.code,{children:"compose.yaml"})," as follows:"]}),"\n",(0,i.jsx)(n.pre,{children:(0,i.jsx)(n.code,{className:"language-yaml",children:"services:\n redis-leader:\n container_name: redis-leader\n image: redis:latest\n ports:\n - '6379'\n\n redis-replica:\n container_name: redis-replica\n image: redis:latest\n ports:\n - '6379'\n command: redis-server --replicaof redis-leader 6379\n\n redis-replica-2:\n container_name: redis-replica-2\n image: redis:latest\n ports:\n - '6379'\n command: redis-server --replicaof redis-leader 6379\n\n web:\n container_name: web\n build: ./web\n environment:\n - REDIS_REPLICAS=redis-replica1,redis-replica2\n ports:\n - '8080:8080'\n"})}),"\n",(0,i.jsxs)(n.p,{children:["Run ",(0,i.jsx)(n.code,{children:"podman compose up -d"})," again to ensure the new container has been added and the new environment variable has propagated:"]}),"\n",(0,i.jsx)(n.pre,{children:(0,i.jsx)(n.code,{className:"language-sh",children:'podman compose up -d\n>>>> Executing external compose provider "/usr/local/bin/docker-compose". Please refer to the documentation for details. <<<<\n\n[+] Running 4/4\n \u2714 Container redis-replica-2 Started 0.0s\n \u2714 Container redis-leader Running 0.0s\n \u2714 Container web Started 0.0s\n \u2714 Container redis-replica Running 0.0s\n'})})]})}function p(e={}){const{wrapper:n}={...(0,s.a)(),...e.components};return n?(0,i.jsx)(n,{...e,children:(0,i.jsx)(l,{...e})}):l(e)}},23698:(e,n,o)=>{o.d(n,{Z:()=>i});const i=o.p+"assets/images/helloworld-516adc89ef8a509fb5ce998d3b0ea94b.png"},29856:(e,n,o)=>{o.d(n,{Z:()=>i});const i=o.p+"assets/images/onboarding-9b66ae02eaf2ebbec75dd092f78f26a3.png"},10517:(e,n,o)=>{o.d(n,{Z:()=>i});const i=o.p+"assets/images/openbrowser-9e28829878b62d868b2194a5a341fa1e.png"},70256:(e,n,o)=>{o.d(n,{Z:()=>i});const i=o.p+"assets/images/openterminal-648b30f8ad2add37bf4d5bafc37bfd46.png"},24207:(e,n,o)=>{o.d(n,{Z:()=>i});const i=o.p+"assets/images/redis-cli-d4648788bc57c0d57e0a7cdae4475d1d.png"},58645:(e,n,o)=>{o.d(n,{Z:()=>i});const i=o.p+"assets/images/redisreplica-31a441bbbe1383b80fb79a2f4dd52c56.png"},71670:(e,n,o)=>{o.d(n,{Z:()=>r,a:()=>t});var i=o(27378);const s={},a=i.createContext(s);function t(e){const n=i.useContext(a);return i.useMemo((function(){return"function"==typeof e?e(n):{...n,...e}}),[n,e])}function r(e){let n;return n=e.disableParentContext?"function"==typeof e.components?e.components(s):e.components||s:t(e.components),i.createElement(a.Provider,{value:n},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/8873cf50.cdb9f62c.js b/assets/js/8873cf50.cdb9f62c.js new file mode 100644 index 00000000000..6dc2689d608 --- /dev/null +++ b/assets/js/8873cf50.cdb9f62c.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkdocs=self.webpackChunkdocs||[]).push([[485],{16472:(e,n,o)=>{o.r(n),o.d(n,{assets:()=>d,contentTitle:()=>t,default:()=>p,frontMatter:()=>a,metadata:()=>r,toc:()=>c});var i=o(24246),s=o(71670);const a={title:"Getting started with Compose on Podman Desktop",description:"Getting started with Compose on Podman Desktop",slug:"getting-started-with-compose",authors:["cdrage"],tags:["podman-desktop","story","compose","containers","containerfile","docker-compose","dockerfile","multi-container"],hide_table_of_contents:!1},t=void 0,r={permalink:"/blog/getting-started-with-compose",source:"@site/blog/2024-01-02-getting-started-with-compose.md",title:"Getting started with Compose on Podman Desktop",description:"Getting started with Compose on Podman Desktop",date:"2024-01-02T00:00:00.000Z",formattedDate:"January 2, 2024",tags:[{label:"podman-desktop",permalink:"/blog/tags/podman-desktop"},{label:"story",permalink:"/blog/tags/story"},{label:"compose",permalink:"/blog/tags/compose"},{label:"containers",permalink:"/blog/tags/containers"},{label:"containerfile",permalink:"/blog/tags/containerfile"},{label:"docker-compose",permalink:"/blog/tags/docker-compose"},{label:"dockerfile",permalink:"/blog/tags/dockerfile"},{label:"multi-container",permalink:"/blog/tags/multi-container"}],readingTime:4.475,hasTruncateMarker:!1,authors:[{name:"Charlie Drage",title:"Software Engineer",url:"https://github.com/cdrage",imageURL:"https://github.com/cdrage.png",key:"cdrage"}],frontMatter:{title:"Getting started with Compose on Podman Desktop",description:"Getting started with Compose on Podman Desktop",slug:"getting-started-with-compose",authors:["cdrage"],tags:["podman-desktop","story","compose","containers","containerfile","docker-compose","dockerfile","multi-container"],hide_table_of_contents:!1},unlisted:!1,nextItem:{title:"Release Notes - Podman Desktop 1.6",permalink:"/blog/podman-desktop-release-1.6"}},d={authorsImageUrls:[void 0]},c=[{value:"Objectives",id:"objectives",level:2},{value:"What is Compose",id:"what-is-compose",level:2},{value:"Before we begin",id:"before-we-begin",level:2},{value:"Download and run the example application",id:"download-and-run-the-example-application",level:2},{value:"Viewing the guestbook application",id:"viewing-the-guestbook-application",level:2},{value:"Viewing and modifying the database",id:"viewing-and-modifying-the-database",level:2},{value:"How does it work?",id:"how-does-it-work",level:2},{value:"Scaling more replicas",id:"scaling-more-replicas",level:2}];function l(e){const n={a:"a",code:"code",h2:"h2",img:"img",li:"li",ol:"ol",p:"p",pre:"pre",strong:"strong",ul:"ul",...(0,s.a)(),...e.components},{Icon:a}=n;return a||function(e,n){throw new Error("Expected "+(n?"component":"object")+" `"+e+"` to be defined: you likely forgot to import, pass, or provide it.")}("Icon",!0),(0,i.jsxs)(i.Fragment,{children:[(0,i.jsx)(n.p,{children:"In this blog post we will learn how take a multi-container Compose application and use it within Podman Desktop."}),"\n",(0,i.jsx)(n.h2,{id:"objectives",children:"Objectives"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["Start the Compose YAML through ",(0,i.jsx)(n.code,{children:"podman compose up"}),"."]}),"\n",(0,i.jsx)(n.li,{children:"View the guestbook web application."}),"\n",(0,i.jsx)(n.li,{children:"Confirm the web application is being synchronized and running correctly with the database."}),"\n",(0,i.jsx)(n.li,{children:"Use Podman Desktop to view, inspect and access the terminal of the Redis cluster."}),"\n"]}),"\n",(0,i.jsx)(n.h2,{id:"what-is-compose",children:"What is Compose"}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.a,{href:"https://www.compose-spec.io/",children:"Compose is a specification"})," for defining and running multi-container Docker applications. With pose, you use a YAML file to configure your application\u2019s services, networks, and volumes. This allows you to capture in a single file the entire configuration necessary to run a set of interconnected containers as an application. For example, if you have an application that requires a web server, a database, and a caching service, you can define these components and their relationships in your Compose file."]}),"\n",(0,i.jsxs)(n.p,{children:["To use the Compose YAML, you can use a specification implementation such as ",(0,i.jsx)(n.a,{href:"https://docs.podman.io/en/latest/markdown/podman-compose.1.html",children:(0,i.jsx)(n.code,{children:"podman compose"})})," and ",(0,i.jsx)(n.a,{href:"https://github.com/docker/compose",children:(0,i.jsx)(n.code,{children:"docker compose"})}),"."]}),"\n",(0,i.jsx)(n.h2,{id:"before-we-begin",children:"Before we begin"}),"\n",(0,i.jsx)(n.p,{children:"If you do not have Compose installed, let's go through the onboarding process to install the Compose implementation binary:"}),"\n",(0,i.jsxs)(n.ol,{children:["\n",(0,i.jsxs)(n.li,{children:["Get to Resources under ",(0,i.jsxs)(n.strong,{children:[(0,i.jsx)(a,{icon:"fa-solid fa-cog",size:"lg"})," Settings > Resources"]}),"."]}),"\n",(0,i.jsxs)(n.li,{children:["Click ",(0,i.jsx)(n.strong,{children:"Setup"})," under Compose (it will appear if it has not been installed yet)."]}),"\n",(0,i.jsx)(n.li,{children:"Go through the onboarding process."}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.img,{alt:"Onboarding process",src:o(29856).Z+"",width:"1222",height:"946"})}),"\n",(0,i.jsxs)(n.p,{children:["Confirm that you are able to run ",(0,i.jsx)(n.code,{children:"podman compose"}),":"]}),"\n",(0,i.jsx)(n.pre,{children:(0,i.jsx)(n.code,{className:"language-sh",children:"podman compose\nRun compose workloads via an external provider such as docker-compose or podman-compose\n\nDescription:\n This command is a thin wrapper around an external compose provider such as docker-compose or podman-compose. This means that podman compose is executing another tool that implements the compose functionality but sets up the environment in a way to let the compose provider communicate transparently with the local Podman socket. The specified options as well the command and argument are passed directly to the compose provider.\n...\n"})}),"\n",(0,i.jsx)(n.h2,{id:"download-and-run-the-example-application",children:"Download and run the example application"}),"\n",(0,i.jsxs)(n.p,{children:["Our example application is located at ",(0,i.jsx)(n.a,{href:"https://github.com/redhat-developer/podman-desktop-demo",children:"github.com/redhat-developer/podman-desktop-demo"}),"."]}),"\n",(0,i.jsxs)(n.p,{children:["We will use ",(0,i.jsx)(n.code,{children:"git clone"})," so we can build the Go binary web application:"]}),"\n",(0,i.jsx)(n.pre,{children:(0,i.jsx)(n.code,{className:"language-sh",children:"git clone https://github.com/redhat-developer/podman-desktop-demo\ncd podman-desktop-demo/guestbook-compose\n"})}),"\n",(0,i.jsxs)(n.p,{children:["Run ",(0,i.jsx)(n.code,{children:"podman compose up -d"})," to start the application:"]}),"\n",(0,i.jsx)(n.pre,{children:(0,i.jsx)(n.code,{className:"language-sh",children:'podman compose up -d\n>>>> Executing external compose provider "/usr/local/bin/docker-compose". Please refer to the documentation for details. <<<<\n\n[+] Running 3/3\n \u2714 Container redis-replica Started 0.0s\n \u2714 Container web Started 0.0s\n \u2714 Container redis-leader Started 0.0s\n'})}),"\n",(0,i.jsx)(n.h2,{id:"viewing-the-guestbook-application",children:"Viewing the guestbook application"}),"\n",(0,i.jsx)(n.p,{children:"Within Podman Desktop, you can now see that all three containers are up and operational."}),"\n",(0,i.jsx)(n.p,{children:'Click the "Open Browser" button to view the web application:'}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.img,{alt:"Open browser",src:o(10517).Z+"",width:"1098",height:"812"})}),"\n",(0,i.jsx)(n.p,{children:"Within the Guestbook web application, you can:"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:'"Sign" the guestbook, which will write to the Redis leader and synchronize to the replicas.'}),"\n",(0,i.jsx)(n.li,{children:'"Read" from the guestbook, which will read from the pool of Redis replicas. This allows for readability even if the Redis leader is unavailable.'}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.code,{children:"/env"}),": View the container's environment variables."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.code,{children:"/info"}),": View information about the Redis cluster."]}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.img,{alt:"Guestbook application",src:o(23698).Z+"",width:"949",height:"653"})}),"\n",(0,i.jsx)(n.h2,{id:"viewing-and-modifying-the-database",children:"Viewing and modifying the database"}),"\n",(0,i.jsx)(n.p,{children:"Using Podman Desktop, you can also access the container's terminal directly from the GUI and modify the database."}),"\n",(0,i.jsxs)(n.p,{children:['Click "Open Terminal" to access the ',(0,i.jsx)(n.code,{children:"redis-leader"})," terminal:"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.img,{alt:"Open terminal",src:o(70256).Z+"",width:"1353",height:"1003"})}),"\n",(0,i.jsx)(n.p,{children:"Modify the database as if you are doing database administration:"}),"\n",(0,i.jsxs)(n.ol,{children:["\n",(0,i.jsxs)(n.li,{children:["Run ",(0,i.jsx)(n.code,{children:"redis-cli"})," within the container to access the Redis database."]}),"\n",(0,i.jsxs)(n.li,{children:["Type ",(0,i.jsx)(n.code,{children:'LPUSH guestbook "Hello World!"'})," and you will see your web application update in real-time."]}),"\n",(0,i.jsxs)(n.li,{children:["Type ",(0,i.jsx)(n.code,{children:"DEL guestbook"})," and you will see that your database drops the ",(0,i.jsx)(n.code,{children:"guestbook"})," key and clears the database."]}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.img,{alt:"Redis CLI",src:o(24207).Z+"",width:"1353",height:"1003"})}),"\n",(0,i.jsx)(n.p,{children:"Changes will reflect in real-time on the guestbook."}),"\n",(0,i.jsx)(n.p,{children:"You can further modify the database and see the changes propagate to the Redis replicas."}),"\n",(0,i.jsxs)(n.p,{children:["For example, view the logs of the ",(0,i.jsx)(n.code,{children:"redis-replica"}),", and you will notice that there are periodic database synchronizations as well as reads to the database:"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.img,{alt:"Redis replica logs",src:o(58645).Z+"",width:"1353",height:"1003"})}),"\n",(0,i.jsx)(n.h2,{id:"how-does-it-work",children:"How does it work?"}),"\n",(0,i.jsx)(n.p,{children:"A quick overview of how the architecture works in this multi-container scenario:"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["Within the Guestbook application, it looks for a database with the names ",(0,i.jsx)(n.code,{children:"redis-leader"})," and ",(0,i.jsx)(n.code,{children:"redis-replica"})," on port 6379."]}),"\n",(0,i.jsx)(n.li,{children:"Because it is a Compose application, the containers are connected on the same network. This means that a neighboring container can be network-accessible simply by its container name."}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:"There is a set of environment variables that the web application can modify in the Compose application:"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.code,{children:"REDIS_LEADER"}),": The default is ",(0,i.jsx)(n.code,{children:"redis-leader"}),"."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.code,{children:"REDIS_REPLICAS"}),": The default is ",(0,i.jsx)(n.code,{children:"redis-replica"}),". Can be comma-separated, such as ",(0,i.jsx)(n.code,{children:"redis-replica-1,redis-replica-2"}),"."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.code,{children:"REDIS_PORT"}),": The default is ",(0,i.jsx)(n.code,{children:"6379"}),"."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.code,{children:"SERVER_PORT"}),": The default is ",(0,i.jsx)(n.code,{children:"8080"}),"."]}),"\n"]}),"\n",(0,i.jsx)(n.h2,{id:"scaling-more-replicas",children:"Scaling more replicas"}),"\n",(0,i.jsxs)(n.p,{children:["Want to scale more replicas? This can be achieved by adding an environment variable to your ",(0,i.jsx)(n.code,{children:"compose.yaml"})," and duplicating your ",(0,i.jsx)(n.code,{children:"redis-replica"})," entry."]}),"\n",(0,i.jsxs)(n.p,{children:["Modify your ",(0,i.jsx)(n.code,{children:"compose.yaml"})," as follows:"]}),"\n",(0,i.jsx)(n.pre,{children:(0,i.jsx)(n.code,{className:"language-yaml",children:"services:\n redis-leader:\n container_name: redis-leader\n image: redis:latest\n ports:\n - '6379'\n\n redis-replica:\n container_name: redis-replica\n image: redis:latest\n ports:\n - '6379'\n command: redis-server --replicaof redis-leader 6379\n\n redis-replica-2:\n container_name: redis-replica-2\n image: redis:latest\n ports:\n - '6379'\n command: redis-server --replicaof redis-leader 6379\n\n web:\n container_name: web\n build: ./web\n environment:\n - REDIS_REPLICAS=redis-replica1,redis-replica2\n ports:\n - '8080:8080'\n"})}),"\n",(0,i.jsxs)(n.p,{children:["Run ",(0,i.jsx)(n.code,{children:"podman compose up -d"})," again to ensure the new container has been added and the new environment variable has propagated:"]}),"\n",(0,i.jsx)(n.pre,{children:(0,i.jsx)(n.code,{className:"language-sh",children:'podman compose up -d\n>>>> Executing external compose provider "/usr/local/bin/docker-compose". Please refer to the documentation for details. <<<<\n\n[+] Running 4/4\n \u2714 Container redis-replica-2 Started 0.0s\n \u2714 Container redis-leader Running 0.0s\n \u2714 Container web Started 0.0s\n \u2714 Container redis-replica Running 0.0s\n'})})]})}function p(e={}){const{wrapper:n}={...(0,s.a)(),...e.components};return n?(0,i.jsx)(n,{...e,children:(0,i.jsx)(l,{...e})}):l(e)}},23698:(e,n,o)=>{o.d(n,{Z:()=>i});const i=o.p+"assets/images/helloworld-516adc89ef8a509fb5ce998d3b0ea94b.png"},29856:(e,n,o)=>{o.d(n,{Z:()=>i});const i=o.p+"assets/images/onboarding-9b66ae02eaf2ebbec75dd092f78f26a3.png"},10517:(e,n,o)=>{o.d(n,{Z:()=>i});const i=o.p+"assets/images/openbrowser-9e28829878b62d868b2194a5a341fa1e.png"},70256:(e,n,o)=>{o.d(n,{Z:()=>i});const i=o.p+"assets/images/openterminal-648b30f8ad2add37bf4d5bafc37bfd46.png"},24207:(e,n,o)=>{o.d(n,{Z:()=>i});const i=o.p+"assets/images/redis-cli-d4648788bc57c0d57e0a7cdae4475d1d.png"},58645:(e,n,o)=>{o.d(n,{Z:()=>i});const i=o.p+"assets/images/redisreplica-31a441bbbe1383b80fb79a2f4dd52c56.png"},71670:(e,n,o)=>{o.d(n,{Z:()=>r,a:()=>t});var i=o(27378);const s={},a=i.createContext(s);function t(e){const n=i.useContext(a);return i.useMemo((function(){return"function"==typeof e?e(n):{...n,...e}}),[n,e])}function r(e){let n;return n=e.disableParentContext?"function"==typeof e.components?e.components(s):e.components||s:t(e.components),i.createElement(a.Provider,{value:n},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/8873cf50.fcadc71b.js b/assets/js/8873cf50.fcadc71b.js deleted file mode 100644 index 6b11462dc35..00000000000 --- a/assets/js/8873cf50.fcadc71b.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkdocs=self.webpackChunkdocs||[]).push([[485],{16472:(e,n,o)=>{o.r(n),o.d(n,{assets:()=>d,contentTitle:()=>t,default:()=>p,frontMatter:()=>a,metadata:()=>r,toc:()=>c});var i=o(24246),s=o(71670);const a={title:"Getting started with Compose on Podman Desktop",description:"Getting started with Compose on Podman Desktop",slug:"getting-started-with-compose",authors:["cdrage"],tags:["podman-desktop","story","compose","containers","containerfile","docker-compose","dockerfile","multi-container"],hide_table_of_contents:!1},t=void 0,r={permalink:"/blog/getting-started-with-compose",source:"@site/blog/2024-01-02-getting-started-with-compose.md",title:"Getting started with Compose on Podman Desktop",description:"Getting started with Compose on Podman Desktop",date:"2024-01-02T00:00:00.000Z",formattedDate:"January 2, 2024",tags:[{label:"podman-desktop",permalink:"/blog/tags/podman-desktop"},{label:"story",permalink:"/blog/tags/story"},{label:"compose",permalink:"/blog/tags/compose"},{label:"containers",permalink:"/blog/tags/containers"},{label:"containerfile",permalink:"/blog/tags/containerfile"},{label:"docker-compose",permalink:"/blog/tags/docker-compose"},{label:"dockerfile",permalink:"/blog/tags/dockerfile"},{label:"multi-container",permalink:"/blog/tags/multi-container"}],readingTime:4.475,hasTruncateMarker:!1,authors:[{name:"Charlie Drage",title:"Software Engineer",url:"https://github.com/cdrage",imageURL:"https://github.com/cdrage.png",key:"cdrage"}],frontMatter:{title:"Getting started with Compose on Podman Desktop",description:"Getting started with Compose on Podman Desktop",slug:"getting-started-with-compose",authors:["cdrage"],tags:["podman-desktop","story","compose","containers","containerfile","docker-compose","dockerfile","multi-container"],hide_table_of_contents:!1},unlisted:!1,nextItem:{title:"Release Notes - Podman Desktop 1.6",permalink:"/blog/podman-desktop-release-1.6"}},d={authorsImageUrls:[void 0]},c=[{value:"Objectives",id:"objectives",level:2},{value:"What is Compose",id:"what-is-compose",level:2},{value:"Before we begin",id:"before-we-begin",level:2},{value:"Download and run the example application",id:"download-and-run-the-example-application",level:2},{value:"Viewing the guestbook application",id:"viewing-the-guestbook-application",level:2},{value:"Viewing and modifying the database",id:"viewing-and-modifying-the-database",level:2},{value:"How does it work?",id:"how-does-it-work",level:2},{value:"Scaling more replicas",id:"scaling-more-replicas",level:2}];function l(e){const n={a:"a",code:"code",h2:"h2",img:"img",li:"li",ol:"ol",p:"p",pre:"pre",strong:"strong",ul:"ul",...(0,s.a)(),...e.components},{Icon:a}=n;return a||function(e,n){throw new Error("Expected "+(n?"component":"object")+" `"+e+"` to be defined: you likely forgot to import, pass, or provide it.")}("Icon",!0),(0,i.jsxs)(i.Fragment,{children:[(0,i.jsx)(n.p,{children:"In this blog post we will learn how take a multi-container Compose application and use it within Podman Desktop."}),"\n",(0,i.jsx)(n.h2,{id:"objectives",children:"Objectives"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["Start the Compose YAML through ",(0,i.jsx)(n.code,{children:"podman compose up"}),"."]}),"\n",(0,i.jsx)(n.li,{children:"View the guestbook web application."}),"\n",(0,i.jsx)(n.li,{children:"Confirm the web application is being synchronized and running correctly with the database."}),"\n",(0,i.jsx)(n.li,{children:"Use Podman Desktop to view, inspect and access the terminal of the Redis cluster."}),"\n"]}),"\n",(0,i.jsx)(n.h2,{id:"what-is-compose",children:"What is Compose"}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.a,{href:"https://www.compose-spec.io/",children:"Compose is a specification"})," for defining and running multi-container Docker applications. With pose, you use a YAML file to configure your application\u2019s services, networks, and volumes. This allows you to capture in a single file the entire configuration necessary to run a set of interconnected containers as an application. For example, if you have an application that requires a web server, a database, and a caching service, you can define these components and their relationships in your Compose file."]}),"\n",(0,i.jsxs)(n.p,{children:["To use the Compose YAML, you can use a specification implementation such as ",(0,i.jsx)(n.a,{href:"https://docs.podman.io/en/latest/markdown/podman-compose.1.html",children:(0,i.jsx)(n.code,{children:"podman compose"})})," and ",(0,i.jsx)(n.a,{href:"https://github.com/docker/compose",children:(0,i.jsx)(n.code,{children:"docker compose"})}),"."]}),"\n",(0,i.jsx)(n.h2,{id:"before-we-begin",children:"Before we begin"}),"\n",(0,i.jsx)(n.p,{children:"If you do not have Compose installed, let's go through the onboarding process to install the Compose implementation binary:"}),"\n",(0,i.jsxs)(n.ol,{children:["\n",(0,i.jsxs)(n.li,{children:["Get to Resources under ",(0,i.jsxs)(n.strong,{children:[(0,i.jsx)(a,{icon:"fa-solid fa-cog",size:"lg"})," Settings > Resources"]}),"."]}),"\n",(0,i.jsxs)(n.li,{children:["Click ",(0,i.jsx)(n.strong,{children:"Setup"})," under Compose (it will appear if it has not been installed yet)."]}),"\n",(0,i.jsx)(n.li,{children:"Go through the onboarding process."}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.img,{alt:"Onboarding process",src:o(29856).Z+"",width:"1222",height:"946"})}),"\n",(0,i.jsxs)(n.p,{children:["Confirm that you are able to run ",(0,i.jsx)(n.code,{children:"podman compose"}),":"]}),"\n",(0,i.jsx)(n.pre,{children:(0,i.jsx)(n.code,{className:"language-sh",children:"podman compose\nRun compose workloads via an external provider such as docker-compose or podman-compose\n\nDescription:\n This command is a thin wrapper around an external compose provider such as docker-compose or podman-compose. This means that podman compose is executing another tool that implements the compose functionality but sets up the environment in a way to let the compose provider communicate transparently with the local Podman socket. The specified options as well the command and argument are passed directly to the compose provider.\n...\n"})}),"\n",(0,i.jsx)(n.h2,{id:"download-and-run-the-example-application",children:"Download and run the example application"}),"\n",(0,i.jsxs)(n.p,{children:["Our example application is located at ",(0,i.jsx)(n.a,{href:"https://github.com/redhat-developer/podman-desktop-compose-example",children:"github.com/redhat-developer/podman-desktop-compose-example"}),"."]}),"\n",(0,i.jsxs)(n.p,{children:["We will use ",(0,i.jsx)(n.code,{children:"git clone"})," so we can build the Go binary web application:"]}),"\n",(0,i.jsx)(n.pre,{children:(0,i.jsx)(n.code,{className:"language-sh",children:"git clone https://github.com/redhat-developer/podman-desktop-compose-example\ncd podman-desktop-compose-example\n"})}),"\n",(0,i.jsxs)(n.p,{children:["Run ",(0,i.jsx)(n.code,{children:"podman compose up -d"})," to start the application:"]}),"\n",(0,i.jsx)(n.pre,{children:(0,i.jsx)(n.code,{className:"language-sh",children:'podman compose up -d\n>>>> Executing external compose provider "/usr/local/bin/docker-compose". Please refer to the documentation for details. <<<<\n\n[+] Running 3/3\n \u2714 Container redis-replica Started 0.0s\n \u2714 Container web Started 0.0s\n \u2714 Container redis-leader Started 0.0s\n'})}),"\n",(0,i.jsx)(n.h2,{id:"viewing-the-guestbook-application",children:"Viewing the guestbook application"}),"\n",(0,i.jsx)(n.p,{children:"Within Podman Desktop, you can now see that all three containers are up and operational."}),"\n",(0,i.jsx)(n.p,{children:'Click the "Open Browser" button to view the web application:'}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.img,{alt:"Open browser",src:o(10517).Z+"",width:"1098",height:"812"})}),"\n",(0,i.jsx)(n.p,{children:"Within the Guestbook web application, you can:"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:'"Sign" the guestbook, which will write to the Redis leader and synchronize to the replicas.'}),"\n",(0,i.jsx)(n.li,{children:'"Read" from the guestbook, which will read from the pool of Redis replicas. This allows for readability even if the Redis leader is unavailable.'}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.code,{children:"/env"}),": View the container's environment variables."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.code,{children:"/info"}),": View information about the Redis cluster."]}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.img,{alt:"Guestbook application",src:o(23698).Z+"",width:"949",height:"653"})}),"\n",(0,i.jsx)(n.h2,{id:"viewing-and-modifying-the-database",children:"Viewing and modifying the database"}),"\n",(0,i.jsx)(n.p,{children:"Using Podman Desktop, you can also access the container's terminal directly from the GUI and modify the database."}),"\n",(0,i.jsxs)(n.p,{children:['Click "Open Terminal" to access the ',(0,i.jsx)(n.code,{children:"redis-leader"})," terminal:"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.img,{alt:"Open terminal",src:o(70256).Z+"",width:"1353",height:"1003"})}),"\n",(0,i.jsx)(n.p,{children:"Modify the database as if you are doing database administration:"}),"\n",(0,i.jsxs)(n.ol,{children:["\n",(0,i.jsxs)(n.li,{children:["Run ",(0,i.jsx)(n.code,{children:"redis-cli"})," within the container to access the Redis database."]}),"\n",(0,i.jsxs)(n.li,{children:["Type ",(0,i.jsx)(n.code,{children:'LPUSH guestbook "Hello World!"'})," and you will see your web application update in real-time."]}),"\n",(0,i.jsxs)(n.li,{children:["Type ",(0,i.jsx)(n.code,{children:"DEL guestbook"})," and you will see that your database drops the ",(0,i.jsx)(n.code,{children:"guestbook"})," key and clears the database."]}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.img,{alt:"Redis CLI",src:o(24207).Z+"",width:"1353",height:"1003"})}),"\n",(0,i.jsx)(n.p,{children:"Changes will reflect in real-time on the guestbook."}),"\n",(0,i.jsx)(n.p,{children:"You can further modify the database and see the changes propagate to the Redis replicas."}),"\n",(0,i.jsxs)(n.p,{children:["For example, view the logs of the ",(0,i.jsx)(n.code,{children:"redis-replica"}),", and you will notice that there are periodic database synchronizations as well as reads to the database:"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.img,{alt:"Redis replica logs",src:o(58645).Z+"",width:"1353",height:"1003"})}),"\n",(0,i.jsx)(n.h2,{id:"how-does-it-work",children:"How does it work?"}),"\n",(0,i.jsx)(n.p,{children:"A quick overview of how the architecture works in this multi-container scenario:"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["Within the Guestbook application, it looks for a database with the names ",(0,i.jsx)(n.code,{children:"redis-leader"})," and ",(0,i.jsx)(n.code,{children:"redis-replica"})," on port 6379."]}),"\n",(0,i.jsx)(n.li,{children:"Because it is a Compose application, the containers are connected on the same network. This means that a neighboring container can be network-accessible simply by its container name."}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:"There is a set of environment variables that the web application can modify in the Compose application:"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.code,{children:"REDIS_LEADER"}),": The default is ",(0,i.jsx)(n.code,{children:"redis-leader"}),"."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.code,{children:"REDIS_REPLICAS"}),": The default is ",(0,i.jsx)(n.code,{children:"redis-replica"}),". Can be comma-separated, such as ",(0,i.jsx)(n.code,{children:"redis-replica-1,redis-replica-2"}),"."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.code,{children:"REDIS_PORT"}),": The default is ",(0,i.jsx)(n.code,{children:"6379"}),"."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.code,{children:"SERVER_PORT"}),": The default is ",(0,i.jsx)(n.code,{children:"8080"}),"."]}),"\n"]}),"\n",(0,i.jsx)(n.h2,{id:"scaling-more-replicas",children:"Scaling more replicas"}),"\n",(0,i.jsxs)(n.p,{children:["Want to scale more replicas? This can be achieved by adding an environment variable to your ",(0,i.jsx)(n.code,{children:"compose.yaml"})," and duplicating your ",(0,i.jsx)(n.code,{children:"redis-replica"})," entry."]}),"\n",(0,i.jsxs)(n.p,{children:["Modify your ",(0,i.jsx)(n.code,{children:"compose.yaml"})," as follows:"]}),"\n",(0,i.jsx)(n.pre,{children:(0,i.jsx)(n.code,{className:"language-yaml",children:"services:\n redis-leader:\n container_name: redis-leader\n image: redis:latest\n ports:\n - '6379'\n\n redis-replica:\n container_name: redis-replica\n image: redis:latest\n ports:\n - '6379'\n command: redis-server --replicaof redis-leader 6379\n\n redis-replica-2:\n container_name: redis-replica-2\n image: redis:latest\n ports:\n - '6379'\n command: redis-server --replicaof redis-leader 6379\n\n web:\n container_name: web\n build: ./web\n environment:\n - REDIS_REPLICAS=redis-replica1,redis-replica2\n ports:\n - '8080:8080'\n"})}),"\n",(0,i.jsxs)(n.p,{children:["Run ",(0,i.jsx)(n.code,{children:"podman compose up -d"})," again to ensure the new container has been added and the new environment variable has propagated:"]}),"\n",(0,i.jsx)(n.pre,{children:(0,i.jsx)(n.code,{className:"language-sh",children:'podman compose up -d\n>>>> Executing external compose provider "/usr/local/bin/docker-compose". Please refer to the documentation for details. <<<<\n\n[+] Running 4/4\n \u2714 Container redis-replica-2 Started 0.0s\n \u2714 Container redis-leader Running 0.0s\n \u2714 Container web Started 0.0s\n \u2714 Container redis-replica Running 0.0s\n'})})]})}function p(e={}){const{wrapper:n}={...(0,s.a)(),...e.components};return n?(0,i.jsx)(n,{...e,children:(0,i.jsx)(l,{...e})}):l(e)}},23698:(e,n,o)=>{o.d(n,{Z:()=>i});const i=o.p+"assets/images/helloworld-516adc89ef8a509fb5ce998d3b0ea94b.png"},29856:(e,n,o)=>{o.d(n,{Z:()=>i});const i=o.p+"assets/images/onboarding-9b66ae02eaf2ebbec75dd092f78f26a3.png"},10517:(e,n,o)=>{o.d(n,{Z:()=>i});const i=o.p+"assets/images/openbrowser-9e28829878b62d868b2194a5a341fa1e.png"},70256:(e,n,o)=>{o.d(n,{Z:()=>i});const i=o.p+"assets/images/openterminal-648b30f8ad2add37bf4d5bafc37bfd46.png"},24207:(e,n,o)=>{o.d(n,{Z:()=>i});const i=o.p+"assets/images/redis-cli-d4648788bc57c0d57e0a7cdae4475d1d.png"},58645:(e,n,o)=>{o.d(n,{Z:()=>i});const i=o.p+"assets/images/redisreplica-31a441bbbe1383b80fb79a2f4dd52c56.png"},71670:(e,n,o)=>{o.d(n,{Z:()=>r,a:()=>t});var i=o(27378);const s={},a=i.createContext(s);function t(e){const n=i.useContext(a);return i.useMemo((function(){return"function"==typeof e?e(n):{...n,...e}}),[n,e])}function r(e){let n;return n=e.disableParentContext?"function"==typeof e.components?e.components(s):e.components||s:t(e.components),i.createElement(a.Provider,{value:n},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/b2f554cd.72f564fc.js b/assets/js/b2f554cd.72f564fc.js deleted file mode 100644 index 27ced6c088a..00000000000 --- a/assets/js/b2f554cd.72f564fc.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkdocs=self.webpackChunkdocs||[]).push([[1477],{30010:e=>{e.exports=JSON.parse('{"blogPosts":[{"id":"getting-started-with-compose","metadata":{"permalink":"/blog/getting-started-with-compose","source":"@site/blog/2024-01-02-getting-started-with-compose.md","title":"Getting started with Compose on Podman Desktop","description":"Getting started with Compose on Podman Desktop","date":"2024-01-02T00:00:00.000Z","formattedDate":"January 2, 2024","tags":[{"label":"podman-desktop","permalink":"/blog/tags/podman-desktop"},{"label":"story","permalink":"/blog/tags/story"},{"label":"compose","permalink":"/blog/tags/compose"},{"label":"containers","permalink":"/blog/tags/containers"},{"label":"containerfile","permalink":"/blog/tags/containerfile"},{"label":"docker-compose","permalink":"/blog/tags/docker-compose"},{"label":"dockerfile","permalink":"/blog/tags/dockerfile"},{"label":"multi-container","permalink":"/blog/tags/multi-container"}],"readingTime":4.475,"hasTruncateMarker":false,"authors":[{"name":"Charlie Drage","title":"Software Engineer","url":"https://github.com/cdrage","imageURL":"https://github.com/cdrage.png","key":"cdrage"}],"frontMatter":{"title":"Getting started with Compose on Podman Desktop","description":"Getting started with Compose on Podman Desktop","slug":"getting-started-with-compose","authors":["cdrage"],"tags":["podman-desktop","story","compose","containers","containerfile","docker-compose","dockerfile","multi-container"],"hide_table_of_contents":false},"unlisted":false,"nextItem":{"title":"Release Notes - Podman Desktop 1.6","permalink":"/blog/podman-desktop-release-1.6"}},"content":"In this blog post we will learn how take a multi-container Compose application and use it within Podman Desktop.\\n\\n## Objectives\\n\\n- Start the Compose YAML through `podman compose up`.\\n- View the guestbook web application.\\n- Confirm the web application is being synchronized and running correctly with the database.\\n- Use Podman Desktop to view, inspect and access the terminal of the Redis cluster.\\n\\n## What is Compose\\n\\n[Compose is a specification](https://www.compose-spec.io/) for defining and running multi-container Docker applications. With pose, you use a YAML file to configure your application\u2019s services, networks, and volumes. This allows you to capture in a single file the entire configuration necessary to run a set of interconnected containers as an application. For example, if you have an application that requires a web server, a database, and a caching service, you can define these components and their relationships in your Compose file.\\n\\nTo use the Compose YAML, you can use a specification implementation such as [`podman compose`](https://docs.podman.io/en/latest/markdown/podman-compose.1.html) and [`docker compose`](https://github.com/docker/compose).\\n\\n## Before we begin\\n\\nIf you do not have Compose installed, let\'s go through the onboarding process to install the Compose implementation binary:\\n\\n1. Get to Resources under ** Settings > Resources**.\\n2. Click **Setup** under Compose (it will appear if it has not been installed yet).\\n3. Go through the onboarding process.\\n\\n![Onboarding process](img/getting-started-with-compose/onboarding.png)\\n\\nConfirm that you are able to run `podman compose`:\\n\\n```sh\\npodman compose\\nRun compose workloads via an external provider such as docker-compose or podman-compose\\n\\nDescription:\\n This command is a thin wrapper around an external compose provider such as docker-compose or podman-compose. This means that podman compose is executing another tool that implements the compose functionality but sets up the environment in a way to let the compose provider communicate transparently with the local Podman socket. The specified options as well the command and argument are passed directly to the compose provider.\\n...\\n```\\n\\n## Download and run the example application\\n\\nOur example application is located at [github.com/redhat-developer/podman-desktop-compose-example](https://github.com/redhat-developer/podman-desktop-compose-example).\\n\\nWe will use `git clone` so we can build the Go binary web application:\\n\\n```sh\\ngit clone https://github.com/redhat-developer/podman-desktop-compose-example\\ncd podman-desktop-compose-example\\n```\\n\\nRun `podman compose up -d` to start the application:\\n\\n```sh\\npodman compose up -d\\n>>>> Executing external compose provider \\"/usr/local/bin/docker-compose\\". Please refer to the documentation for details. <<<<\\n\\n[+] Running 3/3\\n \u2714 Container redis-replica Started 0.0s\\n \u2714 Container web Started 0.0s\\n \u2714 Container redis-leader Started 0.0s\\n```\\n\\n## Viewing the guestbook application\\n\\nWithin Podman Desktop, you can now see that all three containers are up and operational.\\n\\nClick the \\"Open Browser\\" button to view the web application:\\n\\n![Open browser](img/getting-started-with-compose/openbrowser.png)\\n\\nWithin the Guestbook web application, you can:\\n\\n- \\"Sign\\" the guestbook, which will write to the Redis leader and synchronize to the replicas.\\n- \\"Read\\" from the guestbook, which will read from the pool of Redis replicas. This allows for readability even if the Redis leader is unavailable.\\n- `/env`: View the container\'s environment variables.\\n- `/info`: View information about the Redis cluster.\\n\\n![Guestbook application](img/getting-started-with-compose/helloworld.png)\\n\\n## Viewing and modifying the database\\n\\nUsing Podman Desktop, you can also access the container\'s terminal directly from the GUI and modify the database.\\n\\nClick \\"Open Terminal\\" to access the `redis-leader` terminal:\\n\\n![Open terminal](img/getting-started-with-compose/openterminal.png)\\n\\nModify the database as if you are doing database administration:\\n\\n1. Run `redis-cli` within the container to access the Redis database.\\n2. Type `LPUSH guestbook \\"Hello World!\\"` and you will see your web application update in real-time.\\n3. Type `DEL guestbook` and you will see that your database drops the `guestbook` key and clears the database.\\n\\n![Redis CLI](img/getting-started-with-compose/redis-cli.png)\\n\\nChanges will reflect in real-time on the guestbook.\\n\\nYou can further modify the database and see the changes propagate to the Redis replicas.\\n\\nFor example, view the logs of the `redis-replica`, and you will notice that there are periodic database synchronizations as well as reads to the database:\\n\\n![Redis replica logs](img/getting-started-with-compose/redisreplica.png)\\n\\n## How does it work?\\n\\nA quick overview of how the architecture works in this multi-container scenario:\\n\\n- Within the Guestbook application, it looks for a database with the names `redis-leader` and `redis-replica` on port 6379.\\n- Because it is a Compose application, the containers are connected on the same network. This means that a neighboring container can be network-accessible simply by its container name.\\n\\nThere is a set of environment variables that the web application can modify in the Compose application:\\n\\n- `REDIS_LEADER`: The default is `redis-leader`.\\n- `REDIS_REPLICAS`: The default is `redis-replica`. Can be comma-separated, such as `redis-replica-1,redis-replica-2`.\\n- `REDIS_PORT`: The default is `6379`.\\n- `SERVER_PORT`: The default is `8080`.\\n\\n## Scaling more replicas\\n\\nWant to scale more replicas? This can be achieved by adding an environment variable to your `compose.yaml` and duplicating your `redis-replica` entry.\\n\\nModify your `compose.yaml` as follows:\\n\\n```yaml\\nservices:\\n redis-leader:\\n container_name: redis-leader\\n image: redis:latest\\n ports:\\n - \'6379\'\\n\\n redis-replica:\\n container_name: redis-replica\\n image: redis:latest\\n ports:\\n - \'6379\'\\n command: redis-server --replicaof redis-leader 6379\\n\\n redis-replica-2:\\n container_name: redis-replica-2\\n image: redis:latest\\n ports:\\n - \'6379\'\\n command: redis-server --replicaof redis-leader 6379\\n\\n web:\\n container_name: web\\n build: ./web\\n environment:\\n - REDIS_REPLICAS=redis-replica1,redis-replica2\\n ports:\\n - \'8080:8080\'\\n```\\n\\nRun `podman compose up -d` again to ensure the new container has been added and the new environment variable has propagated:\\n\\n```sh\\npodman compose up -d\\n>>>> Executing external compose provider \\"/usr/local/bin/docker-compose\\". Please refer to the documentation for details. <<<<\\n\\n[+] Running 4/4\\n \u2714 Container redis-replica-2 Started 0.0s\\n \u2714 Container redis-leader Running 0.0s\\n \u2714 Container web Started 0.0s\\n \u2714 Container redis-replica Running 0.0s\\n```"},{"id":"podman-desktop-release-1.6","metadata":{"permalink":"/blog/podman-desktop-release-1.6","source":"@site/blog/2023-12-18-release-1.6.md","title":"Release Notes - Podman Desktop 1.6","description":"Podman Desktop 1.6 has been released!","date":"2023-12-18T00:00:00.000Z","formattedDate":"December 18, 2023","tags":[{"label":"podman-desktop","permalink":"/blog/tags/podman-desktop"},{"label":"release","permalink":"/blog/tags/release"},{"label":"kubernetes","permalink":"/blog/tags/kubernetes"},{"label":"openshift","permalink":"/blog/tags/openshift"},{"label":"onboarding","permalink":"/blog/tags/onboarding"},{"label":"compose","permalink":"/blog/tags/compose"},{"label":"extensions","permalink":"/blog/tags/extensions"},{"label":"settings","permalink":"/blog/tags/settings"}],"readingTime":10.45,"hasTruncateMarker":false,"authors":[{"name":"Stevan Le Meur","title":"Product Manager","url":"https://github.com/slemeur","imageURL":"https://github.com/slemeur.png","key":"slemeur"}],"frontMatter":{"title":"Release Notes - Podman Desktop 1.6","description":"Podman Desktop 1.6 has been released!","slug":"podman-desktop-release-1.6","authors":"slemeur","tags":["podman-desktop","release","kubernetes","openshift","onboarding","compose","extensions","settings"],"hide_table_of_contents":false,"image":"/img/blog/podman-desktop-release-1.6/santaseal.png"},"unlisted":false,"prevItem":{"title":"Getting started with Compose on Podman Desktop","permalink":"/blog/getting-started-with-compose"},"nextItem":{"title":"Share your local podman images with the Kubernetes cluster","permalink":"/blog/sharing-podman-images-with-kubernetes-cluster"}},"content":"import ReactPlayer from \'react-player\'\\n\\nPodman Desktop 1.6 Release! \ud83c\udf89\\n\\n![Podman-desktop-1-6-hero](img/podman-desktop-release-1.6/santaseal.png)\\n\\nThis release introduces:\\n\\n- **Minikube Featured Extension**: Minikube extension to create local Kubernetes clusters in containers.\\n- **Podman 4.8.2**: [Podman 4.8.2](https://github.com/containers/podman/releases) is now included in Windows and Mac installers.\\n- **Setting Page for Command-Line Tools**: Manage and update your CLI tools.\\n- **Kubernetes Contexts Manager**: Browse all your kubernetes contexts, set default and remove unused ones.\\n- **Editable Podman Machine for MacOS**: Easy resize and reconfiguration of the Podman runtime environment.\\n- **Filters for Containers and Pods Lists**: Focus on the containers and Pods you are working with.\\n- **Sorting on Volumes and Images List**: Sort volumes or images with your prefered criterias.\\n- **Environment Colums on Containers and Pods lists**: Easy catch of the environment on which a container or a pod is running on.\\n- **Extension API Improvements**: Another set of improvements to the extension API enabling more goodness for \ud83e\uddad Podman Desktop\'s extensions.\\n\\nPodman Desktop 1.6 is now available. [Click here to download it](/downloads)!\\n\\n---\\n\\n## Release Details\\n\\n### Minikube featured extension\\n\\nFor developers who need to run Kubernetes locally and reproduce an environment close to production for development and experimentation purposes, Podman Desktop allows users to easily set up that environment on a local machine. There are two extensions providing the capability to configure a open source Kubernetes cluster locally, you can either choose between [Kind](https://kind.sigs.k8s.io/) or [Minikube](https://minikube.sigs.k8s.io/docs/).\\n\\nThe Minikube extension allows you to install Minikube on your workstation and also to setup a Kubernetes cluster locally running in a container! Yes, you read that correctly - in a container similar to how Kind works. The advantage is that it\'s lighter and faster to start. With Minikube, one of the advantage, is that you can build your images locally with Podman and get them automatically available in your local Kubernetes cluster - which will speed up your turnarounds when you want to test your application. If you want to learn more this, read the [following blog post](https://podman-desktop.io/blog/sharing-podman-images-with-kubernetes-cluster).\\n\\n![Minikube-feature-extension](img/podman-desktop-release-1.6/minikube-feature-extension.png)\\n\\n### Command-Line Tools Configuration: Compose and Kubectl\\n\\nConfiguring and managing your setup is getting easier with the addition of a new section in the Settings to manage command-line tools. In Podman Desktop, extensions can list command-line tools that are helpful to their users or required to make use of the installed extensions.\\n\\nThere are two command-line tools within Podman Desktop that allows you to view whether they are installed or require an update:\\n\\n- Compose binary for running \'podman compose\' commands.\\n- kubectl for interacting with Kubernetes clusters.\\n\\n![cli-tools](img/podman-desktop-release-1.6/cli-tools.png)\\n\\nFrom the settings you can see the command-line tools that are installed, and you can see the version - and when a new version is available, you\'ll get a small notification to allow you easily update to that version.\\n\\n![Compose-Update](img/podman-desktop-release-1.6/compose-update.png)\\n\\n### Kubernetes Contexts Manager\\n\\nWe are introducing a new screen available from the Settings which allows you to easily manage your Kubernetes contexts. Podman Desktop was already providing the handy context switcher available from the status bar, but when you get to work with multiple Kubernetes environments, it\'s not uncommon to end with a big and long list of Kubernetes contexts.\\n\\nThe new Kubernetes Contexts screen allows you to easily see all your registered Kubernetes contexts. You can use the screen to clean up your registered contexts, or set the current (default) context.\\n\\n![Kubernetes Contexts List](img/podman-desktop-release-1.6/kubernetes-contexts.png)\\n\\n### Editable Podman Machine\\n\\nA Podman machine is a virtual environment specifically designed to run Podman containers on Mac and Windows. It allows users to manage and operate containerized applications in an isolated and controlled setting. When creating a Podman machine, you configure its settings: memory, CPU(s) and disk size.\\n\\nWe\'ve received the feedback regarding the ability to reconfigure your Podman machine on the go. This is now possible for macOS users, and particularly useful when you start with an environment and need to scale it up based on new needs and containers you would like to run in your Podman environment.\\n\\n![Editable podman machine](https://github.com/containers/podman-desktop/assets/1636769/91150767-58a9-47b5-abbc-58d2d50f4fca)\\n\\nYou\'ll notice we improved the sliders to configure the Podman machine\'s options - and also introduced a way to enter numeric values directly.\\n\\n### Tabs/Filters for Containers and Pods\\n\\nBeing able to quickly identify the containers and the pods you are working with is critical when you are iterating on the development of your application. For this reason, we added filters at the top of the lists of Containers and Pods that allow you to easily view all the containers/pods, only those that are running, or only those that are stopped.\\n\\n![Filters for containers and pods](https://github.com/containers/podman-desktop/assets/1636769/37190c74-7fa5-485e-81a4-bd970f606286)\\n\\n### Sorting for Volumes and Images lists\\n\\nThe lists of Volumes and Images have improved and are now have the ability to be sorted by the criteria of your choice. You can for example filter images by their size - which can be convenient when you want to clean up your environment.\\n\\n![Sorting for Volumes and Images](https://github.com/containers/podman-desktop/assets/1636769/0d20b5c2-517c-4ccc-8992-b8df275bcc30)\\n\\n### Environment columns on Containers and Pods lists\\n\\nPodman Desktop is able to work with multiple providers: it could work with multiple container engines and multiple Kubernetes environments too. In order to make it easier to identify the containers and the pods and differentiate them depending on which environment they are running onto, we are introducing a new environment column in the list of Containers and Pods to display a badge.\\n\\n![Environment Column](img/podman-desktop-release-1.6/environment-column.png)\\n\\n#### Better visibility to the containers running in Pods\\n\\nThe list of Pods has been refined to provide easier visibility and access to the containers running within each of them. Each of the containers now have one dot and you can hover each dot to display the info about the container - and if you click on it you\'ll be able to access the details of the container.\\n\\n![Visibility for containers in Pods](https://github.com/containers/podman-desktop/assets/1636769/0e88a88e-9a17-4261-b60f-b4d09ca19127)\\n\\n### Extension API improvements\\n\\nThe \ud83e\uddad Podman Desktop extension API received many improvements, including:\\n\\n- Documentation explaining how to create an onboarding workflow for an extension [#4837](https://github.com/containers/podman-desktop/pull/4837)\\n- Documented how extensions hook into UI [#4633](https://github.com/containers/podman-desktop/pull/4633)\\n- Documented how to implement api client [#4636](https://github.com/containers/podman-desktop/pull/4636)\\n- Image checker extension API [#4662](https://github.com/containers/podman-desktop/pull/4662)\\n- Added api to register cli updater [#5064](https://github.com/containers/podman-desktop/pull/5064)\\n\\n---\\n\\n## Other Notable Enhancements\\n\\n- Show container connection type and endpoint [#5098](https://github.com/containers/podman-desktop/pull/5098)\\n- Environment column to pods/containers [#4583](https://github.com/containers/podman-desktop/pull/4583)\\n- Displaying extension icons in the list of extensions [#5101](https://github.com/containers/podman-desktop/pull/5101)\\n- Introduced UI icon image component [#5117](https://github.com/containers/podman-desktop/pull/5117)\\n- Added icon to extensionInfo [#5089](https://github.com/containers/podman-desktop/pull/5089)\\n- Added encoding option on RunOptions [#4942](https://github.com/containers/podman-desktop/pull/4942)\\n- Introduced property for appearance but for now only dark is supported [#4887](https://github.com/containers/podman-desktop/pull/4887)\\n- Default table sorting [#4860](https://github.com/containers/podman-desktop/pull/4860)\\n- Display notification for completed onboarding in task manager [#4811](https://github.com/containers/podman-desktop/pull/4811)\\n- Added purple dot when new content is available in dashboard [#4782](https://github.com/containers/podman-desktop/pull/4782)\\n- Argos CI: Introduce Argos CI to track and detect visual regressions on the website\\n- Added command palette: add enablement property [#4630](https://github.com/containers/podman-desktop/pull/4630)\\n- Added documentation for telemetry and usage data [#4618](https://github.com/containers/podman-desktop/pull/4619)\\n- Introduced table component [#4545](https://github.com/containers/podman-desktop/pull/4545)\\n- Added ability to abort build image [#4538](https://github.com/containers/podman-desktop/pull/4538)\\n- Added support in command palette for category [#4531](https://github.com/containers/podman-desktop/pull/4531)\\n- Upgraded flatpak to org.freedesktop.Platform version 23.08 [#3968](https://github.com/containers/podman-desktop/pull/3968)\\n- Added open exposed url to pod details [#3762](https://github.com/containers/podman-desktop/pull/3762)\\n\\n---\\n\\n## Notable Bug Fixes\\n\\n- Fix reconnect to `/events` if disconnected [#4809](https://github.com/containers/podman-desktop/pull/4809)\\n- fix: reset loggerhandlerKey after restarting machine [#5168](https://github.com/containers/podman-desktop/pull/5168)\\n- fix: fix: podman machine created with wrong flags [#5178](https://github.com/containers/podman-desktop/pull/5178)\\n- fix: avoid to crash if configuration is invalid [#5182](https://github.com/containers/podman-desktop/pull/5182)\\n- fix: extension installation checks architecture and os [#5191](https://github.com/containers/podman-desktop/pull/5191)\\n- fix: use URL for proxy specification and add validation [#4825](https://github.com/containers/podman-desktop/pull/4825)\\n- fix: do not change color and underline of markdown buttons [#5138](https://github.com/containers/podman-desktop/pull/5138)\\n- fix: do not reconnect when connection is removed [#5131](https://github.com/containers/podman-desktop/pull/5131)\\n- fix: table headers shouldn\'t allow text selection [#5118](https://github.com/containers/podman-desktop/pull/5118)\\n- fix: add style to link [#5108](https://github.com/containers/podman-desktop/pull/5108)\\n- fix: launch.json references wrong script [#5094](https://github.com/containers/podman-desktop/pull/5094)\\n- fix: don\'t link to k8s cluster server [5087](https://github.com/containers/podman-desktop/pull/5087)\\n- fix: pass the complete imageInfo to the check function [#5069](https://github.com/containers/podman-desktop/pull/5069)\\n- fix: container tabs should match pods [#5057](https://github.com/containers/podman-desktop/pull/5057)\\n- fix: revert styling of disabled buttons [#5056](https://github.com/containers/podman-desktop/pull/5056)\\n- fix: update current context reactively [#5055](https://github.com/containers/podman-desktop/pull/5055)\\n- fix: make ProviderResultPage do not change input values [#5030](https://github.com/containers/podman-desktop/pull/5030)\\n- fix: add rowgroup to tables [#5005](https://github.com/containers/podman-desktop/pull/5005)\\n- fix: add path prop for route object [#4981](https://github.com/containers/podman-desktop/pull/4981)\\n- fix: remove errant hash mark [#4971](https://github.com/containers/podman-desktop/pull/4971)\\n- fix: check extension folder contains package.json [#4964](https://github.com/containers/podman-desktop/pull/4964)\\n- fix: refactor List UI components [#4953](https://github.com/containers/podman-desktop/pull/4953)\\n- fix: succeeded/completed state for Compose onboarding [#4947](https://github.com/containers/podman-desktop/pull/4947)\\n- fix: remove flex class from markdown button rendering [#4934](https://github.com/containers/podman-desktop/pull/4934)\\n- fix: unable to read wsl version when using chinese as syslang on Windows [#4918](https://github.com/containers/podman-desktop/pull/4918)\\n- fix: retain autostart setting [#4879](https://github.com/containers/podman-desktop/pull/4879)\\n- fix: use vi.waitUtnil instead of cycles with awaiting promises [#4861](https://github.com/containers/podman-desktop/pull/4861)\\n- fix: docker host on windows when executing compose command [#4855](https://github.com/containers/podman-desktop/pull/4855)\\n- fix: merged compose deploy to kube page in UI [#4827](https://github.com/containers/podman-desktop/pull/4827)\\n- fix: use URL for proxy specification and add validation [#4825](https://github.com/containers/podman-desktop/pull/4825)\\n- fix: reconnect to /events if disconnected [#4809](https://github.com/containers/podman-desktop/pull/4809)\\n- fix: remove fixed height after patternfly removal [#4804](https://github.com/containers/podman-desktop/pull/4804)\\n- fix background colours after patternfly removal [#4803](https://github.com/containers/podman-desktop/pull/4803)\\n- fix: report metrics for stopped machines [#4787](https://github.com/containers/podman-desktop/pull/4787)\\n- chore: update to docusaurus v3.0.0 [#4764](https://github.com/containers/podman-desktop/pull/4764)\\n- chore: drop patternfly [#4762](https://github.com/containers/podman-desktop/pull/4762)\\n- fix: avoid to send telemetry usage as this method is called every 5s [#4692](https://github.com/containers/podman-desktop/pull/4692)\\n- fix: location of roots.exe in devmode [#4654](https://github.com/containers/podman-desktop/pull/4654)\\n- fix: disable create/start container if any port is busy [#4637](https://github.com/containers/podman-desktop/pull/4637)\\n- fix: fix setup in build image tests [#4625](https://github.com/containers/podman-desktop/pull/4625)\\n- fix: find a free port [#4616](https://github.com/containers/podman-desktop/pull/4616)\\n- fix: reduce size of provider cards on the dashboard [#4615](https://github.com/containers/podman-desktop/pull/4615)\\n- fix: shorter doc nav section titles [#4613](https://github.com/containers/podman-desktop/pull/4613)\\n- fix: report error if container engine action fails in details page [#4556](https://github.com/containers/podman-desktop/pull/4556)\\n- fix: remove prev/next bar [#4548](https://github.com/containers/podman-desktop/pull/4548)\\n- fix: reduce website footer [#4546](https://github.com/containers/podman-desktop/pull/4546)\\n- fix: handle compose format json that is no longer a JSON array object [#4540](https://github.com/containers/podman-desktop/pull/4540)\\n- fix: disable push to kind menu item if pushing is in progress [#4530](https://github.com/containers/podman-desktop/pull/4530)\\n- fix: check for self signed cert message and use insecure param when editing registry password [#4523](https://github.com/containers/podman-desktop/pull/4523)\\n- fix: add autoscroll to summary pages [#4504](https://github.com/containers/podman-desktop/pull/4504)\\n- fix: report errors when analyzing extensions [#4380](https://github.com/containers/podman-desktop/pull/4380)\\n- fix: allow editing of build containerfile [#4471](https://github.com/containers/podman-desktop/pull/4471)\\n- refactor: updated compose onboarding installation [#4479](https://github.com/containers/podman-desktop/pull/4479)\\n- refactor: remove compose from the status bar [#4492](https://github.com/containers/podman-desktop/pull/4492)\\n\\n---\\n\\n## Documentation\\n\\nComing with this new version of \ud83e\uddad Podman Desktop, the documentation has been getting the following improvements:\\n\\n- Reorganize doc navigation by provider [#4558](https://github.com/containers/podman-desktop/pull/4558)\\n- Added vsc runtime dependency for Windows development [#5091](https://github.com/containers/podman-desktop/pull/5091)\\n- Show location of lima podman socket [#5090](https://github.com/containers/podman-desktop/pull/5090)\\n- Fixed typo in URI for releases [#4909](https://github.com/containers/podman-desktop/pull/4909)\\n- Explain how to create an onboarding workflow for an extension [#4837](https://github.com/containers/podman-desktop/pull/4837)\\n- Make it possible for lima to provide both [#4789](https://github.com/containers/podman-desktop/pull/4789)\\n- Blog post about minikube/sharing images [#4735](https://github.com/containers/podman-desktop/pull/4735)\\n- Remove duplicate text from windows troubleshooting [#4652](https://github.com/containers/podman-desktop/pull/4652)\\n- Add step to implement api client [#4636](https://github.com/containers/podman-desktop/pull/4636)\\n- Fixed the main lima command for limactl [#4623](https://github.com/containers/podman-desktop/pull/4623)\\n- Lima provider cleanup after the improvements in the implementation [#4622](https://github.com/containers/podman-desktop/pull/4622)\\n- Update documentation regarding auto merge [#4519](https://github.com/containers/podman-desktop/pull/4519)\\n- Using standard OS tabs for registries docs [#4497](https://github.com/containers/podman-desktop/pull/4497)\\n- Fixed mahine -> machine [#4495](https://github.com/containers/podman-desktop/pull/4495)\\n- Added screenshots and fixed formatting to the registries section [#4472](https://github.com/containers/podman-desktop/pull/4472)\\n\\n---\\n\\n## Community Thank You\\n\\n\ud83c\udf89 We\u2019d like to say a big thank you to everyone who helped to make \ud83e\uddad Podman Desktop even better. In this\\nrelease we received pull requests from the following people:\\n\\n- [afbjorklund](https://github.com/afbjorklund) in [fix: add website target for running vale ](https://github.com/containers/podman-desktop/pull/4547), [docs: the main lima command is limactl](https://github.com/containers/podman-desktop/pull/4623), [ docs: lima provider cleanup after the merge](https://github.com/containers/podman-desktop/pull/4622), [docs: make it possible for lima to provide both](https://github.com/containers/podman-desktop/pull/4789), [fix: don\'t link to k8s cluster server](https://github.com/containers/podman-desktop/pull/5087), [feat: show the k8s namespace](https://github.com/containers/podman-desktop/pull/5088), [docs: show location of lima podman socket](https://github.com/containers/podman-desktop/pull/5090)\\n\\n- [axel7083](https://github.com/axel7083) in [refactoring: item formats from renderer/preferences in separate files](https://github.com/containers/podman-desktop/pull/3728), [feat: adding optional abort controller to dockerode api](https://github.com/containers/podman-desktop/pull/4364)\\n\\n- [ReadingShades](https://github.com/ReadingShades) in [docs: Added the environment variable set commands of the common windows terminal emulators](https://github.com/containers/podman-desktop/pull/4245)\\n\\n- [jannikbertram](https://github.com/jannikbertram) in [chore: add close button to troubleshooting and help page](https://github.com/containers/podman-desktop/pull/4457)\\n\\n- [singodiyashubham87](https://github.com/singodiyashubham87) in [fix: header line height issue on website](https://github.com/containers/podman-desktop/pull/4494)\\n\\n- [edvardsanta](https://github.com/edvardsanta) in [feat: remove redundant naming in buttons](https://github.com/containers/podman-desktop/pull/4518)\\n\\n- [Mayureshd-18](https://github.com/Mayureshd-18) in [fix typos](https://github.com/containers/podman-desktop/pull/4551)\\n\\n- [jgelens](https://github.com/jgelens) in [Fix rootless command](https://github.com/containers/podman-desktop/pull/4609)\\n\\n- [itecompro](https://github.com/itecompro) in [docs: remove duplicate text from windows troubleshooting](https://github.com/containers/podman-desktop/pull/4652)\\n\\n- [EricSmekens](https://github.com/EricSmekens) in [docs: Fixed typo in URI for releases](https://github.com/containers/podman-desktop/pull/4909)\\n\\n- [ecrookshanks-rh](https://github.com/ecrookshanks-rh) in [fix: added text beside icon for create pods ](https://github.com/containers/podman-desktop/pull/5095)\\n\\n---\\n\\n## Final notes\\n\\n### Fixed Issues\\n\\nThe complete list of issues fixed in this release is available [here](https://github.com/containers/podman-desktop/issues?q=is%3Aclosed+milestone%3A1.6.0).\\n\\n### Where to Download\\n\\nGet the latest release from the [Downloads](/downloads) section of the website and boost your development journey with Podman Desktop. Additionally, visit the [GitHub repository](https://github.com/containers/podman-desktop) and see how you can help us make Podman Desktop better."},{"id":"sharing-podman-images-with-kubernetes-cluster","metadata":{"permalink":"/blog/sharing-podman-images-with-kubernetes-cluster","source":"@site/blog/2023-12-06-sharing-podman-images-with-kubernetes-cluster.md","title":"Share your local podman images with the Kubernetes cluster","description":"Build image and use it directly in your kubernetes cluster","date":"2023-12-06T00:00:00.000Z","formattedDate":"December 6, 2023","tags":[{"label":"podman-desktop","permalink":"/blog/tags/podman-desktop"},{"label":"podman","permalink":"/blog/tags/podman"},{"label":"images","permalink":"/blog/tags/images"},{"label":"kubernetes","permalink":"/blog/tags/kubernetes"}],"readingTime":7.71,"hasTruncateMarker":true,"authors":[{"name":"Florent Benoit","title":"Principal Software Engineer","url":"https://github.com/benoitf","imageURL":"https://github.com/benoitf.png","key":"benoitf"}],"frontMatter":{"title":"Share your local podman images with the Kubernetes cluster","description":"Build image and use it directly in your kubernetes cluster","slug":"sharing-podman-images-with-kubernetes-cluster","authors":["benoitf"],"tags":["podman-desktop","podman","images","kubernetes"],"hide_table_of_contents":false,"image":"/img/blog/sharing-podman-images-with-kubernetes-cluster/selkie-family.png"},"unlisted":false,"prevItem":{"title":"Release Notes - Podman Desktop 1.6","permalink":"/blog/podman-desktop-release-1.6"},"nextItem":{"title":"Release Notes - Podman Desktop 1.5","permalink":"/blog/podman-desktop-release-1.5"}},"content":"As developers we constantly improve and refine our applications. One of the challenges we face is quickly iterating when working with container images and kubernetes deployments/pods.\\n\\nFor example, when we want to try a new image in a kubernetes pod, this image needs to be available on a private/public registry or on the nodes of the kubernetes cluster.\\nSometimes we need to call extra commands such as `kind load docker-image` or `minikube cache add ` or publish the image first to a 3rd party registry.\\n\\nYou\'ll agree that trying out a new image in a Kubernetes pod should be as seamless as building the image itself.\\n\\nIn this blog post, we will explore the best practice for streamlining the image iteration process in Kubernetes with Podman Desktop.\\n\\n![hero](img/sharing-podman-images-with-kubernetes-cluster/selkie-family.png)\\n\\n\x3c!--truncate--\x3e\\n\\n---\\n\\n## Introduction\\n\\nWhen using kind or minikube or other 3rd party tools to setup a local kubernetes cluster, we have several ways to publish images.\\n\\nMinikube published 8 ways of doing that at https://minikube.sigs.k8s.io/docs/handbook/pushing/\\n\\nThere are pros and cons either way. Using a third party registry implies that you need to publish the image after each build of the image before being able to use it in the kubernetes cluster. While Podman Desktop could automate the synchronization between the local registry (where you are doing `podman build`) and the third party registry, there remains a duplication of layers between the local and third party registry. And if you change the first layer, it can take a lot of time to send again all the data.\\n\\nLoading images requires to pack/unpack the files so it\'s not adequate for large images.\\n\\nMinikube offers a Podman environment, but it\'s important to note that it utilizes version 3.4 inside a container within the Podman machine. This implies the existence of two Podman instances.\\n\\nThe 3.4 version is considerably outdated and do not provide new enhancements and support towards compose, compliance with Docker REST API and 3rd party tools.\\n\\nCould we just build the image and use it in kubernetes?\\n\\n## podman and kubernetes/cri-o\\n\\nIn the kubernetes world, we need a container engine runtime. At the early stage, container runtimes were integrated with ad hoc solutions on top of docker, rkt, or others.\\n\\nBut to separate concerns and to be extensible, a new interface was added: CRI for \\"Container Runtime Interface\\". Using the CRI interface we can plug container engines. And there are several runtimes such as containerd, cri-o and others.\\nhttps://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/container-runtime-interface.md\\n\\nWhat is interesting to us is the cri-o project. This project is implementing the CRI interface but also adopting some projects of the [containers](https://github.com/containers) organization where [podman](https://github.com/containers/podman) and [podman-desktop](https://github.com/containers/podman-desktop) live.\\n\\nSo it means cri-o uses image management from https://github.com/containers/image project and handle storage with https://github.com/containers/storage project.\\n\\nAnd this is what is really interesting as a podman user. As it is using common libraries between cri-o and podman, it means that in the same environment, podman and cri-o read and write the images at a common location in `/var/lib/containers` folder.\\n\\nIf we move one step ahead, if we mount the `/var/lib/containers` folder of podman into the cri-o container it means that the kubernetes cluster could find the images that the podman machine is building.\\n\\nOh wait, it means that no more registry, additional steps would be required? Yes just build and load it.\\n\\n## Minikube to the rescue\\n\\nWhile we have the goal of using both cri-o and podman altogether, we can explore the current projects allowing us to quickly setup kubernetes clusters.\\n\\n### kind\\n\\nOn the `kind` side, there is a default configuration that is using containerd and there is no plan to support an alternative such as cri-o https://github.com/kubernetes-sigs/kind/issues/1369#issuecomment-867440704\\n\\nThat said, some people try to maintain a way to do that but not officialy https://gist.github.com/aojea/bd1fb766302779b77b8f68fa0a81c0f2\\n\\nBy doing that, we would also need to mount `/var/lib/containers` folder from the host (the podman machine) to the container. And there is no easy flag in kind.\\n\\n### Minikube\\n\\n#### Minikube options\\n\\nMinikube supports more options and provides a way to select the container engine runtime. And it includes support for cri-o.\\n\\nWe can use the `container-runtime` parameter and ask for `cri-o` runtime. Command-line should include `--container-runtime=cri-o`.\\n\\nThen, we do have a podman/cri-o environment inside the container and can use `eval $(minikube podman-env)` to use the Windows/macOS podman CLI.\\n\\nOne issue is that we then have two \'Podman engines\': one running inside the Podman machine and another one running inside the container. The Podman included in the container is using version 3.4, as it\'s on Debian/Ubuntu stable, while the recent version of Podman is 4.7.x.\\n\\nCan we mount the podman machine `/var/lib/containers` into the container ?\\n\\nYes! minikube provides some options to do additional mount with `--mount-string` argument. It is not obvious but you also need to add the `--mount` in addition to this parameter. Full argument is `--mount --mount-string \\"\\"`\\n\\nBut `/var` is already a mounted folder. So here the idea is to change the path of where cri-o is storing its data.\\n\\nSo we can provide a custom mounted path and make cri-o use that custom location. Let\'s pickup `/host-containers`.\\n\\nWhen starting minikube we need then to add `--mount --mount-string \\"/var/lib/containers:/host-containers\\"`.\\n\\nRegarding the configuration of cri-o, currently, it\'s not achievable using Minikube options. However, Minikube does offer the flexibility to modify the base image.\\n\\n#### Minikube kicbase image\\n\\nLet\'s do our own base image named kicbase image.\\n\\nMinikube includes a default configuration file for cri-o.\\nhttps://github.com/kubernetes/minikube/blob/v1.32.0/deploy/kicbase/02-crio.conf\\n\\nWe need to change this default configuration to say that for storing the images, cri-o needs to use another directory. This new directory `/host-containers` will be mounted from the `/var/lib/containers` folder inside the podman machine. This is how cri-o is able to see podman images.\\n\\nLet\'s include the configuration part in this file.\\n\\n```toml\\n[crio]\\nroot = \\"/host-containers/storage\\"\\nrunroot = \\"/host-containers/storage\\"\\n```\\n\\nLet\'s also upgrade the Podman inside the container by adding the necessary instruction to the Dockerfile.\\n\\nThe Dockerfile is coming from https://github.com/kubernetes/minikube/blob/v1.32.0/deploy/kicbase/Dockerfile#L178-L186\\n\\nIn the file, replace\\n\\n```Dockerfile\\nRUN clean-install podman && \\\\\\n```\\n\\nwith\\n\\n```Dockerfile\\nRUN sh -c \\"echo \'deb https://downloadcontent.opensuse.org/repositories/devel:/kubic:/libcontainers:/unstable/xUbuntu_22.04/ /\' > /etc/apt/sources.list.d/devel:kubic:libcontainers:unstable.list\\" && \\\\\\n curl -LO https://downloadcontent.opensuse.org/repositories/devel:kubic:libcontainers:unstable/xUbuntu_22.04/Release.key && \\\\\\n apt-key add - < Release.key && \\\\\\n # need to add dbus-user-session else we have\\n # cannot open sd-bus: No such file or directory: OCI runtime attempted to invoke a command that was not found\\n clean-install dbus-user-session podman && \\\\\\n```\\n\\nLet\'s rebuild the image and publish it. You can find it at `quay.io/fbenoit/kicbase:multiarch-2023-11-06` .\\nTo build the image, clone https://github.com/kubernetes/minikube repository, and edit the files referenced before.\\n\\nThe command to build the kicbase image is `make local-kicbase`.\\n\\n#### Trying out cri-o using the podman machine storage folder\\n\\nAt the time of writing this blog post, the version `v1.32.0-beta.0` has been used. For different versions you might need to build your own kicbase image.\\n\\nOne crucial note: cri-o is running in root mode, this is why we mount to `/var/lib/containers` (and then in rootful mode).\\n\\nFor simplicity, let\'s use a rootful podman machine to map the same folder at the two locations.\\n\\nOk now let\'s try in two steps:\\n\\n1. Create a podman machine:\\n\\n```shell\\npodman machine init --cpus 4 --memory 6000 --rootful\\n```\\n\\n2. Start the cluster using our kicbase image\\n\\nWe specify Podman as the driver (the default is Docker), state our preference to use cri-o as the container runtime instead of containerd, use our custom image that performs the update of Podman\'s version and the modification of cri-o\'s configuration to use a different storage folder. Finally, we specify an additional mount.\\n\\n```shell\\nminikube start --driver=podman --container-runtime=cri-o --base-image=quay.io/fbenoit/kicbase:multiarch-2023-11-06 --mount --mount-string \\"/var/lib/containers:/host-containers\\"\\n```\\n\\n#### Verification\\n\\nAssuming the cluster was able to start, there is a new kubernetes cluster configured in the `$HOME/.kube/config` file.\\n\\nUsing `kubectl` we can start a deployment\\n\\n```shell\\nkubectl apply -f https://k8s.io/examples/application/deployment.yaml\\n```\\n\\nyou can check pods are running using\\n\\n```shell\\nkubectl get pods -l app=nginx\\n```\\n\\nand if you check your podman images\\n\\n```\\npodman images\\n```\\n\\nyou\'ll see nginx being listed so images are shared.\\n\\nNow, you can build image using a Containerfile or pull an image, connect to the control plane instance in Podman Desktop (open a shell in minikube container) and run\\n\\n```shell\\ncrictl images\\n```\\n\\nIt will list the images of podman\\n\\nNote: by default, kubernetes will use the image pull policy `Always` using the `latest` tag on your image. So it might try to fetch/pull/refresh the image you built locally. Use a specific tag or change the `imagePullPolicy` to `IfNotPresent` in your deployments.\\n\\nYou can now use your own Containerfile/Dockerfile and build an image using `podman build` command. And then check that the image is available as well in the kubernetes cluster by listing images:\\n\\n```shell\\ncrictl images\\n```\\n\\n### Conclusion\\n\\nWe have explored how developers can significantly reduce turnaround times by integrating Podman and Kubernetes seamlessly.\\n\\nNow, let\'s experiment with it and provide feedback through the Podman Desktop issue tracker at https://github.com/containers/podman-desktop/issues/ .\\n\\nHere are the next steps Podman Desktop plans to take to enhance ease of use for users:\\n\\n- To make things easier, automate the process by adding this setup to a creation wizard.\\n- Collaborate with upstream Minikube project to simplify choices and remove the requirement for customized kicbase images.\\n- Enhancing the overall user-friendliness of the solution for an improved developer experience."},{"id":"podman-desktop-release-1.5","metadata":{"permalink":"/blog/podman-desktop-release-1.5","source":"@site/blog/2023-11-03-release-1.5.md","title":"Release Notes - Podman Desktop 1.5","description":"Podman Desktop 1.5 has been released!","date":"2023-11-03T00:00:00.000Z","formattedDate":"November 3, 2023","tags":[{"label":"podman-desktop","permalink":"/blog/tags/podman-desktop"},{"label":"release","permalink":"/blog/tags/release"},{"label":"kubernetes","permalink":"/blog/tags/kubernetes"},{"label":"openshift","permalink":"/blog/tags/openshift"},{"label":"onboarding","permalink":"/blog/tags/onboarding"},{"label":"compose","permalink":"/blog/tags/compose"},{"label":"extensions","permalink":"/blog/tags/extensions"},{"label":"settings","permalink":"/blog/tags/settings"}],"readingTime":8.14,"hasTruncateMarker":false,"authors":[{"name":"M\xe1ir\xedn Duffy","title":"User Experience Designer","url":"https://github.com/mairin","imageURL":"https://github.com/mairin.png","key":"duffy"}],"frontMatter":{"title":"Release Notes - Podman Desktop 1.5","description":"Podman Desktop 1.5 has been released!","slug":"podman-desktop-release-1.5","authors":"duffy","tags":["podman-desktop","release","kubernetes","openshift","onboarding","compose","extensions","settings"],"hide_table_of_contents":false,"image":"/img/blog/podman-desktop-release-1.5/onboarding-selkies.png"},"unlisted":false,"prevItem":{"title":"Share your local podman images with the Kubernetes cluster","permalink":"/blog/sharing-podman-images-with-kubernetes-cluster"},"nextItem":{"title":"Release Notes - Podman Desktop 1.4","permalink":"/blog/podman-desktop-release-1.4"}},"content":"import ReactPlayer from \'react-player\'\\n\\nPodman Desktop 1.5 Release! \ud83c\udf89\\n\\nWith this release of Podman Desktop, we\'re introducing **a new onboarding feature** that we hope will earn your \ud83e\uddad seal of approval! But wait... there\'s so much more!\\n\\n- **Onboarding**: Guided setup and configuration of **Podman** and **Compose**\\n- **Podman 4.7.2**: [Podman 4.7.2](https://github.com/containers/podman/releases) is now included in Windows and Mac installers\\n- **Command Palette**: Gain easy access to various commands via a new keyboard-driven command palette\\n- **Expanded \\"Summary\\" tab for Kubernetes pods**: Go deep with extended details on Kubernetes pods in the pod \\"Summary\\" tab\\n- **Environment file support**: Chart out environment variables for new containers to access on creation\\n- **Enhancements to the Settings area**: Get your bearings with improved Docker compatibility mode controls\\n- **Improved user experience for state changes**: No more dead reckoning on container state with improved visual indication of status\\n- **Extension API improvements**: A boatload of improvements to the extension API enabling more goodness from \ud83e\uddad Podman Desktop\'s extensions\\n\\nPodman Desktop 1.5 is now available. [Click here to download it](/downloads)!\\n\\n![Podman-desktop-1-5-hero](img/podman-desktop-release-1.5/onboarding-selkies.png)\\n\\n---\\n\\n## Release Details\\n\\n### Onboarding\\n\\nWe are introducing a new feature providing guided flows for the initial setup of specific \ud83e\uddad Podman Desktop extensions. Release 1.5 features two new onboarding flows: Podman and Compose.\\n\\nTo start the Podman onboarding flow, you can start from the dashboard notification by clicking the \\"Set up\\" button:\\n![podman-onboarding-start](https://user-images.githubusercontent.com/799683/280362279-598cc052-5ea4-4c31-849c-da9bbbcc3e42.png)\\n![podman-onboarding](https://user-images.githubusercontent.com/799683/280363859-f35b85f8-1dd4-4b7f-a995-25fe5d1ccced.png)\\n\\nVisit **Settings > Resources** screen and click the Compose \\"Setup ...\\" button in order to start Compose onboarding:\\n![compose-onboarding-start](https://user-images.githubusercontent.com/799683/280276847-ca0558ab-70ad-48cc-8dd5-67e3eb465a62.png)\\n![compose-onboarding](https://user-images.githubusercontent.com/799683/280277936-77ba0fb2-5cb0-41de-a7cf-1a3d6400fd89.png)\\n\\n### Command Palette\\n\\nA new, search-driven command palette is now available to enable quick access to various commands available across \ud83e\uddad Podman Desktop. You can try this new tool out by hitting the F1 key. [#4081](https://github.com/containers/podman-desktop/pull/4081) && [#3979](https://github.com/containers/podman-desktop/pull/3979)\\n\\n\\n\\n### Expanded \\"Summary\\" tab for Kubernetes pods\\n\\nKubernetes pods now offer a more comprehensive set of information under the \\"Summary\\" tab, including networking, volumes, environment variables, and other key metadata.\\n\\n\\n\\n### Environment file support\\n\\nWhen creating a container from the Images list, there\'s now an option to provide an environment file to set env variables for the new container. [#4026](https://github.com/containers/podman-desktop/pull/4026) && [#4025](https://github.com/containers/podman-desktop/pull/4025)\\n\\n### Enhancements to the Settings area\\n\\nThe user experience for enabling or disabling Docker compatibility is improved, with a new entry in the **Settings > Preferences** screen that includes contextual guidance. [#4093](https://github.com/containers/podman-desktop/pull/4093)\\n\\n\\n\\n### Improved user experience for state changes\\n\\nThe user experience around state changes for containers, pods, and other objects in the UI is improved, with clear status messages and improved animated visual indicator of state changes. [#4056](https://github.com/containers/podman-desktop/pull/4056)\\n\\n\\n\\n\\n\\n### Extension API improvements\\n\\nThe \ud83e\uddad Podman Desktop extension API received many improvements, including:\\n\\n- In addition to pushing and listing image from an extension, it\'s now possible to pull images from a \ud83e\uddad Podman Desktop extension [#4155](https://github.com/containers/podman-desktop/pull/4155)\\n\\n- The \ud83e\uddad Podman Desktop extension API has been enhanced with both the ability to list images & networks and the ability to create containers & networks. [#4172](https://github.com/containers/podman-desktop/pull/4172)\\n\\n- \ud83e\uddad Podman Desktop extensions now have a consistent way to run administrative tasks. [#4049](https://github.com/containers/podman-desktop/pull/4049)\\n\\n- Extensions now have the ability to register a custom Kubernetes config generator. [#3970](https://github.com/containers/podman-desktop/pull/3970)\\n\\n- The ability of extensions to add commands to UI menus has been extended; previously for action menus it was only available in the Image list screen. It is now possible for extensions to add commands to the action menus of items listed on the Containers list screen as well. [#3947](https://github.com/containers/podman-desktop/pull/3947) & [#3963](https://github.com/containers/podman-desktop/pull/3963)\\n\\n- Extensions have gained the ability to contribute menu items in the UI based on specific conditions. [#3959](https://github.com/containers/podman-desktop/pull/3959)\\n\\n- Enhanced logic for displaying or hiding properties listed under the **Settings > Preferences** screens is now available. [#4159](https://github.com/containers/podman-desktop/pull/4159)\\n\\n\\n\\n---\\n\\n## Other Notable Enhancements\\n\\n- The progress of loading an image into Kind is now visible as a task in the task manager. [#4061](https://github.com/containers/podman-desktop/pull/4061)\\n\\n![kind-progress-task](https://user-images.githubusercontent.com/42176370/270154775-eb7007b4-fd0e-4287-be9e-40ffc412de35.png)\\n\\n- It\'s now possible to start a new Podman machine right after creation, or you can create it and wait to start it later. It\'s up to you! [#4046](https://github.com/containers/podman-desktop/pull/4046)\\n\\n![podman-start-now-or-later](https://user-images.githubusercontent.com/49404737/269941187-f4768833-ecfc-4d0b-8acf-d4afedb428d9.png)\\n\\n- The Podman machine and Kubernetes provider creation forms have an updated look & feel consisted with other forms in the user interface, along with minor bug fixes. [#4317](https://github.com/containers/podman-desktop/pull/4317)\\n\\n![Updated provider creation forms](https://user-images.githubusercontent.com/19958075/274694157-fe89f3bc-e5b8-4735-96e9-669fe52c7a41.png)\\n\\n- The empty screen message shown when a search filter results in no matches now provides a message specific to filter matching, including the specific filter terms and an explicit button for clearing the filter. Previously, the screen displayed a generic message about how to create new objects of the type displayed on the screen, which led to some confusion about the status of the system. [#3988](https://github.com/containers/podman-desktop/pull/3988)\\n\\n\\n\\n- New support for adding spin animations to icons is now available. [#4188](https://github.com/containers/podman-desktop/pull/4188)\\n\\n- There is a new indeterminate progress bar type available for the task manager; this is meant for providing limited status for actions whose APIs do not provide detailed status information. [#4016](https://github.com/containers/podman-desktop/pull/4016)\\n\\n- For authenticating as admin to perform administrative tasks, \ud83e\uddad Podman Desktop now provides touchID support for macOS. [#4050](https://github.com/containers/podman-desktop/pull/4050)\\n\\n![touchID-support](https://user-images.githubusercontent.com/436777/248588015-f08115bd-d211-43ad-bddd-286d7b3a7056.png)\\n\\n\\n\\n- Support for connecting to interactive terminals for containers via tty was added. [#3900](https://github.com/containers/podman-desktop/pull/3900)\\n\\n- It\'s now more clear which container/pod providers will autostart when \ud83e\uddad Podman Desktop starts. Previously autostart had both a global and a per-provider setting. It has been simplified by removing the global setting. [#3840](https://github.com/containers/podman-desktop/pull/3840)\\n\\n- The \\"Working with containers\\" section of the documentation has been reworked and improved. [#3951](https://github.com/containers/podman-desktop/pull/3951)\\n\\n---\\n\\n## Notable Bug Fixes\\n\\n- The disable registry command was not blocking subsequent pulls from disabled registries. This has been corrected. [#4183](https://github.com/containers/podman-desktop/pull/4183)\\n\\n- Some users behind network proxies were unable to complete workflow involving the download of online resources. The mechanism for fetching these resources has been fixed to be proxy compatible to address this issue. [#3994](https://github.com/containers/podman-desktop/pull/3994)\\n\\n- The status of pods running in Kubernetes that are undergoing the deletion process is now accurately reflected in the \ud83e\uddad Podman Desktop UI. [#3877](https://github.com/containers/podman-desktop/pull/3877)\\n\\n- The image details page always listed the image as being \\"not used\\" even when it was. This has been corrected. [#3985](https://github.com/containers/podman-desktop/pull/3985)\\n\\n- Previously, deleting a specific image tag would cause all tags with the same Image ID to be deleted. This has been fixed so only the selected image tag will be deleted. [#3837](https://github.com/containers/podman-desktop/pull/3837)\\n\\n- Could not view the pod details for some remote Kubernetes cluster pods due to an encoding error. [#4371](https://github.com/containers/podman-desktop/pull/4371)\\n\\n- Error logs were being tracked separately from the actions they applied to. This has been addressed for kind cluster creation failure [#4427](https://github.com/containers/podman-desktop/pull/4427) and Compose installation failure [#4407](https://github.com/containers/podman-desktop/pull/4407).\\n\\n- For Linux users, \ud83e\uddad Podman Desktop previously did not appear under the \\"Development\\" menu when installed via Flatpak; it appeared under \\"Utilities.\\" \ud83e\uddad Podman Desktop now appears under the \\"Development\\" menu. [#3911](https://github.com/containers/podman-desktop/pull/3911)\\n\\n- Podman Machine names are no longer prefixed with the \\"Podman Machine\\" string. [#3878](https://github.com/containers/podman-desktop/pull/3878)\\n\\n![touchID-support](https://user-images.githubusercontent.com/19958075/267378447-aafdfbd7-f005-4b94-8626-9e11eec61b95.png)\\n\\n- The initial action state of pods and containers was being displayed as \\"STARTING\\" regardless of actual state; this has been corrected. [#3889](https://github.com/containers/podman-desktop/pull/3889)\\n\\n- Resizing the application window no longer makes the last lines of a container\'s terminal invisible. [#3993](https://github.com/containers/podman-desktop/pull/3993)\\n\\n- An issue with incorrect terminal behavior in response to long lines in the terminal attached to a container has been resolved. [#3955](https://github.com/containers/podman-desktop/pull/3955)\\n\\n- A spacing issue on the run image form has been corrected. [#4089]https://github.com/containers/podman-desktop/pull/4089\\n\\n- The \\"podify\\" icon & button on the Containers list was unusually large in release 1.4. That regression has been corrected in this release. [#4122](https://github.com/containers/podman-desktop/pull/4122)\\n\\n- An error in the instructions for Windows users on migrating from Docker has been corrected. [#4157](https://github.com/containers/podman-desktop/pull/4157)\\n\\n---\\n\\n## Community Thank You\\n\\n\ud83c\udf89 We\u2019d like to say a big thank you to everyone who helped to make \ud83e\uddad Podman Desktop even better. In this\\nrelease we received pull requests from the following people:\\n\\n- [afbjorklund](https://github.com/afbjorklund) in [#4373 - docs: fix broken links and add lima onboarding](https://github.com/containers/podman-desktop/pull/4373), [#4372 - docs: clear up lima column on containers page](https://github.com/containers/podman-desktop/pull/4372), [#4091 - fix: avoid errors with unexpected JSON input](https://github.com/containers/podman-desktop/pull/4091), [#4098 - docs: Lima onboarding details](https://github.com/containers/podman-desktop/pull/4098), and [#3854 - fix: check if machine init rootful flag supported](https://github.com/containers/podman-desktop/pull/3854)\\n\\n- [axel7083](https://github.com/axel7083) in [#4061 - feat: adding task progress for kind](https://github.com/containers/podman-desktop/pull/4061), [#3970 - feat: extension can register custom kube generator](https://github.com/containers/podman-desktop/pull/3970), [#3959 - feat: add when property to extensions menus](https://github.com/containers/podman-desktop/pull/3959), [#4016 - feat: indeterminate progress bar](https://github.com/containers/podman-desktop/pull/4016), [#3963 - fix: ContainerList propagating containers in ComposeActions and PodActions](https://github.com/containers/podman-desktop/pull/3963), and [#3947 - feat: extend menus capabilities](https://github.com/containers/podman-desktop/pull/3947)\\n\\n- [ayushrakesh](https://github.com/ayushrakesh) in [#4415 - Update README.md](https://github.com/containers/podman-desktop/pull/4415#)\\n\\n- [eltociear](https://github.com/eltociear) in [#4194 - Update README.md](https://github.com/containers/podman-desktop/pull/4194)\\n\\n- [foxydeveloper](https://github.com/foxydevloper) in [#4157 - docs: Correct windows instructions for migrating from docker](https://github.com/containers/podman-desktop/pull/4157)\\n\\n- [harsh-solanki21](https://github.com/harsh-solanki21) in [#4162 - fix: Removed fullstop from summary](https://github.com/containers/podman-desktop/pull/4162)\\n\\n- [rahul0x00](https://github.com/rahul0x00) in [#4240 - fix typos in README.md](https://github.com/containers/podman-desktop/pull/4240)\\n\\n- [shelar1423](https://github.com/shelar1423) in [#4221 - chore: document property setting in EXTENSIONS.md](https://github.com/containers/podman-desktop/pull/4221)\\n\\n---\\n\\n## Final notes\\n\\n### Known Issues\\n\\nWe have a discussion board topic where we have posted known issues with this release. If you run into problems, please check this list before filing a bug - if we already have an issue open for it, it saves you the time and trouble of filing, and there may be a workaround posted in the issue.\\n\\n#### [Known Issues: Podman Desktop 1.5.2](https://github.com/containers/podman-desktop/discussions/4635)\\n\\n### Fixed Issues\\n\\nThe complete list of issues fixed in this release is available [here](https://github.com/containers/podman-desktop/issues?q=is%3Aclosed+milestone%3A1.5.0).\\n\\n### Where to Download\\n\\nGet the latest release from the [Downloads](/downloads) section of the website and boost your development journey with Podman Desktop. Additionally, visit the [GitHub repository](https://github.com/containers/podman-desktop) and see how you can help us make Podman Desktop better."},{"id":"podman-desktop-release-1.4","metadata":{"permalink":"/blog/podman-desktop-release-1.4","source":"@site/blog/2023-09-18-release-1.4.md","title":"Release Notes - Podman Desktop 1.4","description":"Podman Desktop 1.4 has been released!","date":"2023-09-18T00:00:00.000Z","formattedDate":"September 18, 2023","tags":[{"label":"podman-desktop","permalink":"/blog/tags/podman-desktop"},{"label":"release","permalink":"/blog/tags/release"},{"label":"kubernetes","permalink":"/blog/tags/kubernetes"},{"label":"openshift","permalink":"/blog/tags/openshift"}],"readingTime":3.415,"hasTruncateMarker":false,"authors":[{"name":"Jeff Maury","title":"Engineering Manager","url":"https://github.com/jeffmaury","imageURL":"https://github.com/jeffmaury.png","key":"jeffmaury"}],"frontMatter":{"title":"Release Notes - Podman Desktop 1.4","description":"Podman Desktop 1.4 has been released!","slug":"podman-desktop-release-1.4","authors":["jeffmaury"],"tags":["podman-desktop","release","kubernetes","openshift"],"hide_table_of_contents":false,"image":"/img/blog/podman-desktop-release-1.4/juggling.png"},"unlisted":false,"prevItem":{"title":"Release Notes - Podman Desktop 1.5","permalink":"/blog/podman-desktop-release-1.5"},"nextItem":{"title":"Release Notes - Podman Desktop 1.3","permalink":"/blog/podman-desktop-release-1.3"}},"content":"import ReactPlayer from \'react-player\'\\n\\nPodman Desktop 1.4 Release! \ud83c\udf89\\n\\nThis is essentially a bug-fix release to fix various issues in UI, but as usual we also added a few new features.\\n\\n- **Podman 4.6.2**: Podman 4.6.2 included with Podman Desktop 1.4\\n- **Windows Arm64**: Native Windows on Arm64 installers and binaries\\n- **Port range mapping**: Start containers and map a range of ports\\n- **Terminal UX Improvement**: Persistent terminal sessions when SSH\'ing in a container\\n- **Volume Creation**: Create volume from the `Volumes` page\\n- **Bash support**: Terminals are now using `bash` if available.\\n\\nPodman Desktop 1.4 is now available. [Click here to download it](/downloads)!\\n\\n![Podman-desktop-1-4-juggling](img/podman-desktop-release-1.4/juggling.png)\\n\\n---\\n\\n## Release Details\\n\\n### Port range mapping [#3654](https://github.com/containers/podman-desktop/pull/3654)\\n\\nWhen starting a new container, you can now map a port range between host and container. If the range is not valid between host and container, an error is raised.\\n\\n![Range mapping](https://user-images.githubusercontent.com/49404737/262927546-da66b67a-0884-40b1-85bd-a9c3ea2f3f9e.gif)\\n\\n### Terminal lifetime [#3725](https://github.com/containers/podman-desktop/pull/3725)\\n\\nWhen a terminal is opened for a container, it can now be reused after you switched to another part of the Podman Desktop UI.\\n\\n![terminal lifetime](img/podman-desktop-release-1.4/terminal.gif)\\n\\n### Create volume [#3742](https://github.com/containers/podman-desktop/pull/3742)\\n\\nThe Volumes tab now has a Create volume button. The Create volume UI has a single field for the volume name.\\n\\n![create volume](img/podman-desktop-release-1.4/create-volume.gif)\\n\\n### bash support [#3750](https://github.com/containers/podman-desktop/pull/3750)\\n\\nWhen a terminal is opened for a container, if bash is available within the container, it will be used. Otherwise, sh will be used.\\n\\n![bash sh](img/podman-desktop-release-1.4/bash-sh.gif)\\n\\n### Notable Bug Fixes\\n\\n- Reduce API calls when listing containers by @benoitf [#3489](https://github.com/containers/podman-desktop/pull/3489)\\n- Removing a connection(podman machine) should redirect to previous page by @benoitf [#3576](https://github.com/containers/podman-desktop/pull/3576)\\n- Enhance error message when image is not there by @benoitf [#3587](https://github.com/containers/podman-desktop/pull/3587)\\n- Dispose kind install button when extension is deactivated (#3586) by @lstocchi [#3610](https://github.com/containers/podman-desktop/pull/3610)\\n- Replace backslash/slash on windows when building image (#3465) by @lstocchi [#3618](https://github.com/containers/podman-desktop/pull/3618)\\n- Handle null value in container command (#3620) by @lstocchi [#3625](https://github.com/containers/podman-desktop/pull/3625)\\n- Add maximum activation time for extensions by @benoitf [#3446](https://github.com/containers/podman-desktop/pull/3446)\\n- Handle single non-spread arguments by @benoitf [#3641](https://github.com/containers/podman-desktop/pull/3641)\\n- Grab usage data of volumes only on-demand by @benoitf [#3635](https://github.com/containers/podman-desktop/pull/3635)\\n- Add arm64 binaries for Windows by @benoitf [#3643](https://github.com/containers/podman-desktop/pull/3643)\\n- Include right airgap file for Windows and arm64 by @benoitf [#3651](https://github.com/containers/podman-desktop/pull/3651)\\n- Redirect to previous page when removing a kubernetes connection by @benoitf [#3650](https://github.com/containers/podman-desktop/pull/3650)\\n- Support port ranges when starting a container (#3204) by @lstocchi [#3654](https://github.com/containers/podman-desktop/pull/3654)\\n- Add a strict undefined check to messagebox result (#3692) by @lstocchi [#3699](https://github.com/containers/podman-desktop/pull/3699)\\n- Only restart if a machine is running by @cdrage [#3491](https://github.com/containers/podman-desktop/pull/3491)\\n- Session to the terminal is reused by @benoitf [#3725](https://github.com/containers/podman-desktop/pull/3725)\\n- Disable next button and show try again when onboarding failed (#3616) by @lstocchi [#3711](https://github.com/containers/podman-desktop/pull/3711)\\n- Add podman in PATH after updating process environment PATH (#3729) by @lstocchi [#3730](https://github.com/containers/podman-desktop/pull/3730)\\n- Allow to create a volume by @benoitf [#3742](https://github.com/containers/podman-desktop/pull/3742)\\n- Using bash if available otherwise sh in terminal by @axel7083 [#3750](https://github.com/containers/podman-desktop/pull/3750)\\n- Allow to embed existing component to onboarding (#3755) by @lstocchi [#3763](https://github.com/containers/podman-desktop/pull/3763)\\n- Some containers never return logs, do not wait for them by @dgolovin [#3784](https://github.com/containers/podman-desktop/pull/3784)\\n- Remove cancel button when on final onboarding step (#3771) by @lstocchi [#3802](https://github.com/containers/podman-desktop/pull/3802)\\n- Onboarding add link micromark for commands by @cdrage [#3747](https://github.com/containers/podman-desktop/pull/3747)\\n- Mounts can be null when using older podman by @afbjorklund [#3806](https://github.com/containers/podman-desktop/pull/3806)\\n- Remove redundant step completion check when onboarding gets started by @lstocchi [#3798](https://github.com/containers/podman-desktop/pull/3798)\\n- Ability to click enter in pull image name input by @deboer-tim [#3850](https://github.com/containers/podman-desktop/pull/3850)\\n- Set proxy environment variable when launching process by @jeffmaury [#3838](https://github.com/containers/podman-desktop/pull/3838)\\n- The socket location was moved for new podman by @afbjorklund [#3853](https://github.com/containers/podman-desktop/pull/3853)\\n- Don\'t log console errors when activating lima extension by @afbjorklund [#3852](https://github.com/containers/podman-desktop/pull/3852)\\n\\n### Community Thank You\\n\\n\ud83c\udf89 We\u2019d like to say a big thank you to everyone who helped to make Podman Desktop even better.\\n\\nA warm welcome to [@tomgoren](https://github.com/tomgoren), [@Julian](https://github.com/Julian), [@Gelob](https://github.com/Gelob) and [@cedricclyburn](https://github.com/cedricclyburn) who made their first contribution to the project in this release.\\n\\n### Final Notes\\n\\nThe complete list of issues fixed in this release is available [here](https://github.com/containers/podman-desktop/issues?q=is%3Aclosed+milestone%3A1.4.0).\\n\\nGet the latest release from the [Downloads](/downloads) section of the website and boost your development journey with Podman Desktop. Additionally, visit the [GitHub repository](https://github.com/containers/podman-desktop) and see how you can help us make Podman Desktop better."},{"id":"podman-desktop-release-1.3","metadata":{"permalink":"/blog/podman-desktop-release-1.3","source":"@site/blog/2023-08-16-release-1.3.md","title":"Release Notes - Podman Desktop 1.3","description":"Podman Desktop 1.3 has been released!","date":"2023-08-16T00:00:00.000Z","formattedDate":"August 16, 2023","tags":[{"label":"podman-desktop","permalink":"/blog/tags/podman-desktop"},{"label":"release","permalink":"/blog/tags/release"},{"label":"kubernetes","permalink":"/blog/tags/kubernetes"},{"label":"openshift","permalink":"/blog/tags/openshift"}],"readingTime":5.195,"hasTruncateMarker":false,"authors":[{"name":"Denis Golovin","title":"Principal Software Engineer","url":"https://github.com/cdrage","imageURL":"https://github.com/dgolovin.png","key":"dgolovin"}],"frontMatter":{"title":"Release Notes - Podman Desktop 1.3","description":"Podman Desktop 1.3 has been released!","slug":"podman-desktop-release-1.3","authors":["dgolovin"],"tags":["podman-desktop","release","kubernetes","openshift"],"hide_table_of_contents":false,"image":"/img/blog/podman-desktop-release-1.3.webp"},"unlisted":false,"prevItem":{"title":"Release Notes - Podman Desktop 1.4","permalink":"/blog/podman-desktop-release-1.4"},"nextItem":{"title":"Release Notes - Podman Desktop 1.2","permalink":"/blog/podman-desktop-release-1.2"}},"content":"import ReactPlayer from \'react-player\'\\n\\nPodman Desktop 1.3 Release! \ud83c\udf89\\n\\nThis 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.\\n\\n- **Podman 4.6.1**: Podman 4.6.1 included in Windows and Mac installers\\n- **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\\n- **Compose group new UI elements**: You can now see summary, inspect, deploy to kubernetes, generate kube yaml and view logs\\n- **Extension packs and extension dependencies**: Install group of extensions in one click\\n- **Resource details page update**: See summary and log for resource\\n- **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\\n- **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\\n- **Podman Initial Onboarding (preview)**: Install and configure podman using included installer\\n\\nPodman Desktop 1.3 is now available. [Click here to download it](/downloads)!\\n\\n![Podman-desktop-1-3-bug-swatting](img/podman-desktop-release-1.3/title-bug-swatting.png)\\n\\n---\\n\\n## Release Details\\n\\n### Compose group Logs tab [#3176](https://github.com/containers/podman-desktop/pull/3176)\\n\\nWhen 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\\nlog for every component individually.\\n\\n![Screenshot 2023-07-11 at 12 48 47 PM](https://github.com/containers/podman-desktop/assets/6422176/743a4ffc-e291-4697-8ac5-8052cc921946)\\n\\n### Podman user-mode networking support to Windows/WSL [#3251](https://github.com/containers/podman-desktop/pull/3251)\\n\\nCertain 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.\\n\\n![user](https://github.com/containers/podman-desktop/assets/620330/2f521576-b6a6-42b5-b24d-08df5b432608)\\n\\n### Compose group Summary tab [#3317](https://github.com/containers/podman-desktop/pull/3317),\\n\\nCompose group Summary tab shows all containers in the group and let you navigate to Details page for specific container.\\n\\n\\n\\n### Compose group Inspect tab [#3316](https://github.com/containers/podman-desktop/pull/3316)\\n\\nCompose group Inspect tab shows an array of \\"container inspect\\" from docker / podman.\\n\\n\\n\\n### `Deploy to kubernetes` in compose actions [#3299](https://github.com/containers/podman-desktop/pull/3295)\\n\\nA button to deploy to kubernetes added to Compose group.\\n\\n\\n\\n### `Generate Kube` in Compose actions and `Kube` tab in compose details [#3253](https://github.com/containers/podman-desktop/pull/3253)\\n\\n`Generate Kube` item added to Compose actions and \\"Kube\\" tab is now available in Compose details view.\\n\\n\\n\\n### Install multiple extensions using extension pack [#3150](https://github.com/containers/podman-desktop/pull/3150)\\n\\nAn Extension pack introduced in Extension engine is a way to declare set of extensions to install them all at once.\\n\\n\\n\\n### Customize icons from extension [#3131](https://github.com/containers/podman-desktop/pull/3131)\\n\\nExtensions now can customize icons for list elements using `when` clause.\\n\\n![image](https://github.com/containers/podman-desktop/assets/49404737/7aae5347-4f07-4854-ba11-1f629b5ccf22)\\n\\n### Resource details page update [#1923](https://github.com/containers/podman-desktop/pull/1923)\\n\\nIf 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).\\n\\n![image](https://user-images.githubusercontent.com/49404737/229542404-bae44f89-5cd3-4baf-8b08-e934e4462697.gif)\\n\\n### `Node\'s container image` field added to `Create a Kind cluster` form [#3508](https://github.com/containers/podman-desktop/pull/3508)\\n\\nThe new `Node\'s container image` field can be used to specify the Kubernetes version used for the control-planed.\\n\\n![image](https://github.com/containers/podman-desktop/assets/42176370/b2a63faf-629f-436d-8496-7c0cd8158679)\\n\\n### Support Docker Desktop extensions using a backend [#3435](https://github.com/containers/podman-desktop/pull/3435)\\n\\nPodman Desktop now loads the containers in the backend as described in the vm section of extension descriptor the same way as Docker Desktop does.\\n\\n### Initial onboarding implementation for podman (experimental) [#3308](https://github.com/containers/podman-desktop/pull/3308)\\n\\nThis is the initial implementation for the onboarding feature. It only covers a simple onboarding for podman. Check system requirements -> install podman -> yay! Done!\\n\\n### Notable Bug Fixes\\n\\n- Updating videos to be adaptive for mobile by @mairin [#3229](https://github.com/containers/podman-desktop/pull/3229)\\n- Consistent max width and padding in settings by @deboer-tim [#3232](https://github.com/containers/podman-desktop/pull/3232)\\n- Settings navigation bar resizing by @deboer-tim in [#3231](https://github.com/containers/podman-desktop/pull/3231)\\n- Move new registry button to header by @deboer-tim [#3245](https://github.com/containers/podman-desktop/pull/3245)\\n- Bigger lima logo by @afbjorklund [#3248](https://github.com/containers/podman-desktop/pull/3248)\\n- Horizontal docker logo by @afbjorklund [#3236](https://github.com/containers/podman-desktop/pull/3236)\\n- Respect LIMA_HOME environment variable by @afbjorklund [#3254](https://github.com/containers/podman-desktop/pull/3254)\\n- Add check before writing to terminal by @lstocchi [#3263](https://github.com/containers/podman-desktop/pull/3263)\\n- Wait until remote side has fully initialized the extensions by @benoitf [#3257](https://github.com/containers/podman-desktop/pull/3257)\\n- Fix loader not centered horizontally by @benoitf [#3270](https://github.com/containers/podman-desktop/pull/3270)\\n- Troubleshooting still waiting after failure by @deboer-tim [#3354](https://github.com/containers/podman-desktop/pull/3354)\\n- Store error for build by @cdrage [#3365](https://github.com/containers/podman-desktop/pull/3365)\\n- Missing checkbox tooltips by @deboer-tim [#3380](https://github.com/containers/podman-desktop/pull/3380)\\n- Load compose logs async not await by @cdrage [#3377](https://github.com/containers/podman-desktop/pull/3377)\\n- Set rootful connection when starting rootful machine by @lstocchi [#3364](https://github.com/containers/podman-desktop/pull/3364)\\n- Default last page by @deboer-tim [#3388](https://github.com/containers/podman-desktop/pull/3388)\\n- Avoid dashboard displaying providers starting while they don\'t by @benoitf [#3451](https://github.com/containers/podman-desktop/pull/3451)\\n- Do not use extensionInfo until it is defined by @benoitf [#V](https://github.com/containers/podman-desktop/pull/3450)\\n- Allow BASIC authentication (all caps) by @cdrage [#3471](https://github.com/containers/podman-desktop/pull/3471)\\n- Allow single domain registry such as localhost:5000 by @cdrage [#3468](https://github.com/containers/podman-desktop/pull/3468)\\n- Create /usr/local/bin directory if it does not exist on binary install by @cdrage [#3425](https://github.com/containers/podman-desktop/pull/3425)\\n- Only delete selected pods by @deboer-tim [#](https://github.com/containers/podman-desktop/pull/3378)\\n- Add back \'Done\' text on the button by @benoitf [#3487](https://github.com/containers/podman-desktop/pull/3487)\\n- Do not wait for more than 5s when checking for podman ping by @benoitf [#3497](https://github.com/containers/podman-desktop/pull/3497)\\n- Add proxy support for extension using patching get and request approach by @dgolovin [#2825](https://github.com/containers/podman-desktop/pull/2825)\\n- Refresh component when field is updated by @benoitf [#3525](https://github.com/containers/podman-desktop/pull/3525)\\n- Higher-res icons for featured extensions list by @mairin [#3511](https://github.com/containers/podman-desktop/pull/3511)\\n- Main nav selection by @deboer-tim [#3510](https://github.com/containers/podman-desktop/pull/3510)\\n- kube event error when switching context by @jeffmaury [#3494](https://github.com/containers/podman-desktop/pull/3494)\\n- Reset error message each time we pull image by @benoitf [#3550](https://github.com/containers/podman-desktop/pull/3550)\\n\\n### Community Thank You\\n\\n\ud83c\udf89 We\u2019d like to say a big thank you to everyone who helped to make Podman Desktop even better.\\n\\nA warm welcome to [@rostalan](https://github.com/rostalan) and [@axel7083](https://github.com/axel7083) who made their first contribution to the project in this release.\\n\\n### Final Notes\\n\\nThe complete list of issues fixed in this release is available [here](https://github.com/containers/podman-desktop/issues?q=is%3Aclosed+milestone%3A1.3.0).\\n\\nGet the latest release from the [Downloads](/downloads) section of the website and boost your development journey with Podman Desktop. Additionally, visit the [GitHub repository](https://github.com/containers/podman-desktop) and see how you can help us make Podman Desktop better."},{"id":"podman-desktop-release-1.2","metadata":{"permalink":"/blog/podman-desktop-release-1.2","source":"@site/blog/2023-07-12-release-1.2.md","title":"Release Notes - Podman Desktop 1.2","description":"Podman Desktop 1.2 has been released!","date":"2023-07-12T00:00:00.000Z","formattedDate":"July 12, 2023","tags":[{"label":"podman-desktop","permalink":"/blog/tags/podman-desktop"},{"label":"release","permalink":"/blog/tags/release"},{"label":"kubernetes","permalink":"/blog/tags/kubernetes"},{"label":"openshift","permalink":"/blog/tags/openshift"}],"readingTime":6.05,"hasTruncateMarker":false,"authors":[{"name":"Charlie Drage","title":"Software Engineer","url":"https://github.com/cdrage","imageURL":"https://github.com/cdrage.png","key":"cdrage"}],"frontMatter":{"title":"Release Notes - Podman Desktop 1.2","description":"Podman Desktop 1.2 has been released!","slug":"podman-desktop-release-1.2","authors":["cdrage"],"tags":["podman-desktop","release","kubernetes","openshift"],"hide_table_of_contents":false,"image":"/img/blog/podman-desktop-release-1.2.webp"},"unlisted":false,"prevItem":{"title":"Release Notes - Podman Desktop 1.3","permalink":"/blog/podman-desktop-release-1.3"},"nextItem":{"title":"Release Notes - Podman Desktop 1.1","permalink":"/blog/podman-desktop-release-1.1"}},"content":"import ReactPlayer from \'react-player\'\\n\\nPodman Desktop 1.2 Release! \ud83c\udf89\\n\\nWe\'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:\\n\\n- **Added start/stop/delete/restart buttons for Compose**: You can now make changes to an entire Compose group of containers\\n- **Kubernetes context on the status bar**: Choose from multiple Kubernetes contexts more easily all from the status bar\\n- **Rename images**: Rename an image with a click of a button\\n- **Protocol handler support**: Added support for protocol handlers such as `open podman-desktop:extension/redhat.openshift-local`\\n- **Troubleshooting page**: A troubleshooting page for helping diagnose Podman Desktop related development issues\\n\\nPodman Desktop 1.2 is now available. [Click here to download it](/downloads)!\\n\\n![Podman-desktop-1-2-hero](img/podman-desktop-release-1.2/podman-desktop-release-1.2.png)\\n\\n---\\n\\n## Release Details\\n\\n### Added start/stop/delete/restart buttons for Compose\\n\\nIn 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`.\\n\\nStay 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.\\n\\n\\n\\n### Kubernetes context on the status bar\\n\\nWith 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.\\n\\n\\n\\n### Rename images\\n\\nDeployed 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](https://github.com/tuckerrc) who added the new feature.\\n\\n\\n\\n### Troubleshooting page\\n\\nDeveloping 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!\\n\\nClick on the lightbulb button on the bottom right to access the page.\\n\\n\\n\\n### Protocol handler support\\n\\nPodman 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.\\n\\n\\n\\n---\\n\\n## Other Notable Features\\n\\n- Background colors and FormPage ([PR #2977](https://github.com/containers/podman-desktop/pull/2977))\\n- Add ability to add insecure registry / skipping cert verify ([PR #2896](https://github.com/containers/podman-desktop/pull/2896))\\n- Add support for icon contribution ([PR #2984](https://github.com/containers/podman-desktop/pull/2984))\\n- Add warning dialog message that virtual machine has low memory limit ([PR #2822](https://github.com/containers/podman-desktop/pull/2822))\\n- Propose indexed name for new pod ([PR #3028](https://github.com/containers/podman-desktop/pull/3028))\\n- Add restart button after enabling / disabling mac os compatibility ([PR #2841](https://github.com/containers/podman-desktop/pull/2841))\\n- Add environment related helper constants ([PR #3079](https://github.com/containers/podman-desktop/pull/3079))\\n- Allow entrypoint and cmd when starting container ([PR #3031](https://github.com/containers/podman-desktop/pull/3031))\\n- Add a way to debug stores in troubleshooting page ([PR #3121](https://github.com/containers/podman-desktop/pull/3121))\\n- Add custompick component (#2855) ([PR #3012](https://github.com/containers/podman-desktop/pull/3012))\\n- Dynamic breadcrumbs ([PR #3119](https://github.com/containers/podman-desktop/pull/3119))\\n- Icons on form pages ([PR #3155](https://github.com/containers/podman-desktop/pull/3155))\\n- Switch more pages to formpage ([PR #3162](https://github.com/containers/podman-desktop/pull/3162))\\n- Add rename image button ([PR #2588](https://github.com/containers/podman-desktop/pull/2588))\\n- Fixed headers, improved scrollbars ([PR #2863](https://github.com/containers/podman-desktop/pull/2863))\\n- Reports warnings on failed kube deploy, fixes error out ([PR #3050](https://github.com/containers/podman-desktop/pull/3050))\\n- Kube context on statusbar ([PR #2755](https://github.com/containers/podman-desktop/pull/2755))\\n- Install provider if not installed when clicking on create new button (#2706) ([PR #2817](https://github.com/containers/podman-desktop/pull/2817))\\n- Add tag and authenticated push capacity to the extension API ([PR #2876](https://github.com/containers/podman-desktop/pull/2876))\\n- Add navigation bar e2e tests ([PR #2950](https://github.com/containers/podman-desktop/pull/2950))\\n\\n---\\n\\n## Documentation Updates\\n\\n- Fix documentation for building image of extensions ([PR #2873](https://github.com/containers/podman-desktop/pull/2873))\\n- Add Minikube install docs ([PR #2824](https://github.com/containers/podman-desktop/pull/2824))\\n- Add Minikube documentation ([PR #2694](https://github.com/containers/podman-desktop/pull/2694))\\n- Updated Building an image procedure ([PR #2964](https://github.com/containers/podman-desktop/pull/2964))\\n- Starting a container ([PR #2958](https://github.com/containers/podman-desktop/pull/2958))\\n- Pulling an image ([PR #2956](https://github.com/containers/podman-desktop/pull/2956))\\n- Updated selecting containers to run in a pod ([PR #2970](https://github.com/containers/podman-desktop/pull/2970))\\n- Pushing an image to a registry ([PR #2969](https://github.com/containers/podman-desktop/pull/2969))\\n- How to add an insecure registry ([PR #2953](https://github.com/containers/podman-desktop/pull/2953))\\n- Add documentation for lima ([PR #2995](https://github.com/containers/podman-desktop/pull/2995))\\n- Replace broken link to podman.io ([PR #2994](https://github.com/containers/podman-desktop/pull/2994))\\n- Authenticating to a pre-configured registry ([PR #2965](https://github.com/containers/podman-desktop/pull/2965))\\n- Lima is not a container engine ([PR #3051](https://github.com/containers/podman-desktop/pull/3051))\\n- Using the Troubleshooting page ([PR #3083](https://github.com/containers/podman-desktop/pull/3083))\\n- View and select your current Kubernetes context in the status bar ([PR #3090](https://github.com/containers/podman-desktop/pull/3090))\\n\\n---\\n\\n## Notable Bug Fixes\\n\\n- Deleting a running pod generates an error ([PR #2827](https://github.com/containers/podman-desktop/pull/2827))\\n- If kubeconfig is empty, does not try to do things, cancel ([PR #2874](https://github.com/containers/podman-desktop/pull/2874))\\n- Async telemetry startup ([PR #2885](https://github.com/containers/podman-desktop/pull/2885))\\n- Do not block startup while waiting for kube resource refresh ([PR #2884](https://github.com/containers/podman-desktop/pull/2884))\\n- Images list too wide ([PR #2918](https://github.com/containers/podman-desktop/pull/2918))\\n- Compose deactivate function never called ([PR #2922](https://github.com/containers/podman-desktop/pull/2922))\\n- Auto-scrolling on form pages, layout issues ([PR #2927](https://github.com/containers/podman-desktop/pull/2927))\\n- Show current context in quick pick ([PR #2920](https://github.com/containers/podman-desktop/pull/2920))\\n- Remove sticky position of loader in dashboard UI (#2535) ([PR #2959](https://github.com/containers/podman-desktop/pull/2959))\\n- Undo change that broke the website ([PR #2992](https://github.com/containers/podman-desktop/pull/2992))\\n- Detailspage, resizing & consistency ([PR #2987](https://github.com/containers/podman-desktop/pull/2987))\\n- Quick pick click to close and over nav bar ([PR #2758](https://github.com/containers/podman-desktop/pull/2758))\\n- Only show empty screen when no pods ([PR #2929](https://github.com/containers/podman-desktop/pull/2929))\\n- Do not redirect to /pods when deleting pod in containerlist ([PR #2963](https://github.com/containers/podman-desktop/pull/2963))\\n- Bulk delete on pods should call the pod deletion ([PR #2979](https://github.com/containers/podman-desktop/pull/2979))\\n- Update nodejs version to 18 in .nvmrc to fix yarn install failure ([PR #2989](https://github.com/containers/podman-desktop/pull/2989))\\n- Website check targets ([PR #2996](https://github.com/containers/podman-desktop/pull/2996))\\n- Don\'t show exception to user ([PR #3034](https://github.com/containers/podman-desktop/pull/3034))\\n- Interpret arguments given to info command for example ([PR #3015](https://github.com/containers/podman-desktop/pull/3015))\\n- Change defaults for Podman machine ([PR #3061](https://github.com/containers/podman-desktop/pull/3061))\\n- Normalize development/production folders path ([PR #3113](https://github.com/containers/podman-desktop/pull/3113))\\n- Calculate machine socket path for linux ([PR #3070](https://github.com/containers/podman-desktop/pull/3070))\\n- Replace backslash with slash so to support rendering on Windows (#3120) ([PR #3122](https://github.com/containers/podman-desktop/pull/3122))\\n- Keep stdout and stderr in the error object for Docker Desktop extensions ([PR #3014](https://github.com/containers/podman-desktop/pull/3014))\\n- Mark task completed if there\'s a failure ([PR #3016](https://github.com/containers/podman-desktop/pull/3016))\\n- Handle invalid kubeconfig file ([PR #3129](https://github.com/containers/podman-desktop/pull/3129))\\n- Do not remove registries when podman extension is stopping ([PR #3136](https://github.com/containers/podman-desktop/pull/3136))\\n- Warning should be amber ([PR #3153](https://github.com/containers/podman-desktop/pull/3153))\\n- Load user extensions from plugins as removable ([PR #3152](https://github.com/containers/podman-desktop/pull/3152))\\n- Images with spaces in entrypoints or commands fail to start ([PR #3161](https://github.com/containers/podman-desktop/pull/3161))\\n- Scrolling offscreen when clicking checkbox ([PR #3178](https://github.com/containers/podman-desktop/pull/3178))\\n- Avoid messagebox expanding offscreen ([PR #2778](https://github.com/containers/podman-desktop/pull/2778))\\n- Release-notes-generator run failure ([PR #2752](https://github.com/containers/podman-desktop/pull/2752))\\n- Unable to do a new build if the previous one failed ([PR #2721](https://github.com/containers/podman-desktop/pull/2721))\\n\\n---\\n\\n## Community Thank You\\n\\n\ud83c\udf89 We\u2019d like to say a big thank you to everyone who helped to make Podman Desktop even better.\\n\\nA big shoutout to [@afbjorklund](https://github.com/afbjorklund), [@tuckerrc](https://github.com/tuckerrc) and [@evanshortiss](https://github.com/evanshortiss) who contributed to this release!\\n\\n---\\n\\n## Final notes\\n\\nThe complete list of issues fixed in this release is available [here](https://github.com/containers/podman-desktop/issues?q=is%3Aclosed+milestone%3A1.2.0) and [here](https://github.com/containers/podman-desktop/issues?q=is%3Aclosed+milestone%3A1.2.0).\\n\\nGet the latest release from the [Downloads](/downloads) section of the website and boost your development journey with Podman Desktop. Additionally, visit the [GitHub repository](https://github.com/containers/podman-desktop) and see how you can help us make Podman Desktop better."},{"id":"podman-desktop-release-1.1","metadata":{"permalink":"/blog/podman-desktop-release-1.1","source":"@site/blog/2023-06-08-release-1.1.md","title":"Release Notes - Podman Desktop 1.1","description":"Podman Desktop 1.1 has been released!","date":"2023-06-08T00:00:00.000Z","formattedDate":"June 8, 2023","tags":[{"label":"podman-desktop","permalink":"/blog/tags/podman-desktop"},{"label":"release","permalink":"/blog/tags/release"},{"label":"kubernetes","permalink":"/blog/tags/kubernetes"},{"label":"openshift","permalink":"/blog/tags/openshift"}],"readingTime":2.465,"hasTruncateMarker":true,"authors":[{"name":"Tim deBoer","title":"Architect","url":"https://github.com/deboer-tim","imageURL":"https://github.com/deboer-tim.png","key":"deboer"}],"frontMatter":{"title":"Release Notes - Podman Desktop 1.1","description":"Podman Desktop 1.1 has been released!","slug":"podman-desktop-release-1.1","authors":["deboer"],"tags":["podman-desktop","release","kubernetes","openshift"],"hide_table_of_contents":false,"image":"/img/blog/podman-desktop-release-1.1.webp"},"unlisted":false,"prevItem":{"title":"Release Notes - Podman Desktop 1.2","permalink":"/blog/podman-desktop-release-1.2"},"nextItem":{"title":"Release Notes - Podman Desktop 1.0","permalink":"/blog/podman-desktop-release-1.0"}},"content":"import ReactPlayer from \'react-player\'\\n\\nPodman Desktop 1.1 Release! \ud83c\udf89\\n\\nThis is primarily a bug-fix release to fix a few important issues, but we\'ve managed to squeeze in a few enhancements\\nalong the way.\\n\\n\x3c!--Main Features--\x3e\\n\\n- **Podman 4.5.1**: Podman 4.5.1 now included in Windows and Mac installers.\\n- **Extensions**: Update extensions from within Podman Desktop.\\n- **Lima Support**: Choose engine type and override its name from the settings.\\n- **UX and UI Improvements**: New loading screen.\\n\\nPodman Desktop 1.1 is now available. [Click here to download it](/downloads)!\\n\\n![Podman-desktop-1-1-hero](img/podman-desktop-release-1.1/podman-desktop-release-1.1.png)\\n\\n\x3c!--truncate--\x3e\\n\\n---\\n\\n## Release Details\\n\\n### Podman v4.5.1\\n\\nPodman Desktop 1.1 moves up to [Podman 4.5.1](https://github.com/containers/podman/releases/tag/v4.5.1).\\n\\n### Extensions\\n\\nOptional extensions will follow their own lifecycle and update independently from Podman Desktop. As of\\nthis release you\'ll be able to see when there is an update available and install from within\\nPodman Desktop [#2655](https://github.com/containers/podman-desktop/pull/2655).\\n\\nWe\'ve also added options in **Settings > Preferences** to\\nautomatically check for and install extension updates.\\n\\n\\n\\n![Update extensions](img/podman-desktop-release-1.1/update-extensions.png)\\n\\n### Lima Support\\n\\nThanks to contributor [Anders Bj\xf6rklund](https://github.com/afbjorklund), we have some improvements to the\\nLima extension! In **Settings > Preferences** you can select which\\nengine type Lima runs on and override the instance name [#2674](https://github.com/containers/podman-desktop/pull/2674).\\n\\n![Lima preferences](https://user-images.githubusercontent.com/10364051/241755966-0a6a293b-b18e-4222-9c40-abd6c114d464.png)\\n\\n### Other UI and UX Improvements\\n\\n#### New Loading Screen\\n\\nWe have a new loading screen, Podman Desktop style! [#2743](https://github.com/containers/podman-desktop/pull/2743).\\n\\n\\n\\n---\\n\\n## Other Notable Enhancements\\n\\n- Docker-compose can be installed system-wide [#2718](https://github.com/containers/podman-desktop/pull/2718).\\n- Show warning when creating a pod with two containers that use the same port [#2671](https://github.com/containers/podman-desktop/pull/2671).\\n- Display Kubernetes context name in pod label [#2634](https://github.com/containers/podman-desktop/pull/2634).\\n- Add Docker compatibility button using flatpak-spawn [#1925](https://github.com/containers/podman-desktop/pull/1925).\\n- Improve UI consistency of Pull Image page [#2604](https://github.com/containers/podman-desktop/pull/2604).\\n\\n---\\n\\n## Notable Bug Fixes\\n\\n- Could not install extensions on Windows 10 [#2762](https://github.com/containers/podman-desktop/pull/2762).\\n- Could not use locally built images on Kubernetes [#2710](https://github.com/containers/podman-desktop/pull/2710).\\n- Dashboard still suggests update after installation [#2648](https://github.com/containers/podman-desktop/pull/2648).\\n- Could not Play Kubernetes YAML to Podman on Windows [#2594](https://github.com/containers/podman-desktop/pull/2594).\\n- Pod label wasn\'t always shown in list [#2614](https://github.com/containers/podman-desktop/pull/2614).\\n- Dashboard button state was resetting [#2584](https://github.com/containers/podman-desktop/pull/2584).\\n- Change checkbox style so they don\'t look like stop buttons [#2723](https://github.com/containers/podman-desktop/pull/2723).\\n\\n---\\n\\n## Community Thank You\\n\\n\ud83c\udf89 We\u2019d like to say a big thank you to everyone who helped to make Podman Desktop even better. In this\\nsprint we received pull requests from the following people:\\n\\n- [wangxiaolei](https://github.com/fatelei) in [#2602 - Add meaningful tooltips to build, pull, prune buttons](https://github.com/containers/podman-desktop/pull/2602)\\n- [AsciiWolf](https://github.com/AsciiWolf) in [#2607 - fix typing error in Flathub name](https://github.com/containers/podman-desktop/pull/2607) and [#2609 - fix Flatpak install instructions](https://github.com/containers/podman-desktop/pull/2609)\\n- [Anders Bj\xf6rklund](https://github.com/afbjorklund) in [#2674 - Select engine for Lima provider](https://github.com/containers/podman-desktop/pull/2674)\\n\\n---\\n\\n## Final notes\\n\\nThe complete list of issues fixed in this release is available [here](https://github.com/containers/podman-desktop/issues?q=is%3Aclosed+milestone%3A1.1.0) and [here](https://github.com/containers/podman-desktop/issues?q=is%3Aclosed+milestone%3A1.1.0).\\n\\nGet the latest release from the [Downloads](/downloads) section of the website and boost your development journey with Podman Desktop. Additionally, visit the [GitHub repository](https://github.com/containers/podman-desktop) and see how you can help us make Podman Desktop better."},{"id":"podman-desktop-release-1.0","metadata":{"permalink":"/blog/podman-desktop-release-1.0","source":"@site/blog/2023-05-17-release-1.0.md","title":"Release Notes - Podman Desktop 1.0","description":"Podman Desktop 1.0 has been released!","date":"2023-05-17T00:00:00.000Z","formattedDate":"May 17, 2023","tags":[{"label":"podman-desktop","permalink":"/blog/tags/podman-desktop"},{"label":"release","permalink":"/blog/tags/release"},{"label":"kubernetes","permalink":"/blog/tags/kubernetes"},{"label":"kind","permalink":"/blog/tags/kind"},{"label":"openshift","permalink":"/blog/tags/openshift"}],"readingTime":5,"hasTruncateMarker":true,"authors":[{"name":"Tim deBoer","title":"Architect","url":"https://github.com/deboer-tim","imageURL":"https://github.com/deboer-tim.png","key":"deboer"}],"frontMatter":{"title":"Release Notes - Podman Desktop 1.0","description":"Podman Desktop 1.0 has been released!","slug":"podman-desktop-release-1.0","authors":["deboer"],"tags":["podman-desktop","release","kubernetes","kind","openshift"],"hide_table_of_contents":false,"image":"/img/blog/podman-desktop-release-1.0.jpg"},"unlisted":false,"prevItem":{"title":"Release Notes - Podman Desktop 1.1","permalink":"/blog/podman-desktop-release-1.1"},"nextItem":{"title":"Release Notes - Podman Desktop 0.15","permalink":"/blog/podman-desktop-release-0.15"}},"content":"import ReactPlayer from \'react-player\'\\n\\nPodman Desktop 1.0 Release! \ud83c\udf89\\n\\nWe still have many things planned, but with a little polish and a few more bug fixes we\\nfelt we\'ve reached a level of maturity and it is now time to declare our 1.0 release.\\n\\nThank you to everyone who has been with us on this journey so far! Please keep the\\nfeedback coming!\\n\\n\x3c!--Main Features--\x3e\\n\\n- **Highlighting Featured Extensions**: Easily find and install new extensions.\\n- **Featured Extensions**: Two new extensions supporting OpenShift.\\n- **Podman Machine as Root**: Ability to run a Podman machine as root.\\n- **UX and UI Improvements**: Opening external websites, editing numbers, and tooltips.\\n\\nPodman Desktop 1.0 is now available. [Click here to download it](/downloads)!\\n\\n![Podman-desktop-1-0-hero](img/podman-desktop-release-1.0/podman-desktop-release-1.0.jpg)\\n\\n\x3c!--truncate--\x3e\\n\\n---\\n\\n## Release Details\\n\\n### Highlighting Featured Extensions\\n\\nA critical part of our vision for Podman Desktop is the ability to install extensions to\\nsupport additional container engines, Kubernetes providers, or other tools. However, it\\nhas not been easy to discover new extensions.\\n\\nWith 1.0 we show a list of featured extensions in the **Welcome**\\n[#2354](https://github.com/containers/podman-desktop/pull/2354), the **Dashboard** and in\\n** Settings > Extensions**\\n[#2355](https://github.com/containers/podman-desktop/pull/2355). Check out the new\\nextensions for **Red Hat OpenShift Local** and the **Developer Sandbox for Red Hat OpenShift**!\\n\\n![Featured extensions](img/podman-desktop-release-1.0/featured-extensions.png)\\n\\n### Featured Extensions\\n\\nSpeaking of extensions, let\'s take a minute to turn the spotlight on these two!\\n\\nHave another idea for extending Podman Desktop? We would love to hear from you or see\\nwhat you can create with the [Extension documentation](/docs/extensions),\\nand feature your extension here.\\n\\n#### Red Hat OpenShift Local\\n\\nOpenShift Local is a fully-featured single-node OpenShift cluster designed to run on your local computer.\\nWith this extension you can install, start/stop, and deploy pods or YAML to OpenShift Local,\\nallowing you to test your applications on a full OpenShift environment, ensuring a consistent\\nexperience between development, test, and production.\\n\\nThe recent addition of the MicroShift preset provides a lighter, optimized option that\\nstarts faster and uses less resources for deployments that still want OpenShift compatibility\\nwithout the full set of OpenShift services.\\n\\n![OpenShift Local](img/podman-desktop-release-1.0/openshift-local.png)\\n\\n#### Developer Sandbox for Red Hat OpenShift\\n\\nThe OpenShift Developer Sandbox is a free, cloud-based OpenShift environment that allows developers to\\ncreate, build, and deploy applications to OpenShift for 30 days. With this extension you can sign up\\nand easily deploy pods or YAML to a hosted OpenShift environment without a local installation or\\nleaving Podman Desktop.\\n\\n![Developer Sandbox](img/podman-desktop-release-1.0/sandbox.png)\\n\\n### Podman Machine as Root\\n\\nWhen creating a Podman machine you can now decide to run as root [#2427](https://github.com/containers/podman-desktop/pull/2427). This is a prerequisite for some scenarios, such as running Kind on Windows.\\n\\n![Podman machine as root](img/podman-desktop-release-1.0/podman-root.png)\\n\\n### Other UI and UX Improvements\\n\\n#### Prompt to Open External Website\\n\\nIn the previous release links to external websites were blocked due to the security risk.\\nIn 1.0 you can click to see the URL and have the option of opening or copying it\\n[#2414](https://github.com/containers/podman-desktop/pull/2414).\\n\\n![External link dialog](img/podman-desktop-release-1.0/external-link.png)\\n\\n#### Editable Numeric Preferences\\n\\nTired of clicking +, +, +? Us too. Numeric preferences are now editable so\\nyou can directly enter the value you want\\n[#2368](https://github.com/containers/podman-desktop/pull/2368).\\n\\n![Editing numbers](img/podman-desktop-release-1.0/edit-number.png)\\n\\n#### Navigation tooltips\\n\\nWe like our new navigation bar, but the tooltips were slow to appear. This made it harder for new\\nusers to discover the pages and for power users to see the container/pod/image counts. The\\ntooltips are now a little nicer and appear immediately\\n[#2286](https://github.com/containers/podman-desktop/pull/2286).\\n\\n![Navigation tooltips](img/podman-desktop-release-1.0/nav-tooltips.png)\\n\\n---\\n\\n## Other Notable Enhancements\\n\\n- If you use a non-default Podman machine you are now prompted to make it the default, so\\n that command line tools will use the same machine [#2205](https://github.com/containers/podman-desktop/pull/2205).\\n\\n- Extensions can now be installed without requiring a running local container engine\\n [#2273](https://github.com/containers/podman-desktop/pull/2273).\\n\\n- When extensions fail to load there is a new state (failed!) and an error message\\n to help you fix or report the problem [#2424](https://github.com/containers/podman-desktop/pull/2424).\\n\\n- The showInputBox API has support for Markdown [#2418](https://github.com/containers/podman-desktop/pull/2418).\\n\\n---\\n\\n## Notable Bug Fixes\\n\\n- Fixed shared status when using multiple Podman 4.5 machines [#2441](https://github.com/containers/podman-desktop/pull/2441).\\n- Fixed hang on exit when telemetry is unreachable [#2431](https://github.com/containers/podman-desktop/pull/2431).\\n- Reduced initial Podman REST API calls to improve performance [#2419](https://github.com/containers/podman-desktop/pull/2419).\\n- **Play Kubernetes YAML** now honors the namespace [#2509](https://github.com/containers/podman-desktop/pull/2509).\\n- **Container** list was not remembering expand/collapsed status [#2491](https://github.com/containers/podman-desktop/pull/2491).\\n- Clear previous error when installing Docker extension [#2469](https://github.com/containers/podman-desktop/pull/2469).\\n- Ensure correct path with running Kind CLI [#2455](https://github.com/containers/podman-desktop/pull/2455).\\n- Use IPv4 over IPv6 by default [#2398](https://github.com/containers/podman-desktop/pull/2398).\\n- When changing the Kubernetes pod name, change the app name to match [#2389](https://github.com/containers/podman-desktop/pull/2389).\\n- Fixed incorrect pod status in **Containers** view [#2387](https://github.com/containers/podman-desktop/pull/2387).\\n- **Dashboard** wasn\'t correctly refreshing Podman status [#2359](https://github.com/containers/podman-desktop/pull/2359).\\n\\n---\\n\\n## Community Thank You\\n\\n\ud83c\udf89 We\u2019d like to say a big thank you to everyone who helped to make Podman Desktop even better. In this final\\nsprint we received pull requests from the following people:\\n\\n- [Taha Attari](https://github.com/TahaAttari) in [#2470 - Update docker command in importing-saved-containers.md](https://github.com/containers/podman-desktop/pull/2470)\\n- [Jason Greene](https://github.com/n1hility) in [#2431 - Fix hang on exit when telemetry endpoint is unreachable](https://github.com/containers/podman-desktop/pull/2431)\\n- [Anders Bj\xf6rklund](https://github.com/afbjorklund) in [#2571 - Fix the location of the lima podman socket](https://github.com/containers/podman-desktop/pull/2571) and [#2572 - Fix the state of the lima container provider](https://github.com/containers/podman-desktop/pull/2572)\\n- [Tucker Chapman](https://github.com/tuckerrc) in [#2567 - Add example image name in placeholder](https://github.com/containers/podman-desktop/pull/2567)\\n\\nThere are now a total of 54 people (and two bots!) who have contributed PRs to Podman Desktop, and we\'d\\nlike to extend an extra thanks to all of those outside of the immediate development team who contributed\\nto get us here:\\n\\n[afbjorklund](https://github.com/afbjorklund),\\n[alv67](https://github.com/alv67),\\n[anjannath](https://github.com/anjannath),\\n[ankanroy-code](https://github.com/ankanroy-code),\\n[arixmkii](https://github.com/arixmkii),\\n[cblecker](https://github.com/cblecker),\\n[cfergeau](https://github.com/cfergeau),\\n[chevdor](https://github.com/chevdor),\\n[chrisjsimpson](https://github.com/chrisjsimpson),\\n[cu8code](https://github.com/cu8code),\\n[doehyunbaek](https://github.com/doehyunbaek),\\n[dylanmtaylor](https://github.com/dylanmtaylor),\\n[eidottermihi](https://github.com/eidottermihi),\\n[elervik](https://github.com/elervik),\\n[emmanuelbernard](https://github.com/emmanuelbernard),\\n[evanfpearson](https://github.com/evanfpearson),\\n[gorkem](https://github.com/gorkem),\\n[idjohnson](https://github.com/idjohnson),\\n[imphil](https://github.com/imphil),\\n[iongion](https://github.com/iongion),\\n[jlosito](https://github.com/jlosito),\\n[KevinAtSesam](https://github.com/KevinAtSesam),\\n[lsm5](https://github.com/lsm5),\\n[Mitch9378](https://github.com/Mitch9378),\\n[n1hility](https://github.com/n1hility),\\n[osslate](https://github.com/osslate),\\n[PatentLobster](https://github.com/PatentLobster),\\n[pwright](https://github.com/pwright),\\n[rdwz](https://github.com/rdwz),\\n[redhatrises](https://github.com/redhatrises),\\n[rhatdan](https://github.com/rhatdan),\\n[RobotSail](https://github.com/RobotSail),\\n[rohit-rambade](https://github.com/rohit-rambade),\\n[rsvoboda](https://github.com/rsvoboda),\\n[sfrunza13](https://github.com/sfrunza13),\\n[shemanaev](https://github.com/shemanaev),\\n[sstosh](https://github.com/sstosh),\\n[stickster](https://github.com/stickster),\\n[TahaAttari](https://github.com/TahaAttari),\\n[ths83](https://github.com/ths83),\\n[Tony-Sol](https://github.com/Tony-Sol),\\n[tuckerrc](https://github.com/tuckerrc),\\n[ucomesdag](https://github.com/ucomesdag),\\n[xbabalov](https://github.com/xbabalov),\\nzezo2019.\\n\\n---\\n\\n## Final notes\\n\\nThe complete list of issues fixed in this release is available [here](https://github.com/containers/podman-desktop/issues?q=is%3Aclosed+milestone%3A1.0.0) and [here](https://github.com/containers/podman-desktop/issues?q=is%3Aclosed+milestone%3A1.0.1).\\n\\nGet the latest release from the [Downloads](/downloads) section of the website and boost your development journey with Podman Desktop. Additionally, visit the [GitHub repository](https://github.com/containers/podman-desktop) and see how you can help us make Podman Desktop better."},{"id":"podman-desktop-release-0.15","metadata":{"permalink":"/blog/podman-desktop-release-0.15","source":"@site/blog/2023-05-02-release-0.15.md","title":"Release Notes - Podman Desktop 0.15","description":"Podman Desktop 0.15 has been released!","date":"2023-05-02T00:00:00.000Z","formattedDate":"May 2, 2023","tags":[{"label":"podman-desktop","permalink":"/blog/tags/podman-desktop"},{"label":"release","permalink":"/blog/tags/release"},{"label":"kubernetes","permalink":"/blog/tags/kubernetes"},{"label":"kind","permalink":"/blog/tags/kind"}],"readingTime":3.685,"hasTruncateMarker":true,"authors":[{"name":"Tim deBoer","title":"Architect","url":"https://github.com/deboer-tim","imageURL":"https://github.com/deboer-tim.png","key":"deboer"}],"frontMatter":{"title":"Release Notes - Podman Desktop 0.15","description":"Podman Desktop 0.15 has been released!","slug":"podman-desktop-release-0.15","authors":["deboer"],"tags":["podman-desktop","release","kubernetes","kind"],"hide_table_of_contents":false,"image":"/img/blog/podman-desktop-release-0.15.webp"},"unlisted":false,"prevItem":{"title":"Release Notes - Podman Desktop 1.0","permalink":"/blog/podman-desktop-release-1.0"},"nextItem":{"title":"Setting up and running a Kubernetes cluster locally with Podman Desktop","permalink":"/blog/running-a-local-kubernetes-cluster-with-podman-desktop"}},"content":"import ReactPlayer from \'react-player\'\\n\\nPodman Desktop 0.15 - Cleanliness is next to Podliness!\\n\\nIt has only been two weeks since our last release, but we really wanted to complete a few scenarios,\\nfix a few bugs, and show off several design updates and UI improvements that we have been working on.\\n\\n\x3c!--Main Features--\x3e\\n\\n- **Podman Version**: Podman 4.5 now included in Windows and Mac installers.\\n- **Kind Ingress**: Creating an ingress to expose services outside the Kind cluster.\\n- **Podliness**: Ability to choose external ports when podifying containers.\\n- **Cleanliness**: New navigation bar, dialog, and palette update.\\n- **UX and UI Improvements**: Markdown support for extensions.\\n\\nPodman Desktop 0.15 is now available. [Click here to download it](/downloads)!\\n\\n![Podman-desktop-0-15-hero](img/podman-desktop-release-0.15/podman-desktop-release-0.15.webp)\\n\\n\x3c!--truncate--\x3e\\n\\n---\\n\\n## Release Details\\n\\n### Update to Podman v4.5.O\\n\\nPodman Desktop 0.15 embeds [Podman 4.5.0](https://github.com/containers/podman/releases/tag/v4.5.0) in\\nWindows and macOS installers [#2115](https://github.com/containers/podman-desktop/issues/2115).\\n\\n### Kind Ingress\\n\\nWait a minute, didn\'t we enable this last release? Well yes, last time we did add support for installing\\nthe Contour ingress controller on Kind [#1675](https://github.com/containers/podman-desktop/issues/1675),\\nbut you still couldn\'t access your containers without the corresponding ingress.\\n\\nThis release adds a simple checkbox you can use when deploying to Kind to create an ingress and\\nmake your service accessible [#1322](https://github.com/containers/podman-desktop/issues/1322).\\n\\n\\n\\n### Podliness: Ability to Choose External Ports when Podifying Containers\\n\\nWhen you create a pod from of a set of containers (Podifying!), you probably don\'t want to expose every\\nsingle port from every container to the world. With an updated panel you can now see which ports each container\\nexposes, pick which should remain visible outside the pod, and which are for internal use\\n[#2232](https://github.com/containers/podman-desktop/pull/2232).\\n\\n![Podify page](https://user-images.githubusercontent.com/49404737/234527674-ed14f52c-8f66-445f-8038-c8135bb61136.gif)\\n\\n### Cleanliness: New Navigation Bar, Dialogs, and Palette\\n\\nIt was time to catch up on some design ideas and do some UI cleanup!\\n\\n#### New Navgation Bar\\n\\nThe navigation bar is now always fixed on the left size, without labels. This opens up more space\\nfor the content on each page, and is easier to jump in and out of ** Settings**.\\n[#2167](https://github.com/containers/podman-desktop/issues/2167)\\n\\n![Navigation bar](img/podman-desktop-release-0.15/navigation.png)\\n\\n#### Updated Dialogs\\n\\nWe wanted messages and dialog boxes to feel a bit more integrated, so we have a new message box\\n[#1808](https://github.com/containers/podman-desktop/pull/1808) and use it for all dialogs opened by\\nextensions, pruning containers/pods/images/volumes [#2138](https://github.com/containers/podman-desktop/pull/2138),\\nand updating Podman Desktop itself [#2249](https://github.com/containers/podman-desktop/pull/2249).\\n\\n![Dialog](img/podman-desktop-release-0.15/dialog.png)\\n\\n#### Colors\\n\\nWe spent some time tweaking colors and closing on our final palette\\n[#2199](https://github.com/containers/podman-desktop/pull/2199), updating the colors in the terminal & detail page\\n[#2222](https://github.com/containers/podman-desktop/pull/2222), tweaking the navigation and main page colors\\n[#2223](https://github.com/containers/podman-desktop/pull/2223),\\nand improving the look of forms [#2156](https://github.com/containers/podman-desktop/issues/2156).\\n\\nWe\'re not done yet, but hopefully you will notice a more polished, consistent, good-looking application!\\n\\n### Other UI and UX Improvements\\n\\n#### Markdown Support for Extensions\\n\\nWe added a new component to display markdown [#2219](https://github.com/containers/podman-desktop/pull/2219) and\\nenabled it in preferences [#2253](https://github.com/containers/podman-desktop/pull/2253), and\\nprovider properties/creation pages [#2152](https://github.com/containers/podman-desktop/issues/2152).\\nWe can now embed links and other formatting in preferences, and extensions can use them in many places, for example:\\n\\n![Markdown](img/podman-desktop-release-0.15/markdown.png)\\n\\n---\\n\\n## Other Notable Enhancements\\n\\n- We know which **Settings** page is used the most often, so now it\'s the default: ** Settings > Resources** [#2105](https://github.com/containers/podman-desktop/issues/2105).\\n\\n- Extensions can now use the Tasks API to let long running tasks continue in the background [#2019](https://github.com/containers/podman-desktop/issues/2019) and the existing withProgress API also uses the task manager now\\n [#2187](https://github.com/containers/podman-desktop/pull/2187).\\n\\n![Task API](https://user-images.githubusercontent.com/695993/233560830-85cfa685-5dcd-4efa-9fae-730a8a9eef3b.gif)\\n\\n- Images are now sorted by age [#2311](https://github.com/containers/podman-desktop/pull/2311).\\n\\n- When you start/stop a container or pod, the button is now animated instead of having an separate spinner\\n [#2101](https://github.com/containers/podman-desktop/issues/2101).\\n\\n- The ** Settings > Preferences** page now has a search bar [#2128](https://github.com/containers/podman-desktop/pull/2128).\\n\\n![Search preferences](img/podman-desktop-release-0.15/prefs.png)\\n\\n- The Help page has been updated [#431](https://github.com/containers/podman-desktop/issues/431).\\n\\n![Updated Help](img/podman-desktop-release-0.15/help.png)\\n\\n---\\n\\n## Notable Bug Fixes\\n\\n- There was no way to see log or outcome if you leave the Kind cluster creation page [#2079](https://github.com/containers/podman-desktop/issues/2079).\\n- Kind image load doesn\'t show a notification [#2225](https://github.com/containers/podman-desktop/issues/2225).\\n- Fix odd selection in ** Settings > Extensions** [#2130](https://github.com/containers/podman-desktop/issues/2130).\\n- Menus are now cleaned up properly when extensions are stopped [#2188](https://github.com/containers/podman-desktop/pull/2188).\\n- Kind clusters are now cleaned up when Podman machine is stopped [#2306](https://github.com/containers/podman-desktop/pull/2306).\\n\\n---\\n\\n## Final notes\\n\\nThe complete list of issues fixed in this release is available [here](https://github.com/containers/podman-desktop/issues?q=is%3Aclosed+milestone%3A0.15.0).\\n\\nGet the latest release from the [Downloads](/downloads) section of the website and boost your development journey with Podman Desktop. Additionally, visit the [GitHub repository](https://github.com/containers/podman-desktop) and see how you can help us make Podman Desktop better."},{"id":"running-a-local-kubernetes-cluster-with-podman-desktop","metadata":{"permalink":"/blog/running-a-local-kubernetes-cluster-with-podman-desktop","source":"@site/blog/2023-04-19-running-a-local-kubernetes-cluster-with-podman-desktop.md","title":"Setting up and running a Kubernetes cluster locally with Podman Desktop","description":"Setting up and running a Kubernetes cluster locally with Podman Desktop","date":"2023-04-19T00:00:00.000Z","formattedDate":"April 19, 2023","tags":[{"label":"podman-desktop","permalink":"/blog/tags/podman-desktop"},{"label":"story","permalink":"/blog/tags/story"},{"label":"kubernetes","permalink":"/blog/tags/kubernetes"},{"label":"kind","permalink":"/blog/tags/kind"}],"readingTime":8.86,"hasTruncateMarker":true,"authors":[{"name":"Fabrice Flore-Thebault","title":"Technical writer","url":"https://github.com/themr0c","imageURL":"https://github.com/themr0c.png","key":"themr0c"}],"frontMatter":{"title":"Setting up and running a Kubernetes cluster locally with Podman Desktop","description":"Setting up and running a Kubernetes cluster locally with Podman Desktop","slug":"running-a-local-kubernetes-cluster-with-podman-desktop","authors":["themr0c"],"tags":["podman-desktop","story","kubernetes","kind"],"hide_table_of_contents":false},"unlisted":false,"prevItem":{"title":"Release Notes - Podman Desktop 0.15","permalink":"/blog/podman-desktop-release-0.15"},"nextItem":{"title":"Release Notes - Podman Desktop 0.14","permalink":"/blog/podman-desktop-release-0.14"}},"content":"In this blog post you will learn to use Podman Desktop to run the [Kubernetes documentation example: Deploying PHP Guestbook application with Redis](https://kubernetes.io/docs/tutorials/stateless-application/guestbook/).\\n\\nOn the agenda:\\n\\n1. Installing Podman Desktop.\\n1. Installing and initializing your container engine: Podman.\\n1. Installing and starting your local Kubernetes provider: Kind.\\n1. Starting the Redis leader.\\n1. Starting and scaling the Redis followers.\\n1. Starting and exposing the Guestbook frontend.\\n\\n\x3c!--truncate--\x3e\\n\\n## Installing Podman Desktop\\n\\nYou need Podman Desktop.\\n\\n1. Go to [Podman Desktop installation documentation](/docs/installation).\\n1. Click on your platform name: [Windows](/docs/installation/windows-install), [macOS](/docs/installation/macos-install), or [Linux](/docs/installation/linux-install).\\n1. Follow the instructions. Stick to the default installation method.\\n1. Start **Podman Desktop**.\\n\\nAt this point, you have a graphical user interface to:\\n\\n- Install Podman and Kind.\\n- Control and work with your container engines and Kubernetes clusters.\\n- Run your application on your container engine and migrate it to Kubernetes.\\n\\n## Installing and initializing your container engine: Podman\\n\\nPodman Desktop can control various container engines, such as:\\n\\n- Docker\\n- Lima\\n- Podman\\n\\nConsider installing the Podman container engine for:\\n\\n- Added security\\n- No daemon\\n- Open source\\n\\nContainers are a Linux technology.\\n\\n- On Linux, you can install Podman natively.\\n See: [Installing Podman on Linux](https://podman.io/docs/installation#installing-on-linux).\\n- On macOS and Windows, Podman requires to run in a Linux virtual machine: the Podman machine.\\n Use Podman Desktop to install Podman and initialize your Podman machine:\\n\\n#### Procedure\\n\\n1. Open Podman Desktop **Dashboard**\\n1. The **Dashboard** displays _Podman Desktop was not able to find an installation of Podman_.\\n1. Click on **Install**.\\n1. Podman Desktop checks the prerequisites to install Podman Engine. When necessary, follow the instructions to install prerequisites.\\n1. Podman displays the dialog: _Podman is not installed on this system, would you like to install Podman?_. Click on **Yes** to install Podman.\\n1. Click on **Initialize and start**.\\n\\n#### Verification\\n\\n- The **Dashboard** displays _Podman is running_.\\n\\n ![Podman is running](img/running-a-local-kubernetes-cluster-with-podman-desktop/podman-is-running.png)\\n\\nAt this point, you can start working with containers.\\n\\n## Installing and starting your local Kubernetes provider: Kind\\n\\nYou want to deploy your application to a local Kubernetes cluster.\\n\\nPodman Desktop can help you run Kind-powered local Kubernetes clusters on a container engine, such as Podman.\\n\\nPodman Desktop helps you [installing the `kind` CLI](/docs/kind/installing):\\n\\n1. In the status bar, click on **Kind**, and follow the prompts.\\n1. When the `kind` CLI is available, the status bar does not display **Kind**.\\n1. On Windows, [configure Podman in rootful mode](/docs/kind/configuring-podman-for-kind-on-windows)\\n\\n ```shell-session\\n $ podman system connection default podman-machine-default-root\\n ```\\n\\n1. Go to ** Settings > Resources**\\n1. In the **\\"Podman Podman** tile, click on the **** icon to restart the Podman container engine.\\n1. In the **\\"Kind Kind** tile, click on the **Create new** button.\\n 1. **Name**: enter `kind-cluster`.\\n 1. **Provider Type**: select `podman`.\\n 1. **HTTP Port**: select `9090`.\\n 1. **HTTPS Port**: select `9443`.\\n 1. **Setup an ingress controller**: `Enabled`\\n 1. Click the **Create** button.\\n ![Create a Kind cluster screen](img/running-a-local-kubernetes-cluster-with-podman-desktop/create-a-kind-cluster.png)\\n1. After successful creation, click on the **Go back to resources** button\\n\\n#### Verification\\n\\n1. In ** Settings > Resources** your Kind cluster is running/\\n\\n ![Kind cluster is running](img/running-a-local-kubernetes-cluster-with-podman-desktop/kind-cluster-is-running.png)\\n\\n1. In the **Podman Desktop** tray, open the **Kubernetes** menu: you can set the context to your Kind cluster: `kind-kind-cluster`.\\n\\n ![Kind cluster Kubernetes context in the tray](img/running-a-local-kubernetes-cluster-with-podman-desktop/kind-cluster-context-in-the-tray.png)\\n\\n At this point, you can start working with containers, and your local Kubernetes cluster.\\n\\n#### Additional resources\\n\\n- [Creating a local Kind-powered Kubernetes cluster](/docs/kind/creating-a-kind-cluster)\\n\\n## Starting the Redis leader\\n\\nThe Guestbook application uses Redis to store its data.\\n\\nWith Podman Desktop, you can prepare the Redis leader image and container on your local container engine, and deploy the results to a Kubernetes pod and service.\\nThis is functionally equal to the `redis-leader` deployment that the Kubernetes example propose.\\n\\n#### Procedure\\n\\n1. Open ** Images > Pull an image**.\\n 1. **Image to Pull**: enter `docker.io/redis:6.0.5`\\n 1. Click **Pull image** to pull the image to your container engine local image registry.\\n 1. Click **Done** to get back to the images list.\\n1. ** Search images**: enter `redis:6.0.5` to find the image.\\n1. Click **** to open the **Create a container from image** dialog.\\n 1. **Container name**: enter `leader`,\\n 1. **Local port for `6379/tcp`**: `6379`.\\n 1. Click ** Start Container** to start the container in your container engine.\\n1. ** Search containers**: enter `leader` to find the running container.\\n1. Click **** to stop the container, and leave the `6379` port available for the Redis follower container.\\n\\n1. Click ** > Deploy to Kubernetes** to open the **Deploy generated pod to Kubernetes** screen.\\n\\n 1. **Pod Name**: enter `redis-leader`.\\n 1. **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`.**\\n 1. **Expose service locally using Kubernetes Ingress**: deselect **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`**.\\n 1. **Kubernetes namespaces**: select `default`.\\n 1. Click ** Deploy**.\\n ![Deploy generated leader pod to Kubernetes screen](img/running-a-local-kubernetes-cluster-with-podman-desktop/deploy-generated-leader-pod-to-kubernetes.png)\\n 1. Wait for the pod to reach the state: **Phase: Running**.\\n 1. Click **Done**.\\n\\n#### Verification\\n\\n- The ** Pods** screen lists the running `redis-leader` pod.\\n\\n ![leader pod is running](img/running-a-local-kubernetes-cluster-with-podman-desktop/leader-pod-is-running.png)\\n\\n## Starting the Redis followers\\n\\nAlthough the Redis leader is a single Pod, you can make it highly available and meet traffic demands by adding a few Redis followers, or replicas.\\n\\n**With Podman Desktop, you can prepare the Redis follower image and container on your local container engine, and deploy the results to Kubernetes pods and services.**\\nThis is functionally equal to the `redis-follower` deployment that the Kubernetes example propose.\\n\\n#### Procedure\\n\\n1. Open ** Images > Pull an image**.\\n 1. **Image to Pull**: enter `gcr.io/google_samples/gb-redis-follower:v2`\\n 1. Click **Pull image** to pull the image to your container engine local image registry.\\n 1. Click **Done** to get back to the images list.\\n1. ** Search images**: enter `gb-redis-follower:v2` to find the image.\\n1. Click **** to open the **Create a container from image** dialog.\\n 1. **Container name**: enter `follower`,\\n 1. **Local port for `6379/tcp`**: `6379`.\\n 1. Click ** Start Container** to start the container in your container engine.\\n1. ** Search containers**: enter `follower` to find the running container.\\n1. Click **** to stop the container: you do not need it to run in the container engine.\\n1. Click ** > Deploy to Kubernetes** to open the **Deploy generated pod to Kubernetes** screen.\\n 1. **Pod Name**: enter `redis-follower`.\\n 1. **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`.**\\n 1. **Expose service locally using Kubernetes Ingress**: deselect **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`**.\\n 1. **Kubernetes namespaces**: select `default`.\\n 1. Click ** Deploy**.\\n ![Deploy generated follower pod to Kubernetes screen](img/running-a-local-kubernetes-cluster-with-podman-desktop/deploy-generated-follower-pod-to-kubernetes.png)\\n 1. Wait for the pod to reach the state: **Phase: Running**.\\n 1. Click **Done**.\\n1. To add replicas, repeat the last step with another **Pod Name** value.\\n\\n#### Verification\\n\\n- The ** Pods** screen lists the running `redis-follower` pods.\\n\\n ![follower pods are running](img/running-a-local-kubernetes-cluster-with-podman-desktop/follower-pods-are-running.png)\\n\\n## Starting the default frontend\\n\\nNow that you have the Redis storage of your Guestbook up and running, start the Guestbook web servers.\\nLike the Redis followers, deploy the frontend using Kubernetes pods and services.\\n\\nThe Guestbook app uses a PHP frontend.\\nIt is configured to communicate with either the Redis follower or leader Services, depending on whether the request is a read or a write.\\nThe frontend exposes a JSON interface, and serves a jQuery-Ajax-based UX.\\n\\nWith 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.\\nThis is functionally equal to the `frontend` deployment that the Kubernetes example propose.\\n\\n#### Procedure\\n\\n1. Open ** Images > Pull an image**.\\n 1. **Image to Pull**: enter `gcr.io/google_samples/gb-frontend:v5`\\n 1. Click **Pull image** to pull the image to your container engine local image registry.\\n 1. Wait for the pull to complete.\\n 1. Click **Done** to get back to the images list.\\n1. ** Search images**: enter `gb-frontend:v5` to find the image.\\n1. Click **** to open the **Create a container from image** dialog.\\n 1. **Container name**: enter `frontend`,\\n 1. **Local port for `80/tcp`**: `9000`.\\n 1. Click ** Start Container** to start the container in your container engine.\\n1. ** Search containers**: enter `frontend` to find the running container.\\n1. Click **** to stop the container: you do not need it to run in the container engine.\\n1. Click ** > Deploy to Kubernetes** to open the **Deploy generated pod to Kubernetes** screen.\\n 1. **Pod Name**: enter `frontend`.\\n 1. **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`.**\\n 1. **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`**.\\n 1. **Kubernetes namespaces**: select `default`.\\n 1. Click ** Deploy**.\\n ![Deploy generated frontend pod to Kubernetes screen](img/running-a-local-kubernetes-cluster-with-podman-desktop/deploy-generated-frontend-pod-to-kubernetes.png)\\n 1. Wait for the pod to reach the state: **Phase: Running**.\\n 1. Click **Done**.\\n\\n#### Verification\\n\\n1. The ** Pods** screen lists the running `frontend` pod.\\n\\n ![`frontend` pod is running](img/running-a-local-kubernetes-cluster-with-podman-desktop/frontend-pod-is-running.png)\\n\\n1. Go to `http://localhost:9090`: the Guestbook application is running."},{"id":"podman-desktop-release-0.14","metadata":{"permalink":"/blog/podman-desktop-release-0.14","source":"@site/blog/2023-04-14-release-0.14.md","title":"Release Notes - Podman Desktop 0.14","description":"Podman Desktop 0.14 has been released!","date":"2023-04-14T00:00:00.000Z","formattedDate":"April 14, 2023","tags":[{"label":"podman-desktop","permalink":"/blog/tags/podman-desktop"},{"label":"release","permalink":"/blog/tags/release"},{"label":"kubernetes","permalink":"/blog/tags/kubernetes"},{"label":"kind","permalink":"/blog/tags/kind"}],"readingTime":4.025,"hasTruncateMarker":true,"authors":[{"name":"Tim deBoer","title":"Architect","url":"https://github.com/deboer-tim","imageURL":"https://github.com/deboer-tim.png","key":"deboer"}],"frontMatter":{"title":"Release Notes - Podman Desktop 0.14","description":"Podman Desktop 0.14 has been released!","slug":"podman-desktop-release-0.14","authors":["deboer"],"tags":["podman-desktop","release","kubernetes","kind"],"hide_table_of_contents":false},"unlisted":false,"prevItem":{"title":"Setting up and running a Kubernetes cluster locally with Podman Desktop","permalink":"/blog/running-a-local-kubernetes-cluster-with-podman-desktop"},"nextItem":{"title":"Release Notes - Podman Desktop 0.13","permalink":"/blog/podman-desktop-release-0.13"}},"content":"import ReactPlayer from \'react-player\'\\n\\nPodman Desktop 0.14 - Our Kind-est release yet!\\n\\nWe have been working on a Kind extension for a while now, and decided it is time to promote it\\ninto a release just in time for KubeCon and CloudNativeCon Europe!\\n\\nWe\'re especially excited about releasing Kind because it finally shows the full purpose\\nof Podman Desktop: not just local container engines, but Kubernetes too. More importantly,\\nproviding tools that allow you to manage both environments and seamlessly move between them.\\n\\nSome of these features were available in development mode over the last few releases,\\nbut since they are now in the release build, we will do a full roundup and talk about\\nall the Kind features.\\n\\n\x3c!--Main Features--\x3e\\n\\n- **Kind Installation**: Install Kind from the status bar\\n- **Manage Kind Clusters**: Create and manage Kind clusters from ** Settings > Resources**\\n- **Using Kind**: Deploying YAML and sharing images to a cluster\\n- **Kind Ingress**: Install a Contour ingress controller\\n- **UX and UI Improvements**: Updated preferences and telemetry prompt\\n\\nPodman Desktop 0.14 is now available. [Click here to download it](/downloads)!\\n\\n![Podman-desktop-0-14-hero](img/podman-desktop-release-0.14/podman-desktop-release-0.14.png)\\n\\n\x3c!--truncate--\x3e\\n\\n---\\n\\n## Release details\\n\\n### Kind Installation\\n\\nGet Kind up and running in seconds! The Kind extension is now bundled as part of Podman Desktop\\n[1421](https://github.com/containers/podman-desktop/issues/1421)\\nand allows you to easily [install Kind directly from the status bar](/docs/kind/installing)\\n[1257](https://github.com/containers/podman-desktop/issues/1257).\\n\\nThe installed `kind` CLI is available from the system shell [1516](https://github.com/containers/podman-desktop/issues/1516),\\nallowing you to open a terminal window to `kind get clusters` or work with other tools.\\n\\n### Manage Kind Clusters\\n\\nOnce Kind is installed (or if you already had it), you can manage your clusters in ** Settings > Resources**.\\nFrom here you can [create Kind clusters](/docs/kind/creating-a-kind-cluster),\\nstart/stop [1953](https://github.com/containers/podman-desktop/issues/1953)\\nor delete [1977](https://github.com/containers/podman-desktop/issues/1977) them.\\n\\n![kind-clusters](img/podman-desktop-release-0.14/kind-clusters.png)\\n\\nThe Kind control plane runs as a container. You will see this container\\nin the **Container** list and can also start or stop it from there.\\n\\n### Using Kind\\n\\nNow that you have Kind installed and running, what can you do with it?\\nIf you like terminals, you can always open one up and use the Kind CLI to\\n[interact with your cluster](https://kind.sigs.k8s.io/docs/user/quick-start/#interacting-with-your-cluster).\\n\\nWithin Podman Desktop we have started with two ways to interact with the cluster.\\nThe first is the ability to play local YAML files on your Kind (or any other Kubernetes!) cluster [1261](https://github.com/containers/podman-desktop/issues/1261). This allows you to take existing Kubernetes YAML definitions -\\nyour deployments, services, or other objects - and deploy it to the cluster.\\n\\n\\n\\nAs you deploy pods, they will automatically appear in the list of **Pods** [1263](https://github.com/containers/podman-desktop/issues/1263), allowing you to start, stop, and interact them just like pods running on Podman.\\n\\nOne of the most common uses is to deploy a container that you have been running on Podman, and this will fail\\nif the image is not available in Kind. To solve this we have made it easy to push images from\\nPodman to Kind [1448](https://github.com/containers/podman-desktop/issues/1448).\\n\\n![push-image-kind](img/podman-desktop-release-0.14/push-image-kind.png)\\n\\n### Kind Ingress\\n\\nIf you deploy a pod to Kind, you are also going to want to reach it! To do this you will need to install a load balancer or\\ningress controller so that the pod is accessible from outside the cluster. We made it easy to install the Contour ingress\\ncontroller while creating a Kind cluster [1675](https://github.com/containers/podman-desktop/issues/1675),\\nso if you created your cluster with Podman Desktop it is already there!\\n\\n![kind-ingress](img/podman-desktop-release-0.14/kind-ingress.png)\\n\\nWe have several other Kind and Kubernetes features planned to expand the supported scenarios, but hopefully this\\nmakes it easy to get started with Kind and shows where we\'re headed. As always, feedback is appreciated!\\n\\n### UI and UX improvements\\n\\n#### Updated Preferences\\n\\nThe ** Settings > Preferences** page has been updated with a new design [1913](https://github.com/containers/podman-desktop/pull/1913),\\nmaking it easier to see and change preferences. Changes are live, no more Update button.\\n\\n![preferences](https://user-images.githubusercontent.com/49404737/229498507-e754b55c-dcbd-486d-9ee3-a1fe3bed7271.gif)\\n\\n#### Telemetry Prompt\\n\\nThe prompt to enable or disable telemetry has been moved from its own dialog into the **Welcome** screen.\\n[1927](https://github.com/containers/podman-desktop/pull/1927)\\nThis is more usable, one less prompt, and solves a window-layering issue for some users!\\n\\n![telemetry prompt](https://user-images.githubusercontent.com/19958075/229577331-365a9a01-0426-4482-a95d-f5dfe39af90a.png)\\n\\n---\\n\\n## Other notable enhancements\\n\\n- Extension support for opening an external URL [2028](https://github.com/containers/podman-desktop/pull/2028) and\\n accessing the clipboard [2023](https://github.com/containers/podman-desktop/pull/2023)\\n\\n---\\n\\n## Documentation\\n\\nNaturally, we have a section in the documentation just for [Kind](https://podman-desktop.io/docs/kind).\\n\\n---\\n\\n## Notable bug fixes\\n\\n- Avoid a dialog box if unable to check for updates [2062](https://github.com/containers/podman-desktop/pull/2062)\\n- Unable to get to the Dashboard if Kind (or Kubernetes) cluster was not running [2052](https://github.com/containers/podman-desktop/issues/2052)\\n\\n---\\n\\n## Final notes\\n\\nThe complete list of issues fixed in this release is available [here](https://github.com/containers/podman-desktop/issues?q=is%3Aclosed+milestone%3A0.14.0).\\n\\nGet the latest release from the [Downloads](/downloads) section of the website and boost your development journey with Podman Desktop. Additionally, visit the [GitHub repository](https://github.com/containers/podman-desktop) and see how you can help us make Podman Desktop better."},{"id":"podman-desktop-release-0.13","metadata":{"permalink":"/blog/podman-desktop-release-0.13","source":"@site/blog/2023-03-29-release-0.13.md","title":"Release Notes - Podman Desktop 0.13","description":"Podman Desktop 0.13 has been released!","date":"2023-03-29T00:00:00.000Z","formattedDate":"March 29, 2023","tags":[{"label":"podman-desktop","permalink":"/blog/tags/podman-desktop"},{"label":"release","permalink":"/blog/tags/release"},{"label":"kubernetes","permalink":"/blog/tags/kubernetes"},{"label":"compose","permalink":"/blog/tags/compose"}],"readingTime":3.155,"hasTruncateMarker":true,"authors":[{"name":"Tim deBoer","title":"Architect","url":"https://github.com/deboer-tim","imageURL":"https://github.com/deboer-tim.png","key":"deboer"}],"frontMatter":{"title":"Release Notes - Podman Desktop 0.13","description":"Podman Desktop 0.13 has been released!","slug":"podman-desktop-release-0.13","authors":["deboer"],"tags":["podman-desktop","release","kubernetes","compose"],"hide_table_of_contents":false},"unlisted":false,"prevItem":{"title":"Release Notes - Podman Desktop 0.14","permalink":"/blog/podman-desktop-release-0.14"},"nextItem":{"title":"5 things to know about Podman Desktop for a Docker user","permalink":"/blog/5-things-to-know-for-a-docker-user"}},"content":"import ReactPlayer from \'react-player\'\\n\\nThis release note covers Podman Desktop 0.13 release changes.\\n\\n\x3c!--Main Features--\x3e\\n\\n- **Podman Version**: Podman 4.4.4 now included in Windows and Mac installers.\\n- **Compose**: Support for installing Docker Compose.\\n- **Extensions**: Improved extension support for Podman Desktop with additional capabilities.\\n- **UX and UI Improvements**: Welcome page, task manager, resources, and update alerts.\\n\\nPodman Desktop 0.13 is now available. [Click here to download it](/downloads)!\\n\\n![Podman-desktop-0-13-hero](img/podman-desktop-release-0.13/podman-desktop-release-0.13.png)\\n\\n\x3c!--truncate--\x3e\\n\\n---\\n\\n## Release details\\n\\n### Update to Podman v4.4.4\\n\\nPodman Desktop 0.13 embeds [Podman 4.4.4](https://github.com/containers/podman/releases/tag/v4.4.4) in\\nWindows and macOS installers [#1456](https://github.com/containers/podman-desktop/pull/1456).\\n\\n### Compose support\\n\\nYou can install Docker Compose from the Podman Desktop UI [#1578](https://github.com/containers/podman-desktop/pull/1578). This will allow you use Compose workflows using Podman.\\n\\n### Extensions\\n\\nTo make it easier to extend Podman Desktop we have:\\n\\n- Published the [Podman Desktop Extension API](https://www.npmjs.com/package/@podman-desktop/api) to npmjs [#1727](https://github.com/containers/podman-desktop/pull/1727)\\n- Documented [how to create, publish, and install your own extensions](https://podman-desktop.io/docs/extensions)\\n- Expanded the API for `QuickPickInput` [#1839](https://github.com/containers/podman-desktop/pull/1839)\\n\\n### UI and UX improvements\\n\\n#### Welcome page [#1726](https://github.com/containers/podman-desktop/pull/1726)\\n\\nThe first time every user starts Podman Desktop, they will see a welcome page:\\n\\n![welcome-page](https://user-images.githubusercontent.com/19958075/225682776-e016ba31-5bb9-41d5-87ed-f93caeb3fb84.png)\\n\\nNote 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.\\nOver time, this page will be expanded to help with initial setup and configuration.\\n\\n#### New Task Manager [#1724](https://github.com/containers/podman-desktop/pull/1724)\\n\\nA 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](https://github.com/containers/podman-desktop/pull/1725) and Podman machine [#1742](https://github.com/containers/podman-desktop/pull/1742) are using the task manager.\\n\\n![task-manager](img/podman-desktop-release-0.13/task-manager.png)\\n\\n#### Updated Resources Settings [#1582](https://github.com/containers/podman-desktop/pull/1582)\\n\\nThe ** Settings > Resources** page has been updated with a new design, making it easier to see and control your providers from a single place.\\n\\n![resources](https://user-images.githubusercontent.com/49404737/221908815-595715fe-4c95-4087-89e0-45e5544ed5c9.gif)\\n\\nThe other settings pages have been updated for consistency with this new design.\\n\\n#### Update Alerts [#1827](https://github.com/containers/podman-desktop/pull/1827)\\n\\nA new alert button will appear in the status bar when future updates are available.\\n\\n\\n\\n#### Prune buttons [#1481](https://github.com/containers/podman-desktop/pull/1481), [#1482](https://github.com/containers/podman-desktop/pull/1482), [#1484](https://github.com/containers/podman-desktop/pull/1484)\\n\\nWe\'ve added buttons to prune unused volumes [#1481](https://github.com/containers/podman-desktop/pull/1481), images [#1482](https://github.com/containers/podman-desktop/pull/1482) and pods [#1484](https://github.com/containers/podman-desktop/pull/1484).\\n\\n![prune-image](img/podman-desktop-release-0.13/prune-image.png)\\n\\n---\\n\\n## Other notable enhancements\\n\\n- Kubernetes pods are now shown in the Pods view [#1312](https://github.com/containers/podman-desktop/pull/1312)\\n- Easy button to fix Docker compatibility mode on macOS [#1697](https://github.com/containers/podman-desktop/pull/1697)\\n- Display extension icons [#1058](https://github.com/containers/podman-desktop/pull/1058)\\n- API to cancel long running tasks [#1777](https://github.com/containers/podman-desktop/pull/1777)\\n\\n---\\n\\n## Documentation\\n\\nThe documentation has new content:\\n\\n- [How to create, publish, and install your own Podman Desktop extensions](https://podman-desktop.io/docs/extensions)\\n- [Using Compose](https://podman-desktop.io/docs/compose/podman-compose)\\n- [Restarting Kind](https://podman-desktop.io/docs/kind)\\n\\n---\\n\\n## Notable bug fixes\\n\\n- Periodically check and refresh Podman connection on Windows and Mac [#1662](https://github.com/containers/podman-desktop/pull/1662)\\n- Fix inconsistent Log view behaviour [#1710](https://github.com/containers/podman-desktop/pull/1710)\\n- Don\'t create route for regular Kubernetes clusters [#1707](https://github.com/containers/podman-desktop/pull/1707)\\n- Fix copy button on empty screen [#1804](https://github.com/containers/podman-desktop/pull/1804)\\n- Register extension tray items correctly [#1778](https://github.com/containers/podman-desktop/pull/1778) and handle updates [#1800](https://github.com/containers/podman-desktop/pull/1800)\\n\\n---\\n\\n## Community thank you\\n\\n\ud83c\udf89 We\u2019d like to say a big thank you to everyone who helped to make Podman Desktop 0.13 even better:\\n\\n- [`Tony Soloveyv`](https://github.com/Tony-Sol) in [#1605 - Fix directories inconsistency in `~/.local/share/`](https://github.com/containers/podman-desktop/pull/1605)\\n- [`Oleg`](https://github.com/RobotSail) in [#1567 - Check for Flatpak when calling command from exec](https://github.com/containers/podman-desktop/pull/1567)\\n- [`Christoph Blecker`](https://github.com/cblecker) in [#1556 - Fix: Hide dock icon on macOS if starting minimized](https://github.com/containers/podman-desktop/pull/1556)\\n- [`Paul Wright`](https://github.com/pwright) in [#1604 - Docs: correct syntax of kind doc](https://github.com/containers/podman-desktop/pull/1604)\\n- [`Denis Golovin`](https://github.com/dgolovin) in [#1790 - Feat: add EventEmitter class to extension API](https://github.com/containers/podman-desktop/pull/1790)\\n- [`Christophe Fergeau`](https://github.com/cfergeau) in [#1642 - Fix: Pod list \\"an pod\\" typing error](https://github.com/containers/podman-desktop/pull/1642)\\n\\n## Final notes\\n\\nThe complete list of issues fixed in this release is available [here](https://github.com/containers/podman-desktop/issues?q=is%3Aclosed+milestone%3A0.13.0).\\n\\nGet the latest release from the [Downloads](/downloads) section of the website and boost your development journey with Podman Desktop. Additionally, visit the [GitHub repository](https://github.com/containers/podman-desktop) and see how you can help us make Podman Desktop better."},{"id":"5-things-to-know-for-a-docker-user","metadata":{"permalink":"/blog/5-things-to-know-for-a-docker-user","source":"@site/blog/2023-03-24-5-things-to-know-for-a-docker-user.md","title":"5 things to know about Podman Desktop for a Docker user","description":"Important things to know when switching from Docker Desktop to Podman Desktop","date":"2023-03-24T00:00:00.000Z","formattedDate":"March 24, 2023","tags":[{"label":"podman-desktop","permalink":"/blog/tags/podman-desktop"},{"label":"docker","permalink":"/blog/tags/docker"},{"label":"migrating","permalink":"/blog/tags/migrating"}],"readingTime":4.285,"hasTruncateMarker":true,"authors":[{"name":"Florent Benoit","title":"Principal Software Engineer","url":"https://github.com/benoitf","imageURL":"https://github.com/benoitf.png","key":"benoitf"}],"frontMatter":{"title":"5 things to know about Podman Desktop for a Docker user","description":"Important things to know when switching from Docker Desktop to Podman Desktop","slug":"5-things-to-know-for-a-docker-user","authors":["benoitf"],"tags":["podman-desktop","docker","migrating"],"hide_table_of_contents":false},"unlisted":false,"prevItem":{"title":"Release Notes - Podman Desktop 0.13","permalink":"/blog/podman-desktop-release-0.13"},"nextItem":{"title":"Release Notes - Podman Desktop 0.12","permalink":"/blog/podman-desktop-release-0.12"}},"content":"The 5 things to know being a Docker user by using Podman Desktop:\\n\\n- **Use a single UI**: Podman Desktop works with several container engines, including Docker.\\n- The **compatibility mode**: How to ensure tools are working with Podman instead of Docker.\\n- **Compose** support: How to work with Compose files and Podman.\\n- **Kubernetes** support: How to use Kubernetes with Podman.\\n- **Security**: Use `rootless` mode or containers without root privileges.\\n\\n![5-things-to-know-for-a-docker-user-hero](img/5-things-to-know-for-a-docker-user/5-things-to-know-for-a-docker-user-hero.png)\\n\\n\x3c!--truncate--\x3e\\n\\n---\\n\\n## Use Podman Desktop to interact with containers running in Docker\\n\\nDocker 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.\\n\\nPodman 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.\\n\\nWhen 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.\\n\\n![Many container engines at the same time](img/5-things-to-know-for-a-docker-user/multiple-container-engines.png)\\n\\n## Docker compatibility mode\\n\\nUsing 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.\\n\\n### Socket file compatibility\\n\\nThe socket compatibility mode is a feature of Podman that allows to bind the Podman socket under the Docker socket path.\\n\\nOn 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.\\n\\nThat is not an issue because you can enable it by [invoking a CLI tool](https://podman-desktop.io/docs/migrating-from-docker/using-podman-mac-helper) that will setup the compatibility mode.\\n\\nFor example if you use [`TestContainers`](https://www.testcontainers.org/) in your Java project, you can use the compatibility mode to ensure that the tool will use Podman instead of Docker.\\n\\n### CLI compatibility\\n\\nIf 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.\\n\\nIf 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.\\n\\nIf you do not have the `docker` CLI installed on your computer, you can [Create a script](https://podman-desktop.io/docs/migrating-from-docker/emulating-docker-cli-with-podman) called `docker` that will call the `podman` CLI\\n\\n**_NOTE:_** creating a shell prompt alias, for example `alias docker=podman`, will not work inside scripts that you call.\\n\\n## Compose\\n\\nAs a user of Docker, you might use `docker compose` (or `docker-compose`) to run some of your applications.\\n\\nFor now Podman does not include a `Compose` support directly in the CLI with a command `podman compose`.\\n\\n`Compose` can work with the Podman socket.\\n\\nBased on the compatibility mode (see [section about Docker compatibility mode](#docker-compatibility-mode)):\\n\\n- Enabled: you can use the `compose` binary to run your applications.\\n- Disabled: you need to [export the environment variable DOCKER_HOST](https://podman-desktop.io/docs/migrating-from-docker/using-the-docker_host-environment-variable) before running compose.\\n\\nYou can now use the `compose` binary to run your applications and it will use Podman engine.\\n\\nPodman Desktop has a `compose` extension that can fetch `compose` binary if not already available on the filesystem.\\n\\nPodman Desktop UI displays the containers created by `Compose` are in the same group.\\n\\n![Compose support in the UI](img/5-things-to-know-for-a-docker-user/compose-containers-in-ui.png)\\n\\n## Kubernetes\\n\\nIt is possible to start a Kubernetes cluster with Docker.\\n\\nPodman supports directly a subset of Kubernetes resources that you can use with `.yaml` files.\\n\\nFor 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.\\n\\n![Play Kubernetes YAML](img/5-things-to-know-for-a-docker-user/play-kubernetes-yaml.png)\\n\\nIt 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.\\n\\n![Kubernetes generate](img/5-things-to-know-for-a-docker-user/kube-generate.png)\\n\\nPodman 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.\\n\\n![Pods in the UI](img/5-things-to-know-for-a-docker-user/pods-in-ui.png)\\n\\n![Containers from pod](img/5-things-to-know-for-a-docker-user/containers-from-pod.png)\\n\\nAn experimental `kind` extension is bringing the creation of full-blown Kubernetes cluster with Podman.\\n\\n## Rootless mode\\n\\nOne 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.\\n\\nIt means that for example, starting a container with a port < 1024 will not work. You need to use a port > 1024.\\n\\nIf 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.\\n\\nThe command is `podman machine set --rootful` to enable the execution with root privileges or `podman machine set --rootful=false` to switch back to rootless mode."},{"id":"podman-desktop-release-0.12","metadata":{"permalink":"/blog/podman-desktop-release-0.12","source":"@site/blog/2023-02-15-release-0.12.md","title":"Release Notes - Podman Desktop 0.12","description":"Podman Desktop 0.12 has been released!","date":"2023-02-15T00:00:00.000Z","formattedDate":"February 15, 2023","tags":[{"label":"podman-desktop","permalink":"/blog/tags/podman-desktop"},{"label":"release","permalink":"/blog/tags/release"},{"label":"kubernetes","permalink":"/blog/tags/kubernetes"}],"readingTime":4.505,"hasTruncateMarker":true,"authors":[{"name":"Stevan Le Meur","title":"Product Manager","url":"https://github.com/slemeur","imageURL":"https://github.com/slemeur.png","key":"slemeur"}],"frontMatter":{"title":"Release Notes - Podman Desktop 0.12","description":"Podman Desktop 0.12 has been released!","slug":"podman-desktop-release-0.12","authors":["slemeur"],"tags":["podman-desktop","release","kubernetes"],"hide_table_of_contents":false},"unlisted":false,"prevItem":{"title":"5 things to know about Podman Desktop for a Docker user","permalink":"/blog/5-things-to-know-for-a-docker-user"},"nextItem":{"title":"Release Notes - Podman Desktop 0.11","permalink":"/blog/podman-desktop-release-0.11"}},"content":"import ReactPlayer from \'react-player\'\\n\\nThis release note covers Podman Desktop 0.12 release changes.\\n\\n\x3c!--Main Features--\x3e\\n\\n- **Podman Version**: Podman 4.4.1 now included in Windows and Mac installers.\\n- **Containers Configuration**: Configure port mappings for an image without exported ports.\\n- **Windows Home Support**: Podman Desktop now supports Windows Home Edition.\\n- **Start minimized**: Option to start Podman Desktop minimized to system tray.\\n- **UX and UI Improvements**: Consistent actions, placeholder for logs, unified icons and others.\\n\\nPodman Desktop 0.12 is now available. [Click here to download it](/downloads)!\\n\\n![podman-desktop-0-12-hero](img/podman-desktop-release-0.12/podman-desktop-release-0.12.png)\\n\\n\x3c!--truncate--\x3e\\n\\n---\\n\\n## Release Details\\n\\n### Update to Podman v4.4.1 [#1456](https://github.com/containers/podman-desktop/pull/1456)\\n\\nPodman Desktop 0.12 embeds [Podman 4.4.1](https://github.com/containers/podman/releases/tag/v4.4.1) in Windows and macOS installers. Make sure to upgrade to benefit from the latest Podman features and bug fixes.\\n\\n### Configuring port mappings when an image has no exported port [#1265](https://github.com/containers/podman-desktop/pull/1265)\\n\\nWith 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.\\n\\n![port-mapping](https://user-images.githubusercontent.com/49404737/215112797-86dcf3f0-121a-487e-a71f-ad41e91f93da.gif)\\n\\n### Installing Podman Desktop on Windows Home Edition [#1268](https://github.com/containers/podman-desktop/pull/1268)\\n\\nPodman 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.\\n\\n![install-windows-home-edition-2](https://user-images.githubusercontent.com/436777/215121429-7c757aaa-a838-43db-98a2-78ad368f407e.png)\\n\\n### Option to automatically minimize Podman Desktop on login [#1374](https://github.com/containers/podman-desktop/pull/1374)\\n\\nPodman 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.\\n\\n- Go to ** Settings > Preferences > Login: Minimize** to activate the option.\\n\\n![minimize-on-login](https://user-images.githubusercontent.com/6422176/216651424-bcf756fd-7554-4b24-a838-e3e2f798fe6e.png)\\n\\n### UI and UX Improvements\\n\\n#### Improved actions consistency [#1225](https://github.com/containers/podman-desktop/pull/1225)\\n\\nActions displayed in the list pages for Images and Containers have been reviewed and made consistent between other pages.\\n\\n![action-consistency-1](https://user-images.githubusercontent.com/19958075/214104678-2d4148d7-484e-41f9-9da9-aecee328ae2b.png)\\n\\nActions displayed in the header of the container\'s details page have been improved so that the actions are always displayed in the same order.\\n\\n![action-consistency-2](https://user-images.githubusercontent.com/19958075/214104663-64fa0601-bb79-49bf-8226-6a78a88d3622.png)\\n\\n#### Consistent status icons for Pods, Containers, Images and Volumes [#1326](https://github.com/containers/podman-desktop/pull/1326), [#1377](https://github.com/containers/podman-desktop/pull/1377), [#1459](https://github.com/containers/podman-desktop/pull/1459) and [#1245](https://github.com/containers/podman-desktop/pull/1245)\\n\\nThe status icons for Pods, Containers, Images, and Volumes have been unified and use consistent states.\\n\\n![pods-status-icon](https://user-images.githubusercontent.com/19958075/216671859-bdd8dca4-56b7-40a8-961a-dcb6e01be61e.png)\\n\\nIcons in empty screens have been updated to use the same consistent SVG icon as the status icons.\\n\\n![empty-screen-2](https://user-images.githubusercontent.com/436777/214577726-f4cfde7b-017a-499d-a2a9-e50d455ffaf0.png)\\n\\n#### Placeholder when logs for containers are being fetched [#1353](https://github.com/containers/podman-desktop/pull/1353)\\n\\nA placeholder is now displayed when logs are being fetched.\\n![placeholder-loading-logs](https://user-images.githubusercontent.com/49404737/216952505-899308ae-183e-487a-b6e5-28832a0b6452.gif)\\n\\n#### Fixed alignment in badges from the navigation sidebar [#1357](https://github.com/containers/podman-desktop/pull/1357)\\n\\nBadges in the sidebar are now aligned with the title of the section.\\n\\n![alignement-badges](https://user-images.githubusercontent.com/49404737/216336502-2a34dea3-fd41-4184-8cfe-9226d70da070.png)\\n\\n#### Enable/disable open browser action based on container state [#1395](https://github.com/containers/podman-desktop/pull/1395) and [#1397](https://github.com/containers/podman-desktop/pull/1397)\\n\\nThe 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.\\n\\n![enable-disable-container-actions](https://user-images.githubusercontent.com/49404737/217284414-1bdc820b-30a8-485e-b0f9-485229026696.gif)\\n\\n---\\n\\n## Other Notable Enhancements\\n\\n- Display extension icons [#1058](https://github.com/containers/podman-desktop/pull/1058)\\n- Solid Icons [#1267](https://github.com/containers/podman-desktop/pull/1276)\\n- Differentiate icons compared to status icons [#1268](https://github.com/containers/podman-desktop/pull/1298)\\n- Refactors window initializing [#1309](https://github.com/containers/podman-desktop/pull/1309)\\n- Change window creation background color to dark [#1310](https://github.com/containers/podman-desktop/pull/1310)\\n- Use Podman `machine inspect` to read the address to connect to the Podman machine [#1364](https://github.com/containers/podman-desktop/pull/1364)\\n- Update the editor content when the pod name changes, and disable the deploy button when empty [#1403](https://github.com/containers/podman-desktop/pull/1403)\\n- Ability to manually set color of tray icon for Windows and Linux [#1243](https://github.com/containers/podman-desktop/pull/1243)\\n- Better UI feedback when starting pods [#1242](https://github.com/containers/podman-desktop/pull/1242)\\n\\n---\\n\\n## Documentation\\n\\nThe documentation had many editorial reviews, and new content.\\n\\n- [Link to simple WSL2 installation instructions](/docs/installation/windows-install)\\n- [Refresh Windows Installation](/docs/installation/windows-install)\\n- [Revamped installation introduction](/docs/installation)\\n- [Reorganized Linux installation](/docs/installation/linux-install)\\n- [Installing Podman with OpenShift Local](/docs/podman/installing-podman-with-openshift-local-on-windows)\\n- [Installing Podman Desktop on Windows in a restricted environment](/docs/installation/windows-install/installing-podman-desktop-and-podman-in-a-restricted-environment)\\n- [Fixed documentation on `podman-mac-helper` setup](/docs/migrating-from-docker/using-podman-mac-helper)\\n\\n---\\n\\n## Notable bug fixes\\n\\n- Fixed handling path with spaces on Windows when installing Podman [#1270](https://github.com/containers/podman-desktop/pull/1270)\\n- Removed padding from SVG icons [#1253](https://github.com/containers/podman-desktop/pull/1253)\\n- Website: fixed download links for Windows and macOS binaries [#1255](https://github.com/containers/podman-desktop/pull/1255)\\n- Fixed prettier commands on Windows [#1266](https://github.com/containers/podman-desktop/pull/1267)\\n- Fixed new xterm instance spawn when clicking the logs route [#1344](https://github.com/containers/podman-desktop/pull/1344)\\n- Fixed need to wait that telemetry has been initialized before proceeding [#1373](https://github.com/containers/podman-desktop/pull/1373)\\n- Fixed new xterm instance spawn when clicking the logs route in pod details[#1393](https://github.com/containers/podman-desktop/pull/1393)\\n- Fixed stop spinner if image cannot be retrieved [#1394](https://github.com/containers/podman-desktop/pull/1394)\\n- Fixed escape command with quotes only for Windows [#1462](https://github.com/containers/podman-desktop/pull/1462)\\n- Fixed random CRC status change [#1420](https://github.com/containers/podman-desktop/pull/1420)\\n\\n---\\n\\n## Community Thank You\\n\\n\ud83c\udf89 We\u2019d like to say a big thank you to everyone who helped to make Podman Desktop 0.12 even better:\\n\\n- [Philipp Wagner](https://github.com/imphil) in [#1274 - Link to simple WSL2 installation instructions](https://github.com/containers/podman-desktop/pull/1274)\\n- [Arthur S](https://github.com/arixmkii) in [#1364 - Get podman machine socketPath from podman machine inspect first](https://github.com/containers/podman-desktop/pull/1364)\\n- [Mitch West](https://github.com/Mitch9378) in [#1428 - Fix old documentation for \'podman-mac-helper setup\'](https://github.com/containers/podman-desktop/pull/1428)\\n\\n## Final Notes\\n\\nThe complete list of issues fixed in this release is available [here](https://github.com/containers/podman-desktop/issues?q=is%3Aclosed+milestone%3A0.12.0).\\n\\nGet the latest release from the [Downloads](/downloads) section of the website and boost your development journey with Podman Desktop. Additionally, visit the [GitHub repository](https://github.com/containers/podman-desktop) and see how you can help us make Podman Desktop better."},{"id":"podman-desktop-release-0.11","metadata":{"permalink":"/blog/podman-desktop-release-0.11","source":"@site/blog/2023-01-18-release-0.11.md","title":"Release Notes - Podman Desktop 0.11","description":"Podman Desktop 0.11 has been released!","date":"2023-01-18T00:00:00.000Z","formattedDate":"January 18, 2023","tags":[{"label":"podman-desktop","permalink":"/blog/tags/podman-desktop"},{"label":"release","permalink":"/blog/tags/release"},{"label":"kubernetes","permalink":"/blog/tags/kubernetes"}],"readingTime":9.43,"hasTruncateMarker":true,"authors":[{"name":"Stevan Le Meur","title":"Product Manager","url":"https://github.com/slemeur","imageURL":"https://github.com/slemeur.png","key":"slemeur"}],"frontMatter":{"title":"Release Notes - Podman Desktop 0.11","description":"Podman Desktop 0.11 has been released!","slug":"podman-desktop-release-0.11","authors":["slemeur"],"tags":["podman-desktop","release","kubernetes"],"hide_table_of_contents":false},"unlisted":false,"prevItem":{"title":"Release Notes - Podman Desktop 0.12","permalink":"/blog/podman-desktop-release-0.12"},"nextItem":{"title":"Release Notes - Podman Desktop 0.10","permalink":"/blog/podman-desktop-release-0.10"}},"content":"import ReactPlayer from \'react-player\'\\n\\nThis release note covers Podman Desktop 0.11 release changes.\\n\\n- **Air-Gapped Installation**: New all-in-one binaries for air-gapped installation.\\n- **Feedback**: Submit feedback directly from Podman Desktop.\\n- **Docker Compatibility Mode**: Information about the Docker compatibility mode.\\n- **Proxy Setting**: Toggle on/off the proxy setting.\\n- **Deploy to Kubernetes**: Select the namespace to deploy to Kubernetes.\\n- **Registry Configuration**: Simplified registry configuration for well known registries.\\n- **UX/UI Improvements**: View pod\'s container logs, better visual feedback, configurable editor font size, and more.\\n\\nPodman Desktop 0.11 is now available. [Click here to download it](/downloads)!\\n\\n\x3c!--truncate--\x3e\\n\\n---\\n\\n## Release Details\\n\\n### Air-Gapped installation [#1104](https://github.com/containers/podman-desktop/pull/1104) [#1120](https://github.com/containers/podman-desktop/pull/1120)\\n\\nFor users who are not able to connect to the internet, a new all-in-one (airgap) binary that includes the Podman Desktop application and the Podman binaries is now available for both Mac and Windows. When initializing a new Podman machine using all-in-one binaries, it\'ll use the embedded files and not grab them from internet:\\n\\n- on Mac, it embeds the qemu FCOS binaries.\\n- on Windows, it embeds the WSL binary.\\n\\nTo differentiate the air-gapped binaries from the regular ones, you can check the artifactname, they\'re containing \'airgap\' and are bigger.\\nPlease note, that those binaries are available only on releases and not the pre-releases.\\n\\nThere is also an optional way to provide a custom Podman machine image in the create machine form. By providing the path to the image you want, Podman Desktop will create a machine with that image. Leaving the field empty will use the default image (the one included in the binary).\\n\\n\\n\\n### Feedback within Podman Desktop [#1078](https://github.com/containers/podman-desktop/pull/1078)\\n\\nSubmitting feedback on Podman Desktop is getting easier as it is possible directly within the tool. This will help to get more information about the issues you are facing and will help us to improve the tool.\\n\\n\\n\\nPlease feel free to submit any feedback you have, we are looking forward to hearing from you!\\n\\n### Docker compatibility mode [#1047](https://github.com/containers/podman-desktop/pull/1047)\\n\\nThe Docker compatibility mode is a feature that allows to use Podman as a drop-in replacement for Docker. It relies on the Docker socket helper provided with Podman and automatically handle the local setup of Podman path to the Docker socket. Tools like [Testcontainers](https://www.testcontainers.org/) or others are relying on this to communicate to the container engine.\\n\\nIn this new version of Podman Desktop, we are now providing information to the user about the status of this compatibility mode directly on the dashboard page. The way it works is the following:\\n\\n- When Docker is running: the socket is pointing to Docker.\\n- When Podman is starting and Docker is not running: the docker API socket will use Podman.\\n\\nIn case the compatibility mode is not activated, new documentation on how to activate it and how to easily switch between Docker and Podman is available here: [https://podman-desktop.io/docs/migrating-from-docker](https://podman-desktop.io/docs/migrating-from-docker).\\n\\nThis is a warning displayed for Windows users:\\n![windows-docker-compatibility](https://user-images.githubusercontent.com/436777/209305744-9056addd-f122-4f75-9e03-ad27a0109375.png)\\n\\nThis is the warning for Mac users:\\n![mac-docker-compatibility](https://user-images.githubusercontent.com/6422176/207964861-a9c1f72c-89d6-4816-beab-397af4125620.png)\\n\\n### Allow to toggle on/off the proxy setting [#983](https://github.com/containers/podman-desktop/pull/983)\\n\\nIn 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.\\n\\n\\n\\nNote: extensions can read this information and then update the proxy configuration.\\n\\n### Namespace selection for deploy to Kubernetes [#1008](https://github.com/containers/podman-desktop/pull/1008)\\n\\nA 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.\\n\\nIf the user have set `kubectl config set-context --current --namespace=NAMESPACE` it honors that as the chosen value.\\n\\n![deploy-kubernetes-namespace](https://user-images.githubusercontent.com/7339809/206688886-095e4f15-42ae-4a0a-b1c6-ae4b547fcdfb.gif)\\n\\n### Configure Podman binary path [#941](https://github.com/containers/podman-desktop/pull/941)\\n\\nUsers might 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.\\nThis is useful for users who have installed Podman using a package manager and want to use the binary provided by the package manager.\\nSee: [Unable to set custom binary path for Podman on macOS](/docs/troubleshooting/troubleshooting-podman-on-macos#unable-to-set-custom-binary-path-for-podman-on-macos)\\n![custom-path](https://user-images.githubusercontent.com/6422176/204832063-5858065a-2fc3-49de-8d23-3b99b7d10dbf.png)\\n\\n### Provide pre-defined registries [#1201](https://github.com/containers/podman-desktop/pull/1201)\\n\\nThe 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:\\n\\n- Dockerhub\\n- Red Hat Quay\\n- GitHub\\n- IBM Container Registry\\n- Google Container Registry\\n\\n\\n\\n### UI/UX Improvements\\n\\n#### View Pods logs [#1122](https://github.com/containers/podman-desktop/pull/1122)\\n\\nThe 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.\\n\\n![pods-logs](https://user-images.githubusercontent.com/6422176/211024673-eee9bad8-1b0c-4446-b8d1-97a226282c4d.png)\\n\\n#### Improved feedback when clicking on container list action icons [#1150](https://github.com/containers/podman-desktop/pull/1150) [#1161](https://github.com/containers/podman-desktop/pull/1161)\\n\\nWhen 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.\\n\\n\\n\\nFor 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](https://github.com/containers/podman-desktop/pull/1161).\\n\\n\\n\\n#### Allows to change the default font size for the editor [#1160](https://github.com/containers/podman-desktop/pull/1160)\\n\\nAn 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).\\n\\n\\n\\n#### Keep expanded state of pods when refreshing containers [#1042](https://github.com/containers/podman-desktop/pull/1042)\\n\\nWhen 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.\\n\\n\\n\\n#### Click on the Pod name redirects to the Pod details page [#1159](https://github.com/containers/podman-desktop/pull/1159)\\n\\nThe list of containers also displays pods, now clicking on the pod name directly redirects to the Pod details page.\\n\\n\\n\\n#### Improved styles of buttons for actions [#984](https://github.com/containers/podman-desktop/pull/984)\\n\\nThe 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 visible and the icon\'s color is also changing.\\n\\nOn lists:\\n![list-actions](https://user-images.githubusercontent.com/6422176/205979121-b49a0ddf-03bb-4a4d-8d12-bc8d0bd52387.png)\\n\\nOn details pages:\\n![details-actions](https://user-images.githubusercontent.com/6422176/205979123-ea420b17-e834-4029-82eb-22949889eee9.png)\\n\\n#### Improved alignments in pages with lists [#1182](https://github.com/containers/podman-desktop/pull/1182)\\n\\nThe 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.\\n\\n![list-actions](https://user-images.githubusercontent.com/19958075/212712580-096fd090-0beb-40a4-8dc6-b3fdc5e81e35.png)\\n\\n---\\n\\n## Other Notable Enhancements\\n\\n- Statistics area in container details are always shown. ([#1131](https://github.com/containers/podman-desktop/pull/1131))\\n- Add more descriptive wording and more information to extensions. ([#985](https://github.com/containers/podman-desktop/pull/985))\\n- Allow to install on-the fly Podman Desktop extensions using an OCI image. ([#1187](https://github.com/containers/podman-desktop/pull/1187))\\n- Display correctly non-multiplexed stream in logs (when using non interactive mode). ([#1197](https://github.com/containers/podman-desktop/pull/1197))\\n- Font changed from white to gray for non-name sections (creation date, size). ([#1206](https://github.com/containers/podman-desktop/pull/1206))\\n- Add Help/about menu for macOS/Windows/Linux. ([#1207](https://github.com/containers/podman-desktop/pull/1207))\\n\\n---\\n\\n## Documentation\\n\\nComing with this new version of Podman Desktop, the documentation has been getting attention (with number of editorial reviews) and new content have been added.\\n\\nContent for helping users to migrate from Docker to Podman has been added:\\n\\n- [Using the `podman-mac-helper` tool to migrate from Docker to Podman on macOS](https://github.com/containers/podman-desktop/pull/1088)\\n- [better identify podman-mac-helper verification steps](https://github.com/containers/podman-desktop/pull/1129)\\n- [Emulating Docker CLI using Podman to migrate from Docker to Podman](https://github.com/containers/podman-desktop/pull/1143)\\n- [Migrating from Docker section](https://github.com/containers/podman-desktop/pull/1146)\\n- [Verifying that your tools are using Podman](https://github.com/containers/podman-desktop/pull/1152)\\n- [Importing saved containers](https://github.com/containers/podman-desktop/pull/1144)\\n\\nSeveral of other improvements have been made to the documentation and the website:\\n\\n- [Troubleshooting for Apple Silicon and brew x86_64 installs](https://github.com/containers/podman-desktop/pull/962)\\n- [Change text of custom binary location, add docs](https://github.com/containers/podman-desktop/pull/972)\\n- [Silent install option for windows](https://github.com/containers/podman-desktop/pull/974)\\n- [Upgrade to vite v4 and rollup v3](https://github.com/containers/podman-desktop/pull/1079)\\n- [Refreshing documentation on installing on Linux](https://github.com/containers/podman-desktop/pull/1118)\\n- [Identify the shell sessions in Installing on Linux](https://github.com/containers/podman-desktop/pull/1130)\\n- [Website: the linux binary is not a source, it should be promoted as a binary](https://github.com/containers/podman-desktop/pull/1133)\\n- [Introducing tabs for operatings systems and container engines](https://github.com/containers/podman-desktop/pull/1162)\\n- [website: In the landing page, update plugins and container engines lists](https://github.com/containers/podman-desktop/pull/1165)\\n- [Document where code is located within Podman Desktop](https://github.com/containers/podman-desktop/pull/1163)\\n- [(extension-api): Documentation on how to write an extension and use the api](https://github.com/containers/podman-desktop/pull/1172)\\n\\n---\\n\\n## Notable bug fixes\\n\\n- Update to v0.3.2 Docker Desktop API for extensions - [#1070](https://github.com/containers/podman-desktop/pull/1070)\\n- Updated link to the Matrix room - [#1076](https://github.com/containers/podman-desktop/pull/1076)\\n- Report error when container name already exists - [#1142](https://github.com/containers/podman-desktop/pull/1142)\\n- Fixed connectivity to the Podman machine when the generated socket length is greater than 104 characters in MacOS - [#1145](https://github.com/containers/podman-desktop/pull/1145)\\n- Do not use long calls for external clients - [#1151](https://github.com/containers/podman-desktop/pull/1151)\\n- Invalid name/tag for images with registries using a different port - [#1127](https://github.com/containers/podman-desktop/pull/1127)\\n- Invalid badge count for images when two images have the same tag - [#1124](https://github.com/containers/podman-desktop/pull/1124)\\n- Fixed detection of WSL2 - [#981](https://github.com/containers/podman-desktop/pull/981)\\n- Handle invalid kubeconfig files instead of crashing - [#953](https://github.com/containers/podman-desktop/pull/953)\\n- Removed redundant actions from details pages - [#1200](https://github.com/containers/podman-desktop/pull/1200)\\n- Fixed registry URL not aligned with header - [#1205](https://github.com/containers/podman-desktop/pull/1205)\\n- Moved SVGs to reusable components - [#1211](https://github.com/containers/podman-desktop/pull/1211)\\n\\n**Extensions API has also been improved in this new release:**\\n\\n- (extension-api): Allows to register a factory for kubernetes connection objects (like for container connections) - [#1040](https://github.com/containers/podman-desktop/pull/1040)\\n- (extension-api): List or inspect containers, be notified on events - [#1041](https://github.com/containers/podman-desktop/pull/1041)\\n- (extension-api): Allows to get provider notification - [#1045](https://github.com/containers/podman-desktop/pull/1045)\\n- (dd-extension-api): Implement toast API - [#1154](https://github.com/containers/podman-desktop/pull/1154)\\n- (extension-api): Moved extension properties to preferences - [#948](https://github.com/containers/podman-desktop/pull/948)\\n- (dd-extension-api): Added open dev console on dd webview in development mode - [#1071](https://github.com/containers/podman-desktop/pull/1071)\\n- (extension-api): Added notes on extension and frameworks/tooling of Podman Desktop - [#1166](https://github.com/containers/podman-desktop/pull/1166)\\n- (extension-api): Documentation on how to write an extension and use the api - [#1172](https://github.com/containers/podman-desktop/pull/1172)\\n- (dd-extension-api): DD extensions should see only minimal information on containers - [#1191](https://github.com/containers/podman-desktop/pull/1191)\\n\\n---\\n\\n## Community Thank You\\n\\n\ud83c\udf89 We\u2019d like to say a big thank you to everyone who helped to make Podman Desktop 0.11 even better:\\n\\n- [Emmanuel Bernard](https://github.com/emmanuelbernard) in [#962 - Troubleshooting for Apple Silicon](https://github.com/containers/podman-desktop/pull/962)\\n- [Michael Prankl](https://github.com/eidottermihi) in [#974 - Silent install option for windows](https://github.com/containers/podman-desktop/pull/974)\\n- [Endre Lervik](https://github.com/elervik) in [#1008 - Namespace selection for deploy to kubernetes](https://github.com/containers/podman-desktop/pull/1008)\\n- [Evan FP](https://github.com/evanfpearson) in [#1145 - fixed socket path length error](https://github.com/containers/podman-desktop/pull/1145)\\n- [Lokesh Mandvekar](https://github.com/lsm5) in [#956 - add repository key to package.json](https://github.com/containers/podman-desktop/pull/956)\\n- [Jean Fran\xe7ois Maury](https://github.com/jeffmaury) in [#1194 - Cannot create Kind cluster on Windows](https://github.com/containers/podman-desktop/pull/1194)\\n\\n## Final Notes\\n\\nThe complete list of issues fixed in this release is available [here](https://github.com/containers/podman-desktop/issues?q=is%3Aclosed+milestone%3A0.11.0).\\n\\nGet the latest release from the [Downloads](/downloads) section of the website and boost your development journey with Podman Desktop. Additionally, visit the [GitHub repository](https://github.com/containers/podman-desktop) and see how you can help us make Podman Desktop better."},{"id":"podman-desktop-release-0.10","metadata":{"permalink":"/blog/podman-desktop-release-0.10","source":"@site/blog/2022-12-01-release-0.10-blog.md","title":"Release Notes - Podman Desktop 0.10","description":"Podman Desktop 0.10 has been released! New Create Container Wizard, improved Kubernetes workflows, revamped registries configuration, and more!","date":"2022-12-01T00:00:00.000Z","formattedDate":"December 1, 2022","tags":[{"label":"podman-desktop","permalink":"/blog/tags/podman-desktop"},{"label":"release","permalink":"/blog/tags/release"},{"label":"kubernetes","permalink":"/blog/tags/kubernetes"}],"readingTime":4.115,"hasTruncateMarker":true,"authors":[{"name":"Dev Kumar","title":"Technical PMM Intern","url":"https://github.com/deekay2310","imageURL":"https://github.com/deekay2310.png","key":"deekay2310"}],"frontMatter":{"title":"Release Notes - Podman Desktop 0.10","description":"Podman Desktop 0.10 has been released! New Create Container Wizard, improved Kubernetes workflows, revamped registries configuration, and more!","slug":"podman-desktop-release-0.10","authors":["deekay2310"],"tags":["podman-desktop","release","kubernetes"],"hide_table_of_contents":false},"unlisted":false,"prevItem":{"title":"Release Notes - Podman Desktop 0.11","permalink":"/blog/podman-desktop-release-0.11"},"nextItem":{"title":"Build & run Podman Desktop in a DevContainer","permalink":"/blog/develop-using-devcontainer"}},"content":"This release note covers Podman Desktop 0.10 release changes.\\n\\n- **Containers Configuration**: Container creation wizzard allowing to define environment variables, networking and more configuration options.\\n- **Kubernetes Improvements**: Play Kubernetes YAML, custom Kubeconfig path support, reload of kube context.\\n- **Registries Configuration**: Revamped registries configuration UI.\\n- **Podman Version**: Podman 4.3.1 now included in Windows and Mac installers.\\n- **UX/UI Improvements**: Improved lists, better contrast, and more.\\n\\nPodman Desktop 0.10 is now available. [Click here to download it](/downloads)!\\n\\n\x3c!--truncate--\x3e\\n\\n---\\n\\n## Release Details\\n\\n### New configuration wizzard to create containers ([#773](https://github.com/containers/podman-desktop/pull/773))\\n\\nUntil 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.\\n\\n![new container creation wizard](img/podman-desktop-release-0.10/new_container_creation_wizard.gif)\\n\\n### Kubernetes Capabilities Improvements\\n\\n**Custom Kubeconfig file path ([#780](https://github.com/containers/podman-desktop/pull/780))**\\n\\nKubeconfig 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.\\n\\n![custom kubeconfig file path](img/podman-desktop-release-0.10/custom-kubeconfig.png)\\n\\n**Play Kubernetes YAML from the Pods list ([#739](https://github.com/containers/podman-desktop/pull/739))**\\n\\nPodman 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.\\n\\n![play k8s yaml](img/podman-desktop-release-0.10/play_k8s_yaml.gif)\\n\\n**Kube context automatically reloaded when updated ([#813](https://github.com/containers/podman-desktop/pull/813))**\\n\\nAny 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.\\n\\n### Revamped Container Registries UI ([#446](https://github.com/containers/podman-desktop/issues/446))\\n\\nThe 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.\\n\\n![registries](img/podman-desktop-release-0.10/registries.png)\\n\\n### Update to Podman 4.3.1 ([#913](https://github.com/containers/podman-desktop/issues/913))\\n\\nPodman Desktop 0.10 is now embedding [Podman 4.3.1](https://github.com/containers/podman/releases/tag/v4.3.1) in Windows and macOS installers.\\n\\n### UI/UX Improvements\\n\\n**Improved lists UX ([#877](https://github.com/containers/podman-desktop/pull/877))**\\n\\nTo 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.\\n\\n![kebab menu](img/podman-desktop-release-0.10/kebab-menu.png)\\n\\n**Delay appearance of text in navbar ([#767](https://github.com/containers/podman-desktop/pull/767))**\\n\\nWhen minimizing or expanding the navbar, the text was overlapping for a few second the page. Now it\'s displayed with a fading animation.\\n\\n**Selected state: better text color contrast ([#802](https://github.com/containers/podman-desktop/pull/802))**\\n\\nIn 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.\\n\\n![text color when hover](img/podman-desktop-release-0.10/text-color.gif)\\n\\n**On Linux and Windows, the menu bar is now hidden by default ([#668](https://github.com/containers/podman-desktop/pull/668))**\\n\\nWith 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](https://github.com/dylanmtaylor) for contributing to fix this.\\n\\n**Exit when clicking on the close icon of the dashboard on Linux ([#671](https://github.com/containers/podman-desktop/pull/671))**\\n\\nFor 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](https://github.com/dylanmtaylor) 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.\\n\\n---\\n\\n## Other Notable Enhancements\\n\\n- Rename `Started` into `Age` in Containers list.([#878](https://github.com/containers/podman-desktop/pull/878))\\n- Added domain validation when adding a registry. ([#838](https://github.com/containers/podman-desktop/pull/838))\\n- Provided a consistent behavior with Podman CLI, `podman-machine-default` is now the default name when creating a Podman machine from Podman Desktop. ([#775](https://github.com/containers/podman-desktop/pull/775))\\n\\n---\\n\\n## Notable bug fixes\\n\\n- Fixed error handling when pulling images of Desktop Extensions. ([#782](https://github.com/containers/podman-desktop/pull/782))\\n- Fixed use of the full height of the screen when displaying log in the details of a container. ([#946](https://github.com/containers/podman-desktop/discussions/946))\\n- Fixed First start of Podman Desktop on flatpak was not seeing the podman engine ([#860](https://github.com/containers/podman-desktop/pull/860))\\n\\n## Community Thank You\\n\\n\ud83c\udf89 We\u2019d like to say a big thank you to everyone who helped to make Podman Desktop 0.10 even better:\\n\\n- [Dylan M. Taylor](https://github.com/dylanmtaylor) in [#671](https://github.com/containers/podman-desktop/pull/671)\\n- [Fionn Kelleher](https://github.com/osslate) in [#713](https://github.com/containers/podman-desktop/pull/713)\\n- [Rostislav Svoboda](https://github.com/rsvoboda) in [#737](https://github.com/containers/podman-desktop/pull/737)\\n- [Denis Shemanaev](https://github.com/shemanaev) in [#783](https://github.com/containers/podman-desktop/pull/783)\\n- [Fabrice Flore-Th\xe9bault](https://github.com/themr0c) in [#856](https://github.com/containers/podman-desktop/pull/856)\\n- [Kevin](https://github.com/KevinAtSesam) in [#864](https://github.com/containers/podman-desktop/pull/864)\\n- [@sfrunza13](https://github.com/sfrunza13) in [#872](https://github.com/containers/podman-desktop/pull/872)\\n- [Anjan Nath](https://github.com/anjannath) in [#918](https://github.com/containers/podman-desktop/pull/918)\\n\\n## Final Notes\\n\\nThe complete list of issues fixed in this release is available [here](https://github.com/containers/podman-desktop/issues?q=is%3Aclosed+milestone%3A0.10.0).\\n\\nGet the latest release from the [Downloads](/downloads) section of the website and boost your development journey with Podman Desktop. Additionally, visit the [GitHub repository](https://github.com/containers/podman-desktop) and see how you can help us make Podman Desktop better."},{"id":"develop-using-devcontainer","metadata":{"permalink":"/blog/develop-using-devcontainer","source":"@site/blog/2022-11-17-develop-podman-using-codespaces.md","title":"Build & run Podman Desktop in a DevContainer","description":"Develop Podman Desktop using a DevContainer locally or using GitHub Codespaces.","date":"2022-11-17T00:00:00.000Z","formattedDate":"November 17, 2022","tags":[{"label":"podman-desktop","permalink":"/blog/tags/podman-desktop"},{"label":"devcontainer","permalink":"/blog/tags/devcontainer"},{"label":"codespaces","permalink":"/blog/tags/codespaces"}],"readingTime":6.985,"hasTruncateMarker":true,"authors":[{"name":"Florent Benoit","title":"Principal Software Engineer","url":"https://github.com/benoitf","imageURL":"https://github.com/benoitf.png","key":"benoitf"}],"frontMatter":{"title":"Build & run Podman Desktop in a DevContainer","description":"Develop Podman Desktop using a DevContainer locally or using GitHub Codespaces.","slug":"develop-using-devcontainer","authors":["benoitf"],"tags":["podman-desktop","devcontainer","codespaces"],"hide_table_of_contents":false},"unlisted":false,"prevItem":{"title":"Release Notes - Podman Desktop 0.10","permalink":"/blog/podman-desktop-release-0.10"}},"content":"GitHub [announced last week](https://github.blog/changelog/2022-11-09-codespaces-for-free-and-pro-accounts/) that Codespaces is available for everyone and it includes free minutes.\\n\\nLet see how we can use a [Development Container](https://containers.dev/) 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.\\n\\nThe challenges are to run a desktop tool (Podman Desktop) and running a container engine (Podman) inside this Development Container without using too many memory !\\n\\n\x3c!--truncate--\x3e\\n\\n## Defining image of the container\\n\\nThe first thing is in the choice of the image for the container. It is possible to pick-up a default image and add some features but there is no existing feature for Podman at https://github.com/devcontainers/features/tree/main/src and most of the features are expecting to run on top of Debian/Ubuntu\\n\\nIf you are not interested in how to setup the image, jump to the [next section](#configure-the-devcontainer-using-devcontainerjson).\\n\\nPodman binaries are available quickly after the releases for Fedora. I decided then to use `Fedora 37` as the base image.\\n\\nLet start the Containerfile using:\\n\\n```docker\\nFROM quay.io/fedora/fedora:37\\n```\\n\\nThen I install Node.js 16 from official nodejs.org repository. It\'s easier to switch to the version that we need.\\n\\n```docker\\n# install Node.js + yarn\\nENV NODE_VERSION 16.18.1\\nRUN curl -SLO \\"https://nodejs.org/dist/v$NODE_VERSION/node-v$NODE_VERSION-linux-x64.tar.gz\\" && \\\\\\n tar -xzf \\"node-v$NODE_VERSION-linux-x64.tar.gz\\" -C /usr/local --strip-components=1 && \\\\\\n rm \\"node-v$NODE_VERSION-linux-x64.tar.gz\\" && \\\\\\n npm install -g yarn\\n```\\n\\nNow, all system dependencies used to run an Electron application needs to be installed.\\n\\nPodman is also installed so we can run some containers inside this container.\\n\\nAnd of course, we need to install VNC (I choose [tigervnc](https://tigervnc.org/)) with a light Window Manager ([fluxbox](http://fluxbox.org/)).\\n\\nTo connect to the display of the container, we need to expose VNC over HTML/websocket using [noVNC](https://novnc.com/)\\n\\nxterm is installed to start a terminal from the VNC side.\\n\\n```docker\\nRUN dnf -y update && \\\\\\n yum -y reinstall shadow-utils && \\\\\\n yum install -y git \\\\\\n # dependencies for Podman Desktop\\n nss \\\\\\n atk \\\\\\n at-spi2-atk \\\\\\n cups-libs \\\\\\n gtk3 \\\\\\n # for remote Display\\n fluxbox \\\\\\n tigervnc-server \\\\\\n xorg-x11-fonts-Type1 \\\\\\n novnc \\\\\\n supervisor \\\\\\n xdpyinfo \\\\\\n # for podman\\n podman \\\\\\n fuse-overlayfs --exclude container-selinux \\\\\\n xterm && \\\\\\n rm -rf /var/cache /var/log/dnf* /var/log/yum.*\\n```\\n\\nSupervisord setup the launch of the VNC server and the Window manager\\n\\n```docker\\nCOPY supervisord.conf /etc/supervisord.conf\\n```\\n\\nA custom theme for fluxbox:\\n\\n```docker\\nCOPY fluxbox /usr/share/fluxbox/init\\n```\\n\\nThen we need a special configuration to allow to have Podman working inside the container\\n\\nWe add the `podman-desktop` user with correct range on subuid and subgid when running containers. I used the [tutorial](https://github.com/containers/podman/blob/main/docs/tutorials/rootless_tutorial.md#etcsubuid-and-etcsubgid-configuration).\\n\\n```docker\\nRUN useradd -u 1000 podman-desktop && echo podman-desktop:10000:5000 > /etc/subuid && echo podman-desktop:10000:5000 > /etc/subgid\\n```\\n\\nThen use some default configuration files\\n\\n```docker\\n# initialize conf files\\nADD https://raw.githubusercontent.com/containers/libpod/master/contrib/podmanimage/stable/containers.conf /etc/containers/containers.conf\\nADD https://raw.githubusercontent.com/containers/libpod/master/contrib/podmanimage/stable/podman-containers.conf /home/podman-desktop/.config/containers/containers.conf\\n```\\n\\nand make sure that all permissions are correct following the guide [https://www.redhat.com/sysadmin/podman-inside-container](https://www.redhat.com/sysadmin/podman-inside-container)\\n\\n```docker\\n# set permissions\\nRUN chown podman-desktop:podman-desktop -R /home/podman-desktop && chmod 644 /etc/containers/containers.conf && \\\\\\n mkdir -p /var/lib/shared/overlay-images /var/lib/shared/overlay-layers /var/lib/shared/vfs-images /var/lib/shared/vfs-layers; touch /var/lib/shared/overlay-images/images.lock; touch /var/lib/shared/overlay-layers/layers.lock; touch /var/lib/shared/vfs-images/images.lock; touch /var/lib/shared/vfs-layers/layers.lock && \\\\\\n mkdir -p /run/user/1000 && chown podman-desktop:podman-desktop /run/user/1000\\n```\\n\\nplus define an empty user namespace.\\n\\n```docker\\nENV _CONTAINERS_USERNS_CONFIGURED=\\"\\"\\n```\\n\\nMake sure Podman will create the socket in an expected directory:\\n\\n```docker\\n# socket path for podman\\nENV XDG_RUNTIME_DIR=/run/user/1000\\n```\\n\\nOK ! we have a custom Containerfile providing all the tools to build and run Podman Desktop (using VNC for the display), run Podman and run Electron.\\n\\nThe current file is available at https://github.com/containers/podman-desktop/blob/main/.devcontainer/.parent/Containerfile\\n\\nLet\'s configure the DevContainer.\\n\\n## Configure the DevContainer using devcontainer.json\\n\\nDevContainer definition is stored at `.devcontainer/devcontainer.json` file.\\n\\nWe need to reuse the image of the previous step. For that let\'s use the build section of the `devcontainer.json` file.\\n\\n```json\\n\\"build\\": {\\n \\"dockerfile\\": \\"Containerfile\\"\\n},\\n```\\n\\nIn order to avoid to redo all the build steps each time we open a workspace using this dev container, we published the image to quay.io at [quay.io/podman-desktop/devcontainer-parent:next\\n](https://quay.io/repository/podman-desktop/devcontainer-parent?tab=tags&tag=next). This parent image is not changing much so it\'s better to use is as a parent one.\\n\\nInside `.devcontainer` directory there is a `.parent` directory with everything related to the parent image.\\n\\nAnd in the `.devcontainer/Containerfile` file we reference this image\\n\\n```docker\\nFROM quay.io/podman-desktop/devcontainer-parent:next\\n```\\n\\nBy default, we will be `root` in the container and this is probably not what we expect. Let\'s change that.\\n\\n```json\\n\\"containerUser\\": \\"podman-desktop\\"\\n```\\n\\nSome Visual Studio Code extensions are nice to use and we can add them\\n\\n```json\\n \\"extensions\\": [\\"svelte.svelte-vscode\\", \\"bradlc.vscode-tailwindcss\\"]\\n```\\n\\nThen here is the tricky part, how to run our container allowing to run again inside the container some containers with podman.\\n\\nWe specify the arguments to make it possible. It\'s possible to use `--privileged` flag but I prefer to list the subset of permissions.\\nUsing `--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.\\n\\n```json\\n\\"runArgs\\": [\\n \\"--cap-add=sys_admin\\",\\n \\"--security-opt\\",\\n \\"seccomp=unconfined\\",\\n \\"--device\\",\\n \\"/dev/fuse\\",\\n \\"--security-opt\\",\\n \\"label=disable\\",\\n \\"--security-opt\\",\\n \\"apparmor=unconfined\\"\\n ],\\n```\\n\\nSource code of Podman Desktop needs to be editable within the DevContainer so it needs to be mounted.\\n\\n```json\\n\\"workspaceMount\\": \\"source=${localWorkspaceFolder},target=/workspace,type=bind\\",\\n\\"workspaceFolder\\": \\"/workspace\\",\\n```\\n\\nThen we need a command to build Podman Desktop.\\n\\nFor that, we use `onCreateCommand` hook with a custom command\\n\\n```json\\n\\"onCreateCommand\\": \\"${containerWorkspaceFolder}/.devcontainer/onCreateCommand.sh\\",\\n```\\n\\nand in the `.devcontainer` folder the `onCreateCommand.sh` script is the following\\n\\n```shell\\n#!/bin/sh\\nyarn\\n\\nMODE=production yarn run build && yarn run electron-builder build --linux --dir --config .electron-builder.config.cjs\\n```\\n\\nTwo instructions:\\n\\n1. Fetch all Node.js dependencies.\\n2. build Podman Desktop in the `dist` folder using `Linux` as target Operating System.\\n\\nAfter the start of the container, how to launch Podman Desktop, the website and VNC, etc ?\\n\\nJust use `postStartCommand` hook.\\n\\n```json\\n\\"postStartCommand\\": \\"${containerWorkspaceFolder}/.devcontainer/postStartCommand.sh\\",\\n```\\n\\nand in the `.devcontainer` folder the `postStartCommand.sh` script is the following:\\n\\n```shell\\n#!/bin/sh\\n\\n# Start all services\\n/usr/bin/supervisord -c /etc/supervisord.conf &\\n\\n# wait X server to be ready or after 2mn exit\\necho \\"Waiting for X server to be ready\\"\\ntimeout 120 bash -c \'until xdpyinfo -display :0 &> /dev/null; do printf \\".\\"; sleep 1; done\'\\n\\n# launch podman desktop\\necho \\"Launching Podman Desktop\\"\\ncd dist/linux-unpacked/&& ./podman-desktop &\\n\\n# Launch the 9000 redirect after 20 seconds\\nsleep 20\\nwebsockify --web=/usr/share/novnc localhost:9000 localhost:5900 &\\n\\n# launch the website rendering\\necho \\"Launching Website\\"\\ncd website && yarn start\\n```\\n\\nIt starts VNC and noVNC, start precompiled Podman Desktop and start the documentation rendering.\\n\\nIt is not launching the Watch mode/development mode of Podman Desktop as it requires a container having more than 8GB of memory.\\n\\nPicking up a larger instance with for example 16GB, it\'s possible to use development mode.\\n\\nOf course, to make VNC happy, we need to specify the `DISPLAY` environment variable.\\n\\n```json\\n\\"remoteEnv\\": {\\n \\"DISPLAY\\": \\":0\\"\\n}\\n```\\n\\nWhen the DevContainer is fully available, we want to have a way to quickly open the `Website rendering URL` and `noVNC`\\n\\nLet\'s tweak the `devcontainer.json` file by adding the `portsAttributes` section\\n\\n```json\\n\\"portsAttributes\\": {\\n \\"9000\\": {\\n \\"label\\": \\"vnc\\",\\n \\"onAutoForward\\": \\"openPreview\\"\\n },\\n \\"3000\\": {\\n \\"label\\": \\"website\\"\\n }\\n}\\n```\\n\\nAfter 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.\\n\\n## Using the DevContainer.json on Github Codespace\\n\\nAs a user, opening a workspace with all what we configured is done using a single click.\\n\\nGo to https://github.com/containers/podman-desktop then click on the `< > Code` dropdown and click on `Create codespace on main` button.\\n\\n![Open Codespace](img/develop-podman-using-codespaces/codespaces-click-repository.png)\\n\\nOnce you click on the button, the codespace is setting up:\\n\\n![Preparing Codespace](img/develop-podman-using-codespaces/codespaces-preparing-codespace.png)\\n\\nAfter few minutes, as there is not yet [prebuilt codespaces](https://docs.github.com/en/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds), the codespace is opening.\\n\\nThe simple Browser displays the noVNC window:\\n![Opening Codespace](img/develop-podman-using-codespaces/codespaces-open-novnc.png)\\n\\nClick 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.\\n![Testing Codespace](img/develop-podman-using-codespaces/codespaces-testing-podman-desktop.png)\\n\\nIt\'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.\\n\\nDepending on the usecase, it\'s also possible to open documentation in the preview browser.\\n\\n![Edit website Codespace](img/develop-podman-using-codespaces/codespaces-edit-website.png)\\n\\n## Conclusion\\n\\nThe 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/assets/js/b2f554cd.ebcd0c9c.js b/assets/js/b2f554cd.ebcd0c9c.js new file mode 100644 index 00000000000..ea406bf49e7 --- /dev/null +++ b/assets/js/b2f554cd.ebcd0c9c.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkdocs=self.webpackChunkdocs||[]).push([[1477],{30010:e=>{e.exports=JSON.parse('{"blogPosts":[{"id":"getting-started-with-compose","metadata":{"permalink":"/blog/getting-started-with-compose","source":"@site/blog/2024-01-02-getting-started-with-compose.md","title":"Getting started with Compose on Podman Desktop","description":"Getting started with Compose on Podman Desktop","date":"2024-01-02T00:00:00.000Z","formattedDate":"January 2, 2024","tags":[{"label":"podman-desktop","permalink":"/blog/tags/podman-desktop"},{"label":"story","permalink":"/blog/tags/story"},{"label":"compose","permalink":"/blog/tags/compose"},{"label":"containers","permalink":"/blog/tags/containers"},{"label":"containerfile","permalink":"/blog/tags/containerfile"},{"label":"docker-compose","permalink":"/blog/tags/docker-compose"},{"label":"dockerfile","permalink":"/blog/tags/dockerfile"},{"label":"multi-container","permalink":"/blog/tags/multi-container"}],"readingTime":4.475,"hasTruncateMarker":false,"authors":[{"name":"Charlie Drage","title":"Software Engineer","url":"https://github.com/cdrage","imageURL":"https://github.com/cdrage.png","key":"cdrage"}],"frontMatter":{"title":"Getting started with Compose on Podman Desktop","description":"Getting started with Compose on Podman Desktop","slug":"getting-started-with-compose","authors":["cdrage"],"tags":["podman-desktop","story","compose","containers","containerfile","docker-compose","dockerfile","multi-container"],"hide_table_of_contents":false},"unlisted":false,"nextItem":{"title":"Release Notes - Podman Desktop 1.6","permalink":"/blog/podman-desktop-release-1.6"}},"content":"In this blog post we will learn how take a multi-container Compose application and use it within Podman Desktop.\\n\\n## Objectives\\n\\n- Start the Compose YAML through `podman compose up`.\\n- View the guestbook web application.\\n- Confirm the web application is being synchronized and running correctly with the database.\\n- Use Podman Desktop to view, inspect and access the terminal of the Redis cluster.\\n\\n## What is Compose\\n\\n[Compose is a specification](https://www.compose-spec.io/) for defining and running multi-container Docker applications. With pose, you use a YAML file to configure your application\u2019s services, networks, and volumes. This allows you to capture in a single file the entire configuration necessary to run a set of interconnected containers as an application. For example, if you have an application that requires a web server, a database, and a caching service, you can define these components and their relationships in your Compose file.\\n\\nTo use the Compose YAML, you can use a specification implementation such as [`podman compose`](https://docs.podman.io/en/latest/markdown/podman-compose.1.html) and [`docker compose`](https://github.com/docker/compose).\\n\\n## Before we begin\\n\\nIf you do not have Compose installed, let\'s go through the onboarding process to install the Compose implementation binary:\\n\\n1. Get to Resources under ** Settings > Resources**.\\n2. Click **Setup** under Compose (it will appear if it has not been installed yet).\\n3. Go through the onboarding process.\\n\\n![Onboarding process](img/getting-started-with-compose/onboarding.png)\\n\\nConfirm that you are able to run `podman compose`:\\n\\n```sh\\npodman compose\\nRun compose workloads via an external provider such as docker-compose or podman-compose\\n\\nDescription:\\n This command is a thin wrapper around an external compose provider such as docker-compose or podman-compose. This means that podman compose is executing another tool that implements the compose functionality but sets up the environment in a way to let the compose provider communicate transparently with the local Podman socket. The specified options as well the command and argument are passed directly to the compose provider.\\n...\\n```\\n\\n## Download and run the example application\\n\\nOur example application is located at [github.com/redhat-developer/podman-desktop-demo](https://github.com/redhat-developer/podman-desktop-demo).\\n\\nWe will use `git clone` so we can build the Go binary web application:\\n\\n```sh\\ngit clone https://github.com/redhat-developer/podman-desktop-demo\\ncd podman-desktop-demo/guestbook-compose\\n```\\n\\nRun `podman compose up -d` to start the application:\\n\\n```sh\\npodman compose up -d\\n>>>> Executing external compose provider \\"/usr/local/bin/docker-compose\\". Please refer to the documentation for details. <<<<\\n\\n[+] Running 3/3\\n \u2714 Container redis-replica Started 0.0s\\n \u2714 Container web Started 0.0s\\n \u2714 Container redis-leader Started 0.0s\\n```\\n\\n## Viewing the guestbook application\\n\\nWithin Podman Desktop, you can now see that all three containers are up and operational.\\n\\nClick the \\"Open Browser\\" button to view the web application:\\n\\n![Open browser](img/getting-started-with-compose/openbrowser.png)\\n\\nWithin the Guestbook web application, you can:\\n\\n- \\"Sign\\" the guestbook, which will write to the Redis leader and synchronize to the replicas.\\n- \\"Read\\" from the guestbook, which will read from the pool of Redis replicas. This allows for readability even if the Redis leader is unavailable.\\n- `/env`: View the container\'s environment variables.\\n- `/info`: View information about the Redis cluster.\\n\\n![Guestbook application](img/getting-started-with-compose/helloworld.png)\\n\\n## Viewing and modifying the database\\n\\nUsing Podman Desktop, you can also access the container\'s terminal directly from the GUI and modify the database.\\n\\nClick \\"Open Terminal\\" to access the `redis-leader` terminal:\\n\\n![Open terminal](img/getting-started-with-compose/openterminal.png)\\n\\nModify the database as if you are doing database administration:\\n\\n1. Run `redis-cli` within the container to access the Redis database.\\n2. Type `LPUSH guestbook \\"Hello World!\\"` and you will see your web application update in real-time.\\n3. Type `DEL guestbook` and you will see that your database drops the `guestbook` key and clears the database.\\n\\n![Redis CLI](img/getting-started-with-compose/redis-cli.png)\\n\\nChanges will reflect in real-time on the guestbook.\\n\\nYou can further modify the database and see the changes propagate to the Redis replicas.\\n\\nFor example, view the logs of the `redis-replica`, and you will notice that there are periodic database synchronizations as well as reads to the database:\\n\\n![Redis replica logs](img/getting-started-with-compose/redisreplica.png)\\n\\n## How does it work?\\n\\nA quick overview of how the architecture works in this multi-container scenario:\\n\\n- Within the Guestbook application, it looks for a database with the names `redis-leader` and `redis-replica` on port 6379.\\n- Because it is a Compose application, the containers are connected on the same network. This means that a neighboring container can be network-accessible simply by its container name.\\n\\nThere is a set of environment variables that the web application can modify in the Compose application:\\n\\n- `REDIS_LEADER`: The default is `redis-leader`.\\n- `REDIS_REPLICAS`: The default is `redis-replica`. Can be comma-separated, such as `redis-replica-1,redis-replica-2`.\\n- `REDIS_PORT`: The default is `6379`.\\n- `SERVER_PORT`: The default is `8080`.\\n\\n## Scaling more replicas\\n\\nWant to scale more replicas? This can be achieved by adding an environment variable to your `compose.yaml` and duplicating your `redis-replica` entry.\\n\\nModify your `compose.yaml` as follows:\\n\\n```yaml\\nservices:\\n redis-leader:\\n container_name: redis-leader\\n image: redis:latest\\n ports:\\n - \'6379\'\\n\\n redis-replica:\\n container_name: redis-replica\\n image: redis:latest\\n ports:\\n - \'6379\'\\n command: redis-server --replicaof redis-leader 6379\\n\\n redis-replica-2:\\n container_name: redis-replica-2\\n image: redis:latest\\n ports:\\n - \'6379\'\\n command: redis-server --replicaof redis-leader 6379\\n\\n web:\\n container_name: web\\n build: ./web\\n environment:\\n - REDIS_REPLICAS=redis-replica1,redis-replica2\\n ports:\\n - \'8080:8080\'\\n```\\n\\nRun `podman compose up -d` again to ensure the new container has been added and the new environment variable has propagated:\\n\\n```sh\\npodman compose up -d\\n>>>> Executing external compose provider \\"/usr/local/bin/docker-compose\\". Please refer to the documentation for details. <<<<\\n\\n[+] Running 4/4\\n \u2714 Container redis-replica-2 Started 0.0s\\n \u2714 Container redis-leader Running 0.0s\\n \u2714 Container web Started 0.0s\\n \u2714 Container redis-replica Running 0.0s\\n```"},{"id":"podman-desktop-release-1.6","metadata":{"permalink":"/blog/podman-desktop-release-1.6","source":"@site/blog/2023-12-18-release-1.6.md","title":"Release Notes - Podman Desktop 1.6","description":"Podman Desktop 1.6 has been released!","date":"2023-12-18T00:00:00.000Z","formattedDate":"December 18, 2023","tags":[{"label":"podman-desktop","permalink":"/blog/tags/podman-desktop"},{"label":"release","permalink":"/blog/tags/release"},{"label":"kubernetes","permalink":"/blog/tags/kubernetes"},{"label":"openshift","permalink":"/blog/tags/openshift"},{"label":"onboarding","permalink":"/blog/tags/onboarding"},{"label":"compose","permalink":"/blog/tags/compose"},{"label":"extensions","permalink":"/blog/tags/extensions"},{"label":"settings","permalink":"/blog/tags/settings"}],"readingTime":10.45,"hasTruncateMarker":false,"authors":[{"name":"Stevan Le Meur","title":"Product Manager","url":"https://github.com/slemeur","imageURL":"https://github.com/slemeur.png","key":"slemeur"}],"frontMatter":{"title":"Release Notes - Podman Desktop 1.6","description":"Podman Desktop 1.6 has been released!","slug":"podman-desktop-release-1.6","authors":"slemeur","tags":["podman-desktop","release","kubernetes","openshift","onboarding","compose","extensions","settings"],"hide_table_of_contents":false,"image":"/img/blog/podman-desktop-release-1.6/santaseal.png"},"unlisted":false,"prevItem":{"title":"Getting started with Compose on Podman Desktop","permalink":"/blog/getting-started-with-compose"},"nextItem":{"title":"Share your local podman images with the Kubernetes cluster","permalink":"/blog/sharing-podman-images-with-kubernetes-cluster"}},"content":"import ReactPlayer from \'react-player\'\\n\\nPodman Desktop 1.6 Release! \ud83c\udf89\\n\\n![Podman-desktop-1-6-hero](img/podman-desktop-release-1.6/santaseal.png)\\n\\nThis release introduces:\\n\\n- **Minikube Featured Extension**: Minikube extension to create local Kubernetes clusters in containers.\\n- **Podman 4.8.2**: [Podman 4.8.2](https://github.com/containers/podman/releases) is now included in Windows and Mac installers.\\n- **Setting Page for Command-Line Tools**: Manage and update your CLI tools.\\n- **Kubernetes Contexts Manager**: Browse all your kubernetes contexts, set default and remove unused ones.\\n- **Editable Podman Machine for MacOS**: Easy resize and reconfiguration of the Podman runtime environment.\\n- **Filters for Containers and Pods Lists**: Focus on the containers and Pods you are working with.\\n- **Sorting on Volumes and Images List**: Sort volumes or images with your prefered criterias.\\n- **Environment Colums on Containers and Pods lists**: Easy catch of the environment on which a container or a pod is running on.\\n- **Extension API Improvements**: Another set of improvements to the extension API enabling more goodness for \ud83e\uddad Podman Desktop\'s extensions.\\n\\nPodman Desktop 1.6 is now available. [Click here to download it](/downloads)!\\n\\n---\\n\\n## Release Details\\n\\n### Minikube featured extension\\n\\nFor developers who need to run Kubernetes locally and reproduce an environment close to production for development and experimentation purposes, Podman Desktop allows users to easily set up that environment on a local machine. There are two extensions providing the capability to configure a open source Kubernetes cluster locally, you can either choose between [Kind](https://kind.sigs.k8s.io/) or [Minikube](https://minikube.sigs.k8s.io/docs/).\\n\\nThe Minikube extension allows you to install Minikube on your workstation and also to setup a Kubernetes cluster locally running in a container! Yes, you read that correctly - in a container similar to how Kind works. The advantage is that it\'s lighter and faster to start. With Minikube, one of the advantage, is that you can build your images locally with Podman and get them automatically available in your local Kubernetes cluster - which will speed up your turnarounds when you want to test your application. If you want to learn more this, read the [following blog post](https://podman-desktop.io/blog/sharing-podman-images-with-kubernetes-cluster).\\n\\n![Minikube-feature-extension](img/podman-desktop-release-1.6/minikube-feature-extension.png)\\n\\n### Command-Line Tools Configuration: Compose and Kubectl\\n\\nConfiguring and managing your setup is getting easier with the addition of a new section in the Settings to manage command-line tools. In Podman Desktop, extensions can list command-line tools that are helpful to their users or required to make use of the installed extensions.\\n\\nThere are two command-line tools within Podman Desktop that allows you to view whether they are installed or require an update:\\n\\n- Compose binary for running \'podman compose\' commands.\\n- kubectl for interacting with Kubernetes clusters.\\n\\n![cli-tools](img/podman-desktop-release-1.6/cli-tools.png)\\n\\nFrom the settings you can see the command-line tools that are installed, and you can see the version - and when a new version is available, you\'ll get a small notification to allow you easily update to that version.\\n\\n![Compose-Update](img/podman-desktop-release-1.6/compose-update.png)\\n\\n### Kubernetes Contexts Manager\\n\\nWe are introducing a new screen available from the Settings which allows you to easily manage your Kubernetes contexts. Podman Desktop was already providing the handy context switcher available from the status bar, but when you get to work with multiple Kubernetes environments, it\'s not uncommon to end with a big and long list of Kubernetes contexts.\\n\\nThe new Kubernetes Contexts screen allows you to easily see all your registered Kubernetes contexts. You can use the screen to clean up your registered contexts, or set the current (default) context.\\n\\n![Kubernetes Contexts List](img/podman-desktop-release-1.6/kubernetes-contexts.png)\\n\\n### Editable Podman Machine\\n\\nA Podman machine is a virtual environment specifically designed to run Podman containers on Mac and Windows. It allows users to manage and operate containerized applications in an isolated and controlled setting. When creating a Podman machine, you configure its settings: memory, CPU(s) and disk size.\\n\\nWe\'ve received the feedback regarding the ability to reconfigure your Podman machine on the go. This is now possible for macOS users, and particularly useful when you start with an environment and need to scale it up based on new needs and containers you would like to run in your Podman environment.\\n\\n![Editable podman machine](https://github.com/containers/podman-desktop/assets/1636769/91150767-58a9-47b5-abbc-58d2d50f4fca)\\n\\nYou\'ll notice we improved the sliders to configure the Podman machine\'s options - and also introduced a way to enter numeric values directly.\\n\\n### Tabs/Filters for Containers and Pods\\n\\nBeing able to quickly identify the containers and the pods you are working with is critical when you are iterating on the development of your application. For this reason, we added filters at the top of the lists of Containers and Pods that allow you to easily view all the containers/pods, only those that are running, or only those that are stopped.\\n\\n![Filters for containers and pods](https://github.com/containers/podman-desktop/assets/1636769/37190c74-7fa5-485e-81a4-bd970f606286)\\n\\n### Sorting for Volumes and Images lists\\n\\nThe lists of Volumes and Images have improved and are now have the ability to be sorted by the criteria of your choice. You can for example filter images by their size - which can be convenient when you want to clean up your environment.\\n\\n![Sorting for Volumes and Images](https://github.com/containers/podman-desktop/assets/1636769/0d20b5c2-517c-4ccc-8992-b8df275bcc30)\\n\\n### Environment columns on Containers and Pods lists\\n\\nPodman Desktop is able to work with multiple providers: it could work with multiple container engines and multiple Kubernetes environments too. In order to make it easier to identify the containers and the pods and differentiate them depending on which environment they are running onto, we are introducing a new environment column in the list of Containers and Pods to display a badge.\\n\\n![Environment Column](img/podman-desktop-release-1.6/environment-column.png)\\n\\n#### Better visibility to the containers running in Pods\\n\\nThe list of Pods has been refined to provide easier visibility and access to the containers running within each of them. Each of the containers now have one dot and you can hover each dot to display the info about the container - and if you click on it you\'ll be able to access the details of the container.\\n\\n![Visibility for containers in Pods](https://github.com/containers/podman-desktop/assets/1636769/0e88a88e-9a17-4261-b60f-b4d09ca19127)\\n\\n### Extension API improvements\\n\\nThe \ud83e\uddad Podman Desktop extension API received many improvements, including:\\n\\n- Documentation explaining how to create an onboarding workflow for an extension [#4837](https://github.com/containers/podman-desktop/pull/4837)\\n- Documented how extensions hook into UI [#4633](https://github.com/containers/podman-desktop/pull/4633)\\n- Documented how to implement api client [#4636](https://github.com/containers/podman-desktop/pull/4636)\\n- Image checker extension API [#4662](https://github.com/containers/podman-desktop/pull/4662)\\n- Added api to register cli updater [#5064](https://github.com/containers/podman-desktop/pull/5064)\\n\\n---\\n\\n## Other Notable Enhancements\\n\\n- Show container connection type and endpoint [#5098](https://github.com/containers/podman-desktop/pull/5098)\\n- Environment column to pods/containers [#4583](https://github.com/containers/podman-desktop/pull/4583)\\n- Displaying extension icons in the list of extensions [#5101](https://github.com/containers/podman-desktop/pull/5101)\\n- Introduced UI icon image component [#5117](https://github.com/containers/podman-desktop/pull/5117)\\n- Added icon to extensionInfo [#5089](https://github.com/containers/podman-desktop/pull/5089)\\n- Added encoding option on RunOptions [#4942](https://github.com/containers/podman-desktop/pull/4942)\\n- Introduced property for appearance but for now only dark is supported [#4887](https://github.com/containers/podman-desktop/pull/4887)\\n- Default table sorting [#4860](https://github.com/containers/podman-desktop/pull/4860)\\n- Display notification for completed onboarding in task manager [#4811](https://github.com/containers/podman-desktop/pull/4811)\\n- Added purple dot when new content is available in dashboard [#4782](https://github.com/containers/podman-desktop/pull/4782)\\n- Argos CI: Introduce Argos CI to track and detect visual regressions on the website\\n- Added command palette: add enablement property [#4630](https://github.com/containers/podman-desktop/pull/4630)\\n- Added documentation for telemetry and usage data [#4618](https://github.com/containers/podman-desktop/pull/4619)\\n- Introduced table component [#4545](https://github.com/containers/podman-desktop/pull/4545)\\n- Added ability to abort build image [#4538](https://github.com/containers/podman-desktop/pull/4538)\\n- Added support in command palette for category [#4531](https://github.com/containers/podman-desktop/pull/4531)\\n- Upgraded flatpak to org.freedesktop.Platform version 23.08 [#3968](https://github.com/containers/podman-desktop/pull/3968)\\n- Added open exposed url to pod details [#3762](https://github.com/containers/podman-desktop/pull/3762)\\n\\n---\\n\\n## Notable Bug Fixes\\n\\n- Fix reconnect to `/events` if disconnected [#4809](https://github.com/containers/podman-desktop/pull/4809)\\n- fix: reset loggerhandlerKey after restarting machine [#5168](https://github.com/containers/podman-desktop/pull/5168)\\n- fix: fix: podman machine created with wrong flags [#5178](https://github.com/containers/podman-desktop/pull/5178)\\n- fix: avoid to crash if configuration is invalid [#5182](https://github.com/containers/podman-desktop/pull/5182)\\n- fix: extension installation checks architecture and os [#5191](https://github.com/containers/podman-desktop/pull/5191)\\n- fix: use URL for proxy specification and add validation [#4825](https://github.com/containers/podman-desktop/pull/4825)\\n- fix: do not change color and underline of markdown buttons [#5138](https://github.com/containers/podman-desktop/pull/5138)\\n- fix: do not reconnect when connection is removed [#5131](https://github.com/containers/podman-desktop/pull/5131)\\n- fix: table headers shouldn\'t allow text selection [#5118](https://github.com/containers/podman-desktop/pull/5118)\\n- fix: add style to link [#5108](https://github.com/containers/podman-desktop/pull/5108)\\n- fix: launch.json references wrong script [#5094](https://github.com/containers/podman-desktop/pull/5094)\\n- fix: don\'t link to k8s cluster server [5087](https://github.com/containers/podman-desktop/pull/5087)\\n- fix: pass the complete imageInfo to the check function [#5069](https://github.com/containers/podman-desktop/pull/5069)\\n- fix: container tabs should match pods [#5057](https://github.com/containers/podman-desktop/pull/5057)\\n- fix: revert styling of disabled buttons [#5056](https://github.com/containers/podman-desktop/pull/5056)\\n- fix: update current context reactively [#5055](https://github.com/containers/podman-desktop/pull/5055)\\n- fix: make ProviderResultPage do not change input values [#5030](https://github.com/containers/podman-desktop/pull/5030)\\n- fix: add rowgroup to tables [#5005](https://github.com/containers/podman-desktop/pull/5005)\\n- fix: add path prop for route object [#4981](https://github.com/containers/podman-desktop/pull/4981)\\n- fix: remove errant hash mark [#4971](https://github.com/containers/podman-desktop/pull/4971)\\n- fix: check extension folder contains package.json [#4964](https://github.com/containers/podman-desktop/pull/4964)\\n- fix: refactor List UI components [#4953](https://github.com/containers/podman-desktop/pull/4953)\\n- fix: succeeded/completed state for Compose onboarding [#4947](https://github.com/containers/podman-desktop/pull/4947)\\n- fix: remove flex class from markdown button rendering [#4934](https://github.com/containers/podman-desktop/pull/4934)\\n- fix: unable to read wsl version when using chinese as syslang on Windows [#4918](https://github.com/containers/podman-desktop/pull/4918)\\n- fix: retain autostart setting [#4879](https://github.com/containers/podman-desktop/pull/4879)\\n- fix: use vi.waitUtnil instead of cycles with awaiting promises [#4861](https://github.com/containers/podman-desktop/pull/4861)\\n- fix: docker host on windows when executing compose command [#4855](https://github.com/containers/podman-desktop/pull/4855)\\n- fix: merged compose deploy to kube page in UI [#4827](https://github.com/containers/podman-desktop/pull/4827)\\n- fix: use URL for proxy specification and add validation [#4825](https://github.com/containers/podman-desktop/pull/4825)\\n- fix: reconnect to /events if disconnected [#4809](https://github.com/containers/podman-desktop/pull/4809)\\n- fix: remove fixed height after patternfly removal [#4804](https://github.com/containers/podman-desktop/pull/4804)\\n- fix background colours after patternfly removal [#4803](https://github.com/containers/podman-desktop/pull/4803)\\n- fix: report metrics for stopped machines [#4787](https://github.com/containers/podman-desktop/pull/4787)\\n- chore: update to docusaurus v3.0.0 [#4764](https://github.com/containers/podman-desktop/pull/4764)\\n- chore: drop patternfly [#4762](https://github.com/containers/podman-desktop/pull/4762)\\n- fix: avoid to send telemetry usage as this method is called every 5s [#4692](https://github.com/containers/podman-desktop/pull/4692)\\n- fix: location of roots.exe in devmode [#4654](https://github.com/containers/podman-desktop/pull/4654)\\n- fix: disable create/start container if any port is busy [#4637](https://github.com/containers/podman-desktop/pull/4637)\\n- fix: fix setup in build image tests [#4625](https://github.com/containers/podman-desktop/pull/4625)\\n- fix: find a free port [#4616](https://github.com/containers/podman-desktop/pull/4616)\\n- fix: reduce size of provider cards on the dashboard [#4615](https://github.com/containers/podman-desktop/pull/4615)\\n- fix: shorter doc nav section titles [#4613](https://github.com/containers/podman-desktop/pull/4613)\\n- fix: report error if container engine action fails in details page [#4556](https://github.com/containers/podman-desktop/pull/4556)\\n- fix: remove prev/next bar [#4548](https://github.com/containers/podman-desktop/pull/4548)\\n- fix: reduce website footer [#4546](https://github.com/containers/podman-desktop/pull/4546)\\n- fix: handle compose format json that is no longer a JSON array object [#4540](https://github.com/containers/podman-desktop/pull/4540)\\n- fix: disable push to kind menu item if pushing is in progress [#4530](https://github.com/containers/podman-desktop/pull/4530)\\n- fix: check for self signed cert message and use insecure param when editing registry password [#4523](https://github.com/containers/podman-desktop/pull/4523)\\n- fix: add autoscroll to summary pages [#4504](https://github.com/containers/podman-desktop/pull/4504)\\n- fix: report errors when analyzing extensions [#4380](https://github.com/containers/podman-desktop/pull/4380)\\n- fix: allow editing of build containerfile [#4471](https://github.com/containers/podman-desktop/pull/4471)\\n- refactor: updated compose onboarding installation [#4479](https://github.com/containers/podman-desktop/pull/4479)\\n- refactor: remove compose from the status bar [#4492](https://github.com/containers/podman-desktop/pull/4492)\\n\\n---\\n\\n## Documentation\\n\\nComing with this new version of \ud83e\uddad Podman Desktop, the documentation has been getting the following improvements:\\n\\n- Reorganize doc navigation by provider [#4558](https://github.com/containers/podman-desktop/pull/4558)\\n- Added vsc runtime dependency for Windows development [#5091](https://github.com/containers/podman-desktop/pull/5091)\\n- Show location of lima podman socket [#5090](https://github.com/containers/podman-desktop/pull/5090)\\n- Fixed typo in URI for releases [#4909](https://github.com/containers/podman-desktop/pull/4909)\\n- Explain how to create an onboarding workflow for an extension [#4837](https://github.com/containers/podman-desktop/pull/4837)\\n- Make it possible for lima to provide both [#4789](https://github.com/containers/podman-desktop/pull/4789)\\n- Blog post about minikube/sharing images [#4735](https://github.com/containers/podman-desktop/pull/4735)\\n- Remove duplicate text from windows troubleshooting [#4652](https://github.com/containers/podman-desktop/pull/4652)\\n- Add step to implement api client [#4636](https://github.com/containers/podman-desktop/pull/4636)\\n- Fixed the main lima command for limactl [#4623](https://github.com/containers/podman-desktop/pull/4623)\\n- Lima provider cleanup after the improvements in the implementation [#4622](https://github.com/containers/podman-desktop/pull/4622)\\n- Update documentation regarding auto merge [#4519](https://github.com/containers/podman-desktop/pull/4519)\\n- Using standard OS tabs for registries docs [#4497](https://github.com/containers/podman-desktop/pull/4497)\\n- Fixed mahine -> machine [#4495](https://github.com/containers/podman-desktop/pull/4495)\\n- Added screenshots and fixed formatting to the registries section [#4472](https://github.com/containers/podman-desktop/pull/4472)\\n\\n---\\n\\n## Community Thank You\\n\\n\ud83c\udf89 We\u2019d like to say a big thank you to everyone who helped to make \ud83e\uddad Podman Desktop even better. In this\\nrelease we received pull requests from the following people:\\n\\n- [afbjorklund](https://github.com/afbjorklund) in [fix: add website target for running vale ](https://github.com/containers/podman-desktop/pull/4547), [docs: the main lima command is limactl](https://github.com/containers/podman-desktop/pull/4623), [ docs: lima provider cleanup after the merge](https://github.com/containers/podman-desktop/pull/4622), [docs: make it possible for lima to provide both](https://github.com/containers/podman-desktop/pull/4789), [fix: don\'t link to k8s cluster server](https://github.com/containers/podman-desktop/pull/5087), [feat: show the k8s namespace](https://github.com/containers/podman-desktop/pull/5088), [docs: show location of lima podman socket](https://github.com/containers/podman-desktop/pull/5090)\\n\\n- [axel7083](https://github.com/axel7083) in [refactoring: item formats from renderer/preferences in separate files](https://github.com/containers/podman-desktop/pull/3728), [feat: adding optional abort controller to dockerode api](https://github.com/containers/podman-desktop/pull/4364)\\n\\n- [ReadingShades](https://github.com/ReadingShades) in [docs: Added the environment variable set commands of the common windows terminal emulators](https://github.com/containers/podman-desktop/pull/4245)\\n\\n- [jannikbertram](https://github.com/jannikbertram) in [chore: add close button to troubleshooting and help page](https://github.com/containers/podman-desktop/pull/4457)\\n\\n- [singodiyashubham87](https://github.com/singodiyashubham87) in [fix: header line height issue on website](https://github.com/containers/podman-desktop/pull/4494)\\n\\n- [edvardsanta](https://github.com/edvardsanta) in [feat: remove redundant naming in buttons](https://github.com/containers/podman-desktop/pull/4518)\\n\\n- [Mayureshd-18](https://github.com/Mayureshd-18) in [fix typos](https://github.com/containers/podman-desktop/pull/4551)\\n\\n- [jgelens](https://github.com/jgelens) in [Fix rootless command](https://github.com/containers/podman-desktop/pull/4609)\\n\\n- [itecompro](https://github.com/itecompro) in [docs: remove duplicate text from windows troubleshooting](https://github.com/containers/podman-desktop/pull/4652)\\n\\n- [EricSmekens](https://github.com/EricSmekens) in [docs: Fixed typo in URI for releases](https://github.com/containers/podman-desktop/pull/4909)\\n\\n- [ecrookshanks-rh](https://github.com/ecrookshanks-rh) in [fix: added text beside icon for create pods ](https://github.com/containers/podman-desktop/pull/5095)\\n\\n---\\n\\n## Final notes\\n\\n### Fixed Issues\\n\\nThe complete list of issues fixed in this release is available [here](https://github.com/containers/podman-desktop/issues?q=is%3Aclosed+milestone%3A1.6.0).\\n\\n### Where to Download\\n\\nGet the latest release from the [Downloads](/downloads) section of the website and boost your development journey with Podman Desktop. Additionally, visit the [GitHub repository](https://github.com/containers/podman-desktop) and see how you can help us make Podman Desktop better."},{"id":"sharing-podman-images-with-kubernetes-cluster","metadata":{"permalink":"/blog/sharing-podman-images-with-kubernetes-cluster","source":"@site/blog/2023-12-06-sharing-podman-images-with-kubernetes-cluster.md","title":"Share your local podman images with the Kubernetes cluster","description":"Build image and use it directly in your kubernetes cluster","date":"2023-12-06T00:00:00.000Z","formattedDate":"December 6, 2023","tags":[{"label":"podman-desktop","permalink":"/blog/tags/podman-desktop"},{"label":"podman","permalink":"/blog/tags/podman"},{"label":"images","permalink":"/blog/tags/images"},{"label":"kubernetes","permalink":"/blog/tags/kubernetes"}],"readingTime":7.71,"hasTruncateMarker":true,"authors":[{"name":"Florent Benoit","title":"Principal Software Engineer","url":"https://github.com/benoitf","imageURL":"https://github.com/benoitf.png","key":"benoitf"}],"frontMatter":{"title":"Share your local podman images with the Kubernetes cluster","description":"Build image and use it directly in your kubernetes cluster","slug":"sharing-podman-images-with-kubernetes-cluster","authors":["benoitf"],"tags":["podman-desktop","podman","images","kubernetes"],"hide_table_of_contents":false,"image":"/img/blog/sharing-podman-images-with-kubernetes-cluster/selkie-family.png"},"unlisted":false,"prevItem":{"title":"Release Notes - Podman Desktop 1.6","permalink":"/blog/podman-desktop-release-1.6"},"nextItem":{"title":"Release Notes - Podman Desktop 1.5","permalink":"/blog/podman-desktop-release-1.5"}},"content":"As developers we constantly improve and refine our applications. One of the challenges we face is quickly iterating when working with container images and kubernetes deployments/pods.\\n\\nFor example, when we want to try a new image in a kubernetes pod, this image needs to be available on a private/public registry or on the nodes of the kubernetes cluster.\\nSometimes we need to call extra commands such as `kind load docker-image` or `minikube cache add ` or publish the image first to a 3rd party registry.\\n\\nYou\'ll agree that trying out a new image in a Kubernetes pod should be as seamless as building the image itself.\\n\\nIn this blog post, we will explore the best practice for streamlining the image iteration process in Kubernetes with Podman Desktop.\\n\\n![hero](img/sharing-podman-images-with-kubernetes-cluster/selkie-family.png)\\n\\n\x3c!--truncate--\x3e\\n\\n---\\n\\n## Introduction\\n\\nWhen using kind or minikube or other 3rd party tools to setup a local kubernetes cluster, we have several ways to publish images.\\n\\nMinikube published 8 ways of doing that at https://minikube.sigs.k8s.io/docs/handbook/pushing/\\n\\nThere are pros and cons either way. Using a third party registry implies that you need to publish the image after each build of the image before being able to use it in the kubernetes cluster. While Podman Desktop could automate the synchronization between the local registry (where you are doing `podman build`) and the third party registry, there remains a duplication of layers between the local and third party registry. And if you change the first layer, it can take a lot of time to send again all the data.\\n\\nLoading images requires to pack/unpack the files so it\'s not adequate for large images.\\n\\nMinikube offers a Podman environment, but it\'s important to note that it utilizes version 3.4 inside a container within the Podman machine. This implies the existence of two Podman instances.\\n\\nThe 3.4 version is considerably outdated and do not provide new enhancements and support towards compose, compliance with Docker REST API and 3rd party tools.\\n\\nCould we just build the image and use it in kubernetes?\\n\\n## podman and kubernetes/cri-o\\n\\nIn the kubernetes world, we need a container engine runtime. At the early stage, container runtimes were integrated with ad hoc solutions on top of docker, rkt, or others.\\n\\nBut to separate concerns and to be extensible, a new interface was added: CRI for \\"Container Runtime Interface\\". Using the CRI interface we can plug container engines. And there are several runtimes such as containerd, cri-o and others.\\nhttps://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/container-runtime-interface.md\\n\\nWhat is interesting to us is the cri-o project. This project is implementing the CRI interface but also adopting some projects of the [containers](https://github.com/containers) organization where [podman](https://github.com/containers/podman) and [podman-desktop](https://github.com/containers/podman-desktop) live.\\n\\nSo it means cri-o uses image management from https://github.com/containers/image project and handle storage with https://github.com/containers/storage project.\\n\\nAnd this is what is really interesting as a podman user. As it is using common libraries between cri-o and podman, it means that in the same environment, podman and cri-o read and write the images at a common location in `/var/lib/containers` folder.\\n\\nIf we move one step ahead, if we mount the `/var/lib/containers` folder of podman into the cri-o container it means that the kubernetes cluster could find the images that the podman machine is building.\\n\\nOh wait, it means that no more registry, additional steps would be required? Yes just build and load it.\\n\\n## Minikube to the rescue\\n\\nWhile we have the goal of using both cri-o and podman altogether, we can explore the current projects allowing us to quickly setup kubernetes clusters.\\n\\n### kind\\n\\nOn the `kind` side, there is a default configuration that is using containerd and there is no plan to support an alternative such as cri-o https://github.com/kubernetes-sigs/kind/issues/1369#issuecomment-867440704\\n\\nThat said, some people try to maintain a way to do that but not officialy https://gist.github.com/aojea/bd1fb766302779b77b8f68fa0a81c0f2\\n\\nBy doing that, we would also need to mount `/var/lib/containers` folder from the host (the podman machine) to the container. And there is no easy flag in kind.\\n\\n### Minikube\\n\\n#### Minikube options\\n\\nMinikube supports more options and provides a way to select the container engine runtime. And it includes support for cri-o.\\n\\nWe can use the `container-runtime` parameter and ask for `cri-o` runtime. Command-line should include `--container-runtime=cri-o`.\\n\\nThen, we do have a podman/cri-o environment inside the container and can use `eval $(minikube podman-env)` to use the Windows/macOS podman CLI.\\n\\nOne issue is that we then have two \'Podman engines\': one running inside the Podman machine and another one running inside the container. The Podman included in the container is using version 3.4, as it\'s on Debian/Ubuntu stable, while the recent version of Podman is 4.7.x.\\n\\nCan we mount the podman machine `/var/lib/containers` into the container ?\\n\\nYes! minikube provides some options to do additional mount with `--mount-string` argument. It is not obvious but you also need to add the `--mount` in addition to this parameter. Full argument is `--mount --mount-string \\"\\"`\\n\\nBut `/var` is already a mounted folder. So here the idea is to change the path of where cri-o is storing its data.\\n\\nSo we can provide a custom mounted path and make cri-o use that custom location. Let\'s pickup `/host-containers`.\\n\\nWhen starting minikube we need then to add `--mount --mount-string \\"/var/lib/containers:/host-containers\\"`.\\n\\nRegarding the configuration of cri-o, currently, it\'s not achievable using Minikube options. However, Minikube does offer the flexibility to modify the base image.\\n\\n#### Minikube kicbase image\\n\\nLet\'s do our own base image named kicbase image.\\n\\nMinikube includes a default configuration file for cri-o.\\nhttps://github.com/kubernetes/minikube/blob/v1.32.0/deploy/kicbase/02-crio.conf\\n\\nWe need to change this default configuration to say that for storing the images, cri-o needs to use another directory. This new directory `/host-containers` will be mounted from the `/var/lib/containers` folder inside the podman machine. This is how cri-o is able to see podman images.\\n\\nLet\'s include the configuration part in this file.\\n\\n```toml\\n[crio]\\nroot = \\"/host-containers/storage\\"\\nrunroot = \\"/host-containers/storage\\"\\n```\\n\\nLet\'s also upgrade the Podman inside the container by adding the necessary instruction to the Dockerfile.\\n\\nThe Dockerfile is coming from https://github.com/kubernetes/minikube/blob/v1.32.0/deploy/kicbase/Dockerfile#L178-L186\\n\\nIn the file, replace\\n\\n```Dockerfile\\nRUN clean-install podman && \\\\\\n```\\n\\nwith\\n\\n```Dockerfile\\nRUN sh -c \\"echo \'deb https://downloadcontent.opensuse.org/repositories/devel:/kubic:/libcontainers:/unstable/xUbuntu_22.04/ /\' > /etc/apt/sources.list.d/devel:kubic:libcontainers:unstable.list\\" && \\\\\\n curl -LO https://downloadcontent.opensuse.org/repositories/devel:kubic:libcontainers:unstable/xUbuntu_22.04/Release.key && \\\\\\n apt-key add - < Release.key && \\\\\\n # need to add dbus-user-session else we have\\n # cannot open sd-bus: No such file or directory: OCI runtime attempted to invoke a command that was not found\\n clean-install dbus-user-session podman && \\\\\\n```\\n\\nLet\'s rebuild the image and publish it. You can find it at `quay.io/fbenoit/kicbase:multiarch-2023-11-06` .\\nTo build the image, clone https://github.com/kubernetes/minikube repository, and edit the files referenced before.\\n\\nThe command to build the kicbase image is `make local-kicbase`.\\n\\n#### Trying out cri-o using the podman machine storage folder\\n\\nAt the time of writing this blog post, the version `v1.32.0-beta.0` has been used. For different versions you might need to build your own kicbase image.\\n\\nOne crucial note: cri-o is running in root mode, this is why we mount to `/var/lib/containers` (and then in rootful mode).\\n\\nFor simplicity, let\'s use a rootful podman machine to map the same folder at the two locations.\\n\\nOk now let\'s try in two steps:\\n\\n1. Create a podman machine:\\n\\n```shell\\npodman machine init --cpus 4 --memory 6000 --rootful\\n```\\n\\n2. Start the cluster using our kicbase image\\n\\nWe specify Podman as the driver (the default is Docker), state our preference to use cri-o as the container runtime instead of containerd, use our custom image that performs the update of Podman\'s version and the modification of cri-o\'s configuration to use a different storage folder. Finally, we specify an additional mount.\\n\\n```shell\\nminikube start --driver=podman --container-runtime=cri-o --base-image=quay.io/fbenoit/kicbase:multiarch-2023-11-06 --mount --mount-string \\"/var/lib/containers:/host-containers\\"\\n```\\n\\n#### Verification\\n\\nAssuming the cluster was able to start, there is a new kubernetes cluster configured in the `$HOME/.kube/config` file.\\n\\nUsing `kubectl` we can start a deployment\\n\\n```shell\\nkubectl apply -f https://k8s.io/examples/application/deployment.yaml\\n```\\n\\nyou can check pods are running using\\n\\n```shell\\nkubectl get pods -l app=nginx\\n```\\n\\nand if you check your podman images\\n\\n```\\npodman images\\n```\\n\\nyou\'ll see nginx being listed so images are shared.\\n\\nNow, you can build image using a Containerfile or pull an image, connect to the control plane instance in Podman Desktop (open a shell in minikube container) and run\\n\\n```shell\\ncrictl images\\n```\\n\\nIt will list the images of podman\\n\\nNote: by default, kubernetes will use the image pull policy `Always` using the `latest` tag on your image. So it might try to fetch/pull/refresh the image you built locally. Use a specific tag or change the `imagePullPolicy` to `IfNotPresent` in your deployments.\\n\\nYou can now use your own Containerfile/Dockerfile and build an image using `podman build` command. And then check that the image is available as well in the kubernetes cluster by listing images:\\n\\n```shell\\ncrictl images\\n```\\n\\n### Conclusion\\n\\nWe have explored how developers can significantly reduce turnaround times by integrating Podman and Kubernetes seamlessly.\\n\\nNow, let\'s experiment with it and provide feedback through the Podman Desktop issue tracker at https://github.com/containers/podman-desktop/issues/ .\\n\\nHere are the next steps Podman Desktop plans to take to enhance ease of use for users:\\n\\n- To make things easier, automate the process by adding this setup to a creation wizard.\\n- Collaborate with upstream Minikube project to simplify choices and remove the requirement for customized kicbase images.\\n- Enhancing the overall user-friendliness of the solution for an improved developer experience."},{"id":"podman-desktop-release-1.5","metadata":{"permalink":"/blog/podman-desktop-release-1.5","source":"@site/blog/2023-11-03-release-1.5.md","title":"Release Notes - Podman Desktop 1.5","description":"Podman Desktop 1.5 has been released!","date":"2023-11-03T00:00:00.000Z","formattedDate":"November 3, 2023","tags":[{"label":"podman-desktop","permalink":"/blog/tags/podman-desktop"},{"label":"release","permalink":"/blog/tags/release"},{"label":"kubernetes","permalink":"/blog/tags/kubernetes"},{"label":"openshift","permalink":"/blog/tags/openshift"},{"label":"onboarding","permalink":"/blog/tags/onboarding"},{"label":"compose","permalink":"/blog/tags/compose"},{"label":"extensions","permalink":"/blog/tags/extensions"},{"label":"settings","permalink":"/blog/tags/settings"}],"readingTime":8.14,"hasTruncateMarker":false,"authors":[{"name":"M\xe1ir\xedn Duffy","title":"User Experience Designer","url":"https://github.com/mairin","imageURL":"https://github.com/mairin.png","key":"duffy"}],"frontMatter":{"title":"Release Notes - Podman Desktop 1.5","description":"Podman Desktop 1.5 has been released!","slug":"podman-desktop-release-1.5","authors":"duffy","tags":["podman-desktop","release","kubernetes","openshift","onboarding","compose","extensions","settings"],"hide_table_of_contents":false,"image":"/img/blog/podman-desktop-release-1.5/onboarding-selkies.png"},"unlisted":false,"prevItem":{"title":"Share your local podman images with the Kubernetes cluster","permalink":"/blog/sharing-podman-images-with-kubernetes-cluster"},"nextItem":{"title":"Release Notes - Podman Desktop 1.4","permalink":"/blog/podman-desktop-release-1.4"}},"content":"import ReactPlayer from \'react-player\'\\n\\nPodman Desktop 1.5 Release! \ud83c\udf89\\n\\nWith this release of Podman Desktop, we\'re introducing **a new onboarding feature** that we hope will earn your \ud83e\uddad seal of approval! But wait... there\'s so much more!\\n\\n- **Onboarding**: Guided setup and configuration of **Podman** and **Compose**\\n- **Podman 4.7.2**: [Podman 4.7.2](https://github.com/containers/podman/releases) is now included in Windows and Mac installers\\n- **Command Palette**: Gain easy access to various commands via a new keyboard-driven command palette\\n- **Expanded \\"Summary\\" tab for Kubernetes pods**: Go deep with extended details on Kubernetes pods in the pod \\"Summary\\" tab\\n- **Environment file support**: Chart out environment variables for new containers to access on creation\\n- **Enhancements to the Settings area**: Get your bearings with improved Docker compatibility mode controls\\n- **Improved user experience for state changes**: No more dead reckoning on container state with improved visual indication of status\\n- **Extension API improvements**: A boatload of improvements to the extension API enabling more goodness from \ud83e\uddad Podman Desktop\'s extensions\\n\\nPodman Desktop 1.5 is now available. [Click here to download it](/downloads)!\\n\\n![Podman-desktop-1-5-hero](img/podman-desktop-release-1.5/onboarding-selkies.png)\\n\\n---\\n\\n## Release Details\\n\\n### Onboarding\\n\\nWe are introducing a new feature providing guided flows for the initial setup of specific \ud83e\uddad Podman Desktop extensions. Release 1.5 features two new onboarding flows: Podman and Compose.\\n\\nTo start the Podman onboarding flow, you can start from the dashboard notification by clicking the \\"Set up\\" button:\\n![podman-onboarding-start](https://user-images.githubusercontent.com/799683/280362279-598cc052-5ea4-4c31-849c-da9bbbcc3e42.png)\\n![podman-onboarding](https://user-images.githubusercontent.com/799683/280363859-f35b85f8-1dd4-4b7f-a995-25fe5d1ccced.png)\\n\\nVisit **Settings > Resources** screen and click the Compose \\"Setup ...\\" button in order to start Compose onboarding:\\n![compose-onboarding-start](https://user-images.githubusercontent.com/799683/280276847-ca0558ab-70ad-48cc-8dd5-67e3eb465a62.png)\\n![compose-onboarding](https://user-images.githubusercontent.com/799683/280277936-77ba0fb2-5cb0-41de-a7cf-1a3d6400fd89.png)\\n\\n### Command Palette\\n\\nA new, search-driven command palette is now available to enable quick access to various commands available across \ud83e\uddad Podman Desktop. You can try this new tool out by hitting the F1 key. [#4081](https://github.com/containers/podman-desktop/pull/4081) && [#3979](https://github.com/containers/podman-desktop/pull/3979)\\n\\n\\n\\n### Expanded \\"Summary\\" tab for Kubernetes pods\\n\\nKubernetes pods now offer a more comprehensive set of information under the \\"Summary\\" tab, including networking, volumes, environment variables, and other key metadata.\\n\\n\\n\\n### Environment file support\\n\\nWhen creating a container from the Images list, there\'s now an option to provide an environment file to set env variables for the new container. [#4026](https://github.com/containers/podman-desktop/pull/4026) && [#4025](https://github.com/containers/podman-desktop/pull/4025)\\n\\n### Enhancements to the Settings area\\n\\nThe user experience for enabling or disabling Docker compatibility is improved, with a new entry in the **Settings > Preferences** screen that includes contextual guidance. [#4093](https://github.com/containers/podman-desktop/pull/4093)\\n\\n\\n\\n### Improved user experience for state changes\\n\\nThe user experience around state changes for containers, pods, and other objects in the UI is improved, with clear status messages and improved animated visual indicator of state changes. [#4056](https://github.com/containers/podman-desktop/pull/4056)\\n\\n\\n\\n\\n\\n### Extension API improvements\\n\\nThe \ud83e\uddad Podman Desktop extension API received many improvements, including:\\n\\n- In addition to pushing and listing image from an extension, it\'s now possible to pull images from a \ud83e\uddad Podman Desktop extension [#4155](https://github.com/containers/podman-desktop/pull/4155)\\n\\n- The \ud83e\uddad Podman Desktop extension API has been enhanced with both the ability to list images & networks and the ability to create containers & networks. [#4172](https://github.com/containers/podman-desktop/pull/4172)\\n\\n- \ud83e\uddad Podman Desktop extensions now have a consistent way to run administrative tasks. [#4049](https://github.com/containers/podman-desktop/pull/4049)\\n\\n- Extensions now have the ability to register a custom Kubernetes config generator. [#3970](https://github.com/containers/podman-desktop/pull/3970)\\n\\n- The ability of extensions to add commands to UI menus has been extended; previously for action menus it was only available in the Image list screen. It is now possible for extensions to add commands to the action menus of items listed on the Containers list screen as well. [#3947](https://github.com/containers/podman-desktop/pull/3947) & [#3963](https://github.com/containers/podman-desktop/pull/3963)\\n\\n- Extensions have gained the ability to contribute menu items in the UI based on specific conditions. [#3959](https://github.com/containers/podman-desktop/pull/3959)\\n\\n- Enhanced logic for displaying or hiding properties listed under the **Settings > Preferences** screens is now available. [#4159](https://github.com/containers/podman-desktop/pull/4159)\\n\\n\\n\\n---\\n\\n## Other Notable Enhancements\\n\\n- The progress of loading an image into Kind is now visible as a task in the task manager. [#4061](https://github.com/containers/podman-desktop/pull/4061)\\n\\n![kind-progress-task](https://user-images.githubusercontent.com/42176370/270154775-eb7007b4-fd0e-4287-be9e-40ffc412de35.png)\\n\\n- It\'s now possible to start a new Podman machine right after creation, or you can create it and wait to start it later. It\'s up to you! [#4046](https://github.com/containers/podman-desktop/pull/4046)\\n\\n![podman-start-now-or-later](https://user-images.githubusercontent.com/49404737/269941187-f4768833-ecfc-4d0b-8acf-d4afedb428d9.png)\\n\\n- The Podman machine and Kubernetes provider creation forms have an updated look & feel consisted with other forms in the user interface, along with minor bug fixes. [#4317](https://github.com/containers/podman-desktop/pull/4317)\\n\\n![Updated provider creation forms](https://user-images.githubusercontent.com/19958075/274694157-fe89f3bc-e5b8-4735-96e9-669fe52c7a41.png)\\n\\n- The empty screen message shown when a search filter results in no matches now provides a message specific to filter matching, including the specific filter terms and an explicit button for clearing the filter. Previously, the screen displayed a generic message about how to create new objects of the type displayed on the screen, which led to some confusion about the status of the system. [#3988](https://github.com/containers/podman-desktop/pull/3988)\\n\\n\\n\\n- New support for adding spin animations to icons is now available. [#4188](https://github.com/containers/podman-desktop/pull/4188)\\n\\n- There is a new indeterminate progress bar type available for the task manager; this is meant for providing limited status for actions whose APIs do not provide detailed status information. [#4016](https://github.com/containers/podman-desktop/pull/4016)\\n\\n- For authenticating as admin to perform administrative tasks, \ud83e\uddad Podman Desktop now provides touchID support for macOS. [#4050](https://github.com/containers/podman-desktop/pull/4050)\\n\\n![touchID-support](https://user-images.githubusercontent.com/436777/248588015-f08115bd-d211-43ad-bddd-286d7b3a7056.png)\\n\\n\\n\\n- Support for connecting to interactive terminals for containers via tty was added. [#3900](https://github.com/containers/podman-desktop/pull/3900)\\n\\n- It\'s now more clear which container/pod providers will autostart when \ud83e\uddad Podman Desktop starts. Previously autostart had both a global and a per-provider setting. It has been simplified by removing the global setting. [#3840](https://github.com/containers/podman-desktop/pull/3840)\\n\\n- The \\"Working with containers\\" section of the documentation has been reworked and improved. [#3951](https://github.com/containers/podman-desktop/pull/3951)\\n\\n---\\n\\n## Notable Bug Fixes\\n\\n- The disable registry command was not blocking subsequent pulls from disabled registries. This has been corrected. [#4183](https://github.com/containers/podman-desktop/pull/4183)\\n\\n- Some users behind network proxies were unable to complete workflow involving the download of online resources. The mechanism for fetching these resources has been fixed to be proxy compatible to address this issue. [#3994](https://github.com/containers/podman-desktop/pull/3994)\\n\\n- The status of pods running in Kubernetes that are undergoing the deletion process is now accurately reflected in the \ud83e\uddad Podman Desktop UI. [#3877](https://github.com/containers/podman-desktop/pull/3877)\\n\\n- The image details page always listed the image as being \\"not used\\" even when it was. This has been corrected. [#3985](https://github.com/containers/podman-desktop/pull/3985)\\n\\n- Previously, deleting a specific image tag would cause all tags with the same Image ID to be deleted. This has been fixed so only the selected image tag will be deleted. [#3837](https://github.com/containers/podman-desktop/pull/3837)\\n\\n- Could not view the pod details for some remote Kubernetes cluster pods due to an encoding error. [#4371](https://github.com/containers/podman-desktop/pull/4371)\\n\\n- Error logs were being tracked separately from the actions they applied to. This has been addressed for kind cluster creation failure [#4427](https://github.com/containers/podman-desktop/pull/4427) and Compose installation failure [#4407](https://github.com/containers/podman-desktop/pull/4407).\\n\\n- For Linux users, \ud83e\uddad Podman Desktop previously did not appear under the \\"Development\\" menu when installed via Flatpak; it appeared under \\"Utilities.\\" \ud83e\uddad Podman Desktop now appears under the \\"Development\\" menu. [#3911](https://github.com/containers/podman-desktop/pull/3911)\\n\\n- Podman Machine names are no longer prefixed with the \\"Podman Machine\\" string. [#3878](https://github.com/containers/podman-desktop/pull/3878)\\n\\n![touchID-support](https://user-images.githubusercontent.com/19958075/267378447-aafdfbd7-f005-4b94-8626-9e11eec61b95.png)\\n\\n- The initial action state of pods and containers was being displayed as \\"STARTING\\" regardless of actual state; this has been corrected. [#3889](https://github.com/containers/podman-desktop/pull/3889)\\n\\n- Resizing the application window no longer makes the last lines of a container\'s terminal invisible. [#3993](https://github.com/containers/podman-desktop/pull/3993)\\n\\n- An issue with incorrect terminal behavior in response to long lines in the terminal attached to a container has been resolved. [#3955](https://github.com/containers/podman-desktop/pull/3955)\\n\\n- A spacing issue on the run image form has been corrected. [#4089]https://github.com/containers/podman-desktop/pull/4089\\n\\n- The \\"podify\\" icon & button on the Containers list was unusually large in release 1.4. That regression has been corrected in this release. [#4122](https://github.com/containers/podman-desktop/pull/4122)\\n\\n- An error in the instructions for Windows users on migrating from Docker has been corrected. [#4157](https://github.com/containers/podman-desktop/pull/4157)\\n\\n---\\n\\n## Community Thank You\\n\\n\ud83c\udf89 We\u2019d like to say a big thank you to everyone who helped to make \ud83e\uddad Podman Desktop even better. In this\\nrelease we received pull requests from the following people:\\n\\n- [afbjorklund](https://github.com/afbjorklund) in [#4373 - docs: fix broken links and add lima onboarding](https://github.com/containers/podman-desktop/pull/4373), [#4372 - docs: clear up lima column on containers page](https://github.com/containers/podman-desktop/pull/4372), [#4091 - fix: avoid errors with unexpected JSON input](https://github.com/containers/podman-desktop/pull/4091), [#4098 - docs: Lima onboarding details](https://github.com/containers/podman-desktop/pull/4098), and [#3854 - fix: check if machine init rootful flag supported](https://github.com/containers/podman-desktop/pull/3854)\\n\\n- [axel7083](https://github.com/axel7083) in [#4061 - feat: adding task progress for kind](https://github.com/containers/podman-desktop/pull/4061), [#3970 - feat: extension can register custom kube generator](https://github.com/containers/podman-desktop/pull/3970), [#3959 - feat: add when property to extensions menus](https://github.com/containers/podman-desktop/pull/3959), [#4016 - feat: indeterminate progress bar](https://github.com/containers/podman-desktop/pull/4016), [#3963 - fix: ContainerList propagating containers in ComposeActions and PodActions](https://github.com/containers/podman-desktop/pull/3963), and [#3947 - feat: extend menus capabilities](https://github.com/containers/podman-desktop/pull/3947)\\n\\n- [ayushrakesh](https://github.com/ayushrakesh) in [#4415 - Update README.md](https://github.com/containers/podman-desktop/pull/4415#)\\n\\n- [eltociear](https://github.com/eltociear) in [#4194 - Update README.md](https://github.com/containers/podman-desktop/pull/4194)\\n\\n- [foxydeveloper](https://github.com/foxydevloper) in [#4157 - docs: Correct windows instructions for migrating from docker](https://github.com/containers/podman-desktop/pull/4157)\\n\\n- [harsh-solanki21](https://github.com/harsh-solanki21) in [#4162 - fix: Removed fullstop from summary](https://github.com/containers/podman-desktop/pull/4162)\\n\\n- [rahul0x00](https://github.com/rahul0x00) in [#4240 - fix typos in README.md](https://github.com/containers/podman-desktop/pull/4240)\\n\\n- [shelar1423](https://github.com/shelar1423) in [#4221 - chore: document property setting in EXTENSIONS.md](https://github.com/containers/podman-desktop/pull/4221)\\n\\n---\\n\\n## Final notes\\n\\n### Known Issues\\n\\nWe have a discussion board topic where we have posted known issues with this release. If you run into problems, please check this list before filing a bug - if we already have an issue open for it, it saves you the time and trouble of filing, and there may be a workaround posted in the issue.\\n\\n#### [Known Issues: Podman Desktop 1.5.2](https://github.com/containers/podman-desktop/discussions/4635)\\n\\n### Fixed Issues\\n\\nThe complete list of issues fixed in this release is available [here](https://github.com/containers/podman-desktop/issues?q=is%3Aclosed+milestone%3A1.5.0).\\n\\n### Where to Download\\n\\nGet the latest release from the [Downloads](/downloads) section of the website and boost your development journey with Podman Desktop. Additionally, visit the [GitHub repository](https://github.com/containers/podman-desktop) and see how you can help us make Podman Desktop better."},{"id":"podman-desktop-release-1.4","metadata":{"permalink":"/blog/podman-desktop-release-1.4","source":"@site/blog/2023-09-18-release-1.4.md","title":"Release Notes - Podman Desktop 1.4","description":"Podman Desktop 1.4 has been released!","date":"2023-09-18T00:00:00.000Z","formattedDate":"September 18, 2023","tags":[{"label":"podman-desktop","permalink":"/blog/tags/podman-desktop"},{"label":"release","permalink":"/blog/tags/release"},{"label":"kubernetes","permalink":"/blog/tags/kubernetes"},{"label":"openshift","permalink":"/blog/tags/openshift"}],"readingTime":3.415,"hasTruncateMarker":false,"authors":[{"name":"Jeff Maury","title":"Engineering Manager","url":"https://github.com/jeffmaury","imageURL":"https://github.com/jeffmaury.png","key":"jeffmaury"}],"frontMatter":{"title":"Release Notes - Podman Desktop 1.4","description":"Podman Desktop 1.4 has been released!","slug":"podman-desktop-release-1.4","authors":["jeffmaury"],"tags":["podman-desktop","release","kubernetes","openshift"],"hide_table_of_contents":false,"image":"/img/blog/podman-desktop-release-1.4/juggling.png"},"unlisted":false,"prevItem":{"title":"Release Notes - Podman Desktop 1.5","permalink":"/blog/podman-desktop-release-1.5"},"nextItem":{"title":"Release Notes - Podman Desktop 1.3","permalink":"/blog/podman-desktop-release-1.3"}},"content":"import ReactPlayer from \'react-player\'\\n\\nPodman Desktop 1.4 Release! \ud83c\udf89\\n\\nThis is essentially a bug-fix release to fix various issues in UI, but as usual we also added a few new features.\\n\\n- **Podman 4.6.2**: Podman 4.6.2 included with Podman Desktop 1.4\\n- **Windows Arm64**: Native Windows on Arm64 installers and binaries\\n- **Port range mapping**: Start containers and map a range of ports\\n- **Terminal UX Improvement**: Persistent terminal sessions when SSH\'ing in a container\\n- **Volume Creation**: Create volume from the `Volumes` page\\n- **Bash support**: Terminals are now using `bash` if available.\\n\\nPodman Desktop 1.4 is now available. [Click here to download it](/downloads)!\\n\\n![Podman-desktop-1-4-juggling](img/podman-desktop-release-1.4/juggling.png)\\n\\n---\\n\\n## Release Details\\n\\n### Port range mapping [#3654](https://github.com/containers/podman-desktop/pull/3654)\\n\\nWhen starting a new container, you can now map a port range between host and container. If the range is not valid between host and container, an error is raised.\\n\\n![Range mapping](https://user-images.githubusercontent.com/49404737/262927546-da66b67a-0884-40b1-85bd-a9c3ea2f3f9e.gif)\\n\\n### Terminal lifetime [#3725](https://github.com/containers/podman-desktop/pull/3725)\\n\\nWhen a terminal is opened for a container, it can now be reused after you switched to another part of the Podman Desktop UI.\\n\\n![terminal lifetime](img/podman-desktop-release-1.4/terminal.gif)\\n\\n### Create volume [#3742](https://github.com/containers/podman-desktop/pull/3742)\\n\\nThe Volumes tab now has a Create volume button. The Create volume UI has a single field for the volume name.\\n\\n![create volume](img/podman-desktop-release-1.4/create-volume.gif)\\n\\n### bash support [#3750](https://github.com/containers/podman-desktop/pull/3750)\\n\\nWhen a terminal is opened for a container, if bash is available within the container, it will be used. Otherwise, sh will be used.\\n\\n![bash sh](img/podman-desktop-release-1.4/bash-sh.gif)\\n\\n### Notable Bug Fixes\\n\\n- Reduce API calls when listing containers by @benoitf [#3489](https://github.com/containers/podman-desktop/pull/3489)\\n- Removing a connection(podman machine) should redirect to previous page by @benoitf [#3576](https://github.com/containers/podman-desktop/pull/3576)\\n- Enhance error message when image is not there by @benoitf [#3587](https://github.com/containers/podman-desktop/pull/3587)\\n- Dispose kind install button when extension is deactivated (#3586) by @lstocchi [#3610](https://github.com/containers/podman-desktop/pull/3610)\\n- Replace backslash/slash on windows when building image (#3465) by @lstocchi [#3618](https://github.com/containers/podman-desktop/pull/3618)\\n- Handle null value in container command (#3620) by @lstocchi [#3625](https://github.com/containers/podman-desktop/pull/3625)\\n- Add maximum activation time for extensions by @benoitf [#3446](https://github.com/containers/podman-desktop/pull/3446)\\n- Handle single non-spread arguments by @benoitf [#3641](https://github.com/containers/podman-desktop/pull/3641)\\n- Grab usage data of volumes only on-demand by @benoitf [#3635](https://github.com/containers/podman-desktop/pull/3635)\\n- Add arm64 binaries for Windows by @benoitf [#3643](https://github.com/containers/podman-desktop/pull/3643)\\n- Include right airgap file for Windows and arm64 by @benoitf [#3651](https://github.com/containers/podman-desktop/pull/3651)\\n- Redirect to previous page when removing a kubernetes connection by @benoitf [#3650](https://github.com/containers/podman-desktop/pull/3650)\\n- Support port ranges when starting a container (#3204) by @lstocchi [#3654](https://github.com/containers/podman-desktop/pull/3654)\\n- Add a strict undefined check to messagebox result (#3692) by @lstocchi [#3699](https://github.com/containers/podman-desktop/pull/3699)\\n- Only restart if a machine is running by @cdrage [#3491](https://github.com/containers/podman-desktop/pull/3491)\\n- Session to the terminal is reused by @benoitf [#3725](https://github.com/containers/podman-desktop/pull/3725)\\n- Disable next button and show try again when onboarding failed (#3616) by @lstocchi [#3711](https://github.com/containers/podman-desktop/pull/3711)\\n- Add podman in PATH after updating process environment PATH (#3729) by @lstocchi [#3730](https://github.com/containers/podman-desktop/pull/3730)\\n- Allow to create a volume by @benoitf [#3742](https://github.com/containers/podman-desktop/pull/3742)\\n- Using bash if available otherwise sh in terminal by @axel7083 [#3750](https://github.com/containers/podman-desktop/pull/3750)\\n- Allow to embed existing component to onboarding (#3755) by @lstocchi [#3763](https://github.com/containers/podman-desktop/pull/3763)\\n- Some containers never return logs, do not wait for them by @dgolovin [#3784](https://github.com/containers/podman-desktop/pull/3784)\\n- Remove cancel button when on final onboarding step (#3771) by @lstocchi [#3802](https://github.com/containers/podman-desktop/pull/3802)\\n- Onboarding add link micromark for commands by @cdrage [#3747](https://github.com/containers/podman-desktop/pull/3747)\\n- Mounts can be null when using older podman by @afbjorklund [#3806](https://github.com/containers/podman-desktop/pull/3806)\\n- Remove redundant step completion check when onboarding gets started by @lstocchi [#3798](https://github.com/containers/podman-desktop/pull/3798)\\n- Ability to click enter in pull image name input by @deboer-tim [#3850](https://github.com/containers/podman-desktop/pull/3850)\\n- Set proxy environment variable when launching process by @jeffmaury [#3838](https://github.com/containers/podman-desktop/pull/3838)\\n- The socket location was moved for new podman by @afbjorklund [#3853](https://github.com/containers/podman-desktop/pull/3853)\\n- Don\'t log console errors when activating lima extension by @afbjorklund [#3852](https://github.com/containers/podman-desktop/pull/3852)\\n\\n### Community Thank You\\n\\n\ud83c\udf89 We\u2019d like to say a big thank you to everyone who helped to make Podman Desktop even better.\\n\\nA warm welcome to [@tomgoren](https://github.com/tomgoren), [@Julian](https://github.com/Julian), [@Gelob](https://github.com/Gelob) and [@cedricclyburn](https://github.com/cedricclyburn) who made their first contribution to the project in this release.\\n\\n### Final Notes\\n\\nThe complete list of issues fixed in this release is available [here](https://github.com/containers/podman-desktop/issues?q=is%3Aclosed+milestone%3A1.4.0).\\n\\nGet the latest release from the [Downloads](/downloads) section of the website and boost your development journey with Podman Desktop. Additionally, visit the [GitHub repository](https://github.com/containers/podman-desktop) and see how you can help us make Podman Desktop better."},{"id":"podman-desktop-release-1.3","metadata":{"permalink":"/blog/podman-desktop-release-1.3","source":"@site/blog/2023-08-16-release-1.3.md","title":"Release Notes - Podman Desktop 1.3","description":"Podman Desktop 1.3 has been released!","date":"2023-08-16T00:00:00.000Z","formattedDate":"August 16, 2023","tags":[{"label":"podman-desktop","permalink":"/blog/tags/podman-desktop"},{"label":"release","permalink":"/blog/tags/release"},{"label":"kubernetes","permalink":"/blog/tags/kubernetes"},{"label":"openshift","permalink":"/blog/tags/openshift"}],"readingTime":5.195,"hasTruncateMarker":false,"authors":[{"name":"Denis Golovin","title":"Principal Software Engineer","url":"https://github.com/cdrage","imageURL":"https://github.com/dgolovin.png","key":"dgolovin"}],"frontMatter":{"title":"Release Notes - Podman Desktop 1.3","description":"Podman Desktop 1.3 has been released!","slug":"podman-desktop-release-1.3","authors":["dgolovin"],"tags":["podman-desktop","release","kubernetes","openshift"],"hide_table_of_contents":false,"image":"/img/blog/podman-desktop-release-1.3.webp"},"unlisted":false,"prevItem":{"title":"Release Notes - Podman Desktop 1.4","permalink":"/blog/podman-desktop-release-1.4"},"nextItem":{"title":"Release Notes - Podman Desktop 1.2","permalink":"/blog/podman-desktop-release-1.2"}},"content":"import ReactPlayer from \'react-player\'\\n\\nPodman Desktop 1.3 Release! \ud83c\udf89\\n\\nThis 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.\\n\\n- **Podman 4.6.1**: Podman 4.6.1 included in Windows and Mac installers\\n- **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\\n- **Compose group new UI elements**: You can now see summary, inspect, deploy to kubernetes, generate kube yaml and view logs\\n- **Extension packs and extension dependencies**: Install group of extensions in one click\\n- **Resource details page update**: See summary and log for resource\\n- **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\\n- **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\\n- **Podman Initial Onboarding (preview)**: Install and configure podman using included installer\\n\\nPodman Desktop 1.3 is now available. [Click here to download it](/downloads)!\\n\\n![Podman-desktop-1-3-bug-swatting](img/podman-desktop-release-1.3/title-bug-swatting.png)\\n\\n---\\n\\n## Release Details\\n\\n### Compose group Logs tab [#3176](https://github.com/containers/podman-desktop/pull/3176)\\n\\nWhen 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\\nlog for every component individually.\\n\\n![Screenshot 2023-07-11 at 12 48 47 PM](https://github.com/containers/podman-desktop/assets/6422176/743a4ffc-e291-4697-8ac5-8052cc921946)\\n\\n### Podman user-mode networking support to Windows/WSL [#3251](https://github.com/containers/podman-desktop/pull/3251)\\n\\nCertain 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.\\n\\n![user](https://github.com/containers/podman-desktop/assets/620330/2f521576-b6a6-42b5-b24d-08df5b432608)\\n\\n### Compose group Summary tab [#3317](https://github.com/containers/podman-desktop/pull/3317),\\n\\nCompose group Summary tab shows all containers in the group and let you navigate to Details page for specific container.\\n\\n\\n\\n### Compose group Inspect tab [#3316](https://github.com/containers/podman-desktop/pull/3316)\\n\\nCompose group Inspect tab shows an array of \\"container inspect\\" from docker / podman.\\n\\n\\n\\n### `Deploy to kubernetes` in compose actions [#3299](https://github.com/containers/podman-desktop/pull/3295)\\n\\nA button to deploy to kubernetes added to Compose group.\\n\\n\\n\\n### `Generate Kube` in Compose actions and `Kube` tab in compose details [#3253](https://github.com/containers/podman-desktop/pull/3253)\\n\\n`Generate Kube` item added to Compose actions and \\"Kube\\" tab is now available in Compose details view.\\n\\n\\n\\n### Install multiple extensions using extension pack [#3150](https://github.com/containers/podman-desktop/pull/3150)\\n\\nAn Extension pack introduced in Extension engine is a way to declare set of extensions to install them all at once.\\n\\n\\n\\n### Customize icons from extension [#3131](https://github.com/containers/podman-desktop/pull/3131)\\n\\nExtensions now can customize icons for list elements using `when` clause.\\n\\n![image](https://github.com/containers/podman-desktop/assets/49404737/7aae5347-4f07-4854-ba11-1f629b5ccf22)\\n\\n### Resource details page update [#1923](https://github.com/containers/podman-desktop/pull/1923)\\n\\nIf 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).\\n\\n![image](https://user-images.githubusercontent.com/49404737/229542404-bae44f89-5cd3-4baf-8b08-e934e4462697.gif)\\n\\n### `Node\'s container image` field added to `Create a Kind cluster` form [#3508](https://github.com/containers/podman-desktop/pull/3508)\\n\\nThe new `Node\'s container image` field can be used to specify the Kubernetes version used for the control-planed.\\n\\n![image](https://github.com/containers/podman-desktop/assets/42176370/b2a63faf-629f-436d-8496-7c0cd8158679)\\n\\n### Support Docker Desktop extensions using a backend [#3435](https://github.com/containers/podman-desktop/pull/3435)\\n\\nPodman Desktop now loads the containers in the backend as described in the vm section of extension descriptor the same way as Docker Desktop does.\\n\\n### Initial onboarding implementation for podman (experimental) [#3308](https://github.com/containers/podman-desktop/pull/3308)\\n\\nThis is the initial implementation for the onboarding feature. It only covers a simple onboarding for podman. Check system requirements -> install podman -> yay! Done!\\n\\n### Notable Bug Fixes\\n\\n- Updating videos to be adaptive for mobile by @mairin [#3229](https://github.com/containers/podman-desktop/pull/3229)\\n- Consistent max width and padding in settings by @deboer-tim [#3232](https://github.com/containers/podman-desktop/pull/3232)\\n- Settings navigation bar resizing by @deboer-tim in [#3231](https://github.com/containers/podman-desktop/pull/3231)\\n- Move new registry button to header by @deboer-tim [#3245](https://github.com/containers/podman-desktop/pull/3245)\\n- Bigger lima logo by @afbjorklund [#3248](https://github.com/containers/podman-desktop/pull/3248)\\n- Horizontal docker logo by @afbjorklund [#3236](https://github.com/containers/podman-desktop/pull/3236)\\n- Respect LIMA_HOME environment variable by @afbjorklund [#3254](https://github.com/containers/podman-desktop/pull/3254)\\n- Add check before writing to terminal by @lstocchi [#3263](https://github.com/containers/podman-desktop/pull/3263)\\n- Wait until remote side has fully initialized the extensions by @benoitf [#3257](https://github.com/containers/podman-desktop/pull/3257)\\n- Fix loader not centered horizontally by @benoitf [#3270](https://github.com/containers/podman-desktop/pull/3270)\\n- Troubleshooting still waiting after failure by @deboer-tim [#3354](https://github.com/containers/podman-desktop/pull/3354)\\n- Store error for build by @cdrage [#3365](https://github.com/containers/podman-desktop/pull/3365)\\n- Missing checkbox tooltips by @deboer-tim [#3380](https://github.com/containers/podman-desktop/pull/3380)\\n- Load compose logs async not await by @cdrage [#3377](https://github.com/containers/podman-desktop/pull/3377)\\n- Set rootful connection when starting rootful machine by @lstocchi [#3364](https://github.com/containers/podman-desktop/pull/3364)\\n- Default last page by @deboer-tim [#3388](https://github.com/containers/podman-desktop/pull/3388)\\n- Avoid dashboard displaying providers starting while they don\'t by @benoitf [#3451](https://github.com/containers/podman-desktop/pull/3451)\\n- Do not use extensionInfo until it is defined by @benoitf [#V](https://github.com/containers/podman-desktop/pull/3450)\\n- Allow BASIC authentication (all caps) by @cdrage [#3471](https://github.com/containers/podman-desktop/pull/3471)\\n- Allow single domain registry such as localhost:5000 by @cdrage [#3468](https://github.com/containers/podman-desktop/pull/3468)\\n- Create /usr/local/bin directory if it does not exist on binary install by @cdrage [#3425](https://github.com/containers/podman-desktop/pull/3425)\\n- Only delete selected pods by @deboer-tim [#](https://github.com/containers/podman-desktop/pull/3378)\\n- Add back \'Done\' text on the button by @benoitf [#3487](https://github.com/containers/podman-desktop/pull/3487)\\n- Do not wait for more than 5s when checking for podman ping by @benoitf [#3497](https://github.com/containers/podman-desktop/pull/3497)\\n- Add proxy support for extension using patching get and request approach by @dgolovin [#2825](https://github.com/containers/podman-desktop/pull/2825)\\n- Refresh component when field is updated by @benoitf [#3525](https://github.com/containers/podman-desktop/pull/3525)\\n- Higher-res icons for featured extensions list by @mairin [#3511](https://github.com/containers/podman-desktop/pull/3511)\\n- Main nav selection by @deboer-tim [#3510](https://github.com/containers/podman-desktop/pull/3510)\\n- kube event error when switching context by @jeffmaury [#3494](https://github.com/containers/podman-desktop/pull/3494)\\n- Reset error message each time we pull image by @benoitf [#3550](https://github.com/containers/podman-desktop/pull/3550)\\n\\n### Community Thank You\\n\\n\ud83c\udf89 We\u2019d like to say a big thank you to everyone who helped to make Podman Desktop even better.\\n\\nA warm welcome to [@rostalan](https://github.com/rostalan) and [@axel7083](https://github.com/axel7083) who made their first contribution to the project in this release.\\n\\n### Final Notes\\n\\nThe complete list of issues fixed in this release is available [here](https://github.com/containers/podman-desktop/issues?q=is%3Aclosed+milestone%3A1.3.0).\\n\\nGet the latest release from the [Downloads](/downloads) section of the website and boost your development journey with Podman Desktop. Additionally, visit the [GitHub repository](https://github.com/containers/podman-desktop) and see how you can help us make Podman Desktop better."},{"id":"podman-desktop-release-1.2","metadata":{"permalink":"/blog/podman-desktop-release-1.2","source":"@site/blog/2023-07-12-release-1.2.md","title":"Release Notes - Podman Desktop 1.2","description":"Podman Desktop 1.2 has been released!","date":"2023-07-12T00:00:00.000Z","formattedDate":"July 12, 2023","tags":[{"label":"podman-desktop","permalink":"/blog/tags/podman-desktop"},{"label":"release","permalink":"/blog/tags/release"},{"label":"kubernetes","permalink":"/blog/tags/kubernetes"},{"label":"openshift","permalink":"/blog/tags/openshift"}],"readingTime":6.05,"hasTruncateMarker":false,"authors":[{"name":"Charlie Drage","title":"Software Engineer","url":"https://github.com/cdrage","imageURL":"https://github.com/cdrage.png","key":"cdrage"}],"frontMatter":{"title":"Release Notes - Podman Desktop 1.2","description":"Podman Desktop 1.2 has been released!","slug":"podman-desktop-release-1.2","authors":["cdrage"],"tags":["podman-desktop","release","kubernetes","openshift"],"hide_table_of_contents":false,"image":"/img/blog/podman-desktop-release-1.2.webp"},"unlisted":false,"prevItem":{"title":"Release Notes - Podman Desktop 1.3","permalink":"/blog/podman-desktop-release-1.3"},"nextItem":{"title":"Release Notes - Podman Desktop 1.1","permalink":"/blog/podman-desktop-release-1.1"}},"content":"import ReactPlayer from \'react-player\'\\n\\nPodman Desktop 1.2 Release! \ud83c\udf89\\n\\nWe\'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:\\n\\n- **Added start/stop/delete/restart buttons for Compose**: You can now make changes to an entire Compose group of containers\\n- **Kubernetes context on the status bar**: Choose from multiple Kubernetes contexts more easily all from the status bar\\n- **Rename images**: Rename an image with a click of a button\\n- **Protocol handler support**: Added support for protocol handlers such as `open podman-desktop:extension/redhat.openshift-local`\\n- **Troubleshooting page**: A troubleshooting page for helping diagnose Podman Desktop related development issues\\n\\nPodman Desktop 1.2 is now available. [Click here to download it](/downloads)!\\n\\n![Podman-desktop-1-2-hero](img/podman-desktop-release-1.2/podman-desktop-release-1.2.png)\\n\\n---\\n\\n## Release Details\\n\\n### Added start/stop/delete/restart buttons for Compose\\n\\nIn 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`.\\n\\nStay 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.\\n\\n\\n\\n### Kubernetes context on the status bar\\n\\nWith 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.\\n\\n\\n\\n### Rename images\\n\\nDeployed 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](https://github.com/tuckerrc) who added the new feature.\\n\\n\\n\\n### Troubleshooting page\\n\\nDeveloping 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!\\n\\nClick on the lightbulb button on the bottom right to access the page.\\n\\n\\n\\n### Protocol handler support\\n\\nPodman 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.\\n\\n\\n\\n---\\n\\n## Other Notable Features\\n\\n- Background colors and FormPage ([PR #2977](https://github.com/containers/podman-desktop/pull/2977))\\n- Add ability to add insecure registry / skipping cert verify ([PR #2896](https://github.com/containers/podman-desktop/pull/2896))\\n- Add support for icon contribution ([PR #2984](https://github.com/containers/podman-desktop/pull/2984))\\n- Add warning dialog message that virtual machine has low memory limit ([PR #2822](https://github.com/containers/podman-desktop/pull/2822))\\n- Propose indexed name for new pod ([PR #3028](https://github.com/containers/podman-desktop/pull/3028))\\n- Add restart button after enabling / disabling mac os compatibility ([PR #2841](https://github.com/containers/podman-desktop/pull/2841))\\n- Add environment related helper constants ([PR #3079](https://github.com/containers/podman-desktop/pull/3079))\\n- Allow entrypoint and cmd when starting container ([PR #3031](https://github.com/containers/podman-desktop/pull/3031))\\n- Add a way to debug stores in troubleshooting page ([PR #3121](https://github.com/containers/podman-desktop/pull/3121))\\n- Add custompick component (#2855) ([PR #3012](https://github.com/containers/podman-desktop/pull/3012))\\n- Dynamic breadcrumbs ([PR #3119](https://github.com/containers/podman-desktop/pull/3119))\\n- Icons on form pages ([PR #3155](https://github.com/containers/podman-desktop/pull/3155))\\n- Switch more pages to formpage ([PR #3162](https://github.com/containers/podman-desktop/pull/3162))\\n- Add rename image button ([PR #2588](https://github.com/containers/podman-desktop/pull/2588))\\n- Fixed headers, improved scrollbars ([PR #2863](https://github.com/containers/podman-desktop/pull/2863))\\n- Reports warnings on failed kube deploy, fixes error out ([PR #3050](https://github.com/containers/podman-desktop/pull/3050))\\n- Kube context on statusbar ([PR #2755](https://github.com/containers/podman-desktop/pull/2755))\\n- Install provider if not installed when clicking on create new button (#2706) ([PR #2817](https://github.com/containers/podman-desktop/pull/2817))\\n- Add tag and authenticated push capacity to the extension API ([PR #2876](https://github.com/containers/podman-desktop/pull/2876))\\n- Add navigation bar e2e tests ([PR #2950](https://github.com/containers/podman-desktop/pull/2950))\\n\\n---\\n\\n## Documentation Updates\\n\\n- Fix documentation for building image of extensions ([PR #2873](https://github.com/containers/podman-desktop/pull/2873))\\n- Add Minikube install docs ([PR #2824](https://github.com/containers/podman-desktop/pull/2824))\\n- Add Minikube documentation ([PR #2694](https://github.com/containers/podman-desktop/pull/2694))\\n- Updated Building an image procedure ([PR #2964](https://github.com/containers/podman-desktop/pull/2964))\\n- Starting a container ([PR #2958](https://github.com/containers/podman-desktop/pull/2958))\\n- Pulling an image ([PR #2956](https://github.com/containers/podman-desktop/pull/2956))\\n- Updated selecting containers to run in a pod ([PR #2970](https://github.com/containers/podman-desktop/pull/2970))\\n- Pushing an image to a registry ([PR #2969](https://github.com/containers/podman-desktop/pull/2969))\\n- How to add an insecure registry ([PR #2953](https://github.com/containers/podman-desktop/pull/2953))\\n- Add documentation for lima ([PR #2995](https://github.com/containers/podman-desktop/pull/2995))\\n- Replace broken link to podman.io ([PR #2994](https://github.com/containers/podman-desktop/pull/2994))\\n- Authenticating to a pre-configured registry ([PR #2965](https://github.com/containers/podman-desktop/pull/2965))\\n- Lima is not a container engine ([PR #3051](https://github.com/containers/podman-desktop/pull/3051))\\n- Using the Troubleshooting page ([PR #3083](https://github.com/containers/podman-desktop/pull/3083))\\n- View and select your current Kubernetes context in the status bar ([PR #3090](https://github.com/containers/podman-desktop/pull/3090))\\n\\n---\\n\\n## Notable Bug Fixes\\n\\n- Deleting a running pod generates an error ([PR #2827](https://github.com/containers/podman-desktop/pull/2827))\\n- If kubeconfig is empty, does not try to do things, cancel ([PR #2874](https://github.com/containers/podman-desktop/pull/2874))\\n- Async telemetry startup ([PR #2885](https://github.com/containers/podman-desktop/pull/2885))\\n- Do not block startup while waiting for kube resource refresh ([PR #2884](https://github.com/containers/podman-desktop/pull/2884))\\n- Images list too wide ([PR #2918](https://github.com/containers/podman-desktop/pull/2918))\\n- Compose deactivate function never called ([PR #2922](https://github.com/containers/podman-desktop/pull/2922))\\n- Auto-scrolling on form pages, layout issues ([PR #2927](https://github.com/containers/podman-desktop/pull/2927))\\n- Show current context in quick pick ([PR #2920](https://github.com/containers/podman-desktop/pull/2920))\\n- Remove sticky position of loader in dashboard UI (#2535) ([PR #2959](https://github.com/containers/podman-desktop/pull/2959))\\n- Undo change that broke the website ([PR #2992](https://github.com/containers/podman-desktop/pull/2992))\\n- Detailspage, resizing & consistency ([PR #2987](https://github.com/containers/podman-desktop/pull/2987))\\n- Quick pick click to close and over nav bar ([PR #2758](https://github.com/containers/podman-desktop/pull/2758))\\n- Only show empty screen when no pods ([PR #2929](https://github.com/containers/podman-desktop/pull/2929))\\n- Do not redirect to /pods when deleting pod in containerlist ([PR #2963](https://github.com/containers/podman-desktop/pull/2963))\\n- Bulk delete on pods should call the pod deletion ([PR #2979](https://github.com/containers/podman-desktop/pull/2979))\\n- Update nodejs version to 18 in .nvmrc to fix yarn install failure ([PR #2989](https://github.com/containers/podman-desktop/pull/2989))\\n- Website check targets ([PR #2996](https://github.com/containers/podman-desktop/pull/2996))\\n- Don\'t show exception to user ([PR #3034](https://github.com/containers/podman-desktop/pull/3034))\\n- Interpret arguments given to info command for example ([PR #3015](https://github.com/containers/podman-desktop/pull/3015))\\n- Change defaults for Podman machine ([PR #3061](https://github.com/containers/podman-desktop/pull/3061))\\n- Normalize development/production folders path ([PR #3113](https://github.com/containers/podman-desktop/pull/3113))\\n- Calculate machine socket path for linux ([PR #3070](https://github.com/containers/podman-desktop/pull/3070))\\n- Replace backslash with slash so to support rendering on Windows (#3120) ([PR #3122](https://github.com/containers/podman-desktop/pull/3122))\\n- Keep stdout and stderr in the error object for Docker Desktop extensions ([PR #3014](https://github.com/containers/podman-desktop/pull/3014))\\n- Mark task completed if there\'s a failure ([PR #3016](https://github.com/containers/podman-desktop/pull/3016))\\n- Handle invalid kubeconfig file ([PR #3129](https://github.com/containers/podman-desktop/pull/3129))\\n- Do not remove registries when podman extension is stopping ([PR #3136](https://github.com/containers/podman-desktop/pull/3136))\\n- Warning should be amber ([PR #3153](https://github.com/containers/podman-desktop/pull/3153))\\n- Load user extensions from plugins as removable ([PR #3152](https://github.com/containers/podman-desktop/pull/3152))\\n- Images with spaces in entrypoints or commands fail to start ([PR #3161](https://github.com/containers/podman-desktop/pull/3161))\\n- Scrolling offscreen when clicking checkbox ([PR #3178](https://github.com/containers/podman-desktop/pull/3178))\\n- Avoid messagebox expanding offscreen ([PR #2778](https://github.com/containers/podman-desktop/pull/2778))\\n- Release-notes-generator run failure ([PR #2752](https://github.com/containers/podman-desktop/pull/2752))\\n- Unable to do a new build if the previous one failed ([PR #2721](https://github.com/containers/podman-desktop/pull/2721))\\n\\n---\\n\\n## Community Thank You\\n\\n\ud83c\udf89 We\u2019d like to say a big thank you to everyone who helped to make Podman Desktop even better.\\n\\nA big shoutout to [@afbjorklund](https://github.com/afbjorklund), [@tuckerrc](https://github.com/tuckerrc) and [@evanshortiss](https://github.com/evanshortiss) who contributed to this release!\\n\\n---\\n\\n## Final notes\\n\\nThe complete list of issues fixed in this release is available [here](https://github.com/containers/podman-desktop/issues?q=is%3Aclosed+milestone%3A1.2.0) and [here](https://github.com/containers/podman-desktop/issues?q=is%3Aclosed+milestone%3A1.2.0).\\n\\nGet the latest release from the [Downloads](/downloads) section of the website and boost your development journey with Podman Desktop. Additionally, visit the [GitHub repository](https://github.com/containers/podman-desktop) and see how you can help us make Podman Desktop better."},{"id":"podman-desktop-release-1.1","metadata":{"permalink":"/blog/podman-desktop-release-1.1","source":"@site/blog/2023-06-08-release-1.1.md","title":"Release Notes - Podman Desktop 1.1","description":"Podman Desktop 1.1 has been released!","date":"2023-06-08T00:00:00.000Z","formattedDate":"June 8, 2023","tags":[{"label":"podman-desktop","permalink":"/blog/tags/podman-desktop"},{"label":"release","permalink":"/blog/tags/release"},{"label":"kubernetes","permalink":"/blog/tags/kubernetes"},{"label":"openshift","permalink":"/blog/tags/openshift"}],"readingTime":2.465,"hasTruncateMarker":true,"authors":[{"name":"Tim deBoer","title":"Architect","url":"https://github.com/deboer-tim","imageURL":"https://github.com/deboer-tim.png","key":"deboer"}],"frontMatter":{"title":"Release Notes - Podman Desktop 1.1","description":"Podman Desktop 1.1 has been released!","slug":"podman-desktop-release-1.1","authors":["deboer"],"tags":["podman-desktop","release","kubernetes","openshift"],"hide_table_of_contents":false,"image":"/img/blog/podman-desktop-release-1.1.webp"},"unlisted":false,"prevItem":{"title":"Release Notes - Podman Desktop 1.2","permalink":"/blog/podman-desktop-release-1.2"},"nextItem":{"title":"Release Notes - Podman Desktop 1.0","permalink":"/blog/podman-desktop-release-1.0"}},"content":"import ReactPlayer from \'react-player\'\\n\\nPodman Desktop 1.1 Release! \ud83c\udf89\\n\\nThis is primarily a bug-fix release to fix a few important issues, but we\'ve managed to squeeze in a few enhancements\\nalong the way.\\n\\n\x3c!--Main Features--\x3e\\n\\n- **Podman 4.5.1**: Podman 4.5.1 now included in Windows and Mac installers.\\n- **Extensions**: Update extensions from within Podman Desktop.\\n- **Lima Support**: Choose engine type and override its name from the settings.\\n- **UX and UI Improvements**: New loading screen.\\n\\nPodman Desktop 1.1 is now available. [Click here to download it](/downloads)!\\n\\n![Podman-desktop-1-1-hero](img/podman-desktop-release-1.1/podman-desktop-release-1.1.png)\\n\\n\x3c!--truncate--\x3e\\n\\n---\\n\\n## Release Details\\n\\n### Podman v4.5.1\\n\\nPodman Desktop 1.1 moves up to [Podman 4.5.1](https://github.com/containers/podman/releases/tag/v4.5.1).\\n\\n### Extensions\\n\\nOptional extensions will follow their own lifecycle and update independently from Podman Desktop. As of\\nthis release you\'ll be able to see when there is an update available and install from within\\nPodman Desktop [#2655](https://github.com/containers/podman-desktop/pull/2655).\\n\\nWe\'ve also added options in **Settings > Preferences** to\\nautomatically check for and install extension updates.\\n\\n\\n\\n![Update extensions](img/podman-desktop-release-1.1/update-extensions.png)\\n\\n### Lima Support\\n\\nThanks to contributor [Anders Bj\xf6rklund](https://github.com/afbjorklund), we have some improvements to the\\nLima extension! In **Settings > Preferences** you can select which\\nengine type Lima runs on and override the instance name [#2674](https://github.com/containers/podman-desktop/pull/2674).\\n\\n![Lima preferences](https://user-images.githubusercontent.com/10364051/241755966-0a6a293b-b18e-4222-9c40-abd6c114d464.png)\\n\\n### Other UI and UX Improvements\\n\\n#### New Loading Screen\\n\\nWe have a new loading screen, Podman Desktop style! [#2743](https://github.com/containers/podman-desktop/pull/2743).\\n\\n\\n\\n---\\n\\n## Other Notable Enhancements\\n\\n- Docker-compose can be installed system-wide [#2718](https://github.com/containers/podman-desktop/pull/2718).\\n- Show warning when creating a pod with two containers that use the same port [#2671](https://github.com/containers/podman-desktop/pull/2671).\\n- Display Kubernetes context name in pod label [#2634](https://github.com/containers/podman-desktop/pull/2634).\\n- Add Docker compatibility button using flatpak-spawn [#1925](https://github.com/containers/podman-desktop/pull/1925).\\n- Improve UI consistency of Pull Image page [#2604](https://github.com/containers/podman-desktop/pull/2604).\\n\\n---\\n\\n## Notable Bug Fixes\\n\\n- Could not install extensions on Windows 10 [#2762](https://github.com/containers/podman-desktop/pull/2762).\\n- Could not use locally built images on Kubernetes [#2710](https://github.com/containers/podman-desktop/pull/2710).\\n- Dashboard still suggests update after installation [#2648](https://github.com/containers/podman-desktop/pull/2648).\\n- Could not Play Kubernetes YAML to Podman on Windows [#2594](https://github.com/containers/podman-desktop/pull/2594).\\n- Pod label wasn\'t always shown in list [#2614](https://github.com/containers/podman-desktop/pull/2614).\\n- Dashboard button state was resetting [#2584](https://github.com/containers/podman-desktop/pull/2584).\\n- Change checkbox style so they don\'t look like stop buttons [#2723](https://github.com/containers/podman-desktop/pull/2723).\\n\\n---\\n\\n## Community Thank You\\n\\n\ud83c\udf89 We\u2019d like to say a big thank you to everyone who helped to make Podman Desktop even better. In this\\nsprint we received pull requests from the following people:\\n\\n- [wangxiaolei](https://github.com/fatelei) in [#2602 - Add meaningful tooltips to build, pull, prune buttons](https://github.com/containers/podman-desktop/pull/2602)\\n- [AsciiWolf](https://github.com/AsciiWolf) in [#2607 - fix typing error in Flathub name](https://github.com/containers/podman-desktop/pull/2607) and [#2609 - fix Flatpak install instructions](https://github.com/containers/podman-desktop/pull/2609)\\n- [Anders Bj\xf6rklund](https://github.com/afbjorklund) in [#2674 - Select engine for Lima provider](https://github.com/containers/podman-desktop/pull/2674)\\n\\n---\\n\\n## Final notes\\n\\nThe complete list of issues fixed in this release is available [here](https://github.com/containers/podman-desktop/issues?q=is%3Aclosed+milestone%3A1.1.0) and [here](https://github.com/containers/podman-desktop/issues?q=is%3Aclosed+milestone%3A1.1.0).\\n\\nGet the latest release from the [Downloads](/downloads) section of the website and boost your development journey with Podman Desktop. Additionally, visit the [GitHub repository](https://github.com/containers/podman-desktop) and see how you can help us make Podman Desktop better."},{"id":"podman-desktop-release-1.0","metadata":{"permalink":"/blog/podman-desktop-release-1.0","source":"@site/blog/2023-05-17-release-1.0.md","title":"Release Notes - Podman Desktop 1.0","description":"Podman Desktop 1.0 has been released!","date":"2023-05-17T00:00:00.000Z","formattedDate":"May 17, 2023","tags":[{"label":"podman-desktop","permalink":"/blog/tags/podman-desktop"},{"label":"release","permalink":"/blog/tags/release"},{"label":"kubernetes","permalink":"/blog/tags/kubernetes"},{"label":"kind","permalink":"/blog/tags/kind"},{"label":"openshift","permalink":"/blog/tags/openshift"}],"readingTime":5,"hasTruncateMarker":true,"authors":[{"name":"Tim deBoer","title":"Architect","url":"https://github.com/deboer-tim","imageURL":"https://github.com/deboer-tim.png","key":"deboer"}],"frontMatter":{"title":"Release Notes - Podman Desktop 1.0","description":"Podman Desktop 1.0 has been released!","slug":"podman-desktop-release-1.0","authors":["deboer"],"tags":["podman-desktop","release","kubernetes","kind","openshift"],"hide_table_of_contents":false,"image":"/img/blog/podman-desktop-release-1.0.jpg"},"unlisted":false,"prevItem":{"title":"Release Notes - Podman Desktop 1.1","permalink":"/blog/podman-desktop-release-1.1"},"nextItem":{"title":"Release Notes - Podman Desktop 0.15","permalink":"/blog/podman-desktop-release-0.15"}},"content":"import ReactPlayer from \'react-player\'\\n\\nPodman Desktop 1.0 Release! \ud83c\udf89\\n\\nWe still have many things planned, but with a little polish and a few more bug fixes we\\nfelt we\'ve reached a level of maturity and it is now time to declare our 1.0 release.\\n\\nThank you to everyone who has been with us on this journey so far! Please keep the\\nfeedback coming!\\n\\n\x3c!--Main Features--\x3e\\n\\n- **Highlighting Featured Extensions**: Easily find and install new extensions.\\n- **Featured Extensions**: Two new extensions supporting OpenShift.\\n- **Podman Machine as Root**: Ability to run a Podman machine as root.\\n- **UX and UI Improvements**: Opening external websites, editing numbers, and tooltips.\\n\\nPodman Desktop 1.0 is now available. [Click here to download it](/downloads)!\\n\\n![Podman-desktop-1-0-hero](img/podman-desktop-release-1.0/podman-desktop-release-1.0.jpg)\\n\\n\x3c!--truncate--\x3e\\n\\n---\\n\\n## Release Details\\n\\n### Highlighting Featured Extensions\\n\\nA critical part of our vision for Podman Desktop is the ability to install extensions to\\nsupport additional container engines, Kubernetes providers, or other tools. However, it\\nhas not been easy to discover new extensions.\\n\\nWith 1.0 we show a list of featured extensions in the **Welcome**\\n[#2354](https://github.com/containers/podman-desktop/pull/2354), the **Dashboard** and in\\n** Settings > Extensions**\\n[#2355](https://github.com/containers/podman-desktop/pull/2355). Check out the new\\nextensions for **Red Hat OpenShift Local** and the **Developer Sandbox for Red Hat OpenShift**!\\n\\n![Featured extensions](img/podman-desktop-release-1.0/featured-extensions.png)\\n\\n### Featured Extensions\\n\\nSpeaking of extensions, let\'s take a minute to turn the spotlight on these two!\\n\\nHave another idea for extending Podman Desktop? We would love to hear from you or see\\nwhat you can create with the [Extension documentation](/docs/extensions),\\nand feature your extension here.\\n\\n#### Red Hat OpenShift Local\\n\\nOpenShift Local is a fully-featured single-node OpenShift cluster designed to run on your local computer.\\nWith this extension you can install, start/stop, and deploy pods or YAML to OpenShift Local,\\nallowing you to test your applications on a full OpenShift environment, ensuring a consistent\\nexperience between development, test, and production.\\n\\nThe recent addition of the MicroShift preset provides a lighter, optimized option that\\nstarts faster and uses less resources for deployments that still want OpenShift compatibility\\nwithout the full set of OpenShift services.\\n\\n![OpenShift Local](img/podman-desktop-release-1.0/openshift-local.png)\\n\\n#### Developer Sandbox for Red Hat OpenShift\\n\\nThe OpenShift Developer Sandbox is a free, cloud-based OpenShift environment that allows developers to\\ncreate, build, and deploy applications to OpenShift for 30 days. With this extension you can sign up\\nand easily deploy pods or YAML to a hosted OpenShift environment without a local installation or\\nleaving Podman Desktop.\\n\\n![Developer Sandbox](img/podman-desktop-release-1.0/sandbox.png)\\n\\n### Podman Machine as Root\\n\\nWhen creating a Podman machine you can now decide to run as root [#2427](https://github.com/containers/podman-desktop/pull/2427). This is a prerequisite for some scenarios, such as running Kind on Windows.\\n\\n![Podman machine as root](img/podman-desktop-release-1.0/podman-root.png)\\n\\n### Other UI and UX Improvements\\n\\n#### Prompt to Open External Website\\n\\nIn the previous release links to external websites were blocked due to the security risk.\\nIn 1.0 you can click to see the URL and have the option of opening or copying it\\n[#2414](https://github.com/containers/podman-desktop/pull/2414).\\n\\n![External link dialog](img/podman-desktop-release-1.0/external-link.png)\\n\\n#### Editable Numeric Preferences\\n\\nTired of clicking +, +, +? Us too. Numeric preferences are now editable so\\nyou can directly enter the value you want\\n[#2368](https://github.com/containers/podman-desktop/pull/2368).\\n\\n![Editing numbers](img/podman-desktop-release-1.0/edit-number.png)\\n\\n#### Navigation tooltips\\n\\nWe like our new navigation bar, but the tooltips were slow to appear. This made it harder for new\\nusers to discover the pages and for power users to see the container/pod/image counts. The\\ntooltips are now a little nicer and appear immediately\\n[#2286](https://github.com/containers/podman-desktop/pull/2286).\\n\\n![Navigation tooltips](img/podman-desktop-release-1.0/nav-tooltips.png)\\n\\n---\\n\\n## Other Notable Enhancements\\n\\n- If you use a non-default Podman machine you are now prompted to make it the default, so\\n that command line tools will use the same machine [#2205](https://github.com/containers/podman-desktop/pull/2205).\\n\\n- Extensions can now be installed without requiring a running local container engine\\n [#2273](https://github.com/containers/podman-desktop/pull/2273).\\n\\n- When extensions fail to load there is a new state (failed!) and an error message\\n to help you fix or report the problem [#2424](https://github.com/containers/podman-desktop/pull/2424).\\n\\n- The showInputBox API has support for Markdown [#2418](https://github.com/containers/podman-desktop/pull/2418).\\n\\n---\\n\\n## Notable Bug Fixes\\n\\n- Fixed shared status when using multiple Podman 4.5 machines [#2441](https://github.com/containers/podman-desktop/pull/2441).\\n- Fixed hang on exit when telemetry is unreachable [#2431](https://github.com/containers/podman-desktop/pull/2431).\\n- Reduced initial Podman REST API calls to improve performance [#2419](https://github.com/containers/podman-desktop/pull/2419).\\n- **Play Kubernetes YAML** now honors the namespace [#2509](https://github.com/containers/podman-desktop/pull/2509).\\n- **Container** list was not remembering expand/collapsed status [#2491](https://github.com/containers/podman-desktop/pull/2491).\\n- Clear previous error when installing Docker extension [#2469](https://github.com/containers/podman-desktop/pull/2469).\\n- Ensure correct path with running Kind CLI [#2455](https://github.com/containers/podman-desktop/pull/2455).\\n- Use IPv4 over IPv6 by default [#2398](https://github.com/containers/podman-desktop/pull/2398).\\n- When changing the Kubernetes pod name, change the app name to match [#2389](https://github.com/containers/podman-desktop/pull/2389).\\n- Fixed incorrect pod status in **Containers** view [#2387](https://github.com/containers/podman-desktop/pull/2387).\\n- **Dashboard** wasn\'t correctly refreshing Podman status [#2359](https://github.com/containers/podman-desktop/pull/2359).\\n\\n---\\n\\n## Community Thank You\\n\\n\ud83c\udf89 We\u2019d like to say a big thank you to everyone who helped to make Podman Desktop even better. In this final\\nsprint we received pull requests from the following people:\\n\\n- [Taha Attari](https://github.com/TahaAttari) in [#2470 - Update docker command in importing-saved-containers.md](https://github.com/containers/podman-desktop/pull/2470)\\n- [Jason Greene](https://github.com/n1hility) in [#2431 - Fix hang on exit when telemetry endpoint is unreachable](https://github.com/containers/podman-desktop/pull/2431)\\n- [Anders Bj\xf6rklund](https://github.com/afbjorklund) in [#2571 - Fix the location of the lima podman socket](https://github.com/containers/podman-desktop/pull/2571) and [#2572 - Fix the state of the lima container provider](https://github.com/containers/podman-desktop/pull/2572)\\n- [Tucker Chapman](https://github.com/tuckerrc) in [#2567 - Add example image name in placeholder](https://github.com/containers/podman-desktop/pull/2567)\\n\\nThere are now a total of 54 people (and two bots!) who have contributed PRs to Podman Desktop, and we\'d\\nlike to extend an extra thanks to all of those outside of the immediate development team who contributed\\nto get us here:\\n\\n[afbjorklund](https://github.com/afbjorklund),\\n[alv67](https://github.com/alv67),\\n[anjannath](https://github.com/anjannath),\\n[ankanroy-code](https://github.com/ankanroy-code),\\n[arixmkii](https://github.com/arixmkii),\\n[cblecker](https://github.com/cblecker),\\n[cfergeau](https://github.com/cfergeau),\\n[chevdor](https://github.com/chevdor),\\n[chrisjsimpson](https://github.com/chrisjsimpson),\\n[cu8code](https://github.com/cu8code),\\n[doehyunbaek](https://github.com/doehyunbaek),\\n[dylanmtaylor](https://github.com/dylanmtaylor),\\n[eidottermihi](https://github.com/eidottermihi),\\n[elervik](https://github.com/elervik),\\n[emmanuelbernard](https://github.com/emmanuelbernard),\\n[evanfpearson](https://github.com/evanfpearson),\\n[gorkem](https://github.com/gorkem),\\n[idjohnson](https://github.com/idjohnson),\\n[imphil](https://github.com/imphil),\\n[iongion](https://github.com/iongion),\\n[jlosito](https://github.com/jlosito),\\n[KevinAtSesam](https://github.com/KevinAtSesam),\\n[lsm5](https://github.com/lsm5),\\n[Mitch9378](https://github.com/Mitch9378),\\n[n1hility](https://github.com/n1hility),\\n[osslate](https://github.com/osslate),\\n[PatentLobster](https://github.com/PatentLobster),\\n[pwright](https://github.com/pwright),\\n[rdwz](https://github.com/rdwz),\\n[redhatrises](https://github.com/redhatrises),\\n[rhatdan](https://github.com/rhatdan),\\n[RobotSail](https://github.com/RobotSail),\\n[rohit-rambade](https://github.com/rohit-rambade),\\n[rsvoboda](https://github.com/rsvoboda),\\n[sfrunza13](https://github.com/sfrunza13),\\n[shemanaev](https://github.com/shemanaev),\\n[sstosh](https://github.com/sstosh),\\n[stickster](https://github.com/stickster),\\n[TahaAttari](https://github.com/TahaAttari),\\n[ths83](https://github.com/ths83),\\n[Tony-Sol](https://github.com/Tony-Sol),\\n[tuckerrc](https://github.com/tuckerrc),\\n[ucomesdag](https://github.com/ucomesdag),\\n[xbabalov](https://github.com/xbabalov),\\nzezo2019.\\n\\n---\\n\\n## Final notes\\n\\nThe complete list of issues fixed in this release is available [here](https://github.com/containers/podman-desktop/issues?q=is%3Aclosed+milestone%3A1.0.0) and [here](https://github.com/containers/podman-desktop/issues?q=is%3Aclosed+milestone%3A1.0.1).\\n\\nGet the latest release from the [Downloads](/downloads) section of the website and boost your development journey with Podman Desktop. Additionally, visit the [GitHub repository](https://github.com/containers/podman-desktop) and see how you can help us make Podman Desktop better."},{"id":"podman-desktop-release-0.15","metadata":{"permalink":"/blog/podman-desktop-release-0.15","source":"@site/blog/2023-05-02-release-0.15.md","title":"Release Notes - Podman Desktop 0.15","description":"Podman Desktop 0.15 has been released!","date":"2023-05-02T00:00:00.000Z","formattedDate":"May 2, 2023","tags":[{"label":"podman-desktop","permalink":"/blog/tags/podman-desktop"},{"label":"release","permalink":"/blog/tags/release"},{"label":"kubernetes","permalink":"/blog/tags/kubernetes"},{"label":"kind","permalink":"/blog/tags/kind"}],"readingTime":3.685,"hasTruncateMarker":true,"authors":[{"name":"Tim deBoer","title":"Architect","url":"https://github.com/deboer-tim","imageURL":"https://github.com/deboer-tim.png","key":"deboer"}],"frontMatter":{"title":"Release Notes - Podman Desktop 0.15","description":"Podman Desktop 0.15 has been released!","slug":"podman-desktop-release-0.15","authors":["deboer"],"tags":["podman-desktop","release","kubernetes","kind"],"hide_table_of_contents":false,"image":"/img/blog/podman-desktop-release-0.15.webp"},"unlisted":false,"prevItem":{"title":"Release Notes - Podman Desktop 1.0","permalink":"/blog/podman-desktop-release-1.0"},"nextItem":{"title":"Setting up and running a Kubernetes cluster locally with Podman Desktop","permalink":"/blog/running-a-local-kubernetes-cluster-with-podman-desktop"}},"content":"import ReactPlayer from \'react-player\'\\n\\nPodman Desktop 0.15 - Cleanliness is next to Podliness!\\n\\nIt has only been two weeks since our last release, but we really wanted to complete a few scenarios,\\nfix a few bugs, and show off several design updates and UI improvements that we have been working on.\\n\\n\x3c!--Main Features--\x3e\\n\\n- **Podman Version**: Podman 4.5 now included in Windows and Mac installers.\\n- **Kind Ingress**: Creating an ingress to expose services outside the Kind cluster.\\n- **Podliness**: Ability to choose external ports when podifying containers.\\n- **Cleanliness**: New navigation bar, dialog, and palette update.\\n- **UX and UI Improvements**: Markdown support for extensions.\\n\\nPodman Desktop 0.15 is now available. [Click here to download it](/downloads)!\\n\\n![Podman-desktop-0-15-hero](img/podman-desktop-release-0.15/podman-desktop-release-0.15.webp)\\n\\n\x3c!--truncate--\x3e\\n\\n---\\n\\n## Release Details\\n\\n### Update to Podman v4.5.O\\n\\nPodman Desktop 0.15 embeds [Podman 4.5.0](https://github.com/containers/podman/releases/tag/v4.5.0) in\\nWindows and macOS installers [#2115](https://github.com/containers/podman-desktop/issues/2115).\\n\\n### Kind Ingress\\n\\nWait a minute, didn\'t we enable this last release? Well yes, last time we did add support for installing\\nthe Contour ingress controller on Kind [#1675](https://github.com/containers/podman-desktop/issues/1675),\\nbut you still couldn\'t access your containers without the corresponding ingress.\\n\\nThis release adds a simple checkbox you can use when deploying to Kind to create an ingress and\\nmake your service accessible [#1322](https://github.com/containers/podman-desktop/issues/1322).\\n\\n\\n\\n### Podliness: Ability to Choose External Ports when Podifying Containers\\n\\nWhen you create a pod from of a set of containers (Podifying!), you probably don\'t want to expose every\\nsingle port from every container to the world. With an updated panel you can now see which ports each container\\nexposes, pick which should remain visible outside the pod, and which are for internal use\\n[#2232](https://github.com/containers/podman-desktop/pull/2232).\\n\\n![Podify page](https://user-images.githubusercontent.com/49404737/234527674-ed14f52c-8f66-445f-8038-c8135bb61136.gif)\\n\\n### Cleanliness: New Navigation Bar, Dialogs, and Palette\\n\\nIt was time to catch up on some design ideas and do some UI cleanup!\\n\\n#### New Navgation Bar\\n\\nThe navigation bar is now always fixed on the left size, without labels. This opens up more space\\nfor the content on each page, and is easier to jump in and out of ** Settings**.\\n[#2167](https://github.com/containers/podman-desktop/issues/2167)\\n\\n![Navigation bar](img/podman-desktop-release-0.15/navigation.png)\\n\\n#### Updated Dialogs\\n\\nWe wanted messages and dialog boxes to feel a bit more integrated, so we have a new message box\\n[#1808](https://github.com/containers/podman-desktop/pull/1808) and use it for all dialogs opened by\\nextensions, pruning containers/pods/images/volumes [#2138](https://github.com/containers/podman-desktop/pull/2138),\\nand updating Podman Desktop itself [#2249](https://github.com/containers/podman-desktop/pull/2249).\\n\\n![Dialog](img/podman-desktop-release-0.15/dialog.png)\\n\\n#### Colors\\n\\nWe spent some time tweaking colors and closing on our final palette\\n[#2199](https://github.com/containers/podman-desktop/pull/2199), updating the colors in the terminal & detail page\\n[#2222](https://github.com/containers/podman-desktop/pull/2222), tweaking the navigation and main page colors\\n[#2223](https://github.com/containers/podman-desktop/pull/2223),\\nand improving the look of forms [#2156](https://github.com/containers/podman-desktop/issues/2156).\\n\\nWe\'re not done yet, but hopefully you will notice a more polished, consistent, good-looking application!\\n\\n### Other UI and UX Improvements\\n\\n#### Markdown Support for Extensions\\n\\nWe added a new component to display markdown [#2219](https://github.com/containers/podman-desktop/pull/2219) and\\nenabled it in preferences [#2253](https://github.com/containers/podman-desktop/pull/2253), and\\nprovider properties/creation pages [#2152](https://github.com/containers/podman-desktop/issues/2152).\\nWe can now embed links and other formatting in preferences, and extensions can use them in many places, for example:\\n\\n![Markdown](img/podman-desktop-release-0.15/markdown.png)\\n\\n---\\n\\n## Other Notable Enhancements\\n\\n- We know which **Settings** page is used the most often, so now it\'s the default: ** Settings > Resources** [#2105](https://github.com/containers/podman-desktop/issues/2105).\\n\\n- Extensions can now use the Tasks API to let long running tasks continue in the background [#2019](https://github.com/containers/podman-desktop/issues/2019) and the existing withProgress API also uses the task manager now\\n [#2187](https://github.com/containers/podman-desktop/pull/2187).\\n\\n![Task API](https://user-images.githubusercontent.com/695993/233560830-85cfa685-5dcd-4efa-9fae-730a8a9eef3b.gif)\\n\\n- Images are now sorted by age [#2311](https://github.com/containers/podman-desktop/pull/2311).\\n\\n- When you start/stop a container or pod, the button is now animated instead of having an separate spinner\\n [#2101](https://github.com/containers/podman-desktop/issues/2101).\\n\\n- The ** Settings > Preferences** page now has a search bar [#2128](https://github.com/containers/podman-desktop/pull/2128).\\n\\n![Search preferences](img/podman-desktop-release-0.15/prefs.png)\\n\\n- The Help page has been updated [#431](https://github.com/containers/podman-desktop/issues/431).\\n\\n![Updated Help](img/podman-desktop-release-0.15/help.png)\\n\\n---\\n\\n## Notable Bug Fixes\\n\\n- There was no way to see log or outcome if you leave the Kind cluster creation page [#2079](https://github.com/containers/podman-desktop/issues/2079).\\n- Kind image load doesn\'t show a notification [#2225](https://github.com/containers/podman-desktop/issues/2225).\\n- Fix odd selection in ** Settings > Extensions** [#2130](https://github.com/containers/podman-desktop/issues/2130).\\n- Menus are now cleaned up properly when extensions are stopped [#2188](https://github.com/containers/podman-desktop/pull/2188).\\n- Kind clusters are now cleaned up when Podman machine is stopped [#2306](https://github.com/containers/podman-desktop/pull/2306).\\n\\n---\\n\\n## Final notes\\n\\nThe complete list of issues fixed in this release is available [here](https://github.com/containers/podman-desktop/issues?q=is%3Aclosed+milestone%3A0.15.0).\\n\\nGet the latest release from the [Downloads](/downloads) section of the website and boost your development journey with Podman Desktop. Additionally, visit the [GitHub repository](https://github.com/containers/podman-desktop) and see how you can help us make Podman Desktop better."},{"id":"running-a-local-kubernetes-cluster-with-podman-desktop","metadata":{"permalink":"/blog/running-a-local-kubernetes-cluster-with-podman-desktop","source":"@site/blog/2023-04-19-running-a-local-kubernetes-cluster-with-podman-desktop.md","title":"Setting up and running a Kubernetes cluster locally with Podman Desktop","description":"Setting up and running a Kubernetes cluster locally with Podman Desktop","date":"2023-04-19T00:00:00.000Z","formattedDate":"April 19, 2023","tags":[{"label":"podman-desktop","permalink":"/blog/tags/podman-desktop"},{"label":"story","permalink":"/blog/tags/story"},{"label":"kubernetes","permalink":"/blog/tags/kubernetes"},{"label":"kind","permalink":"/blog/tags/kind"}],"readingTime":8.86,"hasTruncateMarker":true,"authors":[{"name":"Fabrice Flore-Thebault","title":"Technical writer","url":"https://github.com/themr0c","imageURL":"https://github.com/themr0c.png","key":"themr0c"}],"frontMatter":{"title":"Setting up and running a Kubernetes cluster locally with Podman Desktop","description":"Setting up and running a Kubernetes cluster locally with Podman Desktop","slug":"running-a-local-kubernetes-cluster-with-podman-desktop","authors":["themr0c"],"tags":["podman-desktop","story","kubernetes","kind"],"hide_table_of_contents":false},"unlisted":false,"prevItem":{"title":"Release Notes - Podman Desktop 0.15","permalink":"/blog/podman-desktop-release-0.15"},"nextItem":{"title":"Release Notes - Podman Desktop 0.14","permalink":"/blog/podman-desktop-release-0.14"}},"content":"In this blog post you will learn to use Podman Desktop to run the [Kubernetes documentation example: Deploying PHP Guestbook application with Redis](https://kubernetes.io/docs/tutorials/stateless-application/guestbook/).\\n\\nOn the agenda:\\n\\n1. Installing Podman Desktop.\\n1. Installing and initializing your container engine: Podman.\\n1. Installing and starting your local Kubernetes provider: Kind.\\n1. Starting the Redis leader.\\n1. Starting and scaling the Redis followers.\\n1. Starting and exposing the Guestbook frontend.\\n\\n\x3c!--truncate--\x3e\\n\\n## Installing Podman Desktop\\n\\nYou need Podman Desktop.\\n\\n1. Go to [Podman Desktop installation documentation](/docs/installation).\\n1. Click on your platform name: [Windows](/docs/installation/windows-install), [macOS](/docs/installation/macos-install), or [Linux](/docs/installation/linux-install).\\n1. Follow the instructions. Stick to the default installation method.\\n1. Start **Podman Desktop**.\\n\\nAt this point, you have a graphical user interface to:\\n\\n- Install Podman and Kind.\\n- Control and work with your container engines and Kubernetes clusters.\\n- Run your application on your container engine and migrate it to Kubernetes.\\n\\n## Installing and initializing your container engine: Podman\\n\\nPodman Desktop can control various container engines, such as:\\n\\n- Docker\\n- Lima\\n- Podman\\n\\nConsider installing the Podman container engine for:\\n\\n- Added security\\n- No daemon\\n- Open source\\n\\nContainers are a Linux technology.\\n\\n- On Linux, you can install Podman natively.\\n See: [Installing Podman on Linux](https://podman.io/docs/installation#installing-on-linux).\\n- On macOS and Windows, Podman requires to run in a Linux virtual machine: the Podman machine.\\n Use Podman Desktop to install Podman and initialize your Podman machine:\\n\\n#### Procedure\\n\\n1. Open Podman Desktop **Dashboard**\\n1. The **Dashboard** displays _Podman Desktop was not able to find an installation of Podman_.\\n1. Click on **Install**.\\n1. Podman Desktop checks the prerequisites to install Podman Engine. When necessary, follow the instructions to install prerequisites.\\n1. Podman displays the dialog: _Podman is not installed on this system, would you like to install Podman?_. Click on **Yes** to install Podman.\\n1. Click on **Initialize and start**.\\n\\n#### Verification\\n\\n- The **Dashboard** displays _Podman is running_.\\n\\n ![Podman is running](img/running-a-local-kubernetes-cluster-with-podman-desktop/podman-is-running.png)\\n\\nAt this point, you can start working with containers.\\n\\n## Installing and starting your local Kubernetes provider: Kind\\n\\nYou want to deploy your application to a local Kubernetes cluster.\\n\\nPodman Desktop can help you run Kind-powered local Kubernetes clusters on a container engine, such as Podman.\\n\\nPodman Desktop helps you [installing the `kind` CLI](/docs/kind/installing):\\n\\n1. In the status bar, click on **Kind**, and follow the prompts.\\n1. When the `kind` CLI is available, the status bar does not display **Kind**.\\n1. On Windows, [configure Podman in rootful mode](/docs/kind/configuring-podman-for-kind-on-windows)\\n\\n ```shell-session\\n $ podman system connection default podman-machine-default-root\\n ```\\n\\n1. Go to ** Settings > Resources**\\n1. In the **\\"Podman Podman** tile, click on the **** icon to restart the Podman container engine.\\n1. In the **\\"Kind Kind** tile, click on the **Create new** button.\\n 1. **Name**: enter `kind-cluster`.\\n 1. **Provider Type**: select `podman`.\\n 1. **HTTP Port**: select `9090`.\\n 1. **HTTPS Port**: select `9443`.\\n 1. **Setup an ingress controller**: `Enabled`\\n 1. Click the **Create** button.\\n ![Create a Kind cluster screen](img/running-a-local-kubernetes-cluster-with-podman-desktop/create-a-kind-cluster.png)\\n1. After successful creation, click on the **Go back to resources** button\\n\\n#### Verification\\n\\n1. In ** Settings > Resources** your Kind cluster is running/\\n\\n ![Kind cluster is running](img/running-a-local-kubernetes-cluster-with-podman-desktop/kind-cluster-is-running.png)\\n\\n1. In the **Podman Desktop** tray, open the **Kubernetes** menu: you can set the context to your Kind cluster: `kind-kind-cluster`.\\n\\n ![Kind cluster Kubernetes context in the tray](img/running-a-local-kubernetes-cluster-with-podman-desktop/kind-cluster-context-in-the-tray.png)\\n\\n At this point, you can start working with containers, and your local Kubernetes cluster.\\n\\n#### Additional resources\\n\\n- [Creating a local Kind-powered Kubernetes cluster](/docs/kind/creating-a-kind-cluster)\\n\\n## Starting the Redis leader\\n\\nThe Guestbook application uses Redis to store its data.\\n\\nWith Podman Desktop, you can prepare the Redis leader image and container on your local container engine, and deploy the results to a Kubernetes pod and service.\\nThis is functionally equal to the `redis-leader` deployment that the Kubernetes example propose.\\n\\n#### Procedure\\n\\n1. Open ** Images > Pull an image**.\\n 1. **Image to Pull**: enter `docker.io/redis:6.0.5`\\n 1. Click **Pull image** to pull the image to your container engine local image registry.\\n 1. Click **Done** to get back to the images list.\\n1. ** Search images**: enter `redis:6.0.5` to find the image.\\n1. Click **** to open the **Create a container from image** dialog.\\n 1. **Container name**: enter `leader`,\\n 1. **Local port for `6379/tcp`**: `6379`.\\n 1. Click ** Start Container** to start the container in your container engine.\\n1. ** Search containers**: enter `leader` to find the running container.\\n1. Click **** to stop the container, and leave the `6379` port available for the Redis follower container.\\n\\n1. Click ** > Deploy to Kubernetes** to open the **Deploy generated pod to Kubernetes** screen.\\n\\n 1. **Pod Name**: enter `redis-leader`.\\n 1. **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`.**\\n 1. **Expose service locally using Kubernetes Ingress**: deselect **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`**.\\n 1. **Kubernetes namespaces**: select `default`.\\n 1. Click ** Deploy**.\\n ![Deploy generated leader pod to Kubernetes screen](img/running-a-local-kubernetes-cluster-with-podman-desktop/deploy-generated-leader-pod-to-kubernetes.png)\\n 1. Wait for the pod to reach the state: **Phase: Running**.\\n 1. Click **Done**.\\n\\n#### Verification\\n\\n- The ** Pods** screen lists the running `redis-leader` pod.\\n\\n ![leader pod is running](img/running-a-local-kubernetes-cluster-with-podman-desktop/leader-pod-is-running.png)\\n\\n## Starting the Redis followers\\n\\nAlthough the Redis leader is a single Pod, you can make it highly available and meet traffic demands by adding a few Redis followers, or replicas.\\n\\n**With Podman Desktop, you can prepare the Redis follower image and container on your local container engine, and deploy the results to Kubernetes pods and services.**\\nThis is functionally equal to the `redis-follower` deployment that the Kubernetes example propose.\\n\\n#### Procedure\\n\\n1. Open ** Images > Pull an image**.\\n 1. **Image to Pull**: enter `gcr.io/google_samples/gb-redis-follower:v2`\\n 1. Click **Pull image** to pull the image to your container engine local image registry.\\n 1. Click **Done** to get back to the images list.\\n1. ** Search images**: enter `gb-redis-follower:v2` to find the image.\\n1. Click **** to open the **Create a container from image** dialog.\\n 1. **Container name**: enter `follower`,\\n 1. **Local port for `6379/tcp`**: `6379`.\\n 1. Click ** Start Container** to start the container in your container engine.\\n1. ** Search containers**: enter `follower` to find the running container.\\n1. Click **** to stop the container: you do not need it to run in the container engine.\\n1. Click ** > Deploy to Kubernetes** to open the **Deploy generated pod to Kubernetes** screen.\\n 1. **Pod Name**: enter `redis-follower`.\\n 1. **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`.**\\n 1. **Expose service locally using Kubernetes Ingress**: deselect **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`**.\\n 1. **Kubernetes namespaces**: select `default`.\\n 1. Click ** Deploy**.\\n ![Deploy generated follower pod to Kubernetes screen](img/running-a-local-kubernetes-cluster-with-podman-desktop/deploy-generated-follower-pod-to-kubernetes.png)\\n 1. Wait for the pod to reach the state: **Phase: Running**.\\n 1. Click **Done**.\\n1. To add replicas, repeat the last step with another **Pod Name** value.\\n\\n#### Verification\\n\\n- The ** Pods** screen lists the running `redis-follower` pods.\\n\\n ![follower pods are running](img/running-a-local-kubernetes-cluster-with-podman-desktop/follower-pods-are-running.png)\\n\\n## Starting the default frontend\\n\\nNow that you have the Redis storage of your Guestbook up and running, start the Guestbook web servers.\\nLike the Redis followers, deploy the frontend using Kubernetes pods and services.\\n\\nThe Guestbook app uses a PHP frontend.\\nIt is configured to communicate with either the Redis follower or leader Services, depending on whether the request is a read or a write.\\nThe frontend exposes a JSON interface, and serves a jQuery-Ajax-based UX.\\n\\nWith 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.\\nThis is functionally equal to the `frontend` deployment that the Kubernetes example propose.\\n\\n#### Procedure\\n\\n1. Open ** Images > Pull an image**.\\n 1. **Image to Pull**: enter `gcr.io/google_samples/gb-frontend:v5`\\n 1. Click **Pull image** to pull the image to your container engine local image registry.\\n 1. Wait for the pull to complete.\\n 1. Click **Done** to get back to the images list.\\n1. ** Search images**: enter `gb-frontend:v5` to find the image.\\n1. Click **** to open the **Create a container from image** dialog.\\n 1. **Container name**: enter `frontend`,\\n 1. **Local port for `80/tcp`**: `9000`.\\n 1. Click ** Start Container** to start the container in your container engine.\\n1. ** Search containers**: enter `frontend` to find the running container.\\n1. Click **** to stop the container: you do not need it to run in the container engine.\\n1. Click ** > Deploy to Kubernetes** to open the **Deploy generated pod to Kubernetes** screen.\\n 1. **Pod Name**: enter `frontend`.\\n 1. **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`.**\\n 1. **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`**.\\n 1. **Kubernetes namespaces**: select `default`.\\n 1. Click ** Deploy**.\\n ![Deploy generated frontend pod to Kubernetes screen](img/running-a-local-kubernetes-cluster-with-podman-desktop/deploy-generated-frontend-pod-to-kubernetes.png)\\n 1. Wait for the pod to reach the state: **Phase: Running**.\\n 1. Click **Done**.\\n\\n#### Verification\\n\\n1. The ** Pods** screen lists the running `frontend` pod.\\n\\n ![`frontend` pod is running](img/running-a-local-kubernetes-cluster-with-podman-desktop/frontend-pod-is-running.png)\\n\\n1. Go to `http://localhost:9090`: the Guestbook application is running."},{"id":"podman-desktop-release-0.14","metadata":{"permalink":"/blog/podman-desktop-release-0.14","source":"@site/blog/2023-04-14-release-0.14.md","title":"Release Notes - Podman Desktop 0.14","description":"Podman Desktop 0.14 has been released!","date":"2023-04-14T00:00:00.000Z","formattedDate":"April 14, 2023","tags":[{"label":"podman-desktop","permalink":"/blog/tags/podman-desktop"},{"label":"release","permalink":"/blog/tags/release"},{"label":"kubernetes","permalink":"/blog/tags/kubernetes"},{"label":"kind","permalink":"/blog/tags/kind"}],"readingTime":4.025,"hasTruncateMarker":true,"authors":[{"name":"Tim deBoer","title":"Architect","url":"https://github.com/deboer-tim","imageURL":"https://github.com/deboer-tim.png","key":"deboer"}],"frontMatter":{"title":"Release Notes - Podman Desktop 0.14","description":"Podman Desktop 0.14 has been released!","slug":"podman-desktop-release-0.14","authors":["deboer"],"tags":["podman-desktop","release","kubernetes","kind"],"hide_table_of_contents":false},"unlisted":false,"prevItem":{"title":"Setting up and running a Kubernetes cluster locally with Podman Desktop","permalink":"/blog/running-a-local-kubernetes-cluster-with-podman-desktop"},"nextItem":{"title":"Release Notes - Podman Desktop 0.13","permalink":"/blog/podman-desktop-release-0.13"}},"content":"import ReactPlayer from \'react-player\'\\n\\nPodman Desktop 0.14 - Our Kind-est release yet!\\n\\nWe have been working on a Kind extension for a while now, and decided it is time to promote it\\ninto a release just in time for KubeCon and CloudNativeCon Europe!\\n\\nWe\'re especially excited about releasing Kind because it finally shows the full purpose\\nof Podman Desktop: not just local container engines, but Kubernetes too. More importantly,\\nproviding tools that allow you to manage both environments and seamlessly move between them.\\n\\nSome of these features were available in development mode over the last few releases,\\nbut since they are now in the release build, we will do a full roundup and talk about\\nall the Kind features.\\n\\n\x3c!--Main Features--\x3e\\n\\n- **Kind Installation**: Install Kind from the status bar\\n- **Manage Kind Clusters**: Create and manage Kind clusters from ** Settings > Resources**\\n- **Using Kind**: Deploying YAML and sharing images to a cluster\\n- **Kind Ingress**: Install a Contour ingress controller\\n- **UX and UI Improvements**: Updated preferences and telemetry prompt\\n\\nPodman Desktop 0.14 is now available. [Click here to download it](/downloads)!\\n\\n![Podman-desktop-0-14-hero](img/podman-desktop-release-0.14/podman-desktop-release-0.14.png)\\n\\n\x3c!--truncate--\x3e\\n\\n---\\n\\n## Release details\\n\\n### Kind Installation\\n\\nGet Kind up and running in seconds! The Kind extension is now bundled as part of Podman Desktop\\n[1421](https://github.com/containers/podman-desktop/issues/1421)\\nand allows you to easily [install Kind directly from the status bar](/docs/kind/installing)\\n[1257](https://github.com/containers/podman-desktop/issues/1257).\\n\\nThe installed `kind` CLI is available from the system shell [1516](https://github.com/containers/podman-desktop/issues/1516),\\nallowing you to open a terminal window to `kind get clusters` or work with other tools.\\n\\n### Manage Kind Clusters\\n\\nOnce Kind is installed (or if you already had it), you can manage your clusters in ** Settings > Resources**.\\nFrom here you can [create Kind clusters](/docs/kind/creating-a-kind-cluster),\\nstart/stop [1953](https://github.com/containers/podman-desktop/issues/1953)\\nor delete [1977](https://github.com/containers/podman-desktop/issues/1977) them.\\n\\n![kind-clusters](img/podman-desktop-release-0.14/kind-clusters.png)\\n\\nThe Kind control plane runs as a container. You will see this container\\nin the **Container** list and can also start or stop it from there.\\n\\n### Using Kind\\n\\nNow that you have Kind installed and running, what can you do with it?\\nIf you like terminals, you can always open one up and use the Kind CLI to\\n[interact with your cluster](https://kind.sigs.k8s.io/docs/user/quick-start/#interacting-with-your-cluster).\\n\\nWithin Podman Desktop we have started with two ways to interact with the cluster.\\nThe first is the ability to play local YAML files on your Kind (or any other Kubernetes!) cluster [1261](https://github.com/containers/podman-desktop/issues/1261). This allows you to take existing Kubernetes YAML definitions -\\nyour deployments, services, or other objects - and deploy it to the cluster.\\n\\n\\n\\nAs you deploy pods, they will automatically appear in the list of **Pods** [1263](https://github.com/containers/podman-desktop/issues/1263), allowing you to start, stop, and interact them just like pods running on Podman.\\n\\nOne of the most common uses is to deploy a container that you have been running on Podman, and this will fail\\nif the image is not available in Kind. To solve this we have made it easy to push images from\\nPodman to Kind [1448](https://github.com/containers/podman-desktop/issues/1448).\\n\\n![push-image-kind](img/podman-desktop-release-0.14/push-image-kind.png)\\n\\n### Kind Ingress\\n\\nIf you deploy a pod to Kind, you are also going to want to reach it! To do this you will need to install a load balancer or\\ningress controller so that the pod is accessible from outside the cluster. We made it easy to install the Contour ingress\\ncontroller while creating a Kind cluster [1675](https://github.com/containers/podman-desktop/issues/1675),\\nso if you created your cluster with Podman Desktop it is already there!\\n\\n![kind-ingress](img/podman-desktop-release-0.14/kind-ingress.png)\\n\\nWe have several other Kind and Kubernetes features planned to expand the supported scenarios, but hopefully this\\nmakes it easy to get started with Kind and shows where we\'re headed. As always, feedback is appreciated!\\n\\n### UI and UX improvements\\n\\n#### Updated Preferences\\n\\nThe ** Settings > Preferences** page has been updated with a new design [1913](https://github.com/containers/podman-desktop/pull/1913),\\nmaking it easier to see and change preferences. Changes are live, no more Update button.\\n\\n![preferences](https://user-images.githubusercontent.com/49404737/229498507-e754b55c-dcbd-486d-9ee3-a1fe3bed7271.gif)\\n\\n#### Telemetry Prompt\\n\\nThe prompt to enable or disable telemetry has been moved from its own dialog into the **Welcome** screen.\\n[1927](https://github.com/containers/podman-desktop/pull/1927)\\nThis is more usable, one less prompt, and solves a window-layering issue for some users!\\n\\n![telemetry prompt](https://user-images.githubusercontent.com/19958075/229577331-365a9a01-0426-4482-a95d-f5dfe39af90a.png)\\n\\n---\\n\\n## Other notable enhancements\\n\\n- Extension support for opening an external URL [2028](https://github.com/containers/podman-desktop/pull/2028) and\\n accessing the clipboard [2023](https://github.com/containers/podman-desktop/pull/2023)\\n\\n---\\n\\n## Documentation\\n\\nNaturally, we have a section in the documentation just for [Kind](https://podman-desktop.io/docs/kind).\\n\\n---\\n\\n## Notable bug fixes\\n\\n- Avoid a dialog box if unable to check for updates [2062](https://github.com/containers/podman-desktop/pull/2062)\\n- Unable to get to the Dashboard if Kind (or Kubernetes) cluster was not running [2052](https://github.com/containers/podman-desktop/issues/2052)\\n\\n---\\n\\n## Final notes\\n\\nThe complete list of issues fixed in this release is available [here](https://github.com/containers/podman-desktop/issues?q=is%3Aclosed+milestone%3A0.14.0).\\n\\nGet the latest release from the [Downloads](/downloads) section of the website and boost your development journey with Podman Desktop. Additionally, visit the [GitHub repository](https://github.com/containers/podman-desktop) and see how you can help us make Podman Desktop better."},{"id":"podman-desktop-release-0.13","metadata":{"permalink":"/blog/podman-desktop-release-0.13","source":"@site/blog/2023-03-29-release-0.13.md","title":"Release Notes - Podman Desktop 0.13","description":"Podman Desktop 0.13 has been released!","date":"2023-03-29T00:00:00.000Z","formattedDate":"March 29, 2023","tags":[{"label":"podman-desktop","permalink":"/blog/tags/podman-desktop"},{"label":"release","permalink":"/blog/tags/release"},{"label":"kubernetes","permalink":"/blog/tags/kubernetes"},{"label":"compose","permalink":"/blog/tags/compose"}],"readingTime":3.155,"hasTruncateMarker":true,"authors":[{"name":"Tim deBoer","title":"Architect","url":"https://github.com/deboer-tim","imageURL":"https://github.com/deboer-tim.png","key":"deboer"}],"frontMatter":{"title":"Release Notes - Podman Desktop 0.13","description":"Podman Desktop 0.13 has been released!","slug":"podman-desktop-release-0.13","authors":["deboer"],"tags":["podman-desktop","release","kubernetes","compose"],"hide_table_of_contents":false},"unlisted":false,"prevItem":{"title":"Release Notes - Podman Desktop 0.14","permalink":"/blog/podman-desktop-release-0.14"},"nextItem":{"title":"5 things to know about Podman Desktop for a Docker user","permalink":"/blog/5-things-to-know-for-a-docker-user"}},"content":"import ReactPlayer from \'react-player\'\\n\\nThis release note covers Podman Desktop 0.13 release changes.\\n\\n\x3c!--Main Features--\x3e\\n\\n- **Podman Version**: Podman 4.4.4 now included in Windows and Mac installers.\\n- **Compose**: Support for installing Docker Compose.\\n- **Extensions**: Improved extension support for Podman Desktop with additional capabilities.\\n- **UX and UI Improvements**: Welcome page, task manager, resources, and update alerts.\\n\\nPodman Desktop 0.13 is now available. [Click here to download it](/downloads)!\\n\\n![Podman-desktop-0-13-hero](img/podman-desktop-release-0.13/podman-desktop-release-0.13.png)\\n\\n\x3c!--truncate--\x3e\\n\\n---\\n\\n## Release details\\n\\n### Update to Podman v4.4.4\\n\\nPodman Desktop 0.13 embeds [Podman 4.4.4](https://github.com/containers/podman/releases/tag/v4.4.4) in\\nWindows and macOS installers [#1456](https://github.com/containers/podman-desktop/pull/1456).\\n\\n### Compose support\\n\\nYou can install Docker Compose from the Podman Desktop UI [#1578](https://github.com/containers/podman-desktop/pull/1578). This will allow you use Compose workflows using Podman.\\n\\n### Extensions\\n\\nTo make it easier to extend Podman Desktop we have:\\n\\n- Published the [Podman Desktop Extension API](https://www.npmjs.com/package/@podman-desktop/api) to npmjs [#1727](https://github.com/containers/podman-desktop/pull/1727)\\n- Documented [how to create, publish, and install your own extensions](https://podman-desktop.io/docs/extensions)\\n- Expanded the API for `QuickPickInput` [#1839](https://github.com/containers/podman-desktop/pull/1839)\\n\\n### UI and UX improvements\\n\\n#### Welcome page [#1726](https://github.com/containers/podman-desktop/pull/1726)\\n\\nThe first time every user starts Podman Desktop, they will see a welcome page:\\n\\n![welcome-page](https://user-images.githubusercontent.com/19958075/225682776-e016ba31-5bb9-41d5-87ed-f93caeb3fb84.png)\\n\\nNote 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.\\nOver time, this page will be expanded to help with initial setup and configuration.\\n\\n#### New Task Manager [#1724](https://github.com/containers/podman-desktop/pull/1724)\\n\\nA 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](https://github.com/containers/podman-desktop/pull/1725) and Podman machine [#1742](https://github.com/containers/podman-desktop/pull/1742) are using the task manager.\\n\\n![task-manager](img/podman-desktop-release-0.13/task-manager.png)\\n\\n#### Updated Resources Settings [#1582](https://github.com/containers/podman-desktop/pull/1582)\\n\\nThe ** Settings > Resources** page has been updated with a new design, making it easier to see and control your providers from a single place.\\n\\n![resources](https://user-images.githubusercontent.com/49404737/221908815-595715fe-4c95-4087-89e0-45e5544ed5c9.gif)\\n\\nThe other settings pages have been updated for consistency with this new design.\\n\\n#### Update Alerts [#1827](https://github.com/containers/podman-desktop/pull/1827)\\n\\nA new alert button will appear in the status bar when future updates are available.\\n\\n\\n\\n#### Prune buttons [#1481](https://github.com/containers/podman-desktop/pull/1481), [#1482](https://github.com/containers/podman-desktop/pull/1482), [#1484](https://github.com/containers/podman-desktop/pull/1484)\\n\\nWe\'ve added buttons to prune unused volumes [#1481](https://github.com/containers/podman-desktop/pull/1481), images [#1482](https://github.com/containers/podman-desktop/pull/1482) and pods [#1484](https://github.com/containers/podman-desktop/pull/1484).\\n\\n![prune-image](img/podman-desktop-release-0.13/prune-image.png)\\n\\n---\\n\\n## Other notable enhancements\\n\\n- Kubernetes pods are now shown in the Pods view [#1312](https://github.com/containers/podman-desktop/pull/1312)\\n- Easy button to fix Docker compatibility mode on macOS [#1697](https://github.com/containers/podman-desktop/pull/1697)\\n- Display extension icons [#1058](https://github.com/containers/podman-desktop/pull/1058)\\n- API to cancel long running tasks [#1777](https://github.com/containers/podman-desktop/pull/1777)\\n\\n---\\n\\n## Documentation\\n\\nThe documentation has new content:\\n\\n- [How to create, publish, and install your own Podman Desktop extensions](https://podman-desktop.io/docs/extensions)\\n- [Using Compose](https://podman-desktop.io/docs/compose/podman-compose)\\n- [Restarting Kind](https://podman-desktop.io/docs/kind)\\n\\n---\\n\\n## Notable bug fixes\\n\\n- Periodically check and refresh Podman connection on Windows and Mac [#1662](https://github.com/containers/podman-desktop/pull/1662)\\n- Fix inconsistent Log view behaviour [#1710](https://github.com/containers/podman-desktop/pull/1710)\\n- Don\'t create route for regular Kubernetes clusters [#1707](https://github.com/containers/podman-desktop/pull/1707)\\n- Fix copy button on empty screen [#1804](https://github.com/containers/podman-desktop/pull/1804)\\n- Register extension tray items correctly [#1778](https://github.com/containers/podman-desktop/pull/1778) and handle updates [#1800](https://github.com/containers/podman-desktop/pull/1800)\\n\\n---\\n\\n## Community thank you\\n\\n\ud83c\udf89 We\u2019d like to say a big thank you to everyone who helped to make Podman Desktop 0.13 even better:\\n\\n- [`Tony Soloveyv`](https://github.com/Tony-Sol) in [#1605 - Fix directories inconsistency in `~/.local/share/`](https://github.com/containers/podman-desktop/pull/1605)\\n- [`Oleg`](https://github.com/RobotSail) in [#1567 - Check for Flatpak when calling command from exec](https://github.com/containers/podman-desktop/pull/1567)\\n- [`Christoph Blecker`](https://github.com/cblecker) in [#1556 - Fix: Hide dock icon on macOS if starting minimized](https://github.com/containers/podman-desktop/pull/1556)\\n- [`Paul Wright`](https://github.com/pwright) in [#1604 - Docs: correct syntax of kind doc](https://github.com/containers/podman-desktop/pull/1604)\\n- [`Denis Golovin`](https://github.com/dgolovin) in [#1790 - Feat: add EventEmitter class to extension API](https://github.com/containers/podman-desktop/pull/1790)\\n- [`Christophe Fergeau`](https://github.com/cfergeau) in [#1642 - Fix: Pod list \\"an pod\\" typing error](https://github.com/containers/podman-desktop/pull/1642)\\n\\n## Final notes\\n\\nThe complete list of issues fixed in this release is available [here](https://github.com/containers/podman-desktop/issues?q=is%3Aclosed+milestone%3A0.13.0).\\n\\nGet the latest release from the [Downloads](/downloads) section of the website and boost your development journey with Podman Desktop. Additionally, visit the [GitHub repository](https://github.com/containers/podman-desktop) and see how you can help us make Podman Desktop better."},{"id":"5-things-to-know-for-a-docker-user","metadata":{"permalink":"/blog/5-things-to-know-for-a-docker-user","source":"@site/blog/2023-03-24-5-things-to-know-for-a-docker-user.md","title":"5 things to know about Podman Desktop for a Docker user","description":"Important things to know when switching from Docker Desktop to Podman Desktop","date":"2023-03-24T00:00:00.000Z","formattedDate":"March 24, 2023","tags":[{"label":"podman-desktop","permalink":"/blog/tags/podman-desktop"},{"label":"docker","permalink":"/blog/tags/docker"},{"label":"migrating","permalink":"/blog/tags/migrating"}],"readingTime":4.285,"hasTruncateMarker":true,"authors":[{"name":"Florent Benoit","title":"Principal Software Engineer","url":"https://github.com/benoitf","imageURL":"https://github.com/benoitf.png","key":"benoitf"}],"frontMatter":{"title":"5 things to know about Podman Desktop for a Docker user","description":"Important things to know when switching from Docker Desktop to Podman Desktop","slug":"5-things-to-know-for-a-docker-user","authors":["benoitf"],"tags":["podman-desktop","docker","migrating"],"hide_table_of_contents":false},"unlisted":false,"prevItem":{"title":"Release Notes - Podman Desktop 0.13","permalink":"/blog/podman-desktop-release-0.13"},"nextItem":{"title":"Release Notes - Podman Desktop 0.12","permalink":"/blog/podman-desktop-release-0.12"}},"content":"The 5 things to know being a Docker user by using Podman Desktop:\\n\\n- **Use a single UI**: Podman Desktop works with several container engines, including Docker.\\n- The **compatibility mode**: How to ensure tools are working with Podman instead of Docker.\\n- **Compose** support: How to work with Compose files and Podman.\\n- **Kubernetes** support: How to use Kubernetes with Podman.\\n- **Security**: Use `rootless` mode or containers without root privileges.\\n\\n![5-things-to-know-for-a-docker-user-hero](img/5-things-to-know-for-a-docker-user/5-things-to-know-for-a-docker-user-hero.png)\\n\\n\x3c!--truncate--\x3e\\n\\n---\\n\\n## Use Podman Desktop to interact with containers running in Docker\\n\\nDocker 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.\\n\\nPodman 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.\\n\\nWhen 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.\\n\\n![Many container engines at the same time](img/5-things-to-know-for-a-docker-user/multiple-container-engines.png)\\n\\n## Docker compatibility mode\\n\\nUsing 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.\\n\\n### Socket file compatibility\\n\\nThe socket compatibility mode is a feature of Podman that allows to bind the Podman socket under the Docker socket path.\\n\\nOn 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.\\n\\nThat is not an issue because you can enable it by [invoking a CLI tool](https://podman-desktop.io/docs/migrating-from-docker/using-podman-mac-helper) that will setup the compatibility mode.\\n\\nFor example if you use [`TestContainers`](https://www.testcontainers.org/) in your Java project, you can use the compatibility mode to ensure that the tool will use Podman instead of Docker.\\n\\n### CLI compatibility\\n\\nIf 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.\\n\\nIf 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.\\n\\nIf you do not have the `docker` CLI installed on your computer, you can [Create a script](https://podman-desktop.io/docs/migrating-from-docker/emulating-docker-cli-with-podman) called `docker` that will call the `podman` CLI\\n\\n**_NOTE:_** creating a shell prompt alias, for example `alias docker=podman`, will not work inside scripts that you call.\\n\\n## Compose\\n\\nAs a user of Docker, you might use `docker compose` (or `docker-compose`) to run some of your applications.\\n\\nFor now Podman does not include a `Compose` support directly in the CLI with a command `podman compose`.\\n\\n`Compose` can work with the Podman socket.\\n\\nBased on the compatibility mode (see [section about Docker compatibility mode](#docker-compatibility-mode)):\\n\\n- Enabled: you can use the `compose` binary to run your applications.\\n- Disabled: you need to [export the environment variable DOCKER_HOST](https://podman-desktop.io/docs/migrating-from-docker/using-the-docker_host-environment-variable) before running compose.\\n\\nYou can now use the `compose` binary to run your applications and it will use Podman engine.\\n\\nPodman Desktop has a `compose` extension that can fetch `compose` binary if not already available on the filesystem.\\n\\nPodman Desktop UI displays the containers created by `Compose` are in the same group.\\n\\n![Compose support in the UI](img/5-things-to-know-for-a-docker-user/compose-containers-in-ui.png)\\n\\n## Kubernetes\\n\\nIt is possible to start a Kubernetes cluster with Docker.\\n\\nPodman supports directly a subset of Kubernetes resources that you can use with `.yaml` files.\\n\\nFor 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.\\n\\n![Play Kubernetes YAML](img/5-things-to-know-for-a-docker-user/play-kubernetes-yaml.png)\\n\\nIt 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.\\n\\n![Kubernetes generate](img/5-things-to-know-for-a-docker-user/kube-generate.png)\\n\\nPodman 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.\\n\\n![Pods in the UI](img/5-things-to-know-for-a-docker-user/pods-in-ui.png)\\n\\n![Containers from pod](img/5-things-to-know-for-a-docker-user/containers-from-pod.png)\\n\\nAn experimental `kind` extension is bringing the creation of full-blown Kubernetes cluster with Podman.\\n\\n## Rootless mode\\n\\nOne 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.\\n\\nIt means that for example, starting a container with a port < 1024 will not work. You need to use a port > 1024.\\n\\nIf 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.\\n\\nThe command is `podman machine set --rootful` to enable the execution with root privileges or `podman machine set --rootful=false` to switch back to rootless mode."},{"id":"podman-desktop-release-0.12","metadata":{"permalink":"/blog/podman-desktop-release-0.12","source":"@site/blog/2023-02-15-release-0.12.md","title":"Release Notes - Podman Desktop 0.12","description":"Podman Desktop 0.12 has been released!","date":"2023-02-15T00:00:00.000Z","formattedDate":"February 15, 2023","tags":[{"label":"podman-desktop","permalink":"/blog/tags/podman-desktop"},{"label":"release","permalink":"/blog/tags/release"},{"label":"kubernetes","permalink":"/blog/tags/kubernetes"}],"readingTime":4.505,"hasTruncateMarker":true,"authors":[{"name":"Stevan Le Meur","title":"Product Manager","url":"https://github.com/slemeur","imageURL":"https://github.com/slemeur.png","key":"slemeur"}],"frontMatter":{"title":"Release Notes - Podman Desktop 0.12","description":"Podman Desktop 0.12 has been released!","slug":"podman-desktop-release-0.12","authors":["slemeur"],"tags":["podman-desktop","release","kubernetes"],"hide_table_of_contents":false},"unlisted":false,"prevItem":{"title":"5 things to know about Podman Desktop for a Docker user","permalink":"/blog/5-things-to-know-for-a-docker-user"},"nextItem":{"title":"Release Notes - Podman Desktop 0.11","permalink":"/blog/podman-desktop-release-0.11"}},"content":"import ReactPlayer from \'react-player\'\\n\\nThis release note covers Podman Desktop 0.12 release changes.\\n\\n\x3c!--Main Features--\x3e\\n\\n- **Podman Version**: Podman 4.4.1 now included in Windows and Mac installers.\\n- **Containers Configuration**: Configure port mappings for an image without exported ports.\\n- **Windows Home Support**: Podman Desktop now supports Windows Home Edition.\\n- **Start minimized**: Option to start Podman Desktop minimized to system tray.\\n- **UX and UI Improvements**: Consistent actions, placeholder for logs, unified icons and others.\\n\\nPodman Desktop 0.12 is now available. [Click here to download it](/downloads)!\\n\\n![podman-desktop-0-12-hero](img/podman-desktop-release-0.12/podman-desktop-release-0.12.png)\\n\\n\x3c!--truncate--\x3e\\n\\n---\\n\\n## Release Details\\n\\n### Update to Podman v4.4.1 [#1456](https://github.com/containers/podman-desktop/pull/1456)\\n\\nPodman Desktop 0.12 embeds [Podman 4.4.1](https://github.com/containers/podman/releases/tag/v4.4.1) in Windows and macOS installers. Make sure to upgrade to benefit from the latest Podman features and bug fixes.\\n\\n### Configuring port mappings when an image has no exported port [#1265](https://github.com/containers/podman-desktop/pull/1265)\\n\\nWith 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.\\n\\n![port-mapping](https://user-images.githubusercontent.com/49404737/215112797-86dcf3f0-121a-487e-a71f-ad41e91f93da.gif)\\n\\n### Installing Podman Desktop on Windows Home Edition [#1268](https://github.com/containers/podman-desktop/pull/1268)\\n\\nPodman 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.\\n\\n![install-windows-home-edition-2](https://user-images.githubusercontent.com/436777/215121429-7c757aaa-a838-43db-98a2-78ad368f407e.png)\\n\\n### Option to automatically minimize Podman Desktop on login [#1374](https://github.com/containers/podman-desktop/pull/1374)\\n\\nPodman 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.\\n\\n- Go to ** Settings > Preferences > Login: Minimize** to activate the option.\\n\\n![minimize-on-login](https://user-images.githubusercontent.com/6422176/216651424-bcf756fd-7554-4b24-a838-e3e2f798fe6e.png)\\n\\n### UI and UX Improvements\\n\\n#### Improved actions consistency [#1225](https://github.com/containers/podman-desktop/pull/1225)\\n\\nActions displayed in the list pages for Images and Containers have been reviewed and made consistent between other pages.\\n\\n![action-consistency-1](https://user-images.githubusercontent.com/19958075/214104678-2d4148d7-484e-41f9-9da9-aecee328ae2b.png)\\n\\nActions displayed in the header of the container\'s details page have been improved so that the actions are always displayed in the same order.\\n\\n![action-consistency-2](https://user-images.githubusercontent.com/19958075/214104663-64fa0601-bb79-49bf-8226-6a78a88d3622.png)\\n\\n#### Consistent status icons for Pods, Containers, Images and Volumes [#1326](https://github.com/containers/podman-desktop/pull/1326), [#1377](https://github.com/containers/podman-desktop/pull/1377), [#1459](https://github.com/containers/podman-desktop/pull/1459) and [#1245](https://github.com/containers/podman-desktop/pull/1245)\\n\\nThe status icons for Pods, Containers, Images, and Volumes have been unified and use consistent states.\\n\\n![pods-status-icon](https://user-images.githubusercontent.com/19958075/216671859-bdd8dca4-56b7-40a8-961a-dcb6e01be61e.png)\\n\\nIcons in empty screens have been updated to use the same consistent SVG icon as the status icons.\\n\\n![empty-screen-2](https://user-images.githubusercontent.com/436777/214577726-f4cfde7b-017a-499d-a2a9-e50d455ffaf0.png)\\n\\n#### Placeholder when logs for containers are being fetched [#1353](https://github.com/containers/podman-desktop/pull/1353)\\n\\nA placeholder is now displayed when logs are being fetched.\\n![placeholder-loading-logs](https://user-images.githubusercontent.com/49404737/216952505-899308ae-183e-487a-b6e5-28832a0b6452.gif)\\n\\n#### Fixed alignment in badges from the navigation sidebar [#1357](https://github.com/containers/podman-desktop/pull/1357)\\n\\nBadges in the sidebar are now aligned with the title of the section.\\n\\n![alignement-badges](https://user-images.githubusercontent.com/49404737/216336502-2a34dea3-fd41-4184-8cfe-9226d70da070.png)\\n\\n#### Enable/disable open browser action based on container state [#1395](https://github.com/containers/podman-desktop/pull/1395) and [#1397](https://github.com/containers/podman-desktop/pull/1397)\\n\\nThe 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.\\n\\n![enable-disable-container-actions](https://user-images.githubusercontent.com/49404737/217284414-1bdc820b-30a8-485e-b0f9-485229026696.gif)\\n\\n---\\n\\n## Other Notable Enhancements\\n\\n- Display extension icons [#1058](https://github.com/containers/podman-desktop/pull/1058)\\n- Solid Icons [#1267](https://github.com/containers/podman-desktop/pull/1276)\\n- Differentiate icons compared to status icons [#1268](https://github.com/containers/podman-desktop/pull/1298)\\n- Refactors window initializing [#1309](https://github.com/containers/podman-desktop/pull/1309)\\n- Change window creation background color to dark [#1310](https://github.com/containers/podman-desktop/pull/1310)\\n- Use Podman `machine inspect` to read the address to connect to the Podman machine [#1364](https://github.com/containers/podman-desktop/pull/1364)\\n- Update the editor content when the pod name changes, and disable the deploy button when empty [#1403](https://github.com/containers/podman-desktop/pull/1403)\\n- Ability to manually set color of tray icon for Windows and Linux [#1243](https://github.com/containers/podman-desktop/pull/1243)\\n- Better UI feedback when starting pods [#1242](https://github.com/containers/podman-desktop/pull/1242)\\n\\n---\\n\\n## Documentation\\n\\nThe documentation had many editorial reviews, and new content.\\n\\n- [Link to simple WSL2 installation instructions](/docs/installation/windows-install)\\n- [Refresh Windows Installation](/docs/installation/windows-install)\\n- [Revamped installation introduction](/docs/installation)\\n- [Reorganized Linux installation](/docs/installation/linux-install)\\n- [Installing Podman with OpenShift Local](/docs/podman/installing-podman-with-openshift-local-on-windows)\\n- [Installing Podman Desktop on Windows in a restricted environment](/docs/installation/windows-install/installing-podman-desktop-and-podman-in-a-restricted-environment)\\n- [Fixed documentation on `podman-mac-helper` setup](/docs/migrating-from-docker/using-podman-mac-helper)\\n\\n---\\n\\n## Notable bug fixes\\n\\n- Fixed handling path with spaces on Windows when installing Podman [#1270](https://github.com/containers/podman-desktop/pull/1270)\\n- Removed padding from SVG icons [#1253](https://github.com/containers/podman-desktop/pull/1253)\\n- Website: fixed download links for Windows and macOS binaries [#1255](https://github.com/containers/podman-desktop/pull/1255)\\n- Fixed prettier commands on Windows [#1266](https://github.com/containers/podman-desktop/pull/1267)\\n- Fixed new xterm instance spawn when clicking the logs route [#1344](https://github.com/containers/podman-desktop/pull/1344)\\n- Fixed need to wait that telemetry has been initialized before proceeding [#1373](https://github.com/containers/podman-desktop/pull/1373)\\n- Fixed new xterm instance spawn when clicking the logs route in pod details[#1393](https://github.com/containers/podman-desktop/pull/1393)\\n- Fixed stop spinner if image cannot be retrieved [#1394](https://github.com/containers/podman-desktop/pull/1394)\\n- Fixed escape command with quotes only for Windows [#1462](https://github.com/containers/podman-desktop/pull/1462)\\n- Fixed random CRC status change [#1420](https://github.com/containers/podman-desktop/pull/1420)\\n\\n---\\n\\n## Community Thank You\\n\\n\ud83c\udf89 We\u2019d like to say a big thank you to everyone who helped to make Podman Desktop 0.12 even better:\\n\\n- [Philipp Wagner](https://github.com/imphil) in [#1274 - Link to simple WSL2 installation instructions](https://github.com/containers/podman-desktop/pull/1274)\\n- [Arthur S](https://github.com/arixmkii) in [#1364 - Get podman machine socketPath from podman machine inspect first](https://github.com/containers/podman-desktop/pull/1364)\\n- [Mitch West](https://github.com/Mitch9378) in [#1428 - Fix old documentation for \'podman-mac-helper setup\'](https://github.com/containers/podman-desktop/pull/1428)\\n\\n## Final Notes\\n\\nThe complete list of issues fixed in this release is available [here](https://github.com/containers/podman-desktop/issues?q=is%3Aclosed+milestone%3A0.12.0).\\n\\nGet the latest release from the [Downloads](/downloads) section of the website and boost your development journey with Podman Desktop. Additionally, visit the [GitHub repository](https://github.com/containers/podman-desktop) and see how you can help us make Podman Desktop better."},{"id":"podman-desktop-release-0.11","metadata":{"permalink":"/blog/podman-desktop-release-0.11","source":"@site/blog/2023-01-18-release-0.11.md","title":"Release Notes - Podman Desktop 0.11","description":"Podman Desktop 0.11 has been released!","date":"2023-01-18T00:00:00.000Z","formattedDate":"January 18, 2023","tags":[{"label":"podman-desktop","permalink":"/blog/tags/podman-desktop"},{"label":"release","permalink":"/blog/tags/release"},{"label":"kubernetes","permalink":"/blog/tags/kubernetes"}],"readingTime":9.43,"hasTruncateMarker":true,"authors":[{"name":"Stevan Le Meur","title":"Product Manager","url":"https://github.com/slemeur","imageURL":"https://github.com/slemeur.png","key":"slemeur"}],"frontMatter":{"title":"Release Notes - Podman Desktop 0.11","description":"Podman Desktop 0.11 has been released!","slug":"podman-desktop-release-0.11","authors":["slemeur"],"tags":["podman-desktop","release","kubernetes"],"hide_table_of_contents":false},"unlisted":false,"prevItem":{"title":"Release Notes - Podman Desktop 0.12","permalink":"/blog/podman-desktop-release-0.12"},"nextItem":{"title":"Release Notes - Podman Desktop 0.10","permalink":"/blog/podman-desktop-release-0.10"}},"content":"import ReactPlayer from \'react-player\'\\n\\nThis release note covers Podman Desktop 0.11 release changes.\\n\\n- **Air-Gapped Installation**: New all-in-one binaries for air-gapped installation.\\n- **Feedback**: Submit feedback directly from Podman Desktop.\\n- **Docker Compatibility Mode**: Information about the Docker compatibility mode.\\n- **Proxy Setting**: Toggle on/off the proxy setting.\\n- **Deploy to Kubernetes**: Select the namespace to deploy to Kubernetes.\\n- **Registry Configuration**: Simplified registry configuration for well known registries.\\n- **UX/UI Improvements**: View pod\'s container logs, better visual feedback, configurable editor font size, and more.\\n\\nPodman Desktop 0.11 is now available. [Click here to download it](/downloads)!\\n\\n\x3c!--truncate--\x3e\\n\\n---\\n\\n## Release Details\\n\\n### Air-Gapped installation [#1104](https://github.com/containers/podman-desktop/pull/1104) [#1120](https://github.com/containers/podman-desktop/pull/1120)\\n\\nFor users who are not able to connect to the internet, a new all-in-one (airgap) binary that includes the Podman Desktop application and the Podman binaries is now available for both Mac and Windows. When initializing a new Podman machine using all-in-one binaries, it\'ll use the embedded files and not grab them from internet:\\n\\n- on Mac, it embeds the qemu FCOS binaries.\\n- on Windows, it embeds the WSL binary.\\n\\nTo differentiate the air-gapped binaries from the regular ones, you can check the artifactname, they\'re containing \'airgap\' and are bigger.\\nPlease note, that those binaries are available only on releases and not the pre-releases.\\n\\nThere is also an optional way to provide a custom Podman machine image in the create machine form. By providing the path to the image you want, Podman Desktop will create a machine with that image. Leaving the field empty will use the default image (the one included in the binary).\\n\\n\\n\\n### Feedback within Podman Desktop [#1078](https://github.com/containers/podman-desktop/pull/1078)\\n\\nSubmitting feedback on Podman Desktop is getting easier as it is possible directly within the tool. This will help to get more information about the issues you are facing and will help us to improve the tool.\\n\\n\\n\\nPlease feel free to submit any feedback you have, we are looking forward to hearing from you!\\n\\n### Docker compatibility mode [#1047](https://github.com/containers/podman-desktop/pull/1047)\\n\\nThe Docker compatibility mode is a feature that allows to use Podman as a drop-in replacement for Docker. It relies on the Docker socket helper provided with Podman and automatically handle the local setup of Podman path to the Docker socket. Tools like [Testcontainers](https://www.testcontainers.org/) or others are relying on this to communicate to the container engine.\\n\\nIn this new version of Podman Desktop, we are now providing information to the user about the status of this compatibility mode directly on the dashboard page. The way it works is the following:\\n\\n- When Docker is running: the socket is pointing to Docker.\\n- When Podman is starting and Docker is not running: the docker API socket will use Podman.\\n\\nIn case the compatibility mode is not activated, new documentation on how to activate it and how to easily switch between Docker and Podman is available here: [https://podman-desktop.io/docs/migrating-from-docker](https://podman-desktop.io/docs/migrating-from-docker).\\n\\nThis is a warning displayed for Windows users:\\n![windows-docker-compatibility](https://user-images.githubusercontent.com/436777/209305744-9056addd-f122-4f75-9e03-ad27a0109375.png)\\n\\nThis is the warning for Mac users:\\n![mac-docker-compatibility](https://user-images.githubusercontent.com/6422176/207964861-a9c1f72c-89d6-4816-beab-397af4125620.png)\\n\\n### Allow to toggle on/off the proxy setting [#983](https://github.com/containers/podman-desktop/pull/983)\\n\\nIn 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.\\n\\n\\n\\nNote: extensions can read this information and then update the proxy configuration.\\n\\n### Namespace selection for deploy to Kubernetes [#1008](https://github.com/containers/podman-desktop/pull/1008)\\n\\nA 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.\\n\\nIf the user have set `kubectl config set-context --current --namespace=NAMESPACE` it honors that as the chosen value.\\n\\n![deploy-kubernetes-namespace](https://user-images.githubusercontent.com/7339809/206688886-095e4f15-42ae-4a0a-b1c6-ae4b547fcdfb.gif)\\n\\n### Configure Podman binary path [#941](https://github.com/containers/podman-desktop/pull/941)\\n\\nUsers might 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.\\nThis is useful for users who have installed Podman using a package manager and want to use the binary provided by the package manager.\\nSee: [Unable to set custom binary path for Podman on macOS](/docs/troubleshooting/troubleshooting-podman-on-macos#unable-to-set-custom-binary-path-for-podman-on-macos)\\n![custom-path](https://user-images.githubusercontent.com/6422176/204832063-5858065a-2fc3-49de-8d23-3b99b7d10dbf.png)\\n\\n### Provide pre-defined registries [#1201](https://github.com/containers/podman-desktop/pull/1201)\\n\\nThe 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:\\n\\n- Dockerhub\\n- Red Hat Quay\\n- GitHub\\n- IBM Container Registry\\n- Google Container Registry\\n\\n\\n\\n### UI/UX Improvements\\n\\n#### View Pods logs [#1122](https://github.com/containers/podman-desktop/pull/1122)\\n\\nThe 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.\\n\\n![pods-logs](https://user-images.githubusercontent.com/6422176/211024673-eee9bad8-1b0c-4446-b8d1-97a226282c4d.png)\\n\\n#### Improved feedback when clicking on container list action icons [#1150](https://github.com/containers/podman-desktop/pull/1150) [#1161](https://github.com/containers/podman-desktop/pull/1161)\\n\\nWhen 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.\\n\\n\\n\\nFor 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](https://github.com/containers/podman-desktop/pull/1161).\\n\\n\\n\\n#### Allows to change the default font size for the editor [#1160](https://github.com/containers/podman-desktop/pull/1160)\\n\\nAn 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).\\n\\n\\n\\n#### Keep expanded state of pods when refreshing containers [#1042](https://github.com/containers/podman-desktop/pull/1042)\\n\\nWhen 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.\\n\\n\\n\\n#### Click on the Pod name redirects to the Pod details page [#1159](https://github.com/containers/podman-desktop/pull/1159)\\n\\nThe list of containers also displays pods, now clicking on the pod name directly redirects to the Pod details page.\\n\\n\\n\\n#### Improved styles of buttons for actions [#984](https://github.com/containers/podman-desktop/pull/984)\\n\\nThe 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 visible and the icon\'s color is also changing.\\n\\nOn lists:\\n![list-actions](https://user-images.githubusercontent.com/6422176/205979121-b49a0ddf-03bb-4a4d-8d12-bc8d0bd52387.png)\\n\\nOn details pages:\\n![details-actions](https://user-images.githubusercontent.com/6422176/205979123-ea420b17-e834-4029-82eb-22949889eee9.png)\\n\\n#### Improved alignments in pages with lists [#1182](https://github.com/containers/podman-desktop/pull/1182)\\n\\nThe 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.\\n\\n![list-actions](https://user-images.githubusercontent.com/19958075/212712580-096fd090-0beb-40a4-8dc6-b3fdc5e81e35.png)\\n\\n---\\n\\n## Other Notable Enhancements\\n\\n- Statistics area in container details are always shown. ([#1131](https://github.com/containers/podman-desktop/pull/1131))\\n- Add more descriptive wording and more information to extensions. ([#985](https://github.com/containers/podman-desktop/pull/985))\\n- Allow to install on-the fly Podman Desktop extensions using an OCI image. ([#1187](https://github.com/containers/podman-desktop/pull/1187))\\n- Display correctly non-multiplexed stream in logs (when using non interactive mode). ([#1197](https://github.com/containers/podman-desktop/pull/1197))\\n- Font changed from white to gray for non-name sections (creation date, size). ([#1206](https://github.com/containers/podman-desktop/pull/1206))\\n- Add Help/about menu for macOS/Windows/Linux. ([#1207](https://github.com/containers/podman-desktop/pull/1207))\\n\\n---\\n\\n## Documentation\\n\\nComing with this new version of Podman Desktop, the documentation has been getting attention (with number of editorial reviews) and new content have been added.\\n\\nContent for helping users to migrate from Docker to Podman has been added:\\n\\n- [Using the `podman-mac-helper` tool to migrate from Docker to Podman on macOS](https://github.com/containers/podman-desktop/pull/1088)\\n- [better identify podman-mac-helper verification steps](https://github.com/containers/podman-desktop/pull/1129)\\n- [Emulating Docker CLI using Podman to migrate from Docker to Podman](https://github.com/containers/podman-desktop/pull/1143)\\n- [Migrating from Docker section](https://github.com/containers/podman-desktop/pull/1146)\\n- [Verifying that your tools are using Podman](https://github.com/containers/podman-desktop/pull/1152)\\n- [Importing saved containers](https://github.com/containers/podman-desktop/pull/1144)\\n\\nSeveral of other improvements have been made to the documentation and the website:\\n\\n- [Troubleshooting for Apple Silicon and brew x86_64 installs](https://github.com/containers/podman-desktop/pull/962)\\n- [Change text of custom binary location, add docs](https://github.com/containers/podman-desktop/pull/972)\\n- [Silent install option for windows](https://github.com/containers/podman-desktop/pull/974)\\n- [Upgrade to vite v4 and rollup v3](https://github.com/containers/podman-desktop/pull/1079)\\n- [Refreshing documentation on installing on Linux](https://github.com/containers/podman-desktop/pull/1118)\\n- [Identify the shell sessions in Installing on Linux](https://github.com/containers/podman-desktop/pull/1130)\\n- [Website: the linux binary is not a source, it should be promoted as a binary](https://github.com/containers/podman-desktop/pull/1133)\\n- [Introducing tabs for operatings systems and container engines](https://github.com/containers/podman-desktop/pull/1162)\\n- [website: In the landing page, update plugins and container engines lists](https://github.com/containers/podman-desktop/pull/1165)\\n- [Document where code is located within Podman Desktop](https://github.com/containers/podman-desktop/pull/1163)\\n- [(extension-api): Documentation on how to write an extension and use the api](https://github.com/containers/podman-desktop/pull/1172)\\n\\n---\\n\\n## Notable bug fixes\\n\\n- Update to v0.3.2 Docker Desktop API for extensions - [#1070](https://github.com/containers/podman-desktop/pull/1070)\\n- Updated link to the Matrix room - [#1076](https://github.com/containers/podman-desktop/pull/1076)\\n- Report error when container name already exists - [#1142](https://github.com/containers/podman-desktop/pull/1142)\\n- Fixed connectivity to the Podman machine when the generated socket length is greater than 104 characters in MacOS - [#1145](https://github.com/containers/podman-desktop/pull/1145)\\n- Do not use long calls for external clients - [#1151](https://github.com/containers/podman-desktop/pull/1151)\\n- Invalid name/tag for images with registries using a different port - [#1127](https://github.com/containers/podman-desktop/pull/1127)\\n- Invalid badge count for images when two images have the same tag - [#1124](https://github.com/containers/podman-desktop/pull/1124)\\n- Fixed detection of WSL2 - [#981](https://github.com/containers/podman-desktop/pull/981)\\n- Handle invalid kubeconfig files instead of crashing - [#953](https://github.com/containers/podman-desktop/pull/953)\\n- Removed redundant actions from details pages - [#1200](https://github.com/containers/podman-desktop/pull/1200)\\n- Fixed registry URL not aligned with header - [#1205](https://github.com/containers/podman-desktop/pull/1205)\\n- Moved SVGs to reusable components - [#1211](https://github.com/containers/podman-desktop/pull/1211)\\n\\n**Extensions API has also been improved in this new release:**\\n\\n- (extension-api): Allows to register a factory for kubernetes connection objects (like for container connections) - [#1040](https://github.com/containers/podman-desktop/pull/1040)\\n- (extension-api): List or inspect containers, be notified on events - [#1041](https://github.com/containers/podman-desktop/pull/1041)\\n- (extension-api): Allows to get provider notification - [#1045](https://github.com/containers/podman-desktop/pull/1045)\\n- (dd-extension-api): Implement toast API - [#1154](https://github.com/containers/podman-desktop/pull/1154)\\n- (extension-api): Moved extension properties to preferences - [#948](https://github.com/containers/podman-desktop/pull/948)\\n- (dd-extension-api): Added open dev console on dd webview in development mode - [#1071](https://github.com/containers/podman-desktop/pull/1071)\\n- (extension-api): Added notes on extension and frameworks/tooling of Podman Desktop - [#1166](https://github.com/containers/podman-desktop/pull/1166)\\n- (extension-api): Documentation on how to write an extension and use the api - [#1172](https://github.com/containers/podman-desktop/pull/1172)\\n- (dd-extension-api): DD extensions should see only minimal information on containers - [#1191](https://github.com/containers/podman-desktop/pull/1191)\\n\\n---\\n\\n## Community Thank You\\n\\n\ud83c\udf89 We\u2019d like to say a big thank you to everyone who helped to make Podman Desktop 0.11 even better:\\n\\n- [Emmanuel Bernard](https://github.com/emmanuelbernard) in [#962 - Troubleshooting for Apple Silicon](https://github.com/containers/podman-desktop/pull/962)\\n- [Michael Prankl](https://github.com/eidottermihi) in [#974 - Silent install option for windows](https://github.com/containers/podman-desktop/pull/974)\\n- [Endre Lervik](https://github.com/elervik) in [#1008 - Namespace selection for deploy to kubernetes](https://github.com/containers/podman-desktop/pull/1008)\\n- [Evan FP](https://github.com/evanfpearson) in [#1145 - fixed socket path length error](https://github.com/containers/podman-desktop/pull/1145)\\n- [Lokesh Mandvekar](https://github.com/lsm5) in [#956 - add repository key to package.json](https://github.com/containers/podman-desktop/pull/956)\\n- [Jean Fran\xe7ois Maury](https://github.com/jeffmaury) in [#1194 - Cannot create Kind cluster on Windows](https://github.com/containers/podman-desktop/pull/1194)\\n\\n## Final Notes\\n\\nThe complete list of issues fixed in this release is available [here](https://github.com/containers/podman-desktop/issues?q=is%3Aclosed+milestone%3A0.11.0).\\n\\nGet the latest release from the [Downloads](/downloads) section of the website and boost your development journey with Podman Desktop. Additionally, visit the [GitHub repository](https://github.com/containers/podman-desktop) and see how you can help us make Podman Desktop better."},{"id":"podman-desktop-release-0.10","metadata":{"permalink":"/blog/podman-desktop-release-0.10","source":"@site/blog/2022-12-01-release-0.10-blog.md","title":"Release Notes - Podman Desktop 0.10","description":"Podman Desktop 0.10 has been released! New Create Container Wizard, improved Kubernetes workflows, revamped registries configuration, and more!","date":"2022-12-01T00:00:00.000Z","formattedDate":"December 1, 2022","tags":[{"label":"podman-desktop","permalink":"/blog/tags/podman-desktop"},{"label":"release","permalink":"/blog/tags/release"},{"label":"kubernetes","permalink":"/blog/tags/kubernetes"}],"readingTime":4.115,"hasTruncateMarker":true,"authors":[{"name":"Dev Kumar","title":"Technical PMM Intern","url":"https://github.com/deekay2310","imageURL":"https://github.com/deekay2310.png","key":"deekay2310"}],"frontMatter":{"title":"Release Notes - Podman Desktop 0.10","description":"Podman Desktop 0.10 has been released! New Create Container Wizard, improved Kubernetes workflows, revamped registries configuration, and more!","slug":"podman-desktop-release-0.10","authors":["deekay2310"],"tags":["podman-desktop","release","kubernetes"],"hide_table_of_contents":false},"unlisted":false,"prevItem":{"title":"Release Notes - Podman Desktop 0.11","permalink":"/blog/podman-desktop-release-0.11"},"nextItem":{"title":"Build & run Podman Desktop in a DevContainer","permalink":"/blog/develop-using-devcontainer"}},"content":"This release note covers Podman Desktop 0.10 release changes.\\n\\n- **Containers Configuration**: Container creation wizzard allowing to define environment variables, networking and more configuration options.\\n- **Kubernetes Improvements**: Play Kubernetes YAML, custom Kubeconfig path support, reload of kube context.\\n- **Registries Configuration**: Revamped registries configuration UI.\\n- **Podman Version**: Podman 4.3.1 now included in Windows and Mac installers.\\n- **UX/UI Improvements**: Improved lists, better contrast, and more.\\n\\nPodman Desktop 0.10 is now available. [Click here to download it](/downloads)!\\n\\n\x3c!--truncate--\x3e\\n\\n---\\n\\n## Release Details\\n\\n### New configuration wizzard to create containers ([#773](https://github.com/containers/podman-desktop/pull/773))\\n\\nUntil 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.\\n\\n![new container creation wizard](img/podman-desktop-release-0.10/new_container_creation_wizard.gif)\\n\\n### Kubernetes Capabilities Improvements\\n\\n**Custom Kubeconfig file path ([#780](https://github.com/containers/podman-desktop/pull/780))**\\n\\nKubeconfig 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.\\n\\n![custom kubeconfig file path](img/podman-desktop-release-0.10/custom-kubeconfig.png)\\n\\n**Play Kubernetes YAML from the Pods list ([#739](https://github.com/containers/podman-desktop/pull/739))**\\n\\nPodman 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.\\n\\n![play k8s yaml](img/podman-desktop-release-0.10/play_k8s_yaml.gif)\\n\\n**Kube context automatically reloaded when updated ([#813](https://github.com/containers/podman-desktop/pull/813))**\\n\\nAny 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.\\n\\n### Revamped Container Registries UI ([#446](https://github.com/containers/podman-desktop/issues/446))\\n\\nThe 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.\\n\\n![registries](img/podman-desktop-release-0.10/registries.png)\\n\\n### Update to Podman 4.3.1 ([#913](https://github.com/containers/podman-desktop/issues/913))\\n\\nPodman Desktop 0.10 is now embedding [Podman 4.3.1](https://github.com/containers/podman/releases/tag/v4.3.1) in Windows and macOS installers.\\n\\n### UI/UX Improvements\\n\\n**Improved lists UX ([#877](https://github.com/containers/podman-desktop/pull/877))**\\n\\nTo 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.\\n\\n![kebab menu](img/podman-desktop-release-0.10/kebab-menu.png)\\n\\n**Delay appearance of text in navbar ([#767](https://github.com/containers/podman-desktop/pull/767))**\\n\\nWhen minimizing or expanding the navbar, the text was overlapping for a few second the page. Now it\'s displayed with a fading animation.\\n\\n**Selected state: better text color contrast ([#802](https://github.com/containers/podman-desktop/pull/802))**\\n\\nIn 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.\\n\\n![text color when hover](img/podman-desktop-release-0.10/text-color.gif)\\n\\n**On Linux and Windows, the menu bar is now hidden by default ([#668](https://github.com/containers/podman-desktop/pull/668))**\\n\\nWith 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](https://github.com/dylanmtaylor) for contributing to fix this.\\n\\n**Exit when clicking on the close icon of the dashboard on Linux ([#671](https://github.com/containers/podman-desktop/pull/671))**\\n\\nFor 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](https://github.com/dylanmtaylor) 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.\\n\\n---\\n\\n## Other Notable Enhancements\\n\\n- Rename `Started` into `Age` in Containers list.([#878](https://github.com/containers/podman-desktop/pull/878))\\n- Added domain validation when adding a registry. ([#838](https://github.com/containers/podman-desktop/pull/838))\\n- Provided a consistent behavior with Podman CLI, `podman-machine-default` is now the default name when creating a Podman machine from Podman Desktop. ([#775](https://github.com/containers/podman-desktop/pull/775))\\n\\n---\\n\\n## Notable bug fixes\\n\\n- Fixed error handling when pulling images of Desktop Extensions. ([#782](https://github.com/containers/podman-desktop/pull/782))\\n- Fixed use of the full height of the screen when displaying log in the details of a container. ([#946](https://github.com/containers/podman-desktop/discussions/946))\\n- Fixed First start of Podman Desktop on flatpak was not seeing the podman engine ([#860](https://github.com/containers/podman-desktop/pull/860))\\n\\n## Community Thank You\\n\\n\ud83c\udf89 We\u2019d like to say a big thank you to everyone who helped to make Podman Desktop 0.10 even better:\\n\\n- [Dylan M. Taylor](https://github.com/dylanmtaylor) in [#671](https://github.com/containers/podman-desktop/pull/671)\\n- [Fionn Kelleher](https://github.com/osslate) in [#713](https://github.com/containers/podman-desktop/pull/713)\\n- [Rostislav Svoboda](https://github.com/rsvoboda) in [#737](https://github.com/containers/podman-desktop/pull/737)\\n- [Denis Shemanaev](https://github.com/shemanaev) in [#783](https://github.com/containers/podman-desktop/pull/783)\\n- [Fabrice Flore-Th\xe9bault](https://github.com/themr0c) in [#856](https://github.com/containers/podman-desktop/pull/856)\\n- [Kevin](https://github.com/KevinAtSesam) in [#864](https://github.com/containers/podman-desktop/pull/864)\\n- [@sfrunza13](https://github.com/sfrunza13) in [#872](https://github.com/containers/podman-desktop/pull/872)\\n- [Anjan Nath](https://github.com/anjannath) in [#918](https://github.com/containers/podman-desktop/pull/918)\\n\\n## Final Notes\\n\\nThe complete list of issues fixed in this release is available [here](https://github.com/containers/podman-desktop/issues?q=is%3Aclosed+milestone%3A0.10.0).\\n\\nGet the latest release from the [Downloads](/downloads) section of the website and boost your development journey with Podman Desktop. Additionally, visit the [GitHub repository](https://github.com/containers/podman-desktop) and see how you can help us make Podman Desktop better."},{"id":"develop-using-devcontainer","metadata":{"permalink":"/blog/develop-using-devcontainer","source":"@site/blog/2022-11-17-develop-podman-using-codespaces.md","title":"Build & run Podman Desktop in a DevContainer","description":"Develop Podman Desktop using a DevContainer locally or using GitHub Codespaces.","date":"2022-11-17T00:00:00.000Z","formattedDate":"November 17, 2022","tags":[{"label":"podman-desktop","permalink":"/blog/tags/podman-desktop"},{"label":"devcontainer","permalink":"/blog/tags/devcontainer"},{"label":"codespaces","permalink":"/blog/tags/codespaces"}],"readingTime":6.985,"hasTruncateMarker":true,"authors":[{"name":"Florent Benoit","title":"Principal Software Engineer","url":"https://github.com/benoitf","imageURL":"https://github.com/benoitf.png","key":"benoitf"}],"frontMatter":{"title":"Build & run Podman Desktop in a DevContainer","description":"Develop Podman Desktop using a DevContainer locally or using GitHub Codespaces.","slug":"develop-using-devcontainer","authors":["benoitf"],"tags":["podman-desktop","devcontainer","codespaces"],"hide_table_of_contents":false},"unlisted":false,"prevItem":{"title":"Release Notes - Podman Desktop 0.10","permalink":"/blog/podman-desktop-release-0.10"}},"content":"GitHub [announced last week](https://github.blog/changelog/2022-11-09-codespaces-for-free-and-pro-accounts/) that Codespaces is available for everyone and it includes free minutes.\\n\\nLet see how we can use a [Development Container](https://containers.dev/) 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.\\n\\nThe challenges are to run a desktop tool (Podman Desktop) and running a container engine (Podman) inside this Development Container without using too many memory !\\n\\n\x3c!--truncate--\x3e\\n\\n## Defining image of the container\\n\\nThe first thing is in the choice of the image for the container. It is possible to pick-up a default image and add some features but there is no existing feature for Podman at https://github.com/devcontainers/features/tree/main/src and most of the features are expecting to run on top of Debian/Ubuntu\\n\\nIf you are not interested in how to setup the image, jump to the [next section](#configure-the-devcontainer-using-devcontainerjson).\\n\\nPodman binaries are available quickly after the releases for Fedora. I decided then to use `Fedora 37` as the base image.\\n\\nLet start the Containerfile using:\\n\\n```docker\\nFROM quay.io/fedora/fedora:37\\n```\\n\\nThen I install Node.js 16 from official nodejs.org repository. It\'s easier to switch to the version that we need.\\n\\n```docker\\n# install Node.js + yarn\\nENV NODE_VERSION 16.18.1\\nRUN curl -SLO \\"https://nodejs.org/dist/v$NODE_VERSION/node-v$NODE_VERSION-linux-x64.tar.gz\\" && \\\\\\n tar -xzf \\"node-v$NODE_VERSION-linux-x64.tar.gz\\" -C /usr/local --strip-components=1 && \\\\\\n rm \\"node-v$NODE_VERSION-linux-x64.tar.gz\\" && \\\\\\n npm install -g yarn\\n```\\n\\nNow, all system dependencies used to run an Electron application needs to be installed.\\n\\nPodman is also installed so we can run some containers inside this container.\\n\\nAnd of course, we need to install VNC (I choose [tigervnc](https://tigervnc.org/)) with a light Window Manager ([fluxbox](http://fluxbox.org/)).\\n\\nTo connect to the display of the container, we need to expose VNC over HTML/websocket using [noVNC](https://novnc.com/)\\n\\nxterm is installed to start a terminal from the VNC side.\\n\\n```docker\\nRUN dnf -y update && \\\\\\n yum -y reinstall shadow-utils && \\\\\\n yum install -y git \\\\\\n # dependencies for Podman Desktop\\n nss \\\\\\n atk \\\\\\n at-spi2-atk \\\\\\n cups-libs \\\\\\n gtk3 \\\\\\n # for remote Display\\n fluxbox \\\\\\n tigervnc-server \\\\\\n xorg-x11-fonts-Type1 \\\\\\n novnc \\\\\\n supervisor \\\\\\n xdpyinfo \\\\\\n # for podman\\n podman \\\\\\n fuse-overlayfs --exclude container-selinux \\\\\\n xterm && \\\\\\n rm -rf /var/cache /var/log/dnf* /var/log/yum.*\\n```\\n\\nSupervisord setup the launch of the VNC server and the Window manager\\n\\n```docker\\nCOPY supervisord.conf /etc/supervisord.conf\\n```\\n\\nA custom theme for fluxbox:\\n\\n```docker\\nCOPY fluxbox /usr/share/fluxbox/init\\n```\\n\\nThen we need a special configuration to allow to have Podman working inside the container\\n\\nWe add the `podman-desktop` user with correct range on subuid and subgid when running containers. I used the [tutorial](https://github.com/containers/podman/blob/main/docs/tutorials/rootless_tutorial.md#etcsubuid-and-etcsubgid-configuration).\\n\\n```docker\\nRUN useradd -u 1000 podman-desktop && echo podman-desktop:10000:5000 > /etc/subuid && echo podman-desktop:10000:5000 > /etc/subgid\\n```\\n\\nThen use some default configuration files\\n\\n```docker\\n# initialize conf files\\nADD https://raw.githubusercontent.com/containers/libpod/master/contrib/podmanimage/stable/containers.conf /etc/containers/containers.conf\\nADD https://raw.githubusercontent.com/containers/libpod/master/contrib/podmanimage/stable/podman-containers.conf /home/podman-desktop/.config/containers/containers.conf\\n```\\n\\nand make sure that all permissions are correct following the guide [https://www.redhat.com/sysadmin/podman-inside-container](https://www.redhat.com/sysadmin/podman-inside-container)\\n\\n```docker\\n# set permissions\\nRUN chown podman-desktop:podman-desktop -R /home/podman-desktop && chmod 644 /etc/containers/containers.conf && \\\\\\n mkdir -p /var/lib/shared/overlay-images /var/lib/shared/overlay-layers /var/lib/shared/vfs-images /var/lib/shared/vfs-layers; touch /var/lib/shared/overlay-images/images.lock; touch /var/lib/shared/overlay-layers/layers.lock; touch /var/lib/shared/vfs-images/images.lock; touch /var/lib/shared/vfs-layers/layers.lock && \\\\\\n mkdir -p /run/user/1000 && chown podman-desktop:podman-desktop /run/user/1000\\n```\\n\\nplus define an empty user namespace.\\n\\n```docker\\nENV _CONTAINERS_USERNS_CONFIGURED=\\"\\"\\n```\\n\\nMake sure Podman will create the socket in an expected directory:\\n\\n```docker\\n# socket path for podman\\nENV XDG_RUNTIME_DIR=/run/user/1000\\n```\\n\\nOK ! we have a custom Containerfile providing all the tools to build and run Podman Desktop (using VNC for the display), run Podman and run Electron.\\n\\nThe current file is available at https://github.com/containers/podman-desktop/blob/main/.devcontainer/.parent/Containerfile\\n\\nLet\'s configure the DevContainer.\\n\\n## Configure the DevContainer using devcontainer.json\\n\\nDevContainer definition is stored at `.devcontainer/devcontainer.json` file.\\n\\nWe need to reuse the image of the previous step. For that let\'s use the build section of the `devcontainer.json` file.\\n\\n```json\\n\\"build\\": {\\n \\"dockerfile\\": \\"Containerfile\\"\\n},\\n```\\n\\nIn order to avoid to redo all the build steps each time we open a workspace using this dev container, we published the image to quay.io at [quay.io/podman-desktop/devcontainer-parent:next\\n](https://quay.io/repository/podman-desktop/devcontainer-parent?tab=tags&tag=next). This parent image is not changing much so it\'s better to use is as a parent one.\\n\\nInside `.devcontainer` directory there is a `.parent` directory with everything related to the parent image.\\n\\nAnd in the `.devcontainer/Containerfile` file we reference this image\\n\\n```docker\\nFROM quay.io/podman-desktop/devcontainer-parent:next\\n```\\n\\nBy default, we will be `root` in the container and this is probably not what we expect. Let\'s change that.\\n\\n```json\\n\\"containerUser\\": \\"podman-desktop\\"\\n```\\n\\nSome Visual Studio Code extensions are nice to use and we can add them\\n\\n```json\\n \\"extensions\\": [\\"svelte.svelte-vscode\\", \\"bradlc.vscode-tailwindcss\\"]\\n```\\n\\nThen here is the tricky part, how to run our container allowing to run again inside the container some containers with podman.\\n\\nWe specify the arguments to make it possible. It\'s possible to use `--privileged` flag but I prefer to list the subset of permissions.\\nUsing `--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.\\n\\n```json\\n\\"runArgs\\": [\\n \\"--cap-add=sys_admin\\",\\n \\"--security-opt\\",\\n \\"seccomp=unconfined\\",\\n \\"--device\\",\\n \\"/dev/fuse\\",\\n \\"--security-opt\\",\\n \\"label=disable\\",\\n \\"--security-opt\\",\\n \\"apparmor=unconfined\\"\\n ],\\n```\\n\\nSource code of Podman Desktop needs to be editable within the DevContainer so it needs to be mounted.\\n\\n```json\\n\\"workspaceMount\\": \\"source=${localWorkspaceFolder},target=/workspace,type=bind\\",\\n\\"workspaceFolder\\": \\"/workspace\\",\\n```\\n\\nThen we need a command to build Podman Desktop.\\n\\nFor that, we use `onCreateCommand` hook with a custom command\\n\\n```json\\n\\"onCreateCommand\\": \\"${containerWorkspaceFolder}/.devcontainer/onCreateCommand.sh\\",\\n```\\n\\nand in the `.devcontainer` folder the `onCreateCommand.sh` script is the following\\n\\n```shell\\n#!/bin/sh\\nyarn\\n\\nMODE=production yarn run build && yarn run electron-builder build --linux --dir --config .electron-builder.config.cjs\\n```\\n\\nTwo instructions:\\n\\n1. Fetch all Node.js dependencies.\\n2. build Podman Desktop in the `dist` folder using `Linux` as target Operating System.\\n\\nAfter the start of the container, how to launch Podman Desktop, the website and VNC, etc ?\\n\\nJust use `postStartCommand` hook.\\n\\n```json\\n\\"postStartCommand\\": \\"${containerWorkspaceFolder}/.devcontainer/postStartCommand.sh\\",\\n```\\n\\nand in the `.devcontainer` folder the `postStartCommand.sh` script is the following:\\n\\n```shell\\n#!/bin/sh\\n\\n# Start all services\\n/usr/bin/supervisord -c /etc/supervisord.conf &\\n\\n# wait X server to be ready or after 2mn exit\\necho \\"Waiting for X server to be ready\\"\\ntimeout 120 bash -c \'until xdpyinfo -display :0 &> /dev/null; do printf \\".\\"; sleep 1; done\'\\n\\n# launch podman desktop\\necho \\"Launching Podman Desktop\\"\\ncd dist/linux-unpacked/&& ./podman-desktop &\\n\\n# Launch the 9000 redirect after 20 seconds\\nsleep 20\\nwebsockify --web=/usr/share/novnc localhost:9000 localhost:5900 &\\n\\n# launch the website rendering\\necho \\"Launching Website\\"\\ncd website && yarn start\\n```\\n\\nIt starts VNC and noVNC, start precompiled Podman Desktop and start the documentation rendering.\\n\\nIt is not launching the Watch mode/development mode of Podman Desktop as it requires a container having more than 8GB of memory.\\n\\nPicking up a larger instance with for example 16GB, it\'s possible to use development mode.\\n\\nOf course, to make VNC happy, we need to specify the `DISPLAY` environment variable.\\n\\n```json\\n\\"remoteEnv\\": {\\n \\"DISPLAY\\": \\":0\\"\\n}\\n```\\n\\nWhen the DevContainer is fully available, we want to have a way to quickly open the `Website rendering URL` and `noVNC`\\n\\nLet\'s tweak the `devcontainer.json` file by adding the `portsAttributes` section\\n\\n```json\\n\\"portsAttributes\\": {\\n \\"9000\\": {\\n \\"label\\": \\"vnc\\",\\n \\"onAutoForward\\": \\"openPreview\\"\\n },\\n \\"3000\\": {\\n \\"label\\": \\"website\\"\\n }\\n}\\n```\\n\\nAfter 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.\\n\\n## Using the DevContainer.json on Github Codespace\\n\\nAs a user, opening a workspace with all what we configured is done using a single click.\\n\\nGo to https://github.com/containers/podman-desktop then click on the `< > Code` dropdown and click on `Create codespace on main` button.\\n\\n![Open Codespace](img/develop-podman-using-codespaces/codespaces-click-repository.png)\\n\\nOnce you click on the button, the codespace is setting up:\\n\\n![Preparing Codespace](img/develop-podman-using-codespaces/codespaces-preparing-codespace.png)\\n\\nAfter few minutes, as there is not yet [prebuilt codespaces](https://docs.github.com/en/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds), the codespace is opening.\\n\\nThe simple Browser displays the noVNC window:\\n![Opening Codespace](img/develop-podman-using-codespaces/codespaces-open-novnc.png)\\n\\nClick 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.\\n![Testing Codespace](img/develop-podman-using-codespaces/codespaces-testing-podman-desktop.png)\\n\\nIt\'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.\\n\\nDepending on the usecase, it\'s also possible to open documentation in the preview browser.\\n\\n![Edit website Codespace](img/develop-podman-using-codespaces/codespaces-edit-website.png)\\n\\n## Conclusion\\n\\nThe 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/assets/js/runtime~main.202464b7.js b/assets/js/runtime~main.d705da89.js similarity index 98% rename from assets/js/runtime~main.202464b7.js rename to assets/js/runtime~main.d705da89.js index 8b215557667..63a1e85e9ce 100644 --- a/assets/js/runtime~main.202464b7.js +++ b/assets/js/runtime~main.d705da89.js @@ -1 +1 @@ -(()=>{"use strict";var e,a,c,f,d,b={},r={};function t(e){var a=r[e];if(void 0!==a)return a.exports;var c=r[e]={exports:{}};return b[e].call(c.exports,c,c.exports,t),c.exports}t.m=b,e=[],t.O=(a,c,f,d)=>{if(!c){var b=1/0;for(n=0;n=d)&&Object.keys(t.O).every((e=>t.O[e](c[o])))?c.splice(o--,1):(r=!1,d0&&e[n-1][2]>d;n--)e[n]=e[n-1];e[n]=[c,f,d]},t.n=e=>{var a=e&&e.__esModule?()=>e.default:()=>e;return t.d(a,{a:a}),a},c=Object.getPrototypeOf?e=>Object.getPrototypeOf(e):e=>e.__proto__,t.t=function(e,f){if(1&f&&(e=this(e)),8&f)return e;if("object"==typeof e&&e){if(4&f&&e.__esModule)return e;if(16&f&&"function"==typeof e.then)return e}var d=Object.create(null);t.r(d);var b={};a=a||[null,c({}),c([]),c(c)];for(var r=2&f&&e;"object"==typeof r&&!~a.indexOf(r);r=c(r))Object.getOwnPropertyNames(r).forEach((a=>b[a]=()=>e[a]));return b.default=()=>e,t.d(d,b),d},t.d=(e,a)=>{for(var c in a)t.o(a,c)&&!t.o(e,c)&&Object.defineProperty(e,c,{enumerable:!0,get:a[c]})},t.f={},t.e=e=>Promise.all(Object.keys(t.f).reduce(((a,c)=>(t.f[c](e,a),a)),[])),t.u=e=>"assets/js/"+({10:"33942509",53:"935f2afb",70:"86f2a982",114:"e665718d",138:"54590fd2",171:"c925d092",182:"c276ecb2",203:"c6aad055",205:"83d480e9",261:"reactPlayerKaltura",347:"bc816bf2",397:"6194ac84",406:"0cbb83d7",465:"f7b7f9b7",485:"8873cf50",506:"9aa62c0e",522:"308aae28",523:"a0323d9f",533:"b2b675dd",534:"4b8121dd",563:"c685778b",592:"b39cdcf9",649:"512fbd77",743:"61d4c13a",745:"64abd3af",809:"840a98fb",816:"4d71dffe",822:"a00af9f0",873:"cabda5f8",899:"b985118d",921:"c37b4a03",944:"b2e1a0c8",945:"df322e14",1021:"901c37e5",1032:"a67ca768",1046:"4cb6c19a",1074:"9e8f4e9c",1297:"34cf6fc7",1342:"a766a857",1425:"fc8a94e3",1441:"382c5d2b",1447:"4974f5d2",1477:"b2f554cd",1625:"de311ed4",1647:"3b5edcc4",1676:"819ef483",1705:"94fb813f",1713:"a7023ddc",1724:"5087625a",1830:"b00bc883",1859:"2295be0e",1866:"1369aff7",1869:"c2ccf160",1896:"25622900",1981:"b799648a",2079:"1a16e8bf",2082:"e85ba0e6",2111:"79665d43",2121:"reactPlayerFacebook",2178:"ba322490",2193:"c5b2f0f9",2217:"d7fbbe43",2242:"1dcf37fa",2323:"6c80b6fe",2339:"17896441",2451:"fb50ea3a",2472:"65a10ffa",2535:"814f3328",2546:"reactPlayerStreamable",2599:"e44de27e",2609:"6269f1c0",2667:"368cce37",2778:"608238a8",2896:"abc85917",2938:"c95aa39f",2958:"86063cd3",3010:"56c3a9b2",3089:"a6aa9e1f",3152:"33a21d7d",3154:"c6346fcf",3163:"232c546d",3207:"6603ef13",3233:"59a6f192",3237:"1df93b7f",3259:"03ccf92d",3296:"181ef600",3317:"846a5e19",3324:"1ce91f4c",3414:"35a7a45c",3427:"bd80aa65",3505:"72486833",3584:"ed75cfcb",3608:"9e4087bc",3636:"8b4dd820",3714:"894e67a6",3743:"reactPlayerVimeo",3751:"3720c009",3820:"a5e1f61e",3840:"562ca3e9",3868:"1b2af15e",3870:"5df556a2",3879:"2d629ea6",3973:"f523fb3f",4013:"01a85c17",4059:"9cb03f5d",4117:"fd684bd6",4121:"55960ee5",4157:"83e10f72",4220:"2bbe04e6",4322:"69c5f318",4356:"a9a76bf7",4368:"a94703ab",4386:"ae79aff5",4439:"reactPlayerYouTube",4459:"19eded63",4573:"f9fb4395",4617:"95366386",4651:"94f3d131",4667:"reactPlayerMixcloud",4672:"03685665",4766:"2f238e8e",4770:"450c2e30",4781:"12f1535e",4918:"24bda87b",4929:"330dfcdb",4940:"c11c87f7",5018:"cd509849",5210:"1949cc8d",5240:"22de4147",5248:"6101b3fc",5255:"71c11e3b",5326:"af231220",5375:"97615df2",5414:"724f3974",5594:"f6360934",5625:"657ac0bc",5708:"f0057c03",5765:"d18d294a",5776:"f0e3a130",5803:"ff8f5ed0",6011:"reactPlayerFilePlayer",6026:"51dec273",6049:"f213dd13",6088:"88efc5aa",6103:"ccc49370",6120:"d4840880",6125:"reactPlayerSoundCloud",6158:"51e516cc",6216:"reactPlayerTwitch",6240:"cb49f262",6308:"e8dc4d98",6328:"c0d19596",6521:"014457dd",6536:"3ed6e2e9",6586:"183053be",6590:"bb8cfc40",6608:"5099f3e0",6623:"b104dd1e",6690:"4816649b",6692:"2ae2e7fe",6766:"e5638e51",6843:"9f97f9d1",6932:"aaabcfd8",7007:"8593ff01",7034:"3e03f778",7134:"0b40a488",7138:"38a042e4",7141:"b5abacaa",7149:"822c343e",7159:"a8ce95ee",7220:"7591d420",7251:"ba5b9f11",7363:"583db3ef",7366:"75281220",7377:"708d858d",7438:"9c021584",7449:"0e4ec2e4",7480:"eb17771c",7536:"f6e0e63c",7573:"48b6ff5f",7586:"ac353d25",7596:"reactPlayerDailyMotion",7622:"dbbb982f",7653:"31de1779",7664:"reactPlayerPreview",7679:"83245ae6",7698:"cd23aec9",7714:"7bdcd7a7",7722:"213182ef",7739:"efc2a09d",7741:"7d88b63f",7759:"ff38b1ce",7847:"43b416ef",7875:"021eaa84",7881:"2658ced2",7918:"10ce918d",7920:"1a4e3797",8055:"reactPlayerWistia",8145:"006e489c",8176:"5660752d",8215:"1cfced13",8221:"6af14956",8262:"059d1c6a",8290:"3fe48f60",8445:"99245987",8502:"b4657d81",8514:"d651e2ee",8518:"a7bd4aaa",8532:"d1b15a6d",8533:"f3d54061",8566:"9dce5486",8610:"6875c492",8626:"c6f0d1b2",8739:"7a957b04",8768:"524ce9a0",8800:"e6fb1369",8811:"3289a752",8860:"0d040286",8888:"reactPlayerVidyard",8893:"ba1dc56d",8960:"6bf124c2",8989:"d4bf7e47",9043:"473de3ed",9106:"72dd8f7e",9133:"02e265ea",9179:"79551407",9341:"a35cf155",9372:"07f59c2a",9387:"b0f1c099",9469:"3b85f227",9492:"92496324",9558:"f41c0109",9579:"09b168a7",9626:"81e486a8",9661:"5e95c892",9671:"0e384e19",9709:"838cf899",9817:"4f561e31",9924:"df203c0f",9944:"08570680",9973:"4213e5b1",9979:"987564cc"}[e]||e)+"."+{10:"998f6ce5",53:"1ac0d812",70:"c1f4341f",114:"3ca680b0",138:"b569aa2b",171:"5762dd53",182:"c229eebf",203:"6cc1a9bc",205:"573e6d62",261:"59b3b0c6",299:"67fe53cf",335:"4805c0ff",347:"08f2aa82",349:"6fd93ebb",397:"83490a42",406:"9fc5c1b7",449:"c6fe4c7c",465:"4c7a59ed",485:"fcadc71b",506:"1333873d",522:"efb62398",523:"bae0097e",533:"26816449",534:"a0101e89",563:"38cad871",592:"ee25241a",649:"d1adf67b",743:"b6bef3d2",745:"38013f83",809:"6db3735a",816:"42f65190",822:"aa516391",873:"a0b4dd3a",899:"c3338ab4",921:"2eaa2de5",944:"1ae3b6d8",945:"a828355e",1006:"19e95ff9",1021:"352aaa75",1032:"a6a8bb90",1046:"62cf6b3b",1074:"fd3d60f8",1297:"8b4d7087",1342:"c51cfec6",1425:"a8c31912",1441:"5f0632de",1447:"5c96ef54",1477:"72f564fc",1625:"e902b2a6",1647:"38cb72ef",1676:"accbe635",1705:"b1bd0aee",1713:"5a56003b",1724:"e683acaf",1830:"31abf427",1856:"2b4c6f80",1859:"6c4f07cc",1866:"628bc491",1869:"d5b19041",1896:"00dc3a40",1981:"f7385425",2079:"a6bac1ac",2082:"7b84efc6",2111:"6fd148ce",2121:"1d5631d2",2178:"13069292",2193:"e0ae080f",2217:"4500992a",2242:"2da98dd6",2323:"4a8d92c7",2339:"a8f7e97d",2451:"7d339ad5",2472:"9fdb1eef",2535:"46080cba",2546:"353efec6",2599:"16dae3fe",2609:"766b98f9",2667:"22327ab1",2778:"52a45067",2896:"d57cbebc",2938:"30b67970",2958:"030a9bcb",3010:"18fcb77a",3041:"4be8b86b",3089:"adf73dea",3152:"1b14defd",3154:"f2c32df8",3163:"8f1e6bda",3207:"06460fe8",3233:"0406b5e1",3237:"f41aab22",3259:"d48e5470",3296:"fbe68b38",3313:"b1117ed6",3317:"2eb33a9d",3324:"ca16a2c4",3414:"793f6bb5",3427:"332d5638",3505:"f8e3b5ab",3584:"29f530b0",3608:"1526f889",3636:"2a7866c5",3714:"fffc18ff",3743:"43335252",3751:"52b86fe9",3820:"2fc73bc7",3840:"4dbff5ee",3868:"a4034df7",3870:"d35f976a",3879:"772bbb02",3973:"9c6324a3",4013:"77711dcc",4059:"347b96b9",4069:"729390c9",4094:"efc68385",4117:"cb1fc7bf",4121:"123b4b64",4157:"280c2c34",4191:"ddc88419",4220:"867fda2c",4322:"7549ee39",4356:"40b6eee7",4366:"ba8f5ab2",4368:"c0e88a45",4386:"b9f0c03a",4439:"7c09aa1f",4459:"b9f7eba1",4573:"41ab2235",4617:"4a2331c8",4651:"900c9c1a",4667:"79c9fa66",4670:"c6602195",4672:"9f8d98b5",4766:"bde1f02f",4770:"956222b0",4781:"8061589b",4854:"93ebc2db",4875:"1b1d16eb",4918:"45518a96",4929:"ba11604a",4940:"b9612c3c",4988:"366d30f5",5018:"076affc0",5067:"9cb86b62",5210:"c20b28f3",5240:"69fe84b9",5248:"3b3048d2",5255:"c3396b4f",5326:"e4e3e788",5375:"1f13aea9",5414:"2c87a2e0",5594:"71a1098b",5625:"c4b6a5f2",5628:"c26ffd78",5708:"f1adb0e5",5711:"51498bc4",5760:"bd2ac63e",5765:"38e4e419",5776:"98f8b21a",5803:"a681401e",5909:"a26f057e",6011:"cac6ee27",6026:"81e7a447",6049:"2835c78e",6070:"a38f944d",6088:"ccc7fd07",6103:"9dd201d7",6120:"5949bfcd",6125:"b843d475",6158:"70ec50c1",6166:"30a60e8a",6216:"32269018",6240:"934cac15",6274:"8f2d8703",6308:"5ce2b518",6328:"7aa75287",6521:"fcc51e46",6536:"c0488fc2",6586:"5528338e",6590:"40494d63",6608:"bd5dfed2",6623:"4cc43386",6690:"99fd0ff4",6692:"601cb7ae",6730:"ffe4ecfc",6766:"e6f76e33",6843:"6f54242f",6932:"9410731b",7007:"2945babe",7034:"89d06177",7076:"b2056ff8",7134:"413b5ea4",7138:"78ce4697",7141:"4564bfc5",7149:"663ec94f",7159:"7c5c1815",7220:"9c7dc65a",7251:"993dc57e",7260:"edee19ff",7363:"9920635e",7366:"3792e34e",7377:"6b4fe40f",7430:"bdba0009",7438:"5c0c4977",7449:"591cc7cf",7480:"bb181ea3",7536:"f0cbb62f",7573:"f1a802cb",7586:"b3f484a4",7596:"f8009a5e",7622:"b17356bb",7653:"2ea50086",7664:"2267cb44",7679:"2268355e",7698:"4f79d26b",7714:"d02b8df8",7722:"ae558d9e",7737:"38d71842",7739:"e6cd623d",7741:"1afbfa31",7759:"809680ab",7847:"2c70676d",7849:"6f99b72f",7875:"0ad319ce",7881:"aed2806c",7918:"73f8b649",7920:"0e623c45",8055:"7ac13b2f",8145:"0820074d",8176:"4a5af7d6",8215:"778f5e2d",8221:"00b1aa0c",8262:"369fdebe",8290:"ed6f8f6c",8315:"0ceeb234",8327:"47f26ce2",8445:"4fc783d0",8502:"08d69c78",8514:"a243eab8",8518:"d1ef6cf4",8532:"43299dd2",8533:"db9e37cb",8566:"846625b8",8610:"70f4caf3",8626:"a1d012d1",8739:"5ec3505b",8768:"95402132",8800:"09f3f410",8811:"2bfa95ba",8860:"3253b143",8888:"aa75b509",8893:"20ffc050",8960:"613d028d",8989:"7fc2e7e3",9043:"abe2e156",9106:"91d0911a",9127:"02f87f8d",9133:"7057011c",9179:"2b666ddf",9341:"05fdb1ad",9372:"e2894edd",9387:"c7defde8",9469:"9a7d7fb2",9492:"2ab62303",9500:"8bb8cb2a",9558:"be5e0ae3",9579:"705c3d78",9626:"918cf6d7",9661:"b7ea4262",9671:"6652f4ad",9709:"d013713d",9812:"935315d5",9817:"1bbc72ba",9924:"2026b37e",9944:"d424f2ea",9964:"8c664f0c",9973:"df3f1309",9979:"1014193e"}[e]+".js",t.miniCssF=e=>{},t.g=function(){if("object"==typeof globalThis)return globalThis;try{return this||new Function("return this")()}catch(e){if("object"==typeof window)return window}}(),t.o=(e,a)=>Object.prototype.hasOwnProperty.call(e,a),f={},d="docs:",t.l=(e,a,c,b)=>{if(f[e])f[e].push(a);else{var r,o;if(void 0!==c)for(var l=document.getElementsByTagName("script"),n=0;n{r.onerror=r.onload=null,clearTimeout(s);var d=f[e];if(delete f[e],r.parentNode&&r.parentNode.removeChild(r),d&&d.forEach((e=>e(c))),a)return a(c)},s=setTimeout(u.bind(null,void 0,{type:"timeout",target:r}),12e4);r.onerror=u.bind(null,r.onerror),r.onload=u.bind(null,r.onload),o&&document.head.appendChild(r)}},t.r=e=>{"undefined"!=typeof Symbol&&Symbol.toStringTag&&Object.defineProperty(e,Symbol.toStringTag,{value:"Module"}),Object.defineProperty(e,"__esModule",{value:!0})},t.p="/",t.gca=function(e){return e={17896441:"2339",25622900:"1896",33942509:"10",72486833:"3505",75281220:"7366",79551407:"9179",92496324:"9492",95366386:"4617",99245987:"8445","935f2afb":"53","86f2a982":"70",e665718d:"114","54590fd2":"138",c925d092:"171",c276ecb2:"182",c6aad055:"203","83d480e9":"205",reactPlayerKaltura:"261",bc816bf2:"347","6194ac84":"397","0cbb83d7":"406",f7b7f9b7:"465","8873cf50":"485","9aa62c0e":"506","308aae28":"522",a0323d9f:"523",b2b675dd:"533","4b8121dd":"534",c685778b:"563",b39cdcf9:"592","512fbd77":"649","61d4c13a":"743","64abd3af":"745","840a98fb":"809","4d71dffe":"816",a00af9f0:"822",cabda5f8:"873",b985118d:"899",c37b4a03:"921",b2e1a0c8:"944",df322e14:"945","901c37e5":"1021",a67ca768:"1032","4cb6c19a":"1046","9e8f4e9c":"1074","34cf6fc7":"1297",a766a857:"1342",fc8a94e3:"1425","382c5d2b":"1441","4974f5d2":"1447",b2f554cd:"1477",de311ed4:"1625","3b5edcc4":"1647","819ef483":"1676","94fb813f":"1705",a7023ddc:"1713","5087625a":"1724",b00bc883:"1830","2295be0e":"1859","1369aff7":"1866",c2ccf160:"1869",b799648a:"1981","1a16e8bf":"2079",e85ba0e6:"2082","79665d43":"2111",reactPlayerFacebook:"2121",ba322490:"2178",c5b2f0f9:"2193",d7fbbe43:"2217","1dcf37fa":"2242","6c80b6fe":"2323",fb50ea3a:"2451","65a10ffa":"2472","814f3328":"2535",reactPlayerStreamable:"2546",e44de27e:"2599","6269f1c0":"2609","368cce37":"2667","608238a8":"2778",abc85917:"2896",c95aa39f:"2938","86063cd3":"2958","56c3a9b2":"3010",a6aa9e1f:"3089","33a21d7d":"3152",c6346fcf:"3154","232c546d":"3163","6603ef13":"3207","59a6f192":"3233","1df93b7f":"3237","03ccf92d":"3259","181ef600":"3296","846a5e19":"3317","1ce91f4c":"3324","35a7a45c":"3414",bd80aa65:"3427",ed75cfcb:"3584","9e4087bc":"3608","8b4dd820":"3636","894e67a6":"3714",reactPlayerVimeo:"3743","3720c009":"3751",a5e1f61e:"3820","562ca3e9":"3840","1b2af15e":"3868","5df556a2":"3870","2d629ea6":"3879",f523fb3f:"3973","01a85c17":"4013","9cb03f5d":"4059",fd684bd6:"4117","55960ee5":"4121","83e10f72":"4157","2bbe04e6":"4220","69c5f318":"4322",a9a76bf7:"4356",a94703ab:"4368",ae79aff5:"4386",reactPlayerYouTube:"4439","19eded63":"4459",f9fb4395:"4573","94f3d131":"4651",reactPlayerMixcloud:"4667","03685665":"4672","2f238e8e":"4766","450c2e30":"4770","12f1535e":"4781","24bda87b":"4918","330dfcdb":"4929",c11c87f7:"4940",cd509849:"5018","1949cc8d":"5210","22de4147":"5240","6101b3fc":"5248","71c11e3b":"5255",af231220:"5326","97615df2":"5375","724f3974":"5414",f6360934:"5594","657ac0bc":"5625",f0057c03:"5708",d18d294a:"5765",f0e3a130:"5776",ff8f5ed0:"5803",reactPlayerFilePlayer:"6011","51dec273":"6026",f213dd13:"6049","88efc5aa":"6088",ccc49370:"6103",d4840880:"6120",reactPlayerSoundCloud:"6125","51e516cc":"6158",reactPlayerTwitch:"6216",cb49f262:"6240",e8dc4d98:"6308",c0d19596:"6328","014457dd":"6521","3ed6e2e9":"6536","183053be":"6586",bb8cfc40:"6590","5099f3e0":"6608",b104dd1e:"6623","4816649b":"6690","2ae2e7fe":"6692",e5638e51:"6766","9f97f9d1":"6843",aaabcfd8:"6932","8593ff01":"7007","3e03f778":"7034","0b40a488":"7134","38a042e4":"7138",b5abacaa:"7141","822c343e":"7149",a8ce95ee:"7159","7591d420":"7220",ba5b9f11:"7251","583db3ef":"7363","708d858d":"7377","9c021584":"7438","0e4ec2e4":"7449",eb17771c:"7480",f6e0e63c:"7536","48b6ff5f":"7573",ac353d25:"7586",reactPlayerDailyMotion:"7596",dbbb982f:"7622","31de1779":"7653",reactPlayerPreview:"7664","83245ae6":"7679",cd23aec9:"7698","7bdcd7a7":"7714","213182ef":"7722",efc2a09d:"7739","7d88b63f":"7741",ff38b1ce:"7759","43b416ef":"7847","021eaa84":"7875","2658ced2":"7881","10ce918d":"7918","1a4e3797":"7920",reactPlayerWistia:"8055","006e489c":"8145","5660752d":"8176","1cfced13":"8215","6af14956":"8221","059d1c6a":"8262","3fe48f60":"8290",b4657d81:"8502",d651e2ee:"8514",a7bd4aaa:"8518",d1b15a6d:"8532",f3d54061:"8533","9dce5486":"8566","6875c492":"8610",c6f0d1b2:"8626","7a957b04":"8739","524ce9a0":"8768",e6fb1369:"8800","3289a752":"8811","0d040286":"8860",reactPlayerVidyard:"8888",ba1dc56d:"8893","6bf124c2":"8960",d4bf7e47:"8989","473de3ed":"9043","72dd8f7e":"9106","02e265ea":"9133",a35cf155:"9341","07f59c2a":"9372",b0f1c099:"9387","3b85f227":"9469",f41c0109:"9558","09b168a7":"9579","81e486a8":"9626","5e95c892":"9661","0e384e19":"9671","838cf899":"9709","4f561e31":"9817",df203c0f:"9924","08570680":"9944","4213e5b1":"9973","987564cc":"9979"}[e]||e,t.p+t.u(e)},(()=>{var e={1303:0,532:0};t.f.j=(a,c)=>{var f=t.o(e,a)?e[a]:void 0;if(0!==f)if(f)c.push(f[2]);else if(/^(1303|532)$/.test(a))e[a]=0;else{var d=new Promise(((c,d)=>f=e[a]=[c,d]));c.push(f[2]=d);var b=t.p+t.u(a),r=new Error;t.l(b,(c=>{if(t.o(e,a)&&(0!==(f=e[a])&&(e[a]=void 0),f)){var d=c&&("load"===c.type?"missing":c.type),b=c&&c.target&&c.target.src;r.message="Loading chunk "+a+" failed.\n("+d+": "+b+")",r.name="ChunkLoadError",r.type=d,r.request=b,f[1](r)}}),"chunk-"+a,a)}},t.O.j=a=>0===e[a];var a=(a,c)=>{var f,d,b=c[0],r=c[1],o=c[2],l=0;if(b.some((a=>0!==e[a]))){for(f in r)t.o(r,f)&&(t.m[f]=r[f]);if(o)var n=o(t)}for(a&&a(c);l{"use strict";var e,a,c,f,d,b={},r={};function t(e){var a=r[e];if(void 0!==a)return a.exports;var c=r[e]={exports:{}};return b[e].call(c.exports,c,c.exports,t),c.exports}t.m=b,e=[],t.O=(a,c,f,d)=>{if(!c){var b=1/0;for(n=0;n=d)&&Object.keys(t.O).every((e=>t.O[e](c[o])))?c.splice(o--,1):(r=!1,d0&&e[n-1][2]>d;n--)e[n]=e[n-1];e[n]=[c,f,d]},t.n=e=>{var a=e&&e.__esModule?()=>e.default:()=>e;return t.d(a,{a:a}),a},c=Object.getPrototypeOf?e=>Object.getPrototypeOf(e):e=>e.__proto__,t.t=function(e,f){if(1&f&&(e=this(e)),8&f)return e;if("object"==typeof e&&e){if(4&f&&e.__esModule)return e;if(16&f&&"function"==typeof e.then)return e}var d=Object.create(null);t.r(d);var b={};a=a||[null,c({}),c([]),c(c)];for(var r=2&f&&e;"object"==typeof r&&!~a.indexOf(r);r=c(r))Object.getOwnPropertyNames(r).forEach((a=>b[a]=()=>e[a]));return b.default=()=>e,t.d(d,b),d},t.d=(e,a)=>{for(var c in a)t.o(a,c)&&!t.o(e,c)&&Object.defineProperty(e,c,{enumerable:!0,get:a[c]})},t.f={},t.e=e=>Promise.all(Object.keys(t.f).reduce(((a,c)=>(t.f[c](e,a),a)),[])),t.u=e=>"assets/js/"+({10:"33942509",53:"935f2afb",70:"86f2a982",114:"e665718d",138:"54590fd2",171:"c925d092",182:"c276ecb2",203:"c6aad055",205:"83d480e9",261:"reactPlayerKaltura",347:"bc816bf2",397:"6194ac84",406:"0cbb83d7",465:"f7b7f9b7",485:"8873cf50",506:"9aa62c0e",522:"308aae28",523:"a0323d9f",533:"b2b675dd",534:"4b8121dd",563:"c685778b",592:"b39cdcf9",649:"512fbd77",743:"61d4c13a",745:"64abd3af",809:"840a98fb",816:"4d71dffe",822:"a00af9f0",873:"cabda5f8",899:"b985118d",921:"c37b4a03",944:"b2e1a0c8",945:"df322e14",1021:"901c37e5",1032:"a67ca768",1046:"4cb6c19a",1074:"9e8f4e9c",1297:"34cf6fc7",1342:"a766a857",1425:"fc8a94e3",1441:"382c5d2b",1447:"4974f5d2",1477:"b2f554cd",1625:"de311ed4",1647:"3b5edcc4",1676:"819ef483",1705:"94fb813f",1713:"a7023ddc",1724:"5087625a",1830:"b00bc883",1859:"2295be0e",1866:"1369aff7",1869:"c2ccf160",1896:"25622900",1981:"b799648a",2079:"1a16e8bf",2082:"e85ba0e6",2111:"79665d43",2121:"reactPlayerFacebook",2178:"ba322490",2193:"c5b2f0f9",2217:"d7fbbe43",2242:"1dcf37fa",2323:"6c80b6fe",2339:"17896441",2451:"fb50ea3a",2472:"65a10ffa",2535:"814f3328",2546:"reactPlayerStreamable",2599:"e44de27e",2609:"6269f1c0",2667:"368cce37",2778:"608238a8",2896:"abc85917",2938:"c95aa39f",2958:"86063cd3",3010:"56c3a9b2",3089:"a6aa9e1f",3152:"33a21d7d",3154:"c6346fcf",3163:"232c546d",3207:"6603ef13",3233:"59a6f192",3237:"1df93b7f",3259:"03ccf92d",3296:"181ef600",3317:"846a5e19",3324:"1ce91f4c",3414:"35a7a45c",3427:"bd80aa65",3505:"72486833",3584:"ed75cfcb",3608:"9e4087bc",3636:"8b4dd820",3714:"894e67a6",3743:"reactPlayerVimeo",3751:"3720c009",3820:"a5e1f61e",3840:"562ca3e9",3868:"1b2af15e",3870:"5df556a2",3879:"2d629ea6",3973:"f523fb3f",4013:"01a85c17",4059:"9cb03f5d",4117:"fd684bd6",4121:"55960ee5",4157:"83e10f72",4220:"2bbe04e6",4322:"69c5f318",4356:"a9a76bf7",4368:"a94703ab",4386:"ae79aff5",4439:"reactPlayerYouTube",4459:"19eded63",4573:"f9fb4395",4617:"95366386",4651:"94f3d131",4667:"reactPlayerMixcloud",4672:"03685665",4766:"2f238e8e",4770:"450c2e30",4781:"12f1535e",4918:"24bda87b",4929:"330dfcdb",4940:"c11c87f7",5018:"cd509849",5210:"1949cc8d",5240:"22de4147",5248:"6101b3fc",5255:"71c11e3b",5326:"af231220",5375:"97615df2",5414:"724f3974",5594:"f6360934",5625:"657ac0bc",5708:"f0057c03",5765:"d18d294a",5776:"f0e3a130",5803:"ff8f5ed0",6011:"reactPlayerFilePlayer",6026:"51dec273",6049:"f213dd13",6088:"88efc5aa",6103:"ccc49370",6120:"d4840880",6125:"reactPlayerSoundCloud",6158:"51e516cc",6216:"reactPlayerTwitch",6240:"cb49f262",6308:"e8dc4d98",6328:"c0d19596",6521:"014457dd",6536:"3ed6e2e9",6586:"183053be",6590:"bb8cfc40",6608:"5099f3e0",6623:"b104dd1e",6690:"4816649b",6692:"2ae2e7fe",6766:"e5638e51",6843:"9f97f9d1",6932:"aaabcfd8",7007:"8593ff01",7034:"3e03f778",7134:"0b40a488",7138:"38a042e4",7141:"b5abacaa",7149:"822c343e",7159:"a8ce95ee",7220:"7591d420",7251:"ba5b9f11",7363:"583db3ef",7366:"75281220",7377:"708d858d",7438:"9c021584",7449:"0e4ec2e4",7480:"eb17771c",7536:"f6e0e63c",7573:"48b6ff5f",7586:"ac353d25",7596:"reactPlayerDailyMotion",7622:"dbbb982f",7653:"31de1779",7664:"reactPlayerPreview",7679:"83245ae6",7698:"cd23aec9",7714:"7bdcd7a7",7722:"213182ef",7739:"efc2a09d",7741:"7d88b63f",7759:"ff38b1ce",7847:"43b416ef",7875:"021eaa84",7881:"2658ced2",7918:"10ce918d",7920:"1a4e3797",8055:"reactPlayerWistia",8145:"006e489c",8176:"5660752d",8215:"1cfced13",8221:"6af14956",8262:"059d1c6a",8290:"3fe48f60",8445:"99245987",8502:"b4657d81",8514:"d651e2ee",8518:"a7bd4aaa",8532:"d1b15a6d",8533:"f3d54061",8566:"9dce5486",8610:"6875c492",8626:"c6f0d1b2",8739:"7a957b04",8768:"524ce9a0",8800:"e6fb1369",8811:"3289a752",8860:"0d040286",8888:"reactPlayerVidyard",8893:"ba1dc56d",8960:"6bf124c2",8989:"d4bf7e47",9043:"473de3ed",9106:"72dd8f7e",9133:"02e265ea",9179:"79551407",9341:"a35cf155",9372:"07f59c2a",9387:"b0f1c099",9469:"3b85f227",9492:"92496324",9558:"f41c0109",9579:"09b168a7",9626:"81e486a8",9661:"5e95c892",9671:"0e384e19",9709:"838cf899",9817:"4f561e31",9924:"df203c0f",9944:"08570680",9973:"4213e5b1",9979:"987564cc"}[e]||e)+"."+{10:"998f6ce5",53:"1ac0d812",70:"c1f4341f",114:"3ca680b0",138:"b569aa2b",171:"5762dd53",182:"c229eebf",203:"6cc1a9bc",205:"573e6d62",261:"59b3b0c6",299:"67fe53cf",335:"4805c0ff",347:"08f2aa82",349:"6fd93ebb",397:"83490a42",406:"9fc5c1b7",449:"c6fe4c7c",465:"4c7a59ed",485:"cdb9f62c",506:"1333873d",522:"efb62398",523:"bae0097e",533:"26816449",534:"a0101e89",563:"38cad871",592:"ee25241a",649:"d1adf67b",743:"b6bef3d2",745:"38013f83",809:"6db3735a",816:"793f696b",822:"aa516391",873:"a0b4dd3a",899:"c3338ab4",921:"2eaa2de5",944:"1ae3b6d8",945:"a828355e",1006:"19e95ff9",1021:"352aaa75",1032:"a6a8bb90",1046:"62cf6b3b",1074:"fd3d60f8",1297:"8b4d7087",1342:"c51cfec6",1425:"a8c31912",1441:"5f0632de",1447:"5c96ef54",1477:"ebcd0c9c",1625:"e902b2a6",1647:"38cb72ef",1676:"accbe635",1705:"b1bd0aee",1713:"5a56003b",1724:"e683acaf",1830:"31abf427",1856:"2b4c6f80",1859:"6c4f07cc",1866:"628bc491",1869:"d5b19041",1896:"00dc3a40",1981:"f7385425",2079:"a6bac1ac",2082:"7b84efc6",2111:"6fd148ce",2121:"1d5631d2",2178:"13069292",2193:"e0ae080f",2217:"4500992a",2242:"2da98dd6",2323:"4a8d92c7",2339:"a8f7e97d",2451:"7d339ad5",2472:"9fdb1eef",2535:"46080cba",2546:"353efec6",2599:"16dae3fe",2609:"766b98f9",2667:"22327ab1",2778:"52a45067",2896:"d57cbebc",2938:"30b67970",2958:"030a9bcb",3010:"18fcb77a",3041:"4be8b86b",3089:"adf73dea",3152:"1b14defd",3154:"f2c32df8",3163:"8f1e6bda",3207:"06460fe8",3233:"0406b5e1",3237:"f41aab22",3259:"d48e5470",3296:"fbe68b38",3313:"b1117ed6",3317:"2eb33a9d",3324:"ca16a2c4",3414:"793f6bb5",3427:"332d5638",3505:"f8e3b5ab",3584:"29f530b0",3608:"1526f889",3636:"2a7866c5",3714:"fffc18ff",3743:"43335252",3751:"52b86fe9",3820:"2fc73bc7",3840:"4dbff5ee",3868:"a4034df7",3870:"d35f976a",3879:"772bbb02",3973:"9c6324a3",4013:"77711dcc",4059:"347b96b9",4069:"729390c9",4094:"efc68385",4117:"cb1fc7bf",4121:"123b4b64",4157:"280c2c34",4191:"ddc88419",4220:"867fda2c",4322:"7549ee39",4356:"40b6eee7",4366:"ba8f5ab2",4368:"c0e88a45",4386:"b9f0c03a",4439:"7c09aa1f",4459:"b9f7eba1",4573:"41ab2235",4617:"4a2331c8",4651:"900c9c1a",4667:"79c9fa66",4670:"c6602195",4672:"9f8d98b5",4766:"bde1f02f",4770:"956222b0",4781:"8061589b",4854:"93ebc2db",4875:"1b1d16eb",4918:"45518a96",4929:"ba11604a",4940:"b9612c3c",4988:"366d30f5",5018:"076affc0",5067:"9cb86b62",5210:"c20b28f3",5240:"69fe84b9",5248:"3b3048d2",5255:"c3396b4f",5326:"e4e3e788",5375:"1f13aea9",5414:"2c87a2e0",5594:"71a1098b",5625:"c4b6a5f2",5628:"c26ffd78",5708:"f1adb0e5",5711:"51498bc4",5760:"bd2ac63e",5765:"38e4e419",5776:"98f8b21a",5803:"a681401e",5909:"a26f057e",6011:"cac6ee27",6026:"81e7a447",6049:"2835c78e",6070:"a38f944d",6088:"ccc7fd07",6103:"9dd201d7",6120:"5949bfcd",6125:"b843d475",6158:"70ec50c1",6166:"30a60e8a",6216:"32269018",6240:"934cac15",6274:"8f2d8703",6308:"5ce2b518",6328:"7aa75287",6521:"fcc51e46",6536:"c0488fc2",6586:"5528338e",6590:"40494d63",6608:"bd5dfed2",6623:"4cc43386",6690:"99fd0ff4",6692:"601cb7ae",6730:"ffe4ecfc",6766:"e6f76e33",6843:"6f54242f",6932:"9410731b",7007:"2945babe",7034:"89d06177",7076:"b2056ff8",7134:"413b5ea4",7138:"78ce4697",7141:"4564bfc5",7149:"663ec94f",7159:"7c5c1815",7220:"9c7dc65a",7251:"993dc57e",7260:"edee19ff",7363:"9920635e",7366:"3792e34e",7377:"6b4fe40f",7430:"bdba0009",7438:"5c0c4977",7449:"591cc7cf",7480:"bb181ea3",7536:"f0cbb62f",7573:"f1a802cb",7586:"b3f484a4",7596:"f8009a5e",7622:"b17356bb",7653:"2ea50086",7664:"2267cb44",7679:"2268355e",7698:"4f79d26b",7714:"d02b8df8",7722:"ae558d9e",7737:"38d71842",7739:"e6cd623d",7741:"1afbfa31",7759:"809680ab",7847:"2c70676d",7849:"6f99b72f",7875:"0ad319ce",7881:"aed2806c",7918:"73f8b649",7920:"0e623c45",8055:"7ac13b2f",8145:"0820074d",8176:"4a5af7d6",8215:"778f5e2d",8221:"00b1aa0c",8262:"369fdebe",8290:"ed6f8f6c",8315:"0ceeb234",8327:"47f26ce2",8445:"4fc783d0",8502:"08d69c78",8514:"a243eab8",8518:"d1ef6cf4",8532:"43299dd2",8533:"db9e37cb",8566:"846625b8",8610:"70f4caf3",8626:"a1d012d1",8739:"5ec3505b",8768:"95402132",8800:"09f3f410",8811:"2bfa95ba",8860:"3253b143",8888:"aa75b509",8893:"20ffc050",8960:"613d028d",8989:"7fc2e7e3",9043:"abe2e156",9106:"91d0911a",9127:"02f87f8d",9133:"7057011c",9179:"2b666ddf",9341:"05fdb1ad",9372:"e2894edd",9387:"c7defde8",9469:"9a7d7fb2",9492:"2ab62303",9500:"8bb8cb2a",9558:"be5e0ae3",9579:"705c3d78",9626:"918cf6d7",9661:"b7ea4262",9671:"6652f4ad",9709:"d013713d",9812:"935315d5",9817:"1bbc72ba",9924:"2026b37e",9944:"d424f2ea",9964:"8c664f0c",9973:"df3f1309",9979:"1014193e"}[e]+".js",t.miniCssF=e=>{},t.g=function(){if("object"==typeof globalThis)return globalThis;try{return this||new Function("return this")()}catch(e){if("object"==typeof window)return window}}(),t.o=(e,a)=>Object.prototype.hasOwnProperty.call(e,a),f={},d="docs:",t.l=(e,a,c,b)=>{if(f[e])f[e].push(a);else{var r,o;if(void 0!==c)for(var l=document.getElementsByTagName("script"),n=0;n{r.onerror=r.onload=null,clearTimeout(s);var d=f[e];if(delete f[e],r.parentNode&&r.parentNode.removeChild(r),d&&d.forEach((e=>e(c))),a)return a(c)},s=setTimeout(u.bind(null,void 0,{type:"timeout",target:r}),12e4);r.onerror=u.bind(null,r.onerror),r.onload=u.bind(null,r.onload),o&&document.head.appendChild(r)}},t.r=e=>{"undefined"!=typeof Symbol&&Symbol.toStringTag&&Object.defineProperty(e,Symbol.toStringTag,{value:"Module"}),Object.defineProperty(e,"__esModule",{value:!0})},t.p="/",t.gca=function(e){return e={17896441:"2339",25622900:"1896",33942509:"10",72486833:"3505",75281220:"7366",79551407:"9179",92496324:"9492",95366386:"4617",99245987:"8445","935f2afb":"53","86f2a982":"70",e665718d:"114","54590fd2":"138",c925d092:"171",c276ecb2:"182",c6aad055:"203","83d480e9":"205",reactPlayerKaltura:"261",bc816bf2:"347","6194ac84":"397","0cbb83d7":"406",f7b7f9b7:"465","8873cf50":"485","9aa62c0e":"506","308aae28":"522",a0323d9f:"523",b2b675dd:"533","4b8121dd":"534",c685778b:"563",b39cdcf9:"592","512fbd77":"649","61d4c13a":"743","64abd3af":"745","840a98fb":"809","4d71dffe":"816",a00af9f0:"822",cabda5f8:"873",b985118d:"899",c37b4a03:"921",b2e1a0c8:"944",df322e14:"945","901c37e5":"1021",a67ca768:"1032","4cb6c19a":"1046","9e8f4e9c":"1074","34cf6fc7":"1297",a766a857:"1342",fc8a94e3:"1425","382c5d2b":"1441","4974f5d2":"1447",b2f554cd:"1477",de311ed4:"1625","3b5edcc4":"1647","819ef483":"1676","94fb813f":"1705",a7023ddc:"1713","5087625a":"1724",b00bc883:"1830","2295be0e":"1859","1369aff7":"1866",c2ccf160:"1869",b799648a:"1981","1a16e8bf":"2079",e85ba0e6:"2082","79665d43":"2111",reactPlayerFacebook:"2121",ba322490:"2178",c5b2f0f9:"2193",d7fbbe43:"2217","1dcf37fa":"2242","6c80b6fe":"2323",fb50ea3a:"2451","65a10ffa":"2472","814f3328":"2535",reactPlayerStreamable:"2546",e44de27e:"2599","6269f1c0":"2609","368cce37":"2667","608238a8":"2778",abc85917:"2896",c95aa39f:"2938","86063cd3":"2958","56c3a9b2":"3010",a6aa9e1f:"3089","33a21d7d":"3152",c6346fcf:"3154","232c546d":"3163","6603ef13":"3207","59a6f192":"3233","1df93b7f":"3237","03ccf92d":"3259","181ef600":"3296","846a5e19":"3317","1ce91f4c":"3324","35a7a45c":"3414",bd80aa65:"3427",ed75cfcb:"3584","9e4087bc":"3608","8b4dd820":"3636","894e67a6":"3714",reactPlayerVimeo:"3743","3720c009":"3751",a5e1f61e:"3820","562ca3e9":"3840","1b2af15e":"3868","5df556a2":"3870","2d629ea6":"3879",f523fb3f:"3973","01a85c17":"4013","9cb03f5d":"4059",fd684bd6:"4117","55960ee5":"4121","83e10f72":"4157","2bbe04e6":"4220","69c5f318":"4322",a9a76bf7:"4356",a94703ab:"4368",ae79aff5:"4386",reactPlayerYouTube:"4439","19eded63":"4459",f9fb4395:"4573","94f3d131":"4651",reactPlayerMixcloud:"4667","03685665":"4672","2f238e8e":"4766","450c2e30":"4770","12f1535e":"4781","24bda87b":"4918","330dfcdb":"4929",c11c87f7:"4940",cd509849:"5018","1949cc8d":"5210","22de4147":"5240","6101b3fc":"5248","71c11e3b":"5255",af231220:"5326","97615df2":"5375","724f3974":"5414",f6360934:"5594","657ac0bc":"5625",f0057c03:"5708",d18d294a:"5765",f0e3a130:"5776",ff8f5ed0:"5803",reactPlayerFilePlayer:"6011","51dec273":"6026",f213dd13:"6049","88efc5aa":"6088",ccc49370:"6103",d4840880:"6120",reactPlayerSoundCloud:"6125","51e516cc":"6158",reactPlayerTwitch:"6216",cb49f262:"6240",e8dc4d98:"6308",c0d19596:"6328","014457dd":"6521","3ed6e2e9":"6536","183053be":"6586",bb8cfc40:"6590","5099f3e0":"6608",b104dd1e:"6623","4816649b":"6690","2ae2e7fe":"6692",e5638e51:"6766","9f97f9d1":"6843",aaabcfd8:"6932","8593ff01":"7007","3e03f778":"7034","0b40a488":"7134","38a042e4":"7138",b5abacaa:"7141","822c343e":"7149",a8ce95ee:"7159","7591d420":"7220",ba5b9f11:"7251","583db3ef":"7363","708d858d":"7377","9c021584":"7438","0e4ec2e4":"7449",eb17771c:"7480",f6e0e63c:"7536","48b6ff5f":"7573",ac353d25:"7586",reactPlayerDailyMotion:"7596",dbbb982f:"7622","31de1779":"7653",reactPlayerPreview:"7664","83245ae6":"7679",cd23aec9:"7698","7bdcd7a7":"7714","213182ef":"7722",efc2a09d:"7739","7d88b63f":"7741",ff38b1ce:"7759","43b416ef":"7847","021eaa84":"7875","2658ced2":"7881","10ce918d":"7918","1a4e3797":"7920",reactPlayerWistia:"8055","006e489c":"8145","5660752d":"8176","1cfced13":"8215","6af14956":"8221","059d1c6a":"8262","3fe48f60":"8290",b4657d81:"8502",d651e2ee:"8514",a7bd4aaa:"8518",d1b15a6d:"8532",f3d54061:"8533","9dce5486":"8566","6875c492":"8610",c6f0d1b2:"8626","7a957b04":"8739","524ce9a0":"8768",e6fb1369:"8800","3289a752":"8811","0d040286":"8860",reactPlayerVidyard:"8888",ba1dc56d:"8893","6bf124c2":"8960",d4bf7e47:"8989","473de3ed":"9043","72dd8f7e":"9106","02e265ea":"9133",a35cf155:"9341","07f59c2a":"9372",b0f1c099:"9387","3b85f227":"9469",f41c0109:"9558","09b168a7":"9579","81e486a8":"9626","5e95c892":"9661","0e384e19":"9671","838cf899":"9709","4f561e31":"9817",df203c0f:"9924","08570680":"9944","4213e5b1":"9973","987564cc":"9979"}[e]||e,t.p+t.u(e)},(()=>{var e={1303:0,532:0};t.f.j=(a,c)=>{var f=t.o(e,a)?e[a]:void 0;if(0!==f)if(f)c.push(f[2]);else if(/^(1303|532)$/.test(a))e[a]=0;else{var d=new Promise(((c,d)=>f=e[a]=[c,d]));c.push(f[2]=d);var b=t.p+t.u(a),r=new Error;t.l(b,(c=>{if(t.o(e,a)&&(0!==(f=e[a])&&(e[a]=void 0),f)){var d=c&&("load"===c.type?"missing":c.type),b=c&&c.target&&c.target.src;r.message="Loading chunk "+a+" failed.\n("+d+": "+b+")",r.name="ChunkLoadError",r.type=d,r.request=b,f[1](r)}}),"chunk-"+a,a)}},t.O.j=a=>0===e[a];var a=(a,c)=>{var f,d,b=c[0],r=c[1],o=c[2],l=0;if(b.some((a=>0!==e[a]))){for(f in r)t.o(r,f)&&(t.m[f]=r[f]);if(o)var n=o(t)}for(a&&a(c);l - + @@ -39,9 +39,9 @@

Confirm that you are able to run podman compose:

podman compose
Run compose workloads via an external provider such as docker-compose or podman-compose

Description:
  This command is a thin wrapper around an external compose provider such as docker-compose or podman-compose.  This means that podman compose is executing another tool that implements the compose functionality but sets up the environment in a way to let the compose provider communicate transparently with the local Podman socket.  The specified options as well the command and argument are passed directly to the compose provider.
...

Download and run the example application​

-

Our example application is located at github.com/redhat-developer/podman-desktop-compose-example.

+

Our example application is located at github.com/redhat-developer/podman-desktop-demo.

We will use git clone so we can build the Go binary web application:

-
git clone https://github.com/redhat-developer/podman-desktop-compose-example
cd podman-desktop-compose-example
+
git clone https://github.com/redhat-developer/podman-desktop-demo
cd podman-desktop-demo/guestbook-compose

Run podman compose up -d to start the application:

podman compose up -d
>>>> Executing external compose provider "/usr/local/bin/docker-compose". Please refer to the documentation for details. <<<<

[+] Running 3/3
 ✔ Container redis-replica  Started                                                                        0.0s
 ✔ Container web            Started                                                                        0.0s
 ✔ Container redis-leader   Started                                                                        0.0s

Viewing the guestbook application​

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 1488d9a064b..f9c37c8749e 100644 --- a/blog/5-things-to-know-for-a-docker-user.html +++ b/blog/5-things-to-know-for-a-docker-user.html @@ -13,7 +13,7 @@ - + diff --git a/blog/archive.html b/blog/archive.html index f17287fd8e1..332f28992ac 100644 --- a/blog/archive.html +++ b/blog/archive.html @@ -13,7 +13,7 @@ - + diff --git a/blog/atom.xml b/blog/atom.xml index ea9fdf68b90..627be9fca1f 100644 --- a/blog/atom.xml +++ b/blog/atom.xml @@ -36,9 +36,9 @@

Confirm that you are able to run podman compose:

podman compose
Run compose workloads via an external provider such as docker-compose or podman-compose

Description:
  This command is a thin wrapper around an external compose provider such as docker-compose or podman-compose.  This means that podman compose is executing another tool that implements the compose functionality but sets up the environment in a way to let the compose provider communicate transparently with the local Podman socket.  The specified options as well the command and argument are passed directly to the compose provider.
...

Download and run the example application​

-

Our example application is located at github.com/redhat-developer/podman-desktop-compose-example.

+

Our example application is located at github.com/redhat-developer/podman-desktop-demo.

We will use git clone so we can build the Go binary web application:

-
git clone https://github.com/redhat-developer/podman-desktop-compose-example
cd podman-desktop-compose-example
+
git clone https://github.com/redhat-developer/podman-desktop-demo
cd podman-desktop-demo/guestbook-compose

Run podman compose up -d to start the application:

podman compose up -d
>>>> Executing external compose provider "/usr/local/bin/docker-compose". Please refer to the documentation for details. <<<<

[+] Running 3/3
 ✔ Container redis-replica  Started                                                                        0.0s
 ✔ Container web            Started                                                                        0.0s
 ✔ Container redis-leader   Started                                                                        0.0s

Viewing the guestbook application​

diff --git a/blog/develop-using-devcontainer.html b/blog/develop-using-devcontainer.html index adca5cc3405..abbe6ef25e8 100644 --- a/blog/develop-using-devcontainer.html +++ b/blog/develop-using-devcontainer.html @@ -13,7 +13,7 @@ - + diff --git a/blog/feed.json b/blog/feed.json index ad5ef197e3d..8069671f5a4 100644 --- a/blog/feed.json +++ b/blog/feed.json @@ -6,7 +6,7 @@ "items": [ { "id": "https://podman-desktop.io/blog/getting-started-with-compose", - "content_html": "

In this blog post we will learn how take a multi-container Compose application and use it within Podman Desktop.

\n

Objectives​

\n
    \n
  • Start the Compose YAML through podman compose up.
    • \n
  • View the guestbook web application.
    • \n
  • Confirm the web application is being synchronized and running correctly with the database.
    • \n
  • Use Podman Desktop to view, inspect and access the terminal of the Redis cluster.
    • \n
\n

What is Compose​

\n

Compose is a specification for defining and running multi-container Docker applications. With pose, you use a YAML file to configure your application’s services, networks, and volumes. This allows you to capture in a single file the entire configuration necessary to run a set of interconnected containers as an application. For example, if you have an application that requires a web server, a database, and a caching service, you can define these components and their relationships in your Compose file.

\n

To use the Compose YAML, you can use a specification implementation such as podman compose and docker compose.

\n

Before we begin​

\n

If you do not have Compose installed, let's go through the onboarding process to install the Compose implementation binary:

\n
    \n
  1. Get to Resources under Settings > Resources.
    2. \n
  2. Click Setup under Compose (it will appear if it has not been installed yet).
    3. \n
  3. Go through the onboarding process.
    4. \n
\n

\"Onboarding

\n

Confirm that you are able to run podman compose:

\n
podman compose
Run compose workloads via an external provider such as docker-compose or podman-compose

Description:
  This command is a thin wrapper around an external compose provider such as docker-compose or podman-compose.  This means that podman compose is executing another tool that implements the compose functionality but sets up the environment in a way to let the compose provider communicate transparently with the local Podman socket.  The specified options as well the command and argument are passed directly to the compose provider.
...
\n

Download and run the example application​

\n

Our example application is located at github.com/redhat-developer/podman-desktop-compose-example.

\n

We will use git clone so we can build the Go binary web application:

\n
git clone https://github.com/redhat-developer/podman-desktop-compose-example
cd podman-desktop-compose-example
\n

Run podman compose up -d to start the application:

\n
podman compose up -d
>>>> Executing external compose provider \"/usr/local/bin/docker-compose\". Please refer to the documentation for details. <<<<

[+] Running 3/3
 ✔ Container redis-replica  Started                                                                        0.0s
 ✔ Container web            Started                                                                        0.0s
 ✔ Container redis-leader   Started                                                                        0.0s
\n

Viewing the guestbook application​

\n

Within Podman Desktop, you can now see that all three containers are up and operational.

\n

Click the \"Open Browser\" button to view the web application:

\n

\"Open

\n

Within the Guestbook web application, you can:

\n
    \n
  • \"Sign\" the guestbook, which will write to the Redis leader and synchronize to the replicas.
    • \n
  • \"Read\" from the guestbook, which will read from the pool of Redis replicas. This allows for readability even if the Redis leader is unavailable.
    • \n
  • /env: View the container's environment variables.
    • \n
  • /info: View information about the Redis cluster.
    • \n
\n

\"Guestbook

\n

Viewing and modifying the database​

\n

Using Podman Desktop, you can also access the container's terminal directly from the GUI and modify the database.

\n

Click \"Open Terminal\" to access the redis-leader terminal:

\n

\"Open

\n

Modify the database as if you are doing database administration:

\n
    \n
  1. Run redis-cli within the container to access the Redis database.
    2. \n
  2. Type LPUSH guestbook \"Hello World!\" and you will see your web application update in real-time.
    3. \n
  3. Type DEL guestbook and you will see that your database drops the guestbook key and clears the database.
    4. \n
\n

\"Redis

\n

Changes will reflect in real-time on the guestbook.

\n

You can further modify the database and see the changes propagate to the Redis replicas.

\n

For example, view the logs of the redis-replica, and you will notice that there are periodic database synchronizations as well as reads to the database:

\n

\"Redis

\n

How does it work?​

\n

A quick overview of how the architecture works in this multi-container scenario:

\n
    \n
  • Within the Guestbook application, it looks for a database with the names redis-leader and redis-replica on port 6379.
    • \n
  • Because it is a Compose application, the containers are connected on the same network. This means that a neighboring container can be network-accessible simply by its container name.
    • \n
\n

There is a set of environment variables that the web application can modify in the Compose application:

\n
    \n
  • REDIS_LEADER: The default is redis-leader.
    • \n
  • REDIS_REPLICAS: The default is redis-replica. Can be comma-separated, such as redis-replica-1,redis-replica-2.
    • \n
  • REDIS_PORT: The default is 6379.
    • \n
  • SERVER_PORT: The default is 8080.
    • \n
\n

Scaling more replicas​

\n

Want to scale more replicas? This can be achieved by adding an environment variable to your compose.yaml and duplicating your redis-replica entry.

\n

Modify your compose.yaml as follows:

\n
services:
  redis-leader:
    container_name: redis-leader
    image: redis:latest
    ports:
      - '6379'

  redis-replica:
    container_name: redis-replica
    image: redis:latest
    ports:
      - '6379'
    command: redis-server --replicaof redis-leader 6379

  redis-replica-2:
    container_name: redis-replica-2
    image: redis:latest
    ports:
      - '6379'
    command: redis-server --replicaof redis-leader 6379

  web:
    container_name: web
    build: ./web
    environment:
      - REDIS_REPLICAS=redis-replica1,redis-replica2
    ports:
      - '8080:8080'
\n

Run podman compose up -d again to ensure the new container has been added and the new environment variable has propagated:

\n
podman compose up -d
>>>> Executing external compose provider \"/usr/local/bin/docker-compose\". Please refer to the documentation for details. <<<<

[+] Running 4/4
 ✔ Container redis-replica-2  Started                                                                      0.0s
 ✔ Container redis-leader     Running                                                                      0.0s
 ✔ Container web              Started                                                                      0.0s
 ✔ Container redis-replica    Running                                                                      0.0s
", + "content_html": "

In this blog post we will learn how take a multi-container Compose application and use it within Podman Desktop.

\n

Objectives​

\n
    \n
  • Start the Compose YAML through podman compose up.
    • \n
  • View the guestbook web application.
    • \n
  • Confirm the web application is being synchronized and running correctly with the database.
    • \n
  • Use Podman Desktop to view, inspect and access the terminal of the Redis cluster.
    • \n
\n

What is Compose​

\n

Compose is a specification for defining and running multi-container Docker applications. With pose, you use a YAML file to configure your application’s services, networks, and volumes. This allows you to capture in a single file the entire configuration necessary to run a set of interconnected containers as an application. For example, if you have an application that requires a web server, a database, and a caching service, you can define these components and their relationships in your Compose file.

\n

To use the Compose YAML, you can use a specification implementation such as podman compose and docker compose.

\n

Before we begin​

\n

If you do not have Compose installed, let's go through the onboarding process to install the Compose implementation binary:

\n
    \n
  1. Get to Resources under Settings > Resources.
    2. \n
  2. Click Setup under Compose (it will appear if it has not been installed yet).
    3. \n
  3. Go through the onboarding process.
    4. \n
\n

\"Onboarding

\n

Confirm that you are able to run podman compose:

\n
podman compose
Run compose workloads via an external provider such as docker-compose or podman-compose

Description:
  This command is a thin wrapper around an external compose provider such as docker-compose or podman-compose.  This means that podman compose is executing another tool that implements the compose functionality but sets up the environment in a way to let the compose provider communicate transparently with the local Podman socket.  The specified options as well the command and argument are passed directly to the compose provider.
...
\n

Download and run the example application​

\n

Our example application is located at github.com/redhat-developer/podman-desktop-demo.

\n

We will use git clone so we can build the Go binary web application:

\n
git clone https://github.com/redhat-developer/podman-desktop-demo
cd podman-desktop-demo/guestbook-compose
\n

Run podman compose up -d to start the application:

\n
podman compose up -d
>>>> Executing external compose provider \"/usr/local/bin/docker-compose\". Please refer to the documentation for details. <<<<

[+] Running 3/3
 ✔ Container redis-replica  Started                                                                        0.0s
 ✔ Container web            Started                                                                        0.0s
 ✔ Container redis-leader   Started                                                                        0.0s
\n

Viewing the guestbook application​

\n

Within Podman Desktop, you can now see that all three containers are up and operational.

\n

Click the \"Open Browser\" button to view the web application:

\n

\"Open

\n

Within the Guestbook web application, you can:

\n
    \n
  • \"Sign\" the guestbook, which will write to the Redis leader and synchronize to the replicas.
    • \n
  • \"Read\" from the guestbook, which will read from the pool of Redis replicas. This allows for readability even if the Redis leader is unavailable.
    • \n
  • /env: View the container's environment variables.
    • \n
  • /info: View information about the Redis cluster.
    • \n
\n

\"Guestbook

\n

Viewing and modifying the database​

\n

Using Podman Desktop, you can also access the container's terminal directly from the GUI and modify the database.

\n

Click \"Open Terminal\" to access the redis-leader terminal:

\n

\"Open

\n

Modify the database as if you are doing database administration:

\n
    \n
  1. Run redis-cli within the container to access the Redis database.
    2. \n
  2. Type LPUSH guestbook \"Hello World!\" and you will see your web application update in real-time.
    3. \n
  3. Type DEL guestbook and you will see that your database drops the guestbook key and clears the database.
    4. \n
\n

\"Redis

\n

Changes will reflect in real-time on the guestbook.

\n

You can further modify the database and see the changes propagate to the Redis replicas.

\n

For example, view the logs of the redis-replica, and you will notice that there are periodic database synchronizations as well as reads to the database:

\n

\"Redis

\n

How does it work?​

\n

A quick overview of how the architecture works in this multi-container scenario:

\n
    \n
  • Within the Guestbook application, it looks for a database with the names redis-leader and redis-replica on port 6379.
    • \n
  • Because it is a Compose application, the containers are connected on the same network. This means that a neighboring container can be network-accessible simply by its container name.
    • \n
\n

There is a set of environment variables that the web application can modify in the Compose application:

\n
    \n
  • REDIS_LEADER: The default is redis-leader.
    • \n
  • REDIS_REPLICAS: The default is redis-replica. Can be comma-separated, such as redis-replica-1,redis-replica-2.
    • \n
  • REDIS_PORT: The default is 6379.
    • \n
  • SERVER_PORT: The default is 8080.
    • \n
\n

Scaling more replicas​

\n

Want to scale more replicas? This can be achieved by adding an environment variable to your compose.yaml and duplicating your redis-replica entry.

\n

Modify your compose.yaml as follows:

\n
services:
  redis-leader:
    container_name: redis-leader
    image: redis:latest
    ports:
      - '6379'

  redis-replica:
    container_name: redis-replica
    image: redis:latest
    ports:
      - '6379'
    command: redis-server --replicaof redis-leader 6379

  redis-replica-2:
    container_name: redis-replica-2
    image: redis:latest
    ports:
      - '6379'
    command: redis-server --replicaof redis-leader 6379

  web:
    container_name: web
    build: ./web
    environment:
      - REDIS_REPLICAS=redis-replica1,redis-replica2
    ports:
      - '8080:8080'
\n

Run podman compose up -d again to ensure the new container has been added and the new environment variable has propagated:

\n
podman compose up -d
>>>> Executing external compose provider \"/usr/local/bin/docker-compose\". Please refer to the documentation for details. <<<<

[+] Running 4/4
 ✔ Container redis-replica-2  Started                                                                      0.0s
 ✔ Container redis-leader     Running                                                                      0.0s
 ✔ Container web              Started                                                                      0.0s
 ✔ Container redis-replica    Running                                                                      0.0s
", "url": "https://podman-desktop.io/blog/getting-started-with-compose", "title": "Getting started with Compose on Podman Desktop", "summary": "Getting started with Compose on Podman Desktop", diff --git a/blog/getting-started-with-compose.html b/blog/getting-started-with-compose.html index 98f5bae7df4..410dc9e7426 100644 --- a/blog/getting-started-with-compose.html +++ b/blog/getting-started-with-compose.html @@ -13,7 +13,7 @@ - + @@ -39,9 +39,9 @@

Confirm that you are able to run podman compose:

podman compose
Run compose workloads via an external provider such as docker-compose or podman-compose

Description:
  This command is a thin wrapper around an external compose provider such as docker-compose or podman-compose.  This means that podman compose is executing another tool that implements the compose functionality but sets up the environment in a way to let the compose provider communicate transparently with the local Podman socket.  The specified options as well the command and argument are passed directly to the compose provider.
...

Download and run the example application​

-

Our example application is located at github.com/redhat-developer/podman-desktop-compose-example.

+

Our example application is located at github.com/redhat-developer/podman-desktop-demo.

We will use git clone so we can build the Go binary web application:

-
git clone https://github.com/redhat-developer/podman-desktop-compose-example
cd podman-desktop-compose-example
+
git clone https://github.com/redhat-developer/podman-desktop-demo
cd podman-desktop-demo/guestbook-compose

Run podman compose up -d to start the application:

podman compose up -d
>>>> Executing external compose provider "/usr/local/bin/docker-compose". Please refer to the documentation for details. <<<<

[+] Running 3/3
 ✔ Container redis-replica  Started                                                                        0.0s
 ✔ Container web            Started                                                                        0.0s
 ✔ Container redis-leader   Started                                                                        0.0s

Viewing the guestbook application​

diff --git a/blog/podman-desktop-release-0.10.html b/blog/podman-desktop-release-0.10.html index 22b91e7d75f..87c57c63ed4 100644 --- a/blog/podman-desktop-release-0.10.html +++ b/blog/podman-desktop-release-0.10.html @@ -13,7 +13,7 @@ - + diff --git a/blog/podman-desktop-release-0.11.html b/blog/podman-desktop-release-0.11.html index a1118258a8a..03d1ac4f5a0 100644 --- a/blog/podman-desktop-release-0.11.html +++ b/blog/podman-desktop-release-0.11.html @@ -13,7 +13,7 @@ - + diff --git a/blog/podman-desktop-release-0.12.html b/blog/podman-desktop-release-0.12.html index c07d3ce4c89..b3df50ff0de 100644 --- a/blog/podman-desktop-release-0.12.html +++ b/blog/podman-desktop-release-0.12.html @@ -13,7 +13,7 @@ - + diff --git a/blog/podman-desktop-release-0.13.html b/blog/podman-desktop-release-0.13.html index fe395bf4e9f..a4eee0b6e80 100644 --- a/blog/podman-desktop-release-0.13.html +++ b/blog/podman-desktop-release-0.13.html @@ -13,7 +13,7 @@ - + diff --git a/blog/podman-desktop-release-0.14.html b/blog/podman-desktop-release-0.14.html index b6516326c9e..d6ef81cf493 100644 --- a/blog/podman-desktop-release-0.14.html +++ b/blog/podman-desktop-release-0.14.html @@ -13,7 +13,7 @@ - + diff --git a/blog/podman-desktop-release-0.15.html b/blog/podman-desktop-release-0.15.html index eba02f737d1..f981f99983e 100644 --- a/blog/podman-desktop-release-0.15.html +++ b/blog/podman-desktop-release-0.15.html @@ -13,7 +13,7 @@ - + diff --git a/blog/podman-desktop-release-1.0.html b/blog/podman-desktop-release-1.0.html index 715537065f7..c6776e66781 100644 --- a/blog/podman-desktop-release-1.0.html +++ b/blog/podman-desktop-release-1.0.html @@ -13,7 +13,7 @@ - + diff --git a/blog/podman-desktop-release-1.1.html b/blog/podman-desktop-release-1.1.html index cdfd97d87d3..f689e88abde 100644 --- a/blog/podman-desktop-release-1.1.html +++ b/blog/podman-desktop-release-1.1.html @@ -13,7 +13,7 @@ - + diff --git a/blog/podman-desktop-release-1.2.html b/blog/podman-desktop-release-1.2.html index 360d2981b22..ef5827ea419 100644 --- a/blog/podman-desktop-release-1.2.html +++ b/blog/podman-desktop-release-1.2.html @@ -13,7 +13,7 @@ - + diff --git a/blog/podman-desktop-release-1.3.html b/blog/podman-desktop-release-1.3.html index 2787b3a0a42..565ad721269 100644 --- a/blog/podman-desktop-release-1.3.html +++ b/blog/podman-desktop-release-1.3.html @@ -13,7 +13,7 @@ - + diff --git a/blog/podman-desktop-release-1.4.html b/blog/podman-desktop-release-1.4.html index 3709731f51b..41599c42a7b 100644 --- a/blog/podman-desktop-release-1.4.html +++ b/blog/podman-desktop-release-1.4.html @@ -13,7 +13,7 @@ - + diff --git a/blog/podman-desktop-release-1.5.html b/blog/podman-desktop-release-1.5.html index 54d8a88419b..e780251cb59 100644 --- a/blog/podman-desktop-release-1.5.html +++ b/blog/podman-desktop-release-1.5.html @@ -13,7 +13,7 @@ - + diff --git a/blog/podman-desktop-release-1.6.html b/blog/podman-desktop-release-1.6.html index 80d8eaafecc..7ffae1c4e81 100644 --- a/blog/podman-desktop-release-1.6.html +++ b/blog/podman-desktop-release-1.6.html @@ -13,7 +13,7 @@ - + diff --git a/blog/rss.xml b/blog/rss.xml index ac10a711f1a..1457b25a071 100644 --- a/blog/rss.xml +++ b/blog/rss.xml @@ -37,9 +37,9 @@

Confirm that you are able to run podman compose:

podman compose
Run compose workloads via an external provider such as docker-compose or podman-compose

Description:
  This command is a thin wrapper around an external compose provider such as docker-compose or podman-compose.  This means that podman compose is executing another tool that implements the compose functionality but sets up the environment in a way to let the compose provider communicate transparently with the local Podman socket.  The specified options as well the command and argument are passed directly to the compose provider.
...

Download and run the example application​

-

Our example application is located at github.com/redhat-developer/podman-desktop-compose-example.

+

Our example application is located at github.com/redhat-developer/podman-desktop-demo.

We will use git clone so we can build the Go binary web application:

-
git clone https://github.com/redhat-developer/podman-desktop-compose-example
cd podman-desktop-compose-example
+
git clone https://github.com/redhat-developer/podman-desktop-demo
cd podman-desktop-demo/guestbook-compose

Run podman compose up -d to start the application:

podman compose up -d
>>>> Executing external compose provider "/usr/local/bin/docker-compose". Please refer to the documentation for details. <<<<

[+] Running 3/3
 ✔ Container redis-replica  Started                                                                        0.0s
 ✔ Container web            Started                                                                        0.0s
 ✔ Container redis-leader   Started                                                                        0.0s

Viewing the guestbook application​

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 34991193c3a..9bcedf98102 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 @@ - + diff --git a/blog/sharing-podman-images-with-kubernetes-cluster.html b/blog/sharing-podman-images-with-kubernetes-cluster.html index f9b5c62a648..896d5089022 100644 --- a/blog/sharing-podman-images-with-kubernetes-cluster.html +++ b/blog/sharing-podman-images-with-kubernetes-cluster.html @@ -13,7 +13,7 @@ - + diff --git a/blog/tags.html b/blog/tags.html index 1279462f099..5d36a8307f5 100644 --- a/blog/tags.html +++ b/blog/tags.html @@ -13,7 +13,7 @@ - + diff --git a/blog/tags/codespaces.html b/blog/tags/codespaces.html index dd15e52b7b9..911bb2f0c34 100644 --- a/blog/tags/codespaces.html +++ b/blog/tags/codespaces.html @@ -13,7 +13,7 @@ - + diff --git a/blog/tags/compose.html b/blog/tags/compose.html index 26fb2387f1d..3ba0bf112d7 100644 --- a/blog/tags/compose.html +++ b/blog/tags/compose.html @@ -13,7 +13,7 @@ - + @@ -39,9 +39,9 @@

Confirm that you are able to run podman compose:

podman compose
Run compose workloads via an external provider such as docker-compose or podman-compose

Description:
  This command is a thin wrapper around an external compose provider such as docker-compose or podman-compose.  This means that podman compose is executing another tool that implements the compose functionality but sets up the environment in a way to let the compose provider communicate transparently with the local Podman socket.  The specified options as well the command and argument are passed directly to the compose provider.
...

Download and run the example application​

-

Our example application is located at github.com/redhat-developer/podman-desktop-compose-example.

+

Our example application is located at github.com/redhat-developer/podman-desktop-demo.

We will use git clone so we can build the Go binary web application:

-
git clone https://github.com/redhat-developer/podman-desktop-compose-example
cd podman-desktop-compose-example
+
git clone https://github.com/redhat-developer/podman-desktop-demo
cd podman-desktop-demo/guestbook-compose

Run podman compose up -d to start the application:

podman compose up -d
>>>> Executing external compose provider "/usr/local/bin/docker-compose". Please refer to the documentation for details. <<<<

[+] Running 3/3
 ✔ Container redis-replica  Started                                                                        0.0s
 ✔ Container web            Started                                                                        0.0s
 ✔ Container redis-leader   Started                                                                        0.0s

Viewing the guestbook application​

diff --git a/blog/tags/containerfile.html b/blog/tags/containerfile.html index 57ade9933a3..a279070ccab 100644 --- a/blog/tags/containerfile.html +++ b/blog/tags/containerfile.html @@ -13,7 +13,7 @@ - + @@ -39,9 +39,9 @@

Confirm that you are able to run podman compose:

podman compose
Run compose workloads via an external provider such as docker-compose or podman-compose

Description:
  This command is a thin wrapper around an external compose provider such as docker-compose or podman-compose.  This means that podman compose is executing another tool that implements the compose functionality but sets up the environment in a way to let the compose provider communicate transparently with the local Podman socket.  The specified options as well the command and argument are passed directly to the compose provider.
...

Download and run the example application​

-

Our example application is located at github.com/redhat-developer/podman-desktop-compose-example.

+

Our example application is located at github.com/redhat-developer/podman-desktop-demo.

We will use git clone so we can build the Go binary web application:

-
git clone https://github.com/redhat-developer/podman-desktop-compose-example
cd podman-desktop-compose-example
+
git clone https://github.com/redhat-developer/podman-desktop-demo
cd podman-desktop-demo/guestbook-compose

Run podman compose up -d to start the application:

podman compose up -d
>>>> Executing external compose provider "/usr/local/bin/docker-compose". Please refer to the documentation for details. <<<<

[+] Running 3/3
 ✔ Container redis-replica  Started                                                                        0.0s
 ✔ Container web            Started                                                                        0.0s
 ✔ Container redis-leader   Started                                                                        0.0s

Viewing the guestbook application​

diff --git a/blog/tags/containers.html b/blog/tags/containers.html index 4c98ee03407..d4eb13ee45f 100644 --- a/blog/tags/containers.html +++ b/blog/tags/containers.html @@ -13,7 +13,7 @@ - + @@ -39,9 +39,9 @@

Confirm that you are able to run podman compose:

podman compose
Run compose workloads via an external provider such as docker-compose or podman-compose

Description:
  This command is a thin wrapper around an external compose provider such as docker-compose or podman-compose.  This means that podman compose is executing another tool that implements the compose functionality but sets up the environment in a way to let the compose provider communicate transparently with the local Podman socket.  The specified options as well the command and argument are passed directly to the compose provider.
...

Download and run the example application​

-

Our example application is located at github.com/redhat-developer/podman-desktop-compose-example.

+

Our example application is located at github.com/redhat-developer/podman-desktop-demo.

We will use git clone so we can build the Go binary web application:

-
git clone https://github.com/redhat-developer/podman-desktop-compose-example
cd podman-desktop-compose-example
+
git clone https://github.com/redhat-developer/podman-desktop-demo
cd podman-desktop-demo/guestbook-compose

Run podman compose up -d to start the application:

podman compose up -d
>>>> Executing external compose provider "/usr/local/bin/docker-compose". Please refer to the documentation for details. <<<<

[+] Running 3/3
 ✔ Container redis-replica  Started                                                                        0.0s
 ✔ Container web            Started                                                                        0.0s
 ✔ Container redis-leader   Started                                                                        0.0s

Viewing the guestbook application​

diff --git a/blog/tags/devcontainer.html b/blog/tags/devcontainer.html index 1d904b7bca9..af38f9d5a0a 100644 --- a/blog/tags/devcontainer.html +++ b/blog/tags/devcontainer.html @@ -13,7 +13,7 @@ - + diff --git a/blog/tags/docker-compose.html b/blog/tags/docker-compose.html index 85b20639107..3b324d20acc 100644 --- a/blog/tags/docker-compose.html +++ b/blog/tags/docker-compose.html @@ -13,7 +13,7 @@ - + @@ -39,9 +39,9 @@

Confirm that you are able to run podman compose:

podman compose
Run compose workloads via an external provider such as docker-compose or podman-compose

Description:
  This command is a thin wrapper around an external compose provider such as docker-compose or podman-compose.  This means that podman compose is executing another tool that implements the compose functionality but sets up the environment in a way to let the compose provider communicate transparently with the local Podman socket.  The specified options as well the command and argument are passed directly to the compose provider.
...

Download and run the example application​

-

Our example application is located at github.com/redhat-developer/podman-desktop-compose-example.

+

Our example application is located at github.com/redhat-developer/podman-desktop-demo.

We will use git clone so we can build the Go binary web application:

-
git clone https://github.com/redhat-developer/podman-desktop-compose-example
cd podman-desktop-compose-example
+
git clone https://github.com/redhat-developer/podman-desktop-demo
cd podman-desktop-demo/guestbook-compose

Run podman compose up -d to start the application:

podman compose up -d
>>>> Executing external compose provider "/usr/local/bin/docker-compose". Please refer to the documentation for details. <<<<

[+] Running 3/3
 ✔ Container redis-replica  Started                                                                        0.0s
 ✔ Container web            Started                                                                        0.0s
 ✔ Container redis-leader   Started                                                                        0.0s

Viewing the guestbook application​

diff --git a/blog/tags/docker.html b/blog/tags/docker.html index b9600fe877f..a41f128c1bc 100644 --- a/blog/tags/docker.html +++ b/blog/tags/docker.html @@ -13,7 +13,7 @@ - + diff --git a/blog/tags/dockerfile.html b/blog/tags/dockerfile.html index 07e8ce4d987..f3e8ff57dda 100644 --- a/blog/tags/dockerfile.html +++ b/blog/tags/dockerfile.html @@ -13,7 +13,7 @@ - + @@ -39,9 +39,9 @@

Confirm that you are able to run podman compose:

podman compose
Run compose workloads via an external provider such as docker-compose or podman-compose

Description:
  This command is a thin wrapper around an external compose provider such as docker-compose or podman-compose.  This means that podman compose is executing another tool that implements the compose functionality but sets up the environment in a way to let the compose provider communicate transparently with the local Podman socket.  The specified options as well the command and argument are passed directly to the compose provider.
...

Download and run the example application​

-

Our example application is located at github.com/redhat-developer/podman-desktop-compose-example.

+

Our example application is located at github.com/redhat-developer/podman-desktop-demo.

We will use git clone so we can build the Go binary web application:

-
git clone https://github.com/redhat-developer/podman-desktop-compose-example
cd podman-desktop-compose-example
+
git clone https://github.com/redhat-developer/podman-desktop-demo
cd podman-desktop-demo/guestbook-compose

Run podman compose up -d to start the application:

podman compose up -d
>>>> Executing external compose provider "/usr/local/bin/docker-compose". Please refer to the documentation for details. <<<<

[+] Running 3/3
 ✔ Container redis-replica  Started                                                                        0.0s
 ✔ Container web            Started                                                                        0.0s
 ✔ Container redis-leader   Started                                                                        0.0s

Viewing the guestbook application​

diff --git a/blog/tags/extensions.html b/blog/tags/extensions.html index aab3bbc13ee..68b449b37d2 100644 --- a/blog/tags/extensions.html +++ b/blog/tags/extensions.html @@ -13,7 +13,7 @@ - + diff --git a/blog/tags/images.html b/blog/tags/images.html index 665b846805c..0b0c9bf6048 100644 --- a/blog/tags/images.html +++ b/blog/tags/images.html @@ -13,7 +13,7 @@ - + diff --git a/blog/tags/kind.html b/blog/tags/kind.html index d310f596742..7d280238c0a 100644 --- a/blog/tags/kind.html +++ b/blog/tags/kind.html @@ -13,7 +13,7 @@ - + diff --git a/blog/tags/kubernetes.html b/blog/tags/kubernetes.html index 748ba8c92d9..bdf38d32f28 100644 --- a/blog/tags/kubernetes.html +++ b/blog/tags/kubernetes.html @@ -13,7 +13,7 @@ - + diff --git a/blog/tags/migrating.html b/blog/tags/migrating.html index d99bd2e3f42..9993134ded4 100644 --- a/blog/tags/migrating.html +++ b/blog/tags/migrating.html @@ -13,7 +13,7 @@ - + diff --git a/blog/tags/multi-container.html b/blog/tags/multi-container.html index 611fcbee717..0f3838dd02a 100644 --- a/blog/tags/multi-container.html +++ b/blog/tags/multi-container.html @@ -13,7 +13,7 @@ - + @@ -39,9 +39,9 @@

Confirm that you are able to run podman compose:

podman compose
Run compose workloads via an external provider such as docker-compose or podman-compose

Description:
  This command is a thin wrapper around an external compose provider such as docker-compose or podman-compose.  This means that podman compose is executing another tool that implements the compose functionality but sets up the environment in a way to let the compose provider communicate transparently with the local Podman socket.  The specified options as well the command and argument are passed directly to the compose provider.
...

Download and run the example application​

-

Our example application is located at github.com/redhat-developer/podman-desktop-compose-example.

+

Our example application is located at github.com/redhat-developer/podman-desktop-demo.

We will use git clone so we can build the Go binary web application:

-
git clone https://github.com/redhat-developer/podman-desktop-compose-example
cd podman-desktop-compose-example
+
git clone https://github.com/redhat-developer/podman-desktop-demo
cd podman-desktop-demo/guestbook-compose

Run podman compose up -d to start the application:

podman compose up -d
>>>> Executing external compose provider "/usr/local/bin/docker-compose". Please refer to the documentation for details. <<<<

[+] Running 3/3
 ✔ Container redis-replica  Started                                                                        0.0s
 ✔ Container web            Started                                                                        0.0s
 ✔ Container redis-leader   Started                                                                        0.0s

Viewing the guestbook application​

diff --git a/blog/tags/onboarding.html b/blog/tags/onboarding.html index 49a3ba0098c..c43d5f8ab34 100644 --- a/blog/tags/onboarding.html +++ b/blog/tags/onboarding.html @@ -13,7 +13,7 @@ - + diff --git a/blog/tags/openshift.html b/blog/tags/openshift.html index 2a6aaba13ea..972d9803001 100644 --- a/blog/tags/openshift.html +++ b/blog/tags/openshift.html @@ -13,7 +13,7 @@ - + diff --git a/blog/tags/podman-desktop.html b/blog/tags/podman-desktop.html index f9fce41e5b7..d78f93945a8 100644 --- a/blog/tags/podman-desktop.html +++ b/blog/tags/podman-desktop.html @@ -13,7 +13,7 @@ - + @@ -39,9 +39,9 @@

Confirm that you are able to run podman compose:

podman compose
Run compose workloads via an external provider such as docker-compose or podman-compose

Description:
  This command is a thin wrapper around an external compose provider such as docker-compose or podman-compose.  This means that podman compose is executing another tool that implements the compose functionality but sets up the environment in a way to let the compose provider communicate transparently with the local Podman socket.  The specified options as well the command and argument are passed directly to the compose provider.
...

Download and run the example application​

-

Our example application is located at github.com/redhat-developer/podman-desktop-compose-example.

+

Our example application is located at github.com/redhat-developer/podman-desktop-demo.

We will use git clone so we can build the Go binary web application:

-
git clone https://github.com/redhat-developer/podman-desktop-compose-example
cd podman-desktop-compose-example
+
git clone https://github.com/redhat-developer/podman-desktop-demo
cd podman-desktop-demo/guestbook-compose

Run podman compose up -d to start the application:

podman compose up -d
>>>> Executing external compose provider "/usr/local/bin/docker-compose". Please refer to the documentation for details. <<<<

[+] Running 3/3
 ✔ Container redis-replica  Started                                                                        0.0s
 ✔ Container web            Started                                                                        0.0s
 ✔ Container redis-leader   Started                                                                        0.0s

Viewing the guestbook application​

diff --git a/blog/tags/podman.html b/blog/tags/podman.html index 699cb81177f..928a6e1f393 100644 --- a/blog/tags/podman.html +++ b/blog/tags/podman.html @@ -13,7 +13,7 @@ - + diff --git a/blog/tags/release.html b/blog/tags/release.html index 1ebdb6c31e3..0f937240f24 100644 --- a/blog/tags/release.html +++ b/blog/tags/release.html @@ -13,7 +13,7 @@ - + diff --git a/blog/tags/settings.html b/blog/tags/settings.html index 986c64dcdb0..8a0ac39bfd0 100644 --- a/blog/tags/settings.html +++ b/blog/tags/settings.html @@ -13,7 +13,7 @@ - + diff --git a/blog/tags/story.html b/blog/tags/story.html index d06435c491f..857d126c348 100644 --- a/blog/tags/story.html +++ b/blog/tags/story.html @@ -13,7 +13,7 @@ - + @@ -39,9 +39,9 @@

Confirm that you are able to run podman compose:

podman compose
Run compose workloads via an external provider such as docker-compose or podman-compose

Description:
  This command is a thin wrapper around an external compose provider such as docker-compose or podman-compose.  This means that podman compose is executing another tool that implements the compose functionality but sets up the environment in a way to let the compose provider communicate transparently with the local Podman socket.  The specified options as well the command and argument are passed directly to the compose provider.
...

Download and run the example application​

-

Our example application is located at github.com/redhat-developer/podman-desktop-compose-example.

+

Our example application is located at github.com/redhat-developer/podman-desktop-demo.

We will use git clone so we can build the Go binary web application:

-
git clone https://github.com/redhat-developer/podman-desktop-compose-example
cd podman-desktop-compose-example
+
git clone https://github.com/redhat-developer/podman-desktop-demo
cd podman-desktop-demo/guestbook-compose

Run podman compose up -d to start the application:

podman compose up -d
>>>> Executing external compose provider "/usr/local/bin/docker-compose". Please refer to the documentation for details. <<<<

[+] Running 3/3
 ✔ Container redis-replica  Started                                                                        0.0s
 ✔ Container web            Started                                                                        0.0s
 ✔ Container redis-leader   Started                                                                        0.0s

Viewing the guestbook application​

diff --git a/core-values.html b/core-values.html index c674d8eff84..9460ce549fb 100644 --- a/core-values.html +++ b/core-values.html @@ -13,7 +13,7 @@ - + diff --git a/docs/compose.html b/docs/compose.html index dcd16dca958..64354906c44 100644 --- a/docs/compose.html +++ b/docs/compose.html @@ -13,7 +13,7 @@ - + diff --git a/docs/compose/running-compose.html b/docs/compose/running-compose.html index bec713a8281..8227a5312d2 100644 --- a/docs/compose/running-compose.html +++ b/docs/compose/running-compose.html @@ -13,7 +13,7 @@ - + diff --git a/docs/compose/setting-up-compose.html b/docs/compose/setting-up-compose.html index 2076d6b23cf..07c5eb83387 100644 --- a/docs/compose/setting-up-compose.html +++ b/docs/compose/setting-up-compose.html @@ -13,7 +13,7 @@ - + diff --git a/docs/containers.html b/docs/containers.html index 4da856e5c62..d0be48be3d6 100644 --- a/docs/containers.html +++ b/docs/containers.html @@ -13,7 +13,7 @@ - + diff --git a/docs/containers/creating-a-pod.html b/docs/containers/creating-a-pod.html index 1d981e9d101..447750dbe1b 100644 --- a/docs/containers/creating-a-pod.html +++ b/docs/containers/creating-a-pod.html @@ -13,7 +13,7 @@ - + diff --git a/docs/containers/images.html b/docs/containers/images.html index d1f4bd0817e..e0af1c12f1c 100644 --- a/docs/containers/images.html +++ b/docs/containers/images.html @@ -13,7 +13,7 @@ - + diff --git a/docs/containers/images/building-an-image.html b/docs/containers/images/building-an-image.html index d10be180c6c..f3ad461ea0c 100644 --- a/docs/containers/images/building-an-image.html +++ b/docs/containers/images/building-an-image.html @@ -13,7 +13,7 @@ - + diff --git a/docs/containers/images/pulling-an-image.html b/docs/containers/images/pulling-an-image.html index 20cf11eea35..e64633fa76e 100644 --- a/docs/containers/images/pulling-an-image.html +++ b/docs/containers/images/pulling-an-image.html @@ -13,7 +13,7 @@ - + diff --git a/docs/containers/images/pushing-an-image-to-a-registry.html b/docs/containers/images/pushing-an-image-to-a-registry.html index e8638cb1845..7691937dd08 100644 --- a/docs/containers/images/pushing-an-image-to-a-registry.html +++ b/docs/containers/images/pushing-an-image-to-a-registry.html @@ -13,7 +13,7 @@ - + diff --git a/docs/containers/onboarding.html b/docs/containers/onboarding.html index 8e31b0a1362..9a18c4dec8a 100644 --- a/docs/containers/onboarding.html +++ b/docs/containers/onboarding.html @@ -13,7 +13,7 @@ - + diff --git a/docs/containers/registries.html b/docs/containers/registries.html index 65d6d7eca9a..47941c0fd1e 100644 --- a/docs/containers/registries.html +++ b/docs/containers/registries.html @@ -13,7 +13,7 @@ - + diff --git a/docs/containers/starting-a-container.html b/docs/containers/starting-a-container.html index 1eb76a26681..a23535d886b 100644 --- a/docs/containers/starting-a-container.html +++ b/docs/containers/starting-a-container.html @@ -13,7 +13,7 @@ - + diff --git a/docs/extensions.html b/docs/extensions.html index 9c761c71083..e77ab08eed9 100644 --- a/docs/extensions.html +++ b/docs/extensions.html @@ -13,7 +13,7 @@ - + diff --git a/docs/extensions/install.html b/docs/extensions/install.html index 42d020bc52b..14538b91e81 100644 --- a/docs/extensions/install.html +++ b/docs/extensions/install.html @@ -13,7 +13,7 @@ - + diff --git a/docs/extensions/publish.html b/docs/extensions/publish.html index fb6b91cca8a..bc4a81c1a26 100644 --- a/docs/extensions/publish.html +++ b/docs/extensions/publish.html @@ -13,7 +13,7 @@ - + diff --git a/docs/extensions/write.html b/docs/extensions/write.html index 1b5b853c70a..551c14dbfe9 100644 --- a/docs/extensions/write.html +++ b/docs/extensions/write.html @@ -13,7 +13,7 @@ - + diff --git a/docs/extensions/write/onboarding-workflow.html b/docs/extensions/write/onboarding-workflow.html index f178398f0dc..e57810f3196 100644 --- a/docs/extensions/write/onboarding-workflow.html +++ b/docs/extensions/write/onboarding-workflow.html @@ -13,7 +13,7 @@ - + diff --git a/docs/extensions/write/when-clause-context.html b/docs/extensions/write/when-clause-context.html index e8dfdf1dc06..cb0813df715 100644 --- a/docs/extensions/write/when-clause-context.html +++ b/docs/extensions/write/when-clause-context.html @@ -13,7 +13,7 @@ - + diff --git a/docs/installation.html b/docs/installation.html index 68089bc6d78..3e1b8beac90 100644 --- a/docs/installation.html +++ b/docs/installation.html @@ -13,7 +13,7 @@ - + diff --git a/docs/installation/linux-install.html b/docs/installation/linux-install.html index ad68d64fe49..25066656fbd 100644 --- a/docs/installation/linux-install.html +++ b/docs/installation/linux-install.html @@ -13,7 +13,7 @@ - + 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 33f1f76161e..2ef62aac4d6 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,7 +13,7 @@ - + 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 55d25e2c2a4..a616d7c0931 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,7 +13,7 @@ - + diff --git a/docs/installation/macos-install.html b/docs/installation/macos-install.html index d1959239cad..9497044375b 100644 --- a/docs/installation/macos-install.html +++ b/docs/installation/macos-install.html @@ -13,7 +13,7 @@ - + diff --git a/docs/installation/windows-install.html b/docs/installation/windows-install.html index 681673190b3..d9e0ea83ea3 100644 --- a/docs/installation/windows-install.html +++ b/docs/installation/windows-install.html @@ -13,7 +13,7 @@ - + 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 820bbfe601c..4508b40029c 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,7 +13,7 @@ - + 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 844f101d0c6..79bcc1e148e 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,7 +13,7 @@ - + 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 08b9e263e91..7770d45ea83 100644 --- a/docs/installation/windows-install/installing-podman-desktop-with-chocolatey.html +++ b/docs/installation/windows-install/installing-podman-desktop-with-chocolatey.html @@ -13,7 +13,7 @@ - + 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 672cb071bc9..7ce25239be4 100644 --- a/docs/installation/windows-install/installing-podman-desktop-with-scoop.html +++ b/docs/installation/windows-install/installing-podman-desktop-with-scoop.html @@ -13,7 +13,7 @@ - + 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 ef60ba625f4..af683ec9722 100644 --- a/docs/installation/windows-install/installing-podman-desktop-with-winget.html +++ b/docs/installation/windows-install/installing-podman-desktop-with-winget.html @@ -13,7 +13,7 @@ - + diff --git a/docs/intro.html b/docs/intro.html index e7078ee110e..18aa79b0245 100644 --- a/docs/intro.html +++ b/docs/intro.html @@ -13,7 +13,7 @@ - + diff --git a/docs/kind.html b/docs/kind.html index 92e6adc7d4f..e4a7489f08c 100644 --- a/docs/kind.html +++ b/docs/kind.html @@ -13,7 +13,7 @@ - + diff --git a/docs/kind/building-an-image-and-testing-it-in-kind.html b/docs/kind/building-an-image-and-testing-it-in-kind.html index 33717fac600..c201966af5a 100644 --- a/docs/kind/building-an-image-and-testing-it-in-kind.html +++ b/docs/kind/building-an-image-and-testing-it-in-kind.html @@ -13,7 +13,7 @@ - + diff --git a/docs/kind/configuring-podman-for-kind-on-windows.html b/docs/kind/configuring-podman-for-kind-on-windows.html index e09a221cab6..c4789a210a2 100644 --- a/docs/kind/configuring-podman-for-kind-on-windows.html +++ b/docs/kind/configuring-podman-for-kind-on-windows.html @@ -13,7 +13,7 @@ - + diff --git a/docs/kind/creating-a-kind-cluster.html b/docs/kind/creating-a-kind-cluster.html index 1582226cdcf..12aa4f5b224 100644 --- a/docs/kind/creating-a-kind-cluster.html +++ b/docs/kind/creating-a-kind-cluster.html @@ -13,7 +13,7 @@ - + diff --git a/docs/kind/deleting-your-kind-cluster.html b/docs/kind/deleting-your-kind-cluster.html index 6280fdd0921..bcf81dac538 100644 --- a/docs/kind/deleting-your-kind-cluster.html +++ b/docs/kind/deleting-your-kind-cluster.html @@ -13,7 +13,7 @@ - + diff --git a/docs/kind/installing.html b/docs/kind/installing.html index eabcee725f4..560c655934e 100644 --- a/docs/kind/installing.html +++ b/docs/kind/installing.html @@ -13,7 +13,7 @@ - + diff --git a/docs/kind/pushing-an-image-to-kind.html b/docs/kind/pushing-an-image-to-kind.html index 0bb0b796fae..2304c08c97c 100644 --- a/docs/kind/pushing-an-image-to-kind.html +++ b/docs/kind/pushing-an-image-to-kind.html @@ -13,7 +13,7 @@ - + diff --git a/docs/kind/restarting-your-kind-cluster.html b/docs/kind/restarting-your-kind-cluster.html index 22f1bc9cfd9..c730e9d26df 100644 --- a/docs/kind/restarting-your-kind-cluster.html +++ b/docs/kind/restarting-your-kind-cluster.html @@ -13,7 +13,7 @@ - + diff --git a/docs/kind/working-with-your-local-kind-cluster.html b/docs/kind/working-with-your-local-kind-cluster.html index 59a7e1d4057..a708e7cc7a3 100644 --- a/docs/kind/working-with-your-local-kind-cluster.html +++ b/docs/kind/working-with-your-local-kind-cluster.html @@ -13,7 +13,7 @@ - + diff --git a/docs/kubernetes.html b/docs/kubernetes.html index 00a09faa14f..6d6119527a8 100644 --- a/docs/kubernetes.html +++ b/docs/kubernetes.html @@ -13,7 +13,7 @@ - + diff --git a/docs/kubernetes/deploying-a-container-to-kubernetes.html b/docs/kubernetes/deploying-a-container-to-kubernetes.html index 12f80b175f9..fc97732f992 100644 --- a/docs/kubernetes/deploying-a-container-to-kubernetes.html +++ b/docs/kubernetes/deploying-a-container-to-kubernetes.html @@ -13,7 +13,7 @@ - + diff --git a/docs/kubernetes/deploying-a-pod-to-kubernetes.html b/docs/kubernetes/deploying-a-pod-to-kubernetes.html index 09f8188fa67..bf84de27402 100644 --- a/docs/kubernetes/deploying-a-pod-to-kubernetes.html +++ b/docs/kubernetes/deploying-a-pod-to-kubernetes.html @@ -13,7 +13,7 @@ - + diff --git a/docs/kubernetes/existing-kubernetes.html b/docs/kubernetes/existing-kubernetes.html index 3fcf239e7e7..66a48d368a1 100644 --- a/docs/kubernetes/existing-kubernetes.html +++ b/docs/kubernetes/existing-kubernetes.html @@ -13,7 +13,7 @@ - + diff --git a/docs/kubernetes/kind/pushing-an-image-to-kind.html b/docs/kubernetes/kind/pushing-an-image-to-kind.html index 65e7bfcb618..7d01429d042 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 @@ - + diff --git a/docs/kubernetes/lima/pushing-an-image-to-lima.html b/docs/kubernetes/lima/pushing-an-image-to-lima.html index 717419e9064..2b300d868d4 100644 --- a/docs/kubernetes/lima/pushing-an-image-to-lima.html +++ b/docs/kubernetes/lima/pushing-an-image-to-lima.html @@ -13,7 +13,7 @@ - + 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 e5799946756..4356f73d75d 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,7 +13,7 @@ - + diff --git a/docs/kubernetes/viewing-and-selecting-current-kubernete-context.html b/docs/kubernetes/viewing-and-selecting-current-kubernete-context.html index 702333da677..b8cb2d96c09 100644 --- a/docs/kubernetes/viewing-and-selecting-current-kubernete-context.html +++ b/docs/kubernetes/viewing-and-selecting-current-kubernete-context.html @@ -13,7 +13,7 @@ - + diff --git a/docs/lima.html b/docs/lima.html index cac328d3244..e6fdb5c60dd 100644 --- a/docs/lima.html +++ b/docs/lima.html @@ -13,7 +13,7 @@ - + diff --git a/docs/lima/creating-a-kubernetes-instance.html b/docs/lima/creating-a-kubernetes-instance.html index fc2f36ae5f3..b45f5c3a508 100644 --- a/docs/lima/creating-a-kubernetes-instance.html +++ b/docs/lima/creating-a-kubernetes-instance.html @@ -13,7 +13,7 @@ - + diff --git a/docs/lima/creating-a-lima-instance.html b/docs/lima/creating-a-lima-instance.html index 985e6f12a2e..6c75256280b 100644 --- a/docs/lima/creating-a-lima-instance.html +++ b/docs/lima/creating-a-lima-instance.html @@ -13,7 +13,7 @@ - + diff --git a/docs/lima/customizing.html b/docs/lima/customizing.html index 9e4df83f423..ab85d6c151a 100644 --- a/docs/lima/customizing.html +++ b/docs/lima/customizing.html @@ -13,7 +13,7 @@ - + diff --git a/docs/lima/installing.html b/docs/lima/installing.html index 9080ca0e0b0..cf8df915efc 100644 --- a/docs/lima/installing.html +++ b/docs/lima/installing.html @@ -13,7 +13,7 @@ - + diff --git a/docs/migrating-from-docker.html b/docs/migrating-from-docker.html index 076ed590e63..b7fc4568bf4 100644 --- a/docs/migrating-from-docker.html +++ b/docs/migrating-from-docker.html @@ -13,7 +13,7 @@ - + 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 a87fc4f991f..5fc4fb68152 100644 --- a/docs/migrating-from-docker/emulating-docker-cli-with-podman.html +++ b/docs/migrating-from-docker/emulating-docker-cli-with-podman.html @@ -13,7 +13,7 @@ - + diff --git a/docs/migrating-from-docker/importing-saved-containers.html b/docs/migrating-from-docker/importing-saved-containers.html index 11cd1e0ba09..5dfd6105549 100644 --- a/docs/migrating-from-docker/importing-saved-containers.html +++ b/docs/migrating-from-docker/importing-saved-containers.html @@ -13,7 +13,7 @@ - + diff --git a/docs/migrating-from-docker/using-podman-mac-helper.html b/docs/migrating-from-docker/using-podman-mac-helper.html index 6f7ad42c9cd..3e191220ee9 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 @@ - + 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 510ad052ba7..f9b4fb17546 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,7 +13,7 @@ - + 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 c815d51f413..a4227539409 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,7 +13,7 @@ - + diff --git a/docs/minikube.html b/docs/minikube.html index 1eeb982b825..377cbd580fd 100644 --- a/docs/minikube.html +++ b/docs/minikube.html @@ -13,7 +13,7 @@ - + diff --git a/docs/minikube/building-an-image-and-testing-it-in-minikube.html b/docs/minikube/building-an-image-and-testing-it-in-minikube.html index 40d6195f93e..e1ff2a54075 100644 --- a/docs/minikube/building-an-image-and-testing-it-in-minikube.html +++ b/docs/minikube/building-an-image-and-testing-it-in-minikube.html @@ -13,7 +13,7 @@ - + diff --git a/docs/minikube/configuring-podman-for-minikube-on-windows.html b/docs/minikube/configuring-podman-for-minikube-on-windows.html index cb925acdef1..028f51748f7 100644 --- a/docs/minikube/configuring-podman-for-minikube-on-windows.html +++ b/docs/minikube/configuring-podman-for-minikube-on-windows.html @@ -13,7 +13,7 @@ - + diff --git a/docs/minikube/creating-a-minikube-cluster.html b/docs/minikube/creating-a-minikube-cluster.html index 50f49bd6d5a..58a0cca76c7 100644 --- a/docs/minikube/creating-a-minikube-cluster.html +++ b/docs/minikube/creating-a-minikube-cluster.html @@ -13,7 +13,7 @@ - + diff --git a/docs/minikube/deleting-your-minikube-cluster.html b/docs/minikube/deleting-your-minikube-cluster.html index d51fac4e995..386644fdddd 100644 --- a/docs/minikube/deleting-your-minikube-cluster.html +++ b/docs/minikube/deleting-your-minikube-cluster.html @@ -13,7 +13,7 @@ - + diff --git a/docs/minikube/installing.html b/docs/minikube/installing.html index f7cec2a1002..e270ac85f8f 100644 --- a/docs/minikube/installing.html +++ b/docs/minikube/installing.html @@ -13,7 +13,7 @@ - + diff --git a/docs/minikube/pushing-an-image-to-minikube.html b/docs/minikube/pushing-an-image-to-minikube.html index 5e4b0e780bc..e1e5328b811 100644 --- a/docs/minikube/pushing-an-image-to-minikube.html +++ b/docs/minikube/pushing-an-image-to-minikube.html @@ -13,7 +13,7 @@ - + diff --git a/docs/minikube/restarting-your-minikube-cluster.html b/docs/minikube/restarting-your-minikube-cluster.html index 1df09e54447..f1563085a3d 100644 --- a/docs/minikube/restarting-your-minikube-cluster.html +++ b/docs/minikube/restarting-your-minikube-cluster.html @@ -13,7 +13,7 @@ - + diff --git a/docs/minikube/working-with-your-local-minikube-cluster.html b/docs/minikube/working-with-your-local-minikube-cluster.html index e177bc33b36..b0add05af51 100644 --- a/docs/minikube/working-with-your-local-minikube-cluster.html +++ b/docs/minikube/working-with-your-local-minikube-cluster.html @@ -13,7 +13,7 @@ - + diff --git a/docs/openshift.html b/docs/openshift.html index ff6f1f1488c..c5fe34b0d98 100644 --- a/docs/openshift.html +++ b/docs/openshift.html @@ -13,7 +13,7 @@ - + diff --git a/docs/openshift/developer-sandbox.html b/docs/openshift/developer-sandbox.html index 735ddc5b6ad..ed8c3dcf369 100644 --- a/docs/openshift/developer-sandbox.html +++ b/docs/openshift/developer-sandbox.html @@ -13,7 +13,7 @@ - + diff --git a/docs/openshift/openshift-local.html b/docs/openshift/openshift-local.html index 62579f18058..234a59d911a 100644 --- a/docs/openshift/openshift-local.html +++ b/docs/openshift/openshift-local.html @@ -13,7 +13,7 @@ - + diff --git a/docs/podman.html b/docs/podman.html index 1f53e2d81aa..8cd5305e0b6 100644 --- a/docs/podman.html +++ b/docs/podman.html @@ -13,7 +13,7 @@ - + diff --git a/docs/podman/creating-a-podman-machine.html b/docs/podman/creating-a-podman-machine.html index a0e8c2ecb2a..cafa26a8f6a 100644 --- a/docs/podman/creating-a-podman-machine.html +++ b/docs/podman/creating-a-podman-machine.html @@ -13,7 +13,7 @@ - + diff --git a/docs/podman/installing-podman-with-openshift-local-on-windows.html b/docs/podman/installing-podman-with-openshift-local-on-windows.html index f92642cee1d..3fa289c6af2 100644 --- a/docs/podman/installing-podman-with-openshift-local-on-windows.html +++ b/docs/podman/installing-podman-with-openshift-local-on-windows.html @@ -13,7 +13,7 @@ - + diff --git a/docs/podman/installing.html b/docs/podman/installing.html index 12e26a31e68..fd774155022 100644 --- a/docs/podman/installing.html +++ b/docs/podman/installing.html @@ -13,7 +13,7 @@ - + diff --git a/docs/podman/setting-podman-machine-default-connection.html b/docs/podman/setting-podman-machine-default-connection.html index d1cf9567418..d234264da9a 100644 --- a/docs/podman/setting-podman-machine-default-connection.html +++ b/docs/podman/setting-podman-machine-default-connection.html @@ -13,7 +13,7 @@ - + diff --git a/docs/proxy.html b/docs/proxy.html index 2e517f9811f..94f0bfc8291 100644 --- a/docs/proxy.html +++ b/docs/proxy.html @@ -13,7 +13,7 @@ - + diff --git a/docs/proxy/using-a-proxy-in-your-containers.html b/docs/proxy/using-a-proxy-in-your-containers.html index 64506dcedef..909cc4d61d2 100644 --- a/docs/proxy/using-a-proxy-in-your-containers.html +++ b/docs/proxy/using-a-proxy-in-your-containers.html @@ -13,7 +13,7 @@ - + diff --git a/docs/proxy/using-a-proxy-on-linux.html b/docs/proxy/using-a-proxy-on-linux.html index 0280c24b6fd..ae8bb1b1bf9 100644 --- a/docs/proxy/using-a-proxy-on-linux.html +++ b/docs/proxy/using-a-proxy-on-linux.html @@ -13,7 +13,7 @@ - + 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 f7fc87864f1..68b7694daee 100644 --- a/docs/proxy/using-a-proxy-requiring-a-custom-ca.html +++ b/docs/proxy/using-a-proxy-requiring-a-custom-ca.html @@ -13,7 +13,7 @@ - + diff --git a/docs/proxy/using-a-proxy.html b/docs/proxy/using-a-proxy.html index 16807344466..1d313db2034 100644 --- a/docs/proxy/using-a-proxy.html +++ b/docs/proxy/using-a-proxy.html @@ -13,7 +13,7 @@ - + diff --git a/docs/proxy/using-a-vpn-on-windows.html b/docs/proxy/using-a-vpn-on-windows.html index 0ed7979ce84..ff0b3b4da40 100644 --- a/docs/proxy/using-a-vpn-on-windows.html +++ b/docs/proxy/using-a-vpn-on-windows.html @@ -13,7 +13,7 @@ - + diff --git a/docs/tags.html b/docs/tags.html index c6417c40f0a..945050ccbe0 100644 --- a/docs/tags.html +++ b/docs/tags.html @@ -13,7 +13,7 @@ - + diff --git a/docs/tags/chocolatey.html b/docs/tags/chocolatey.html index 77b18684859..ba84f5f53b9 100644 --- a/docs/tags/chocolatey.html +++ b/docs/tags/chocolatey.html @@ -13,7 +13,7 @@ - + diff --git a/docs/tags/compose.html b/docs/tags/compose.html index 699b67b340b..292635563bf 100644 --- a/docs/tags/compose.html +++ b/docs/tags/compose.html @@ -13,7 +13,7 @@ - + diff --git a/docs/tags/containers.html b/docs/tags/containers.html index 015013dc659..a095bb7967c 100644 --- a/docs/tags/containers.html +++ b/docs/tags/containers.html @@ -13,7 +13,7 @@ - + diff --git a/docs/tags/docker.html b/docs/tags/docker.html index d43a369b5d9..cf8967a098e 100644 --- a/docs/tags/docker.html +++ b/docs/tags/docker.html @@ -13,7 +13,7 @@ - + diff --git a/docs/tags/extension.html b/docs/tags/extension.html index f46b090bc6f..3119f5137ee 100644 --- a/docs/tags/extension.html +++ b/docs/tags/extension.html @@ -13,7 +13,7 @@ - + diff --git a/docs/tags/flathub.html b/docs/tags/flathub.html index cdb61f6c80d..e8e4a30e1ae 100644 --- a/docs/tags/flathub.html +++ b/docs/tags/flathub.html @@ -13,7 +13,7 @@ - + diff --git a/docs/tags/flatpak.html b/docs/tags/flatpak.html index 55c11017ffc..c5313baa841 100644 --- a/docs/tags/flatpak.html +++ b/docs/tags/flatpak.html @@ -13,7 +13,7 @@ - + diff --git a/docs/tags/images.html b/docs/tags/images.html index e2f336d9dc4..11e5f63c608 100644 --- a/docs/tags/images.html +++ b/docs/tags/images.html @@ -13,7 +13,7 @@ - + diff --git a/docs/tags/installing.html b/docs/tags/installing.html index 66ce8de9e95..fb4a059d554 100644 --- a/docs/tags/installing.html +++ b/docs/tags/installing.html @@ -13,7 +13,7 @@ - + diff --git a/docs/tags/kind.html b/docs/tags/kind.html index 9b1acc9ad3b..3efa5b13b7c 100644 --- a/docs/tags/kind.html +++ b/docs/tags/kind.html @@ -13,7 +13,7 @@ - + diff --git a/docs/tags/kubernetes.html b/docs/tags/kubernetes.html index 7801266e068..055e2cf29fa 100644 --- a/docs/tags/kubernetes.html +++ b/docs/tags/kubernetes.html @@ -13,7 +13,7 @@ - + diff --git a/docs/tags/lima.html b/docs/tags/lima.html index ed7a7d50949..15afa9d4137 100644 --- a/docs/tags/lima.html +++ b/docs/tags/lima.html @@ -13,7 +13,7 @@ - + diff --git a/docs/tags/linux.html b/docs/tags/linux.html index 7c78457c5c7..837f51a3102 100644 --- a/docs/tags/linux.html +++ b/docs/tags/linux.html @@ -13,7 +13,7 @@ - + diff --git a/docs/tags/mac-0-s.html b/docs/tags/mac-0-s.html index 0cb05ab1a2c..076ea302636 100644 --- a/docs/tags/mac-0-s.html +++ b/docs/tags/mac-0-s.html @@ -13,7 +13,7 @@ - + diff --git a/docs/tags/mac-os.html b/docs/tags/mac-os.html index d7ee8b9252d..7ab5feb1c6c 100644 --- a/docs/tags/mac-os.html +++ b/docs/tags/mac-os.html @@ -13,7 +13,7 @@ - + diff --git a/docs/tags/macos.html b/docs/tags/macos.html index 5aae046fbe4..64c4b5ab006 100644 --- a/docs/tags/macos.html +++ b/docs/tags/macos.html @@ -13,7 +13,7 @@ - + diff --git a/docs/tags/migrating-from-docker.html b/docs/tags/migrating-from-docker.html index cb96c840e19..7fbda674b5a 100644 --- a/docs/tags/migrating-from-docker.html +++ b/docs/tags/migrating-from-docker.html @@ -13,7 +13,7 @@ - + diff --git a/docs/tags/migrating-to-kubernetes.html b/docs/tags/migrating-to-kubernetes.html index 0d21ad7d586..0043dd61b61 100644 --- a/docs/tags/migrating-to-kubernetes.html +++ b/docs/tags/migrating-to-kubernetes.html @@ -13,7 +13,7 @@ - + diff --git a/docs/tags/minikube.html b/docs/tags/minikube.html index ca31dceb7b6..1a97d2e9413 100644 --- a/docs/tags/minikube.html +++ b/docs/tags/minikube.html @@ -13,7 +13,7 @@ - + diff --git a/docs/tags/onboarding.html b/docs/tags/onboarding.html index a328b8735f6..97bdbc6e72e 100644 --- a/docs/tags/onboarding.html +++ b/docs/tags/onboarding.html @@ -13,7 +13,7 @@ - + diff --git a/docs/tags/openshift-local.html b/docs/tags/openshift-local.html index 2c2619a7d0d..15480bd6969 100644 --- a/docs/tags/openshift-local.html +++ b/docs/tags/openshift-local.html @@ -13,7 +13,7 @@ - + diff --git a/docs/tags/openshift.html b/docs/tags/openshift.html index 1286b0f65fd..b45a1df8bc8 100644 --- a/docs/tags/openshift.html +++ b/docs/tags/openshift.html @@ -13,7 +13,7 @@ - + diff --git a/docs/tags/podman-desktop.html b/docs/tags/podman-desktop.html index 7af5a6b1fe8..a0f1d8b129c 100644 --- a/docs/tags/podman-desktop.html +++ b/docs/tags/podman-desktop.html @@ -13,7 +13,7 @@ - + diff --git a/docs/tags/podman.html b/docs/tags/podman.html index 635da2113df..69d2f7712ae 100644 --- a/docs/tags/podman.html +++ b/docs/tags/podman.html @@ -13,7 +13,7 @@ - + diff --git a/docs/tags/pods.html b/docs/tags/pods.html index 4197db89df8..b079e1a8cd9 100644 --- a/docs/tags/pods.html +++ b/docs/tags/pods.html @@ -13,7 +13,7 @@ - + diff --git a/docs/tags/proxy.html b/docs/tags/proxy.html index ef56a7fbbc4..647e7021d96 100644 --- a/docs/tags/proxy.html +++ b/docs/tags/proxy.html @@ -13,7 +13,7 @@ - + diff --git a/docs/tags/publishing.html b/docs/tags/publishing.html index 300a1473705..7405d7bdd05 100644 --- a/docs/tags/publishing.html +++ b/docs/tags/publishing.html @@ -13,7 +13,7 @@ - + diff --git a/docs/tags/restricted-environment.html b/docs/tags/restricted-environment.html index a7dfdeac4a0..f429402df08 100644 --- a/docs/tags/restricted-environment.html +++ b/docs/tags/restricted-environment.html @@ -13,7 +13,7 @@ - + diff --git a/docs/tags/scoop.html b/docs/tags/scoop.html index f7f52e42a41..c864a8ce4eb 100644 --- a/docs/tags/scoop.html +++ b/docs/tags/scoop.html @@ -13,7 +13,7 @@ - + diff --git a/docs/tags/vpn.html b/docs/tags/vpn.html index 8401a836c67..579e07a125b 100644 --- a/docs/tags/vpn.html +++ b/docs/tags/vpn.html @@ -13,7 +13,7 @@ - + diff --git a/docs/tags/when-clause.html b/docs/tags/when-clause.html index d442e8a8874..3f75ce32c12 100644 --- a/docs/tags/when-clause.html +++ b/docs/tags/when-clause.html @@ -13,7 +13,7 @@ - + diff --git a/docs/tags/windows.html b/docs/tags/windows.html index d11a04d191f..7ffe59b5c58 100644 --- a/docs/tags/windows.html +++ b/docs/tags/windows.html @@ -13,7 +13,7 @@ - + diff --git a/docs/tags/winget.html b/docs/tags/winget.html index e10cfad43d7..afe5d90d5fa 100644 --- a/docs/tags/winget.html +++ b/docs/tags/winget.html @@ -13,7 +13,7 @@ - + diff --git a/docs/tags/writing.html b/docs/tags/writing.html index e9f4307a0d5..28d1074778f 100644 --- a/docs/tags/writing.html +++ b/docs/tags/writing.html @@ -13,7 +13,7 @@ - + diff --git a/docs/troubleshooting.html b/docs/troubleshooting.html index 1d6a8157f2c..849a7cc47ce 100644 --- a/docs/troubleshooting.html +++ b/docs/troubleshooting.html @@ -13,7 +13,7 @@ - + diff --git a/docs/troubleshooting/troubleshooting-openshift-local.html b/docs/troubleshooting/troubleshooting-openshift-local.html index f14da96b498..454a5feddbe 100644 --- a/docs/troubleshooting/troubleshooting-openshift-local.html +++ b/docs/troubleshooting/troubleshooting-openshift-local.html @@ -13,7 +13,7 @@ - + diff --git a/docs/troubleshooting/troubleshooting-podman-on-linux.html b/docs/troubleshooting/troubleshooting-podman-on-linux.html index 0df09109535..851a5f0c727 100644 --- a/docs/troubleshooting/troubleshooting-podman-on-linux.html +++ b/docs/troubleshooting/troubleshooting-podman-on-linux.html @@ -13,7 +13,7 @@ - + diff --git a/docs/troubleshooting/troubleshooting-podman-on-macos.html b/docs/troubleshooting/troubleshooting-podman-on-macos.html index 6e812aa9e16..778f8d7147b 100644 --- a/docs/troubleshooting/troubleshooting-podman-on-macos.html +++ b/docs/troubleshooting/troubleshooting-podman-on-macos.html @@ -13,7 +13,7 @@ - + diff --git a/docs/troubleshooting/troubleshooting-podman-on-windows.html b/docs/troubleshooting/troubleshooting-podman-on-windows.html index 70c1333c210..fb1860fcdc1 100644 --- a/docs/troubleshooting/troubleshooting-podman-on-windows.html +++ b/docs/troubleshooting/troubleshooting-podman-on-windows.html @@ -13,7 +13,7 @@ - + diff --git a/docs/troubleshooting/troubleshooting-podman.html b/docs/troubleshooting/troubleshooting-podman.html index 3061f3c2b8a..a3592966305 100644 --- a/docs/troubleshooting/troubleshooting-podman.html +++ b/docs/troubleshooting/troubleshooting-podman.html @@ -13,7 +13,7 @@ - + diff --git a/downloads.html b/downloads.html index 9a2e9ca468f..cf29e91fb40 100644 --- a/downloads.html +++ b/downloads.html @@ -13,7 +13,7 @@ - + diff --git a/downloads/linux.html b/downloads/linux.html index 55a7b9c5e7c..8ffc9243fe5 100644 --- a/downloads/linux.html +++ b/downloads/linux.html @@ -13,7 +13,7 @@ - + diff --git a/downloads/macos.html b/downloads/macos.html index 8403e529653..04135037394 100644 --- a/downloads/macos.html +++ b/downloads/macos.html @@ -13,7 +13,7 @@ - + diff --git a/downloads/windows.html b/downloads/windows.html index 4ea36535990..7dfdd001c7c 100644 --- a/downloads/windows.html +++ b/downloads/windows.html @@ -13,7 +13,7 @@ - + diff --git a/extend.html b/extend.html index 985b0fea69a..bb62489e6fe 100644 --- a/extend.html +++ b/extend.html @@ -13,7 +13,7 @@ - + diff --git a/features.html b/features.html index 1a699b84a31..24245bb6ca6 100644 --- a/features.html +++ b/features.html @@ -13,7 +13,7 @@ - + diff --git a/index.html b/index.html index 756abb1687a..c26f1725d66 100644 --- a/index.html +++ b/index.html @@ -13,7 +13,7 @@ - + diff --git a/search.html b/search.html index b0885fc1620..f8880b693d2 100644 --- a/search.html +++ b/search.html @@ -13,7 +13,7 @@ - +