Podman Tutorial Zero to Hero | Full 1 Hour Course

if I say containers what's come to mind Docker right don't worry it's fine but Docker is not the only tool available for creating air running containers there is also podman hello and welcome to this podman tutorial from Zero to Hero my name is jeppe I'm a senior software engineer at Amad together we will explore the world of bman let's start let's begin by answering a simple question what is podman according to the official documentation podman is a demoness open-source Linux native tool designed to make it easy to find run build share and deploy applications using oci containers and container images to put it more simply podman is an oci management tool that offers similar features to Docker for managing container ERS o stand for open container initiative is an open governance structure aiming to create open industry standards around container formats and run times bman offers many features but in term of security I must mention its ability to run rootless containers you may be wondering what a rootless container is it's a way of running and managing containers as a normal user without root privileges this adds an additional layer of security by not allowing root access even if the container is compromised by an attacker before starting to use bman it's important to also mention two other features first podman runs containers in pods a pod is a concept from kubernetes and with podman you can create multicontainer pots locally and Export them as a kubernetes manifest and and as I mentioned earlier when reading the official documentation podman is also demon lless meaning that it doesn't have a demon and interact directly with runc runc is an open-source command line tool for spoing and running containers on Linux according to the oci specification one more thing if you know or if you already used Docker desktop well you would be happy to know that there is also podman desktop podman desktop is an open source graphical interface for managing podman containers and kubernetes from your desktop here the link for the official documentation and I'm going to explain to you in a specific video before you start using podman you need to know how to install it on your local machine in this tutorial I will install podman on Ubuntu 204 and mechos but I will explain also the the commands for installing it on Windows machine let's get started to install podman on buntu you need to use two different commands sud sudo rpt update and Pudo ipt install podman after running this two command you can check the installed version of podman using the command podman info and podman version I'm inside the Linux machine wuntu version 22.4 and I use the First Command Pudo AP update when it's done I use the command P sudo AP get install podman yes to confirm the installation okay once the installation is complete I can check the podman has been installed using the command podman info this command displays all information about podman for example the current storage stats the configure container Registries and the build like the Go version and the podman version I am installed to check the podman version in the system I use the command podman version in the terminal as you can see the podman version I have installed is the version 3.4.4 on a maos machine the simplest way to install podman is by using on Brew you can install podman by running the following command Brew install podman after the installation you can initialize podman Machine by running podman machine init then to start the podman machine you can use the command podman machine start and then to check the information about your podman installation use the following command podman info and to check the version of podman podman version I know what you are wondering why we need the commands podman machine init and pman machine start well containers are a Linux techn techology if containers are a l technology how can I run them on Mac or Windows the answer to this question is well you can't when using other platform the only way to run containers is rely on a Linux virtual machine there is no other way bman or Mac OS and windows requires a virtual machine the default machine name is podman machine default if a machine name is not specify as an argument then podman machine default will be started only one podman virtual machine can be active if our virtual machine is already running the command podman machine start returns an error I switch and I'm inside a mechos machine I have already installed Brew with the current version 4.09 and I'm ready to use the First Command Brew install bman Okay once the installation is complete I can install podman machine with the command podman machine init with this command I can download the VM image okay right now I can start the the podman machine podman machine start perfect the machine with the name podman machine default started and as you can see in the log is currently configure in rootless mode now I want to check the information about podman podman info the output format is the same that I got in Ubuntu but with different value for Example The Go version in this case 1.19 and the podman version 4.4.2 in case I want to see only the current podman version I am installed in this me machine I can type podman version to install podman on a Windows machine go to the official GitHub repository and downloaded the executable file once the download is completed run the file to install podman after the installation podman will be added to your path and you will be able to run the following commands podman machine init podman machine start podman info and podman version one of the popular container Registries is Docker up however you can also use other registries like GitHub container registry redot container registry or your company's private registry thanks to the podman container registry configuration this file is located in the path /c/ containers Registries Doom podan use this file when you pull or push an image every time you attempt to connect with the container registry this file is used by podman instead of changing the default registry configuration you can have a different configuration for your user it's simple to create a separate registry.com file in your user directory with your custom configuration I switch back to the obuntu machine that I'm going to use until the end of this tutorial I can open the default registry to start configuring the podman container registry.com in this configuration file I I can UNC comment the lines or add a new line with a custom configuration once done I save and close the file I don't want to change the default registry.com but instead I want to create a separate registry.com file in my user directory first I have to create the folder containers inside the config folder now I can create the custom Registries Doom file and start to edit it okay inside this file I can add a custom configuration specifying all Container Registries for for the category registry. search this custom configuration will be used by the command pondman search you will understand better in a few minutes I have to type unqualified search Registries equal the list of container Registries as a list I put the dockerhub registry the GitHub registry and redout registry remember that here you can put also your company private registry there are other category that you can use such as Registries do insecure or Registries block for more information these categories refer to the official documentation now I can save and close the file and before moving forward I want to explain to you the command podman search the command podman search search a registry or a list of Registries for a matching image you can specify which registry to search by prefixing the registry in the search term for example docker.io Library theimage Name by default all unqualified search Registries in the Registries Doom are used I switch back inside the terminal to use the podman search searching the classic image busy box bman search buy box here is the list of all Registries I can use to pull the Mage busy box and this Registries are that one that I previously added in my custom registry.com you can play with containers in the same way as you would do with Docker but instead of using the docker command you have to use podman command with all the similar flxs these are the commands that you will use in this first part part of the tutorial podman search podman pool and podman images with podman pool you can download an image from a registry with bodman images you can list all the images you have downloaded I switch back to the terminal and I want to pull the busy box image first I use podman search to search for the Mage and theci side which registry to use okay I want to pull the docker a your library busy box image I haven't specified the tag so podman will try to pull the latest ver version now that it's done I can list all the images present in my system here is the result the list contains only one entry because I pull only one image up to this point I can see information such as the tag when the Mage was created and the repository I used to download the busy box image now that you have pull the required container image you're ready to run it you have to use the commands bman run ID and the image name podman PS and podman PS with the flag a with bman run you can create and run a new container from an image it's important to note that you don't need to run the command with sudo privileges you can run podman as a normal user what does the it flag do it tell podman to allocate a virtual terminal session within the container allowing you to interact with it you will understand stand more in a few minutes when using the podman Run command you can also add the RM option to remove the container after the execution this is considered a best practice to avoid filling up your file system to check if your container is running or not you can use the command podman PS This command shows only the containers that are currently running to see all containers including those that are are not running you have to use the a flag let me try with the image busy box bman run the flag it buy box remember here also to use the RM option great the busy box container is now running and I can interact with it I'm basically inside the container and I can use the command LS to see the content then I can use the common exit to quit the container with this type type of image busy box doing so I have also stopped the container alternative you can stop the container by pressing control+ C to check how many containers are running I use the following command podman PS none right and how many containers are stopped I can use the same command with the flag a to show all containers in the system including those that are not cut ly running perfect the list contains one entry which is the busy box container here I can see the container ID the image from which it has been created and other information like its status and name since I didn't specify the container name using the flag name podman generated for me a random name for the container now let's explore what you can do with container ERS you will be using the following commands podman Run podman start start one or more container using the container IDs or names as input podman inspect this display the lowlevel information on containers and images identified by name or ID bman port list all PO mappings for the containers bman stop to stop the container podman RM to remove the container and podman RMI to remove the container image let's put these commands into practice I will also be using a different container image the classic and most used Enix image first I will search for the Enix container image using the command bodman search engine as a second step I use bman run to create a new container from the Enix image this common pulls the Enix container image if it's not already present and runs a new container with the name PDM and genix the name flag assign the name to my container and the P flag Maps the port 80 inside the container to the port 8080 on the host meaning on my machine before moving on I want to make a quick remark to highlight an important thing in this tutorial I will use the flag name to refer to object like container since it simplify the following commands however this is not a best practice as container engines are shared if you start naming objects you risk running into into naming conflicts how you can avoid this simply don't use the name option and let bman assign a random name to your container all the flags that I use are equivalent to that ones provided by Docker because I haven't specified the registry podman is asking me which registry I want to use this list comes from my custom registry.com file that I've created in the part one okay the container is now running to stop it I need just to Simply press contrl + C to start the PDM Eng genic container again I can use the command podman start with the name of my container PDM and genix this command start the container in the touch red mode meaning it runs in the background to ensure that my container is running I can use the following command podman PS the output shows the container image container ID container name and the port mapping details to obtain more information about the PDM and genix container I can use the command podman inspect with the name of the container this command provides all the information about the container in Jon format by examining the output I can see the container image I can see the name of the container image from which I generate the container and other details about for example the port mapping if I want to check only the port that the container is using I can use the command podman port with the name of the container PDM Eng genix let's use the container by trying to access the Local Host at8 perfect this is the response from engin X to stop the container which was started with the podman start I can use the command podman stop to confirm that the container has been stopped I can use the common podman PS perfect no containers are running now let's double check bodman PS with a flag a as I can see in the console the PDM Eng genix container has been stopped finally to permanently remove the container that I created I can use the command podman RM specify the name of the container let's double check again bman PS with the flag a there are no containers with the name PDM Eng genix however I only deleted the container not the engine X container image that I pull previously here how to remove the container image first I check all the images in my system with the command bman images once I identified the imag ID of the container image that I want to delete I can use the command bodman RMI specify the image ID to check that the operation has been completed successfully without any error I can use the command podman images to see the Mage has been deleted great if you're afraid of forgetting all the commands that you learn don't worry you can always use the command pod band with the flag help to get the Leist of all the commands for example bband logs to retrieve all the logs of the container or podman exec to execute a command in a running container up until now you've learned how to work with existing container images such as Enix or buy box however you can also create your own container image by using a file Docker file to containerize your application and then build the image if you have experience with Docker you probably already know how to do this if you don't know how to create a Docker file don't worry I will guide you through the process step by step in this tutorial here is a quick introduction to the command you'll be using Wim Docker file used to open a Docker file with Vim text editor the docker file is a script that contain instruction on how to build a container image podman build is a command to build a container image using the docker file specify in the current directory the T flag specify the name of the image the tag of the image podman run is a command to run a container based on the previously built image the name flag specify a name for the container the flag P specify the port mapping between the container and the host system in this case the container sport at80 is mapped to the host Port at80 image name and tag specify the image to use in order to create a container image you need to have an application that you want to package into a container in this tutorial we create a simple application in Golan that exposes a web service with a single endpoint the endpoint responds with the message hello podman from go firstly I will ensure that Golan is installed in my system if not I will install it let's check that right now I have goang installing my system perfect now that I have installed go I'm ready to create the project now I can create the main.go file to implement the application logic to expose a web server I use the standard net HTTP Library provided by go without relying on any third party libraries now let's write the logic just to recap this is a simple Golan program that creates a HTTP server listening on a port 80 and responds to requests with the message hello bodman from go let me explain how this work the viral Line Imports the fmt and net HTP packages the fmt package provide formatting functions such as F print L which I Ed to write the text to the HTTP response hello podman from go meanwhile the net HTTP package provide the functionality to create HTTP server the main function is an entry point of the program and performs the following task it registers a endler function for the root path slash using the HTTP Dole fun the endler function takes two arguments are response writer and request the response writer used to create the response back to the client and the request contain information about the incoming HTTP request the endler function uses the fm. F print function to write the message hello podman fromo to the response writer finally the program calls the HTTP do listen and serve to start the HTTP server on the port 880 to run the application background I can type go run m. go then Cur locost 8080 perfect the application works as expected now comes the important part containerizing the application to do this I need to create a file with all necessary instructions even with podman I can use the name Docker file this is the docker file used to build a contain image of a golang application using the Alpine Linux distribution all the commands are included in the file so first from goang this line specified the base image to use for the container which is the official go 1.8 image based on Alpine Linux work de / app set the working directory to/ app the copy command copies the go mode file from the OST machine to the/ up directory in the container image the Run command download and install any dependencies specifying in the file go do mode the other copy command copies all the go file with the dot go extension from the OST machine to the/ app directory in the container image the other run command built the go application and generated an executable name PDM golang which is stored in the root directory slash of the container image expose 880 in for podman that the application will listening on the port 8080 and the last command CMD specify the command to run when the container start which is execute the PDM golang when this Docker file is used to build a container image the result image will contain the compiled go application and all its dependencies make it easy to deploy and run now it's time to build the container image I can use the command podman build this command tell bman to build the container image from the docker file located in the current directory using the dot symbol and assign it the tag PDM golang using the flag t stand for tag let's check the result of the command by listening all the container images present in the system bman images yes ad just perfect I can see my brand new container image PDM Golan ready to use I I haven't specified a version so podman has given my container image the version latest what's next well let's run it podman run the name PDM golang the port 880 map to the port 880 and then the contain image PDM golang and the version and the tag version latest it's currently running to stop it simply press control+ C then bman PS let's start it again you learn how to do it in the previous video bman Start PDM goang now I can try calling my application to see if everything is working fine Cur Local Host 880 yes perfect now that we have build your first container image it's only exist inside your system what can you do next you could share your container image with others to give them the possibility to use the application you have created this mean pushing the container image to a specific container registry how can you do it it's simple and here are the commands that you will learn to use podman registry name is a common use to authenticate with a container registry before pushing an image to the registry registry name specify the name of the container registry to authenticate with Pat build is a common use to build a container image using the docker file specifying the current directory the format username SL image name is commonly used when pushing image to a container registry username specify the username or organization name associated with image and image name specify the name of the image podman push is used to push the container image to The Container registry with the format username SL container name in this tutorial I'm going to use Docker app as a Docker container registry to push the container image PDM golang that I've previously created before continuing ensure that you have chosen the container registry to push to and have the currect credentials first I need to log in to The Container registry with bondan to indicate the specific container registry where I want to push the container image next I need to rebuild the container image by adding my username as a prefix to the image tag using podman build the FL T my username slash the name of the container image PDM goong now inside the system I should also have the container image user name/ PDM goang which is exactly the same as the previous one but with different tag this format username SL image name is important because it tells bman where to publish to push the container image now it's time to publish the container image I can type bman push my username SL PDM goang that's it the container image has been pushed to the registry Hub I can now review the image inside the registry such as Docker up from there I can see all my available docket images including PDM golang next I can simulate someone else who wants to use my container image by pulling it from the cab I need to type the command modman search then podman pull to pull the container image username PDM goang perfect I have successfully pulled my container now let's run it in the command I use the flag D to run the container in background mode and I have decided to use a different port mapping the port 8081 excellent podman is a container engine that offers a remarkable feature of creating pots pots are similar to the kuber pots they provide a way for application to be organized and scaled within a kubernetes cluster kuber API objects such as deployments replica sets and stateful sets are used to manage them now let's dive into the commands you will be using during the first part of the tutorial the podman Pod help command is a lifesaver when working with podman it provides a list of all available commands and options to use when working with pods in podman podman pod create with a flag name podman name command used to create a new nmt pod the podman Pod LS command used to list all created pods is it work the same way as the the ls LS stand for list command works with containers the podman PSA pod command used to list all the containers in the Pod you may remember that in the previous video you learn how to list all containers in the system using podman if you add the option pod to the common podman PS a you can list all the containers in the Pod in conclusion pods in podman provide an excellent way of managing containers and scanning application within a kuber anti cluster with bodman commands you can easily make handle and show list of PODS I switch back to the terminal and type the First Command podman pod with the flag help this command provides all available commands that Bond band offers to manage pods for example create used to create a new empty pod exist to check if a pod exists in the local storage espect displays the configuration of a pod and start stop and RM are used to manage pods according to the description a pod is a group of one or more containers that share the same network PID and net spaces now I will create my first pod using the create command in podman I run podman pod create and specifi the name flag to make it easier to use other commands later however it's recommended to avoid using name flag and let podman assign a random name to avoid potential name collisions as mentioned in the previous video the Pod has been successfully created without any error in console but how can I be certain I use the following command provided by podman to list all the pods created in my system podman pod LS perfect I can see my new created pod in the list it show the status as created 11 seconds ago along with a specific pod ID and a name assign it I can also see that there is one container inside the Pod why is there only one container well when you create an empty pod pod automatically add an infra container this container serves the purpose of holding the net spaces associated with the Pod and allow podman to connect other containers to the Pod this allow you to start and stop containers within the Pod while keeping the Pod running the default infra container is based on this image kis jc. /os and let specify otherwise all pots will have a container based on this default image so in summary when you create an empty pod podman assigns an infra container to all the net space and facilitate communication with the other containers in the Pod to demonstrate this I can use the common pod onps with the flag a to list all the containing in the Pod and the flag pod to display the Pod name here it is you can see the container with the name khhc jc. it status is created and it's associated with the Pod if I run the same command without the Pod flag I can see all the containers in my system including the infra container however in this case I don't know which is the name of the Pod associated with the infra container now you have learned how to be build a pod with bman let's move on to the next step and add a new container to it this will help you improve your skill with containerization specifically we'll be adding the custom container image PDM goang that was created in the part three of this tutorial to add a new container to your pod you will need to use the following commands the First Command podman run will enable you to run a new container an image inside an existing pod remember to use the Pod option to specify the name of the Pod and the end specify the container image name that you want to add to your pod in addition to the Run command you can also use the start stop and RM commands with both containers and pods this will allow you to start stop and remove pots and containers as needed however before before using the RM command to remove a pod it's important to stop it first alternative you can use the force option to remove it without stopping it first I switch back to the terminal and now I want to use the first command to run a new container image inside the Pod that I created podman Run with a flag pod with the name PDM golong inside this pod I want to run the contain image that I created in the previous video part three called PDM goang perfect now let me check it using the command bman PS with a flag a and a flag pod here it is PDM Golan inside the PDM Golan pod and here because I haven't specified the name of the container podman assigned a random name for me of course inside a pod you can also see the infra container let's use the command podman PS here they are currently running and if I specify the flag pod I can see that they are inside the Pod PDM Golem pod I can work with containers using the normal commands like podman stop specify the name of the container now I can see only the infra container running I can start the container with podman start and the name of the container I can try to remove it with the command podman RM but because the container is running I need to stop it first or use the force flag let me stop it and then remove it I cannot see the container created by the image PDM goang anymore because it has been successfully deleted you'll learn all these commands in part two of the Pod band tutorial working with containers even if the container is inside a pod you can use all the available commands to work with containers now it's time to learn the commands to work with BS first let's list all the pods with a common podman pod LS LS stand for list then to stop the Pod I can try to use the command podman stop and the name of the Pod wrong PDM Golan pod is a pod not a container the command podman stop stops a container not a pod this is important so to stop a pod I can use the command podman pod stop and the name of the Pod now it's working to start it well podman pod start and the name of the Pod yes it's running and to remove it well podman podm and the name of the Pod but first I need to stop it perfect as you can see podman provides similar commands to work with containers and pods like start stop LS and remove but with PS you need to specify the keyword pod before the actual command like podman pod start stop LS and remove one of the most fascinating feature of podman which also happens to be my favorite one it's the ability to generate the kubernetes from the podman pots that can save developers a lot of time and effort a kubernetes yaml manifest is a file that contain instructions for kuber nting on how to create and manage think such as BS deployments Services config maps in a kuber cluster the Manifest file contains important details such as which container image to use the environmental variables volume and how thing are related to each other in the cluster the process of generating the kubernetes the following commands podman generate Cube and the name of the Pod podman generate Cube the name of the Pod and append the result to a AML file imagine that you have a CET yl file that defines a pod and container that you want to use on your local podman instance this can be useful feature when you want to test your kubernetes configuration locally podman provides an easy command to achieve this which is podman play Cube this command creates a new pod based on the cubern yaml file provided once the Pod is created you can interact with it this allow you to test the functionality of your kubernetes configuration locally before deploying them to your production environment I returned to the terminal and now I want to create a new pod named PDM Goan POD at the same time I want to create and run a new new container image inside the Pod mapping the port 8081 to the port 80 to of the container I can achieve this using the new keyword let's check it using the command podman pod LS yes my new pod is listed next I want to check the container great I can see my new container created and running with the correct Port m mapping inside a PDM Golem pod of course I still have the infra container now I want to generate a cuber in yam manifest from the PDM Golan pod using the command podman generate Cube here it is the cubern yaml Manifest created by bman the yaml Manifest follows the V1 specification and defines a pod named PDM Golan pod it also includes the section related to The Container image inside the PO the container image is PDM Golan with the specified name and Port mappings I have two options I can copy the content and add it to a file or reuse the podman generate Cube command and openen the output directly to a file specifying the file name such as PDM goang yaml let's check the content yes everything looks good now let's imagine that I don't have a pod named PDM colum pod so let me first delete it perfect I am ready to create a new pod based on the previously generated kubernetes yaml file to do this I can use the command podman play Cube specify the name of the cubern Yammer file this will create a new pod with the same characteristics as the previous one including a container running from the PDM Golan image with the correct Port mappings once the Pod is created I can interact with it just like any other pod this allow me to test the functionality of my kuber ntic configuration locally before deploying them to the production environment it's provide a convenient way to validate my configurations now let's check it using the com podman pod LS yes I can see my new pod created and running based on the cuber netting yaml file bman deskop is a UI tool that makes running and managing containers much easier with an intuitive user experience you can install it on Windows Mac OS and Linux and you also install the underlined podman utility if needed let's start with the installation I'm going to install it on a Macos machine as you can see I don't have podman installed so first thing first go to the official podman desktop webbsite podand desktop. here you can find all the information about potman desktop including the official documentation click on the download link on this page you have to select the right pman deskop to store contrer for your machine podman desktop for Windows Macos or Linux in my case I have to click on download now for the podman desktop for Mac OS once the download is completed I can open the installer to install podman desktop perfect it was faster now I have podman Des installed on my machine and it's up and running this is the UI of the podman desktop in the dashboard view you can see the highlighted information some action that I need to do and the featured extensions here I have a message podman desktop was not able to find an installation of podman yes it's right because I don't have podman installed as you saw previously to start working with containers pman needs to be detected or installed in my case I need to install it how open the terminal and manually do it not at all I can just click on the install button and then yes so in this way I can easily install podman on my system the version that I will install will be the version 4.6.2 as of today click on yes now I can see this popup window where I can click on continue read and agree to the license and then install it perfect now I can start using podman now I switch back inside the terminal to double check the podman installation yes I can see now that bman has been correctly installed on my system version 46 .2 now I switch back to podman desktop I can see now the message podman 4.6.2 has been installed but not ready to start working with containers bman needs to be initialized I click on initialize and start button perfect now podman has be initialized and also podman descoped is ready to be used before starting to use it I want to switch to the terminal and tap the the command podman machine list in order to see the default machine created and currently running this is necessary to run podman on Mac OS and Windows machine we discuss this in the part one introduction to podman okay now let's discover all the views available in podman desktop you have the dashboard view where you can find all the useful resources and the featured extension in the menu bar you can switch between different views like containers view where it lists all the containers the Pod views the image views and the volume view of course all these views are empty because I haven't pulled or run any images yet let's do it click on the image View and on the top right corner I can see two button to pull an image from a registry or build an image I can past the image here and then click on the pull image button yes download completed now inside the image view I can see the new image bman hello pulled I can click on it and see different tabs like the summary tab here the tag in this case latest the history Tab and insect tab where I can see all detail about the image in Jon format I can select the image click on the delete button if I want to completely delete it from my system or as you can see on the right in the action section I can edit the image show the history or push the image to a kind cluster I can easily run the image by clicking on the play button if I do so I will be see a new view with different tabs Basics Advan networking and security settings in the basic tab I can see and customize the basic settings I can choose a name for the container specify the entry point and Define the port mapping I will leave the default settings and click on the start container button and that's it in the view container I can see my brand new container created based on the Mage podman hello also inside the container view I can click click on the container to see more information about it splitting in different tabs summary the logs expect Cube and the terminal inside the log I can see the log produced by the container it's a simple image with the message hello podman world in the expect tab I can find all information about the container such as the image in the cube tab I can find the cubern yam manifest file use to create a pod with a container you learn about this in the part four and last button on list thanks to the terminal tab I can go inside the container in this case I cannot show you the content because the container is not running on the top right corner I can see the action buttons such as relaunching the container let me delete it now I'm going to create a new container ER from an existing image this button takes me to the image view where I can pull the image as I did in part two I will now create a new container from the image Eng genix docker.io genix perfect I have pulled my image now I will go to The Container view click on the create contain erer button select the existing image choose the engine image and then click on the play button in the basic view I can see the H sport mapping the port 9,000 to the 80 inside the container in this case I'm going to assign a name to The Container like for example my Eng genix then I will start the container yes myix container has been created I can stop it delete it or perform other actions let me open the browser as you can see the port is 9,000 yes it's working let me go back to the container view if I click on the container I can see the state of the container running and the port 9,000 and the current log of engine also in this case I can inspect it and view the image I can find the kubernetes yaml file and finally clicking on the terminal tab because the container is still running I can go inside it and check for example the content of the container what's next do you remember the container image called PDM Golan that we created and pushed to the docker Hub registry in part three well let's use it with podman desktop let me copy the image name and paste it here let me specify the tag as latest click on the pull image button perfect now I have successfully pulled the PDM Golan image now I will select the image and click on the play button I will enter the name as PDM Golan and set the port map p as 880 to 880 and then start the container yes I am my beautiful PDM Golan container after running with the port 880 I have the possibility to create the cubern yaml so let me copy it and paste it in a file called PDM Golan pod yaml why I'm doing this you will understand in a moment now as you know better than me in the terminal tab I am inside a container and I can interact with it last but not least I'm going to open it copy the link open a new tab and paste the link here and here it is hello podman fro if you remember we discussed the feature of podman to create a pod in the previous video part four now it's time to show you how to use this feature with bodman desktop in the container view when I click on the play kuber yaml a new windows appears where I can select the yl file from which I want to create the Pod here I'm selecting the PDM golm pod yl file that I previously created select using podman container engine then click on the play button just perfect I can see the Pod and container ID in the output in the Pod view I can see my new pod and inside the container view I can see the containers within the Pod as you can see I have two containers inside the pot BDM golang and the infra container we discuss about the infra container in the previous video part four now I'm going to refresh the page local lost 880 and I can see that my container in set aod created via the is working as expected the last thing that I want to show you is the tab volume where you can easily with just a click create a new volume in podman desktop needed by some container by clicking on the volume I can see just the summary and expect tab the only action I can do for the volume is to delete it in Pand descope you have access to variety of settings that are organized in different sections these settings can be checked and customized according to your needs for example under the resource section you can view the podman machine that has been created and it's currently running you have the option to restart it stop it or delete it additional you can configure a proxy settings add or modify registry and explore other features and this is podman descoped remember that I use the version 4. 6.2 if you want you can even share your feedback in my case positive feedback with the podman team I hope that you enjoyed the complete tutorial of podman and now that you become an hero so what's next don't forget to subscribe to our channel for more exciting video thank you again and see you soon

Channel: Amadeus for Developers

Views: 20,755

Keywords:

Id: YXfA5O5Mr18

Length: 60min 55sec (3655 seconds)

Published: Mon Oct 16 2023