From 21164fe68b3f777d7324d0e5e5e85fa4cffc730c Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Mon, 10 Oct 2022 07:21:01 +0000 Subject: [PATCH] deploy: ebd657b1967f5e51eb75641b67d92263b913d6db --- 404.html | 4 ++-- assets/js/ac371aaa.45ee0f21.js | 1 + assets/js/ac371aaa.9ebb1a23.js | 1 - .../{runtime~main.6d60fd44.js => runtime~main.d0c9cf1a.js} | 2 +- core-values.html | 4 ++-- docs/Installation/linux-install.html | 6 +++--- docs/Installation/macos-install.html | 4 ++-- docs/Installation/windows-install.html | 4 ++-- docs/getting-started/getting-started.html | 4 ++-- docs/intro.html | 4 ++-- docs/tags.html | 4 ++-- docs/tags/getting-started.html | 4 ++-- docs/tags/podman-desktop.html | 4 ++-- docs/troubleshooting.html | 4 ++-- downloads.html | 4 ++-- downloads/linux.html | 4 ++-- downloads/macOS.html | 4 ++-- downloads/windows.html | 4 ++-- extend.html | 4 ++-- features.html | 4 ++-- index.html | 4 ++-- 21 files changed, 39 insertions(+), 39 deletions(-) create mode 100644 assets/js/ac371aaa.45ee0f21.js delete mode 100644 assets/js/ac371aaa.9ebb1a23.js rename assets/js/{runtime~main.6d60fd44.js => runtime~main.d0c9cf1a.js} (97%) diff --git a/404.html b/404.html index 60aff413dcc..158d31b7d42 100644 --- a/404.html +++ b/404.html @@ -5,13 +5,13 @@ Page Not Found | Podman Desktop - +
Skip to main content

Page Not Found

We could not find what you were looking for.

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

- + \ No newline at end of file diff --git a/assets/js/ac371aaa.45ee0f21.js b/assets/js/ac371aaa.45ee0f21.js new file mode 100644 index 00000000000..4bde4c430d4 --- /dev/null +++ b/assets/js/ac371aaa.45ee0f21.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkdocs=self.webpackChunkdocs||[]).push([[130],{5318:function(e,t,n){n.d(t,{Zo:function(){return u},kt:function(){return f}});var a=n(7378);function o(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}function i(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var a=Object.getOwnPropertySymbols(e);t&&(a=a.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,a)}return n}function r(e){for(var t=1;t=0||(o[n]=e[n]);return o}(e,t);if(Object.getOwnPropertySymbols){var i=Object.getOwnPropertySymbols(e);for(a=0;a=0||Object.prototype.propertyIsEnumerable.call(e,n)&&(o[n]=e[n])}return o}var p=a.createContext({}),s=function(e){var t=a.useContext(p),n=t;return e&&(n="function"==typeof e?e(t):r(r({},t),e)),n},u=function(e){var t=s(e.components);return a.createElement(p.Provider,{value:t},e.children)},d={inlineCode:"code",wrapper:function(e){var t=e.children;return a.createElement(a.Fragment,{},t)}},c=a.forwardRef((function(e,t){var n=e.components,o=e.mdxType,i=e.originalType,p=e.parentName,u=l(e,["components","mdxType","originalType","parentName"]),c=s(n),f=o,m=c["".concat(p,".").concat(f)]||c[f]||d[f]||i;return n?a.createElement(m,r(r({ref:t},u),{},{components:n})):a.createElement(m,r({ref:t},u))}));function f(e,t){var n=arguments,o=t&&t.mdxType;if("string"==typeof e||o){var i=n.length,r=new Array(i);r[0]=c;var l={};for(var p in t)hasOwnProperty.call(t,p)&&(l[p]=t[p]);l.originalType=e,l.mdxType="string"==typeof e?e:o,r[1]=l;for(var s=2;s \n")),(0,i.kt)("p",null,"For example:"),(0,i.kt)("pre",null,(0,i.kt)("code",{parentName:"pre",className:"language-sh"},"flatpak install io.podman_desktop.PodmanDesktop\n")),(0,i.kt)("p",null,"Run the following command to start the application,"),(0,i.kt)("pre",null,(0,i.kt)("code",{parentName:"pre",className:"language-sh"},"flatpak run io.podman_desktop.PodmanDesktop\n")),(0,i.kt)("p",null,"You can read more about running Flatpak applications ",(0,i.kt)("a",{parentName:"p",href:"https://docs.flatpak.org/en/latest/using-flatpak.html"},"here"),"."),(0,i.kt)("h3",{id:"2-using-zip-file"},"2. Using zip file"),(0,i.kt)("p",null,"Download the zip file and extract the folder."),(0,i.kt)("p",null,"Navigate within the folder and double-click on the ",(0,i.kt)("inlineCode",{parentName:"p"},"podman-desktop")," executable file. This should start the application for you."))}f.isMDXComponent=!0}}]); \ No newline at end of file diff --git a/assets/js/ac371aaa.9ebb1a23.js b/assets/js/ac371aaa.9ebb1a23.js deleted file mode 100644 index 75c94a027ab..00000000000 --- a/assets/js/ac371aaa.9ebb1a23.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkdocs=self.webpackChunkdocs||[]).push([[130],{5318:function(t,e,n){n.d(e,{Zo:function(){return u},kt:function(){return f}});var a=n(7378);function o(t,e,n){return e in t?Object.defineProperty(t,e,{value:n,enumerable:!0,configurable:!0,writable:!0}):t[e]=n,t}function i(t,e){var n=Object.keys(t);if(Object.getOwnPropertySymbols){var a=Object.getOwnPropertySymbols(t);e&&(a=a.filter((function(e){return Object.getOwnPropertyDescriptor(t,e).enumerable}))),n.push.apply(n,a)}return n}function r(t){for(var e=1;e=0||(o[n]=t[n]);return o}(t,e);if(Object.getOwnPropertySymbols){var i=Object.getOwnPropertySymbols(t);for(a=0;a=0||Object.prototype.propertyIsEnumerable.call(t,n)&&(o[n]=t[n])}return o}var p=a.createContext({}),s=function(t){var e=a.useContext(p),n=e;return t&&(n="function"==typeof t?t(e):r(r({},e),t)),n},u=function(t){var e=s(t.components);return a.createElement(p.Provider,{value:e},t.children)},d={inlineCode:"code",wrapper:function(t){var e=t.children;return a.createElement(a.Fragment,{},e)}},c=a.forwardRef((function(t,e){var n=t.components,o=t.mdxType,i=t.originalType,p=t.parentName,u=l(t,["components","mdxType","originalType","parentName"]),c=s(n),f=o,m=c["".concat(p,".").concat(f)]||c[f]||d[f]||i;return n?a.createElement(m,r(r({ref:e},u),{},{components:n})):a.createElement(m,r({ref:e},u))}));function f(t,e){var n=arguments,o=e&&e.mdxType;if("string"==typeof t||o){var i=n.length,r=new Array(i);r[0]=c;var l={};for(var p in e)hasOwnProperty.call(e,p)&&(l[p]=e[p]);l.originalType=t,l.mdxType="string"==typeof t?t:o,r[1]=l;for(var s=2;s \n")),(0,i.kt)("p",null,"In order to start the application, you need to know the Flatpak identifier for the application. In our case, that is ",(0,i.kt)("inlineCode",{parentName:"p"},"io.podman_desktop.PodmanDesktop")," starting 0.0.6 and ",(0,i.kt)("inlineCode",{parentName:"p"},"com.github.containers.desktop")," for previous versions"),(0,i.kt)("p",null,"Run the following command to start the application,"),(0,i.kt)("pre",null,(0,i.kt)("code",{parentName:"pre",className:"language-sh"},"flatpak run io.podman_desktop.PodmanDesktop\n")),(0,i.kt)("p",null,"You can read more about running Flatpak applications ",(0,i.kt)("a",{parentName:"p",href:"https://docs.flatpak.org/en/latest/using-flatpak.html"},"here"),"."),(0,i.kt)("h3",{id:"2-using-zip-file"},"2. Using zip file"),(0,i.kt)("p",null,"Download the zip file and extract the folder."),(0,i.kt)("p",null,"Navigate within the folder and double-click on the ",(0,i.kt)("inlineCode",{parentName:"p"},"podman-desktop")," executable file. This should start the application for you."))}f.isMDXComponent=!0}}]); \ No newline at end of file diff --git a/assets/js/runtime~main.6d60fd44.js b/assets/js/runtime~main.d0c9cf1a.js similarity index 97% rename from assets/js/runtime~main.6d60fd44.js rename to assets/js/runtime~main.d0c9cf1a.js index 8a2bebb16af..c552d51ef58 100644 --- a/assets/js/runtime~main.6d60fd44.js +++ b/assets/js/runtime~main.d0c9cf1a.js @@ -1 +1 @@ -!function(){"use strict";var e,t,n,r,o,a={},f={};function c(e){var t=f[e];if(void 0!==t)return t.exports;var n=f[e]={id:e,loaded:!1,exports:{}};return a[e].call(n.exports,n,n.exports,c),n.loaded=!0,n.exports}c.m=a,c.c=f,e=[],c.O=function(t,n,r,o){if(!n){var a=1/0;for(d=0;d=o)&&Object.keys(c.O).every((function(e){return c.O[e](n[u])}))?n.splice(u--,1):(f=!1,o0&&e[d-1][2]>o;d--)e[d]=e[d-1];e[d]=[n,r,o]},c.n=function(e){var t=e&&e.__esModule?function(){return e.default}:function(){return e};return c.d(t,{a:t}),t},n=Object.getPrototypeOf?function(e){return Object.getPrototypeOf(e)}:function(e){return e.__proto__},c.t=function(e,r){if(1&r&&(e=this(e)),8&r)return e;if("object"==typeof e&&e){if(4&r&&e.__esModule)return e;if(16&r&&"function"==typeof e.then)return e}var o=Object.create(null);c.r(o);var a={};t=t||[null,n({}),n([]),n(n)];for(var f=2&r&&e;"object"==typeof f&&!~t.indexOf(f);f=n(f))Object.getOwnPropertyNames(f).forEach((function(t){a[t]=function(){return e[t]}}));return a.default=function(){return e},c.d(o,a),o},c.d=function(e,t){for(var n in t)c.o(t,n)&&!c.o(e,n)&&Object.defineProperty(e,n,{enumerable:!0,get:t[n]})},c.f={},c.e=function(e){return Promise.all(Object.keys(c.f).reduce((function(t,n){return c.f[n](e,t),t}),[]))},c.u=function(e){return"assets/js/"+({10:"56c3a9b2",53:"935f2afb",68:"d83d689a",114:"e665718d",121:"55960ee5",130:"ac371aaa",181:"4e8ec325",217:"d7fbbe43",237:"1df93b7f",241:"631e3189",248:"6101b3fc",262:"059d1c6a",360:"9d9f8394",397:"6194ac84",505:"8894e90f",514:"1be78505",625:"657ac0bc",671:"0e384e19",724:"5087625a",751:"3720c009",813:"933a69d3",847:"43b416ef",918:"17896441",924:"df203c0f"}[e]||e)+"."+{10:"e1e8f005",53:"0797f964",68:"ebc9a41d",114:"799b509d",121:"d62ea03c",130:"9ebb1a23",181:"66adac25",217:"a618e07a",237:"7ff7ac20",241:"6ac52e06",248:"361e9a81",262:"eb40e18f",360:"eb0349dd",397:"d85cf47d",505:"5d8cc981",514:"6931c8fd",625:"a4b9eec8",671:"232e08d5",724:"ae4de15f",751:"f121068c",813:"1a4110d4",847:"5483e15d",861:"4d9af264",893:"747bd09a",918:"f3c909ec",924:"0626bb16"}[e]+".js"},c.miniCssF=function(e){},c.g=function(){if("object"==typeof globalThis)return globalThis;try{return this||new Function("return this")()}catch(e){if("object"==typeof window)return window}}(),c.o=function(e,t){return Object.prototype.hasOwnProperty.call(e,t)},r={},o="docs:",c.l=function(e,t,n,a){if(r[e])r[e].push(t);else{var f,u;if(void 0!==n)for(var i=document.getElementsByTagName("script"),d=0;d=o)&&Object.keys(c.O).every((function(e){return c.O[e](n[u])}))?n.splice(u--,1):(f=!1,o0&&e[d-1][2]>o;d--)e[d]=e[d-1];e[d]=[n,r,o]},c.n=function(e){var t=e&&e.__esModule?function(){return e.default}:function(){return e};return c.d(t,{a:t}),t},n=Object.getPrototypeOf?function(e){return Object.getPrototypeOf(e)}:function(e){return e.__proto__},c.t=function(e,r){if(1&r&&(e=this(e)),8&r)return e;if("object"==typeof e&&e){if(4&r&&e.__esModule)return e;if(16&r&&"function"==typeof e.then)return e}var o=Object.create(null);c.r(o);var a={};t=t||[null,n({}),n([]),n(n)];for(var f=2&r&&e;"object"==typeof f&&!~t.indexOf(f);f=n(f))Object.getOwnPropertyNames(f).forEach((function(t){a[t]=function(){return e[t]}}));return a.default=function(){return e},c.d(o,a),o},c.d=function(e,t){for(var n in t)c.o(t,n)&&!c.o(e,n)&&Object.defineProperty(e,n,{enumerable:!0,get:t[n]})},c.f={},c.e=function(e){return Promise.all(Object.keys(c.f).reduce((function(t,n){return c.f[n](e,t),t}),[]))},c.u=function(e){return"assets/js/"+({10:"56c3a9b2",53:"935f2afb",68:"d83d689a",114:"e665718d",121:"55960ee5",130:"ac371aaa",181:"4e8ec325",217:"d7fbbe43",237:"1df93b7f",241:"631e3189",248:"6101b3fc",262:"059d1c6a",360:"9d9f8394",397:"6194ac84",505:"8894e90f",514:"1be78505",625:"657ac0bc",671:"0e384e19",724:"5087625a",751:"3720c009",813:"933a69d3",847:"43b416ef",918:"17896441",924:"df203c0f"}[e]||e)+"."+{10:"e1e8f005",53:"0797f964",68:"ebc9a41d",114:"799b509d",121:"d62ea03c",130:"45ee0f21",181:"66adac25",217:"a618e07a",237:"7ff7ac20",241:"6ac52e06",248:"361e9a81",262:"eb40e18f",360:"eb0349dd",397:"d85cf47d",505:"5d8cc981",514:"6931c8fd",625:"a4b9eec8",671:"232e08d5",724:"ae4de15f",751:"f121068c",813:"1a4110d4",847:"5483e15d",861:"4d9af264",893:"747bd09a",918:"f3c909ec",924:"0626bb16"}[e]+".js"},c.miniCssF=function(e){},c.g=function(){if("object"==typeof globalThis)return globalThis;try{return this||new Function("return this")()}catch(e){if("object"==typeof window)return window}}(),c.o=function(e,t){return Object.prototype.hasOwnProperty.call(e,t)},r={},o="docs:",c.l=function(e,t,n,a){if(r[e])r[e].push(t);else{var f,u;if(void 0!==n)for(var i=document.getElementsByTagName("script"),d=0;d Podman Desktop | Podman Desktop - +

Podman Desktop: Core Values

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

Fast and Light

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

Reactive and light on resources utilized from your environment.

Open

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

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

Simple

Managing a container engine locally can be hard.

Running Kubernetes in a local environment requires knowledge.

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

Extensible Workflow

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

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

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

- + \ No newline at end of file diff --git a/docs/Installation/linux-install.html b/docs/Installation/linux-install.html index 0c1880c7182..0bf38227911 100644 --- a/docs/Installation/linux-install.html +++ b/docs/Installation/linux-install.html @@ -5,13 +5,13 @@ Linux | Podman Desktop - +
-

Linux

Installing Podman Engine​

In order to use Podman Desktop, you need to have a 4.x version of Podman Engine. For example Fedora 36 comes with Podman Engine 4.x. All you need to do is make sure that the linux distribution is using a 4.x version

For other Linux Distributions, click here for a guide to install Podman Engine for different linux Distributions.

Now that you have Podman machine up and running, you can check out the Downloads section of this website to download either the .flatpak file or the zip file depending on your preference.

Installing Podman Desktop​

1. Using flatpak​

Before you follow along, make sure flatpak is set up in your distribution. Click here to learn more about setting up flatpak.

Open the Terminal and go to Downloads directory. 

cd Downloads

Run the following command to install the flatpak application,

flatpak install <name_of_the_flatpak_file>

In order to start the application, you need to know the Flatpak identifier for the application. In our case, that is io.podman_desktop.PodmanDesktop starting 0.0.6 and com.github.containers.desktop for previous versions

Run the following command to start the application,

flatpak run io.podman_desktop.PodmanDesktop

You can read more about running Flatpak applications here.

2. Using zip file​

Download the zip file and extract the folder.

Navigate within the folder and double-click on the podman-desktop executable file. This should start the application for you.

- +

Linux

Installing Podman Engine​

In order to use Podman Desktop, you need to have a 4.x version of Podman Engine. For example Fedora 36 comes with Podman Engine 4.x. All you need to do is make sure that the linux distribution is using a 4.x version

For other Linux Distributions, click here for a guide to install Podman Engine for different linux Distributions.

Now that you have Podman machine up and running, you can check out the Downloads section of this website to download either the .flatpak file or the zip file depending on your preference.

Installing Podman Desktop​

1. Using flatpak​

Before you follow along, make sure flatpak is set up in your distribution. Click here to learn more about setting up flatpak.

Open the Terminal and go to Downloads directory. 

cd Downloads

In order to install & start the application, you need to know the Flatpak identifier for the application. In our case, that is io.podman_desktop.PodmanDesktop starting 0.0.6 and com.github.containers.desktop for previous versions

Run the following command to install the flatpak application,

flatpak install <name_of_the_flatpak_file>

For example:

flatpak install io.podman_desktop.PodmanDesktop

Run the following command to start the application,

flatpak run io.podman_desktop.PodmanDesktop

You can read more about running Flatpak applications here.

2. Using zip file​

Download the zip file and extract the folder.

Navigate within the folder and double-click on the podman-desktop executable file. This should start the application for you.

+ \ No newline at end of file diff --git a/docs/Installation/macos-install.html b/docs/Installation/macos-install.html index 2e4b7913c6c..9381886a08b 100644 --- a/docs/Installation/macos-install.html +++ b/docs/Installation/macos-install.html @@ -5,14 +5,14 @@ MacOS | Podman Desktop - +

MacOS

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

You can install Podman Desktop on Mac:

  • Using the .dmg file,
  • Using Brew

If you don't have Podman installed, Podman Desktop will take care of installing it.

Installing Podman Desktop on MacOS using .dmg file​

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

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

  1. Locate the downloaded file and and double-click on it. (Usually, you'll find the downloaded file under you Downloads folder)

img0

  1. Drag Podman Desktop icon to the Applications folder.

img1

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

img2

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

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

img3

  • Click on the "Install" button next to the "View detection checks" button, and follow the instructions on screen. You will be redirected to the Podman Installer. Follow the instructions on screen and enter your system password when asked.

img4

After installation is complete, close the installer.

  1. You are ready to use Podman Desktop.

Installing Podman Desktop on MacOS using brew.​

Prerequisites​

Installation steps​

  1. Open a terminal on your Mac.
  2. Run the command below brew install podman-desktop.

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

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

Next Steps​

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

- + \ No newline at end of file diff --git a/docs/Installation/windows-install.html b/docs/Installation/windows-install.html index 92946586f4b..a57c557344e 100644 --- a/docs/Installation/windows-install.html +++ b/docs/Installation/windows-install.html @@ -5,13 +5,13 @@ Windows | Podman Desktop - +

Windows

1. Installing Podman Desktop on Windows​

In order to install the latest Podman Desktop application for Windows, visit the Downloads section of this website to download the .exe file.

Simply download the file from the Downloads section and open it in your Desktop to install Podman Desktop.

2. Installing Podman (if not already present)​

If you don't have Podman installed in your Windows computer, Podman Desktop will prompt you to do so as soon as you open the application. With the latest update, Podman Desktop will be able to install and configure Podman once you click on the 'Install' button on the home page.

NOTE: Podman Engine on Windows is backed by a virtualized Windows Subsystem for Linux (WSLv2) instance. If you don't have it installed already, Podman Desktop will prompt you to do so when you initialize a Podman Machine for the first time. You can read more about installing Podman on Windows here.

img1

3. Initialize & Start the Podman Machine​

a. Default Configurations​

Once Podman is installed, you will see a toggle button at "Home" window that will allow you to initialize a Podman Machine with default configurations. Simply activate the toggle to proceed.

img2

If this is your first time initializing Podman Machine after installation and you do not have WSLv2 installed, Podman Desktop will prompt you to do so (as shown in image below). Click 'OK' and wait for the process to complete.

img3

Your device will reboot during the process. You will be again prompted to proceed.

img4

After reboot, the remaining installation process will be performed. Once WSLv2 is installed, you will find that the Podman Machine is initialized.

img5

After initializing a Podman Machine, you should see a toggle to Run Podman. This will start the Podman Machine upon activation.

img6

b. Custom Configurations​

In order to initialize a Podman Machine with custom configurations, go to "Preferences" on the menu present in the left-side of the application. Under Resources, you will find Podman. Clicking on it shall load the configuration settings for the machine. Enter the values that deem fit for your purpose and click on the "Create" button.

img7

Once the machine is created, you can click on the Start button in the Machine Settings to start the Machine.

img8

c. Command Line​

Using the following two commands in the command line, you can initialize and start a Podman Machine the classic way!

To initialize the machine, the command is

podman machine init

After which, you can start the machine with the command

podman machine start

Well that's just it. You shall now be all set to use Podman Desktop on Windows!

- + \ No newline at end of file diff --git a/docs/getting-started/getting-started.html b/docs/getting-started/getting-started.html index 23faef74362..ece0d13480a 100644 --- a/docs/getting-started/getting-started.html +++ b/docs/getting-started/getting-started.html @@ -5,13 +5,13 @@ Getting Started with Podman Desktop | Podman Desktop - +

Getting Started with Podman Desktop

Introduction​

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

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

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

Requirements​

In order to work with Podman Desktop, you firstly require the latest version of Podman Desktop. Depending on your Operating System, you can download it from this page.

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

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

Get Started​

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

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

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

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

1. Build Image​

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

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

img1.1

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

img1.2

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

img1.3

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

img1.4

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

img1.5

2. Create and Run the Container​

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

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

img2.1

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

img2.2

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

img2.3

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

img2.4

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

img2.5

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

img2.6

Conclusion​

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

- + \ No newline at end of file diff --git a/docs/intro.html b/docs/intro.html index c11b78dd32c..568bb35e66b 100644 --- a/docs/intro.html +++ b/docs/intro.html @@ -5,13 +5,13 @@ Introduction | Podman Desktop - +

Introduction

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

Getting Started​

Get started by Downloading the product for your Operating System.

What you'll need​

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

Check podman CLI is working​

Run the development server:

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

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

Project:   https://github.com/containers/podman
Website:   https://podman.io
Documents: https://docs.podman.io
Twitter:   @Podman_io
- + \ No newline at end of file diff --git a/docs/tags.html b/docs/tags.html index ebf7baed81c..657f6441293 100644 --- a/docs/tags.html +++ b/docs/tags.html @@ -5,13 +5,13 @@ Tags | Podman Desktop - +

Tags

- + \ No newline at end of file diff --git a/docs/tags/getting-started.html b/docs/tags/getting-started.html index c7a966005d7..3f235a02ced 100644 --- a/docs/tags/getting-started.html +++ b/docs/tags/getting-started.html @@ -5,13 +5,13 @@ One doc tagged with "getting-started" | Podman Desktop - +

One doc tagged with "getting-started"

View All Tags
- + \ No newline at end of file diff --git a/docs/tags/podman-desktop.html b/docs/tags/podman-desktop.html index 9f49c404175..218f9a49773 100644 --- a/docs/tags/podman-desktop.html +++ b/docs/tags/podman-desktop.html @@ -5,13 +5,13 @@ One doc tagged with "podman-desktop" | Podman Desktop - +

One doc tagged with "podman-desktop"

View All Tags
- + \ No newline at end of file diff --git a/docs/troubleshooting.html b/docs/troubleshooting.html index 7cbda910a49..cb95db36511 100644 --- a/docs/troubleshooting.html +++ b/docs/troubleshooting.html @@ -5,7 +5,7 @@ Troubleshooting | Podman Desktop - + @@ -13,7 +13,7 @@

Troubleshooting

Here, find some answers to the question : I have downloaded Podman Desktop but I am unable to see any of my image or container

Podman​

System Requirements​

The tool connects to Podman using the socket on the host on macOS and on a named pipe on Windows. This is available only on podman 4.0.2+ So, please check your version and update.

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

Check connection​

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

podman machine list

And check a connection can be made with the CLI

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

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

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

Fixing corrupted Podman Machine in Windows​

If at all you are not able to stop your Podman Machine, you will find such an error in the Logs- Error: Error stopping sysd: exit status 1

It is highly unlikely that you may be stuck in such a situation but if you are, here's a quick fix for it.

Assuming the name of the Podman Machine to be my-machine, run the following commands in the terminal:

wsl --list

This shall display a list of active distributions i.e. my-machine in this case.

Then,

wsl --unregister my-machine

(Replacing my-machine with the name that is displayed under wsl --list for your Podman Machine)

This will stop the Podman Machine for you.

Code Ready Containers​

  • Check that podman preset is defined. (crc config get preset)
  • Check that crc binary is available in the user PATH (/usr/local/bin/crc)
  • Check that crc setup --check-only is running without errors.
- + \ No newline at end of file diff --git a/downloads.html b/downloads.html index b1faf0f6c8c..8d17bd024d7 100644 --- a/downloads.html +++ b/downloads.html @@ -5,13 +5,13 @@ Podman Desktop | Podman Desktop - +

Windows

Exe
Version

macOS

Using Brew ?

brew install podman-desktop

universalIntelArm
Version

Linux

Using FlatHub ? Install in one command:

flatpak install --user flathub io.podman_desktop.PodmanDesktop

Flatpakzip
Version
- + \ No newline at end of file diff --git a/downloads/linux.html b/downloads/linux.html index e3e66006e41..0c827878513 100644 --- a/downloads/linux.html +++ b/downloads/linux.html @@ -5,13 +5,13 @@ Podman Desktop | Podman Desktop - +

Linux

Using FlatHub ? Install in one command:

flatpak install --user flathub io.podman_desktop.PodmanDesktop

Flatpakzip
Version
- + \ No newline at end of file diff --git a/downloads/macOS.html b/downloads/macOS.html index a561d1a24ae..15741e21465 100644 --- a/downloads/macOS.html +++ b/downloads/macOS.html @@ -5,13 +5,13 @@ Podman Desktop | Podman Desktop - +

macOS

Using Brew ?

brew install podman-desktop

universalIntelArm
Version
- + \ No newline at end of file diff --git a/downloads/windows.html b/downloads/windows.html index bc7bc11091d..3c90b84edc2 100644 --- a/downloads/windows.html +++ b/downloads/windows.html @@ -5,13 +5,13 @@ Podman Desktop | Podman Desktop - +

Windows

Exe
Version
- + \ No newline at end of file diff --git a/extend.html b/extend.html index 67121cd1f86..c7ee24bdc5a 100644 --- a/extend.html +++ b/extend.html @@ -5,13 +5,13 @@ Podman Desktop | Podman Desktop - +

Extend capabilities with Docker Desktop extensions.

Podman Desktop is able to use Docker Desktop UI plug-ins by adding a wrapper to intercept the API calls.

By adding a Docker Desktop extension, you can extend the capabilities of Podman Desktop.

Extend with Docker Desktop extensionsExtend with Docker Desktop extensionsReuse Docker Desktop extensionsReuse Docker Desktop extensions

Extend capabilities with Podman Desktop plug-ins.

Podman Desktop is using plug-ins under the hood to manage the different container engine.

By adding a new plugin, you can extend the capabilities of Podman Desktop.

For example plug a new container Engine likes Podman, Docker, Lima, etc.

Extensibility diagramExtensibility diagram

Extensions are written in JavaScript/Typescript
It consumes a TypeScript definition of the extension model.

More extension points

Several extension points exists in addition to adding a Provider connection.

User interaction, dialogs, launching commands are among the possible ways to extend Podman Desktop

- + \ No newline at end of file diff --git a/features.html b/features.html index c8962a9e5ac..13d4938c579 100644 --- a/features.html +++ b/features.html @@ -5,13 +5,13 @@ Podman Desktop | Podman Desktop - +

Manage containers

List, Search, Inspect, Connect, Run and Stop containers.

Manage containersManage containers
Pull image and manage registriesPull image and manage registries

Build, Pull and Push images

Build images from the tool.

Pull and push images by managing registries.

Run containers from these images

Management from the tray icon

Check status and start/stop container engines.

Create new machine if needed as well as start or stop Podman machines directly from the tray icon.

Quickly check activity status and stay updated without losing focus from other tasks.

Manage Podman MachineManage Podman Machine
Manage Podman MachineManage Podman Machine

Manage Podman resources

View allocated memory, CPU and storage.

Create new machine if needed

Import Docker Desktop extensions

Specify OCI image of a Docker Desktop extension to import it.

For example: security scanner or deploy to OpenShift extensions.

Pull image and manage registriesPull image and manage registries
- + \ No newline at end of file diff --git a/index.html b/index.html index bfd95ac062e..60bb79a165c 100644 --- a/index.html +++ b/index.html @@ -5,13 +5,13 @@ Leverage Podman with a Desktop App | Podman Desktop - +
Join our Early Adopter Program!

We are seeking users who are interested in helping us improve Podman Desktop. Register your interest to join our Early Adopter Program by filling this form.

Containers and Kubernetes for application developers

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

Download Page
Podman Desktop home page

Available on Windows, Mac and Linux

Use the same UI across different operating systems

Windows

exe or setup.exe

macOS

arm64, x64 or unified dmg

brew install podman-desktop

Linux

flatpak or zip

features

Build, run and manage containers.

Build

Build images from Containerfile or Dockerfile

Run

Pull images from remote registries

Start / Stop / Restart containers

Start / Stop / Restart pods

Inspect

Get a terminal in your container

Inspect logs

Push

Push images to OCI registries

Deploy & Test images on Kubernetes

Discover More

Configure

Multiple configuration options

Registries

Manage OCI registries. Add/edit/delete registries.

Proxy

Configure your proxy settings (in progress..).

Resources Utilization

Configure CPU/Memory/Disk of Podman machines (work in progress)

Container Engines

Handle multiple container engines at the same time (Podman, Docker, Lima...).

extensibility

Bring new features with Podman Desktop plug-ins or Docker Desktop Extensions.

Container engines are plugged through extension points.

JavaScript extensions can contribute new behaviour

Reuse existing extensions directly in Podman Desktop

Current Podman Desktop plug-ins: Podman, Docker, Lima and CRC/OpenShift Local.

Reuse Docker Desktop extensionsReuse Docker Desktop extensions
Learn More

update

Install and keep up to date Podman
Work in progress

Install Podman and other dependencies directly from Podman Desktop if not yet installed.

Check for updates and get notified about new changes.

Available on Windows!

Coming soon on MacOS.

enterprise

Enterprise ready
Work in progress

Match configuration options.

Code signing

macOS binaries are digitally signed (Windows certification is in)

Proxy

Configure proxy within the tool. Avoid any painful files to edit.

Registries

Manage OCI registries. Add/edit/delete registries.

- + \ No newline at end of file