Podman CLI Guide for Docker Users

is the that lets you interact with , a library for running and managing OCI-based containers. It is important to note that Podman doesn't depend on a daemon, and it doesn't require root privileges. Podman command-line interface tool Libpod The first part of this tutorial focuses on similarities between Podman and Docker, and we'll show how you can do the following: Move a Docker image to Podman. Create a bare-bones Nuxt.JS project and build a container image for it Push your container image to Quay.io Pull the image from Quay.io and run it with Docker. In the second part of this tutorial, we'll walk you through two of the most important features that differentiate Podman from Docker. In this section, you will do the following: Create a Pod with Podman Generate a Kubernetes Pod spec with Podman, and deploy it to a Kubernetes cluster. Prerequisites 1. This tutorial is intended for readers who have prior exposure to Docker. In the next sections, you will use commands such as run, build, push, commit, and tag. It is beyond the scope of this tutorial to explain how these commands work. 2. A running Linux system with and installed. Podman Docker You can enter the following command to check that is installed on your system: Podman podman version Version: 1.6.4 RemoteAPI Version: 1 Go Version: go1.12.12 OS/Arch: linux/amd64 Refer for details on how to install Podman. Podman Installation Instructions Use the following command to verify if is installed: Docker docker --version Docker version 18.06.3-ce, build d7080c1 See the page for details on how to install Docker. Get Docker 3. . To check if Git is installed on your system enter, type the following command: Git git version git version 2.18.2 You can refer on details of installing Git. Getting Started - Installing Git 4. or higher. To check if Node.js is installed on your computer, type the following command: Node.js 10 node --version v10.16.3 If Node.js is not installed, you can download the installer from the page. Downloads If you don’t have a running Kubernetes cluster, refer the “Create a Kubernetes Cluster with Kind” section. A Kubernetes Cluster. Additionally, you will need a account. Quay.io Moving Images from Docker to Podman If you've just installed Podman on a system on which you've already used Docker to pull one or more images, you'll notice that running the command doesn't show your Docker images: podman images docker images REPOSITORY TAG IMAGE ID CREATED SIZE cassandra latest b571e0906e1b 10 days ago 324MB podman images REPOSITORY TAG IMAGE ID CREATED SIZE The reason why you don't see your Docker images is that Podman runs without privileges. Thus, its repository is located in the user's home directory - . However, Podman can import an image directly from the Docker daemon running on your machine, through the transport. root ~/.local/share/containers docker-daemon In this section, you'll use Docker to pull the image. Then, you'll import it into Podman. Lastly, you'll run the image with Podman. hello-world hello-world 1. Download and run the image by executing the following command: hello-world sudo docker run hello-world Unable to find image locally latest: Pulling from library/hello-world 1b930d010525: Pull complete Digest: sha256:9572f7cdcee8591948c2963463447a53466950b3fc15a247fcad1917ca215a2f Status: Downloaded newer image hello-world:latest Hello from Docker! This message shows that your installation appears to be working correctly. To generate this message, Docker took the following steps: 1. The Docker client contacted the Docker daemon. 2. The Docker daemon pulled the image from the Docker Hub. (amd64) 3. The Docker daemon created a new container from that image runs the executable that produces the output you are currently reading. 4. The Docker daemon streamed that output to the Docker client, sent it to your terminal. To try something more ambitious, you can run an Ubuntu container with: $ docker run -it ubuntu bash Share images, automate workflows, and more with a free Docker ID: https://hub.docker.com/ For more examples and ideas, visit: https://docs.docker.com/get-started/ 'hello-world:latest' for "hello-world" which which 2. The following command lists the Docker images on your system and pretty-prints the output: docker images sudo docker images --format '{{.Repository}}:{{.Tag}}' hello-world:latest 3. Enter the command specifying the transport ( ) and the name of the image, separated by : podman pull docker-daemon : podman pull docker-daemon:hello-world:latest Getting image signatures Copying blob af0b15c8625b Copying config fce289e99e Writing manifest to image destination Storing signatures fce289e99eb9bca977dae136fbe2a82b6b7d4c372474c9235adc1741675f587e source done done 4. Once you've imported the image, running the command will display the image: podman images hello-world podman images REPOSITORY TAG IMAGE ID CREATED SIZE docker.io/library/hello-world latest fce289e99eb9 13 months ago 5.94 kB 5. To run the image, enter the following command: podman run podman run hello-world Hello from Docker! This message shows that your installation appears to be working correctly. To generate this message, Docker took the following steps: 1. The Docker client contacted the Docker daemon. 2. The Docker daemon pulled the image from the Docker Hub. (amd64) 3. The Docker daemon created a new container from that image runs the executable that produces the output you are currently reading. 4. The Docker daemon streamed that output to the Docker client, sent it to your terminal. To try something more ambitious, you can run an Ubuntu container with: $ docker run -it ubuntu bash Share images, automate workflows, and more with a free Docker ID: https://hub.docker.com/ For more examples and ideas, visit: https://docs.docker.com/get-started/ "hello-world" which which Creating a Basic Nuxt.js Project For the scope of this tutorial, we’ll create a simple web-application using , a progressive Vue-based framework that aims to provide a great experience for developers. Then, in the next sections, you'll use Podman to create a container image for your project and push it Quay.io. Lastly, you'll use Docker to run the container image. Nuxt.JS 1. Nuxt.JS is distributed as an NPM package. To install it, fire up a terminal window, and execute the following command: npm install nuxt + nuxt@2.11.0 added 1067 packages from 490 contributors and audited 9750 packages 75.666s found 0 vulnerabilities in Note that the above output was truncated for brevity. 2. With Nuxt.JS installed on your computer, you can create a new bare-bones project: npx create-nuxt-app podman-nuxtjs-demo You will be prompted to answer a few questions: create-nuxt-app v2.14.0 ✨ Generating Nuxt.js project podman-nuxtjs-demo ? Project name podman-nuxtjs-demo ? Project description Podman Nuxt.JS demo ? Author name Appfleet ? Choose the package manager Npm ? Choose UI framework Bootstrap Vue ? Choose custom server framework None (Recommended) ? Choose Nuxt.js modules (Press to select, to toggle all, to invert selectio n) ? Choose linting tools ESLint ? Choose framework None ? Choose rendering mode Universal (SSR) ? Choose development tools jsconfig.json (Recommended VS Code) in test for Once you answer these questions, will install the required dependencies: npm 🎉 Successfully created project podman-nuxtjs-demo To get started: podman-nuxtjs-demo npm run dev To build & start production: podman-nuxtjs-demo npm run build npm run start cd for cd Note that the above output was truncated for brevity. 3. Enter the following commands to start your new application: podman-nuxtjs-demo/ && npm run dev cd > podman-nuxtjs-demo@1.0.0 dev /home/vagrant/podman-nuxtjs-demo > nuxt ╭─────────────────────────────────────────────╮ │ │ │ Nuxt.js v2.11.0 │ │ Running development mode (universal) │ │ │ │ Listening on: http://localhost:3000/ │ │ │ ╰─────────────────────────────────────────────╯ ℹ Preparing project development 14:39:30 ℹ Initial build may take a 14:39:30 ✔ Builder initialized 14:39:30 ✔ Nuxt files generated 14:39:30 ✔ Client Compiled successfully 23.53s ✔ Server Compiled successfully 17.82s ℹ Waiting file changes 14:39:56 ℹ Memory usage: 209 MB (RSS: 346 MB) 14:39:56 in for while in in for 4. Point your browser to , and you should see something similar to the screenshot below: http://localhost:3000 Building a Container Image for Your Nuxt.JS Project In this section, we'll look at how you can use Podman to build a container image for the project. podman-nextjs-demo 1. Create a file called and place the following content into it: Dockerfile FROM node:10 WORKDIR /usr/src/app COPY package*.json ./ RUN npm install COPY . . EXPOSE 3000 CMD [ , , ] "npm" "run" "dev" ☞ For a quick refresher on the above Dockerfile commands, refer the Create a Docker Image section from the Debug a Node.js Application Running in a Docker Container tutorial. 2. To avoid sending large files to the build context and speed up the process, create a file called with the following content: .dockerignore node_modules npm-debug.log .nuxt As you can see, this is just a plain-text file containing names of the files and directories that Podman should exclude from the build. 3. Build the image. Execute the following command, specifying the flag with the tagged name Podman will apply to the build image: podman build -t podman build -t podman-nuxtjs-demo:podman . STEP 1: FROM node:10 STEP 2: RUN mkdir -p /usr/src/nuxt-app --> Using cache c7198c4f08b90ecb5575bbce23fc095e5c65fe5dc4b4f77b23192e2eae094d6f STEP 3: WORKDIR /usr/src/nuxt-app --> Using cache f1cc5aba3f36e122513c5ff0410f862d6099bcee886453f7fb30859f66e0ac78 STEP 4: COPY . /usr/src/nuxt-app/ --> Using cache fb4c322c98b41d446f5cceb88b3f9c451751d0cfe8ed9d0e6eb153919b498da3 STEP 5: RUN npm install --> Using cache bb5324e79782b4522048dcc5f0f02c41b56e12198438aa59a7588a6824a435e1 STEP 6: RUN npm run build > podman-nuxtjs-demo@1.0.0 build /usr/src/nuxt-app > nuxt build ℹ Production build ✔ Builder initialized ✔ Nuxt files generated ✔ Client Compiled successfully 2.95m ✔ Server Compiled successfully 10.91s Hash: 7c4493c4d1c7b235dd8e Version: webpack 4.41.6 Time: 177257ms Built at: 02/11/2020 4:48:17 PM Asset Size Chunks Chunk Names ../server/client.manifest.json 16.1 KiB [emitted] 7d497fe85470995d6e29.js 2.99 KiB 2 [emitted] [immutable] pages/index 848739217655a36af267.js 671 KiB 4 [emitted] [immutable] [big] vendors.app 90036491716edfc3e86d.js 159 KiB 1 [emitted] [immutable] commons.app LICENSES 1.95 KiB [emitted] b625f5fc00e8ff962762.js 2.31 KiB 3 [emitted] [immutable] runtime eac7116f7d28455b0958.js 36 KiB 0 [emitted] [immutable] app + 2 hidden assets Entrypoint app = b625f5fc00e8ff962762.js 90036491716edfc3e86d.js 848739217655a36af267.js eac7116f7d28455b0958.js WARNING asset size : The following asset(s) exceed the recommended size (244 KiB). This can impact web performance. Assets: 848739217655a36af267.js (671 KiB) Hash: e3d9cfd644a086dc9c5b Version: webpack 4.41.6 Time: 10916ms Built at: 02/11/2020 4:48:29 PM Asset Size Chunks Chunk Names d1d703b09adf296a453d.js 3.07 KiB 1 [emitted] [immutable] pages/index server.js 222 KiB 0 [emitted] app server.manifest.json 145 bytes [emitted] Entrypoint app = server.js 0d239b0083a60482b4b5fa60a99b96dd22045822e50fbd83b8a369d8179bf307 STEP 7: EXPOSE 3000 1d037e041dd4a8d6c94a9f6fb8fe6578f5e00d27aab9168bad83e7ab260bbeae STEP 8: ENV NUXT_HOST=0.0.0.0 40d684a5441a8da38ed5198be722719f393be13a855a9e85cbc49e5c7155f7cc STEP 9: ENV NUXT_PORT=3000 7d07961e058d66e172f4b9e01d50fb355c16060a990252c5bc7cd35d960f5f72 STEP 10: CMD [ , , ] STEP 11: COMMIT podman-nuxtjs-demo:podman 54c55a8a44f30105371652bc2c25e0fbba200ad6c945654077151194aa0a66fe in in in limit limit "npm" "run" "dev" 4. At this point, you can check that everything went well with: podman images REPOSITORY TAG IMAGE ID CREATED SIZE localhost/podman-nuxtjs-demo podman 54c55a8a44f3 About a minute ago 1.09 GB docker.io/library/node 10 bb78c02ca3bf 4 days ago 937 MB 5. To run the container, enter the run command and pass it the following arguments: podman-nuxtjs-demo:podman podman to specify that the container should be run in the background and that Podman should allocate a pseudo-TTY -dt with the port on the host (3000) that’ll be forwarded to the container port (3000), separated by . -p : The name of your image ( ) podman-nuxtjs-demo:podman podman run -dt -p 3000:3000/tcp podman-nuxtjs-demo:podman This will print out to the console the container ID: 4de08084dd1d33fcdae96cd493b3eb20406ea89ce2a3e8dbc833b38c2243ce43 6. You can list your running containers with: podman ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 4de08084dd1d localhost/podman-nuxtjs-demo:podman npm run dev 4 seconds ago Up 4 seconds ago 0.0.0.0:3000->3000/tcp objective_neumann 7. To retrieve detailed information about your running container, enter the command specifying the container ID: podman inspect podman inspect 4de08084dd1d33fcdae96cd493b3eb20406ea89ce2a3e8dbc833b38c2243ce43 podman inspect 4de08084dd1d33fcdae96cd493b3eb20406ea89ce2a3e8dbc833b38c2243ce43 [ { : , : , : , : [ , , ], : { : , : , : , : , : , : , : , : 10637, : 10628, : 0, : , : , : , : { : , : 0, : null } }, : , : , : , : , "Id" "4de08084dd1d33fcdae96cd493b3eb20406ea89ce2a3e8dbc833b38c2243ce43" "Created" "2020-02-11T17:00:06.819669549Z" "Path" "docker-entrypoint.sh" "Args" "npm" "run" "dev" "State" "OciVersion" "1.0.1-dev" "Status" "running" "Running" true "Paused" false "Restarting" false "OOMKilled" false "Dead" false "Pid" "ConmonPid" "ExitCode" "Error" "" "StartedAt" "2020-02-11T17:00:07.317812139Z" "FinishedAt" "0001-01-01T00:00:00Z" "Healthcheck" "Status" "" "FailingStreak" "Log" "Image" "54c55a8a44f30105371652bc2c25e0fbba200ad6c945654077151194aa0a66fe" "ImageName" "localhost/podman-nuxtjs-demo:podman" "Rootfs" "" "Pod" "" Note that the above output was truncated for brevity. To retrieve the logs from your container, run the command specifying the container ID or the flag: podman logs --latest podman logs --latest > podman-nuxtjs-demo@1.0.0 dev /usr/src/nuxt-app > nuxt ╭─────────────────────────────────────────────╮ │ │ │ Nuxt.js v2.11.0 │ │ Running development mode (universal) │ │ │ │ Listening on: http://10.0.2.100:3000/ │ │ │ ╰─────────────────────────────────────────────╯ ℹ Preparing project development ℹ Initial build may take a ✔ Builder initialized ✔ Nuxt files generated ✔ Client Compiled successfully 25.36s ✔ Server Compiled successfully 19.21s ℹ Waiting file changes ℹ Memory usage: 254 MB (RSS: 342 MB) in for while in in for 9. Display the list of running processes inside your container: podman top 4de08084dd1d USER PID PPID %CPU ELAPSED TTY TIME COMMAND root 1 0 0.000 3m52.098907307s pts/0 0s npm root 17 1 0.000 3m51.099829437s pts/0 0s sh -c nuxt root 18 17 11.683 3m51.099997015s pts/0 27s node /usr/src/nuxt-app/node_modules/.bin/nuxt Push Your Podman Image to Quay.io 1. First, you must generate an encrypted password. Point your browser to , and then navigate to the page: http://quay.io Account Settings 2. On the page, select : Account Settings Generate Encrypted Password 3. When prompted, enter your Quay.io password: 4. From the sidebar on the left, select . Then, copy your encrypted password: Docker Login 5. You can now log in to Quay.io. Enter the command specifying: podman login The registry server ( ) quay.io The flag with your username -u The flag with the encrypted password you retrieved earlier -p podman login quay.io -u -p= " " Login Succeeded! 6. To push the image to Quay.io, enter the following command: podman-nuxtjs-demo podman push podman push podman-nuxtjs-demo:podman quay.io/andreipope/podman-nuxtjs-demo:podman Getting image signatures Copying blob 69dfa7bd7a92 Copying blob 4d1ab3827f6b Copying blob 7948c3e5790c Copying blob 01727b1a72df Copying blob 03dc1830d2d5 Copying blob 1d7382716a27 Copying blob 062fc3317d1a Copying blob 3d36b8a4efb1 Copying blob 1708ebc408a9 Copying blob 0aacf878561f Copying blob c49b91e9cfd0 Copying blob 4294ef3571b7 Copying blob 1da55789948c Copying config 54c55a8a44 Writing manifest to image destination Copying config 54c55a8a44 Writing manifest to image destination Storing signatures source done done done done done done done done done done done done done done done In the above command, do not forget to replace our username ( andreipope ) with yours. 7. Point your browser to , navigate to the repository, and make sure the repository is public: https://quay.io/ podman-nuxtjs-demo Run Your Podman Image with Docker Container images are compatible between Podman and Docker. In this section, you'll use Docker to pull the image from Quay.io and run it. Ideally, you would want to run this on a different machine. podman-nuxtjs-demo 1. You can log in to Quay.io by entering the command and passing it the following parameters: docker login The flag with your username -u The flag with your encrypted password (you retrieved it from Quay.io in the previous section) -p The name of the registry ( ) quay.io docker login -u= -p= quay.io " " "YOUR_ENCRYPTED_PASSWORD" WARNING! Using --password via the CLI is insecure. Use --password-stdin. Login Succeeded 2. To run the image, you can use the following command: podman-nuxtjs-demo docker run -dt -p 3000:3000/tcp quay.io/andreipope/podman-nuxtjs-demo:podman Unable to find image locally podman: Pulling from andreipope/podman-nuxtjs-demo 03644a8453bd: Pull complete e2c9fbbb35b2: Pull complete 0c33fe27c91c: Pull complete 957ac2567af6: Pull complete 934d2e09d84d: Pull complete 50c60e376f59: Pull complete 3c43a52a3ecc: Pull complete e74942a3267a: Pull complete af1466e8bc5b: Pull complete 3f24948a552e: Pull complete df2fea35a007: Pull complete 7045f2526057: Pull complete 5090c2f6d806: Pull complete Digest: sha256:fcf90cfc3fe1d0f7e975db8a271003cdd51d6f177e490eb39ec1e44d3659b815 Status: Downloaded newer image quay.io/andreipope/podman-nuxtjs-demo:podman 1c0981690d66f2cd8cb77e9573f1dd4e9d7700869e08797b42fc33590d8baabf 'quay.io/andreipope/podman-nuxtjs-demo:podman' for 3. Wait a bit until Docker pulls the image and creates the container. Then, issue the command to display the list of running containers: docker ps docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 1c0981690d66 quay.io/andreipope/podman-nuxtjs-demo:podman 25 seconds ago Up 20 seconds 0.0.0.0:3000->3000/tcp practical_bose "docker-entrypoint.s…" 4. To make sure everything works as expected, point your browser to . You should see something similar to the screenshot below: http://localhost:3000 Creating Pods Until now, you've used Podman similarly to how Docker is used. However, Podman brings a couple of new features such as the ability to create pods. A Pod is a group of tightly-coupled containers that share their storage and network resources. In a nutshell, you can use a Pod to model a logical host. In this section, we'll walk you through the process of creating a Pod comprised of the podman-nuxtjs-demo container and a PostgreSQL database. Note that it is beyond the scope of this tutorial to show how you can configure the storage and network for your Pod. 1. Create a pod with the container. Enter the with the following arguments: podman-nuxtjs-demo podman run to specify that the container should be run in the background and that Podman should allocate a pseudo-TTY -dt with the name of your new Pod. Specifying indicates that you want to create a new Pod. Otherwise, Podman tries to attach the container to an existing Pod. --pod -new with the port on host (3000) that’ll be forwarded to the container port (3000), separated by . -p : The name of your image ( ) podman-nuxtjs-demo:podman podman run -dt --pod new:podman_demo -p 3000:3000/tcp quay.io/andreipope/podman-nuxtjs-demo:podman This will print the identifier of your new Pod: 972c7c1db0c31a42ba4b41025078dfc6abb046f503aa413d6cca313068042041 2. You can display the list of running Pods with the command: podman pod list podman pod list POD ID NAME STATUS CREATED d15a2abd9d5b podman_demo Running 32 seconds ago 2 6a5bc0360ae2 # OF CONTAINERS INFRA ID In the output above, the number of containers is . This is because all Podman Pods include something called an container, which does nothing except that it goes to sleep. This way, it holds the namespace associated with the Pod so that Podman can attach other containers to the Pod. 2 Infra 3. Print the list of running containers by entering the command followed by the and flags. This lists all containers and prints the identifiers and the names of the Pods your containers are associated with: podman ps -a -p podman ps -ap CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES POD 972c7c1db0c3 quay.io/andreipope/podman-nuxtjs-demo:podman npm run dev 56 seconds ago Up 55 seconds ago 0.0.0.0:3000->3000/tcp festive_yonath d15a2abd9d5b 6a5bc0360ae2 k8s.gcr.io/pause:3.1 56 seconds ago Up 55 seconds ago 0.0.0.0:3000->3000/tcp d15a2abd9d5b-infra d15a2abd9d5b As you can see, the container uses the image. Infra k8s.gcr.io/pause 4. Run the image and associate it with the Pod: postgres:11-alpine podman_demo podman run -dt --pod podman_demo postgres:11-alpine d395bed40988a953257b9501497c66b886b2fb6e81f48aa0ac89d7cfe2639b75 5. This takes a bit of time to complete. Once everything is ready, you should see that the number of containers has been increased to : 3 podman pod list POD ID NAME STATUS CREATED d15a2abd9d5b podman_demo Running 8 minutes ago 3 6a5bc0360ae2 # OF CONTAINERS INFRA ID 6. You can display the list of your running containers with the following command: podman ps podman ps -ap CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES POD ab5bd4810494 docker.io/library/postgres:11-alpine postgres 5 minutes ago Up 3 minutes ago 0.0.0.0:3000->3000/tcp dreamy_jackson d15a2abd9d5b 972c7c1db0c3 quay.io/andreipope/podman-nuxtjs-demo:podman npm run dev 9 minutes ago Up 9 minutes ago 0.0.0.0:3000->3000/tcp festive_yonath d15a2abd9d5b 6a5bc0360ae2 k8s.gcr.io/pause:3.1 9 minutes ago Up 9 minutes ago 7. As an example, you can stop the container. The other containers in the Pod won't be affected, and the status of the Pod will show as : podman-nuxtjs-demo Running podman stop 972c7c1db0c3 972c7c1db0c31a42ba4b41025078dfc6abb046f503aa413d6cca313068042041 podman pod ps POD ID NAME STATUS CREATED d15a2abd9d5b podman_demo Running 12 minutes ago 3 6a5bc0360ae2 # OF CONTAINERS INFRA ID 8. To start again the container, enter the command followed by the identifier of the container you want to start: podman start podman start 972c7c1db0c3 972c7c1db0c31a42ba4b41025078dfc6abb046f503aa413d6cca313068042041 9. At this point, if you run the command, you should see that the status of the container is now : podman ps -ap podman-nuxtjs-demo Up podman ps -ap CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES POD ab5bd4810494 docker.io/library/postgres:11-alpine postgres 7 minutes ago Up 5 minutes ago 0.0.0.0:3000->3000/tcp dreamy_jackson d15a2abd9d5b 972c7c1db0c3 quay.io/andreipope/podman-nuxtjs-demo:podman npm run dev 14 minutes ago Up 54 seconds ago 0.0.0.0:3000->3000/tcp festive_yonath d15a2abd9d5b 6a5bc0360ae2 k8s.gcr.io/pause:3.1 14 minutes ago Up 14 minutes ago 0.0.0.0:3000->3000/tcp d15a2abd9d5b-infra d15a2abd9d5b 10. Lastly, let's top the pod: podman_demo podman pod stop podman_demo d15a2abd9d5bcb6f403515c0ed4dd4cb7df252a87591a88975b5573eb7f20900 11. Enter the following command to make sure your Pod is stopped: podman pod ps POD ID NAME STATUS CREATED d15a2abd9d5b podman_demo Stopped 17 minutes ago 3 6a5bc0360ae2 # OF CONTAINERS INFRA ID Generate a Kubernetes Pod Spec with Podman Podman can perform a snapshot of your container/Pod and generate a Kubernetes spec. This way, it makes it easier for you to orchestrate your containers with Kubernetes. For the scope of this section, we'll illustrate how to use Podman to generate a Kubernetes spec and deploy your Pod to Kubernetes. 1. To create a Kubernetes spec for a container and save it into a file called , run the following command: podman-nuxtjs-demo.yaml podman generate kube podman generate kube > podman-nuxtjs-demo.yaml 2. Let's take a look at what's inside the file: podman-nuxtjs-demo.yaml cat podman-nuxtjs-demo.yaml ```YAML apiVersion: v1 kind: Pod metadata: creationTimestamp: labels: app: objectiveneumann name: objectiveneumann spec: containers: - : - npm - run - dev env: - name: PATH value: /usr/ /sbin:/usr/ /bin:/usr/sbin:/usr/bin:/sbin:/bin - name: TERM value: xterm - name: HOSTNAME - name: container value: podman - name: NODE_VERSION value: 10.19.0 - name: YARN_VERSION value: 1.21.1 - name: NUXT_HOST value: 0.0.0.0 - name: NUXT_PORT value: image: localhost/podman-nuxtjs-demo:podman name: objectiveneumann ports: - containerPort: 3000 hostPort: 3000 protocol: TCP resources: {} securityContext: allowPrivilegeEscalation: capabilities: {} privileged: readOnlyRootFilesystem: tty: workingDir: /usr/src/nuxt-app status: {} # Generation of Kubernetes YAML is still under development! # # Save the output of this file and use kubectl create -f to import # it into Kubernetes. # # Created with podman-1.6.4 "2020-02-12T05:21:44Z" command local local "3000" true false false true There is a lot of output here, but the parts we're interested in are: and . You'll have to give them more meaningful names metadata.labels.app metadata.name spec.containers.image. Since in real life you'll have to pull the images from a registry, you must replace with the address of your Quay.io container image. localhost/podman-nuxtjs-demo:podman 3. Edit the content of the file to the following: podman-nuxtjs-demo.yaml apiVersion: v1 kind: Pod metadata: creationTimestamp: labels: app: podman-nuxtjs-demo name: podman-nuxtjs-demo spec: containers: - : - npm - run - dev env: - name: PATH value: /usr/ /sbin:/usr/ /bin:/usr/sbin:/usr/bin:/sbin:/bin - name: TERM value: xterm - name: HOSTNAME - name: container value: podman - name: NODE_VERSION value: 10.19.0 - name: YARN_VERSION value: 1.21.1 - name: NUXT_HOST value: 0.0.0.0 - name: NUXT_PORT value: image: quay.io/andreipope/podman-nuxtjs-demo:podman name: objectiveneumann ports: - containerPort: 3000 hostPort: 3000 protocol: TCP resources: {} securityContext: allowPrivilegeEscalation: capabilities: {} privileged: readOnlyRootFilesystem: tty: workingDir: /usr/src/nuxt-app status: {} # Generation of Kubernetes YAML is still under development! # # Save the output of this file and use kubectl create -f to import # it into Kubernetes. # # Created with podman-1.6.4 "2020-02-12T05:24:44Z" command local local "3000" true false false true The above spec uses the address of our container image - . Make sure you replace this with your address. quay.io/andreipope/podman-nuxtjs-demo:podman 4. Now, if your Quay.io repository is private, Kubernetes must authenticate with the registry to pull the image. Point your browser to , and then navigate to the section of your repository. http://quay.io Settings Select , and you'll be asked to type your password. From the sidebar on the left, select to download your Kubernetes secrets file: Generate Encrypted Password Kubernetes Secret 5. Next, you must refer to this Kubernetes secret from the . You can do this by adding a field similar to the one below: podman-nuxtjs-demo.yaml imagePullSecrets: - name: andreipope-pull-secret Note that the name of our Kubernetes secret is andreipope-pull-secret , but yours will be different. At this point, your file should look something like the following: podman-nuxtjs-demo.yaml apiVersion: v1 kind: Pod metadata: creationTimestamp: labels: app: podman-nuxtjs-demo name: podman-nuxtjs-demo spec: containers: - : - npm - run - dev env: - name: PATH value: /usr/ /sbin:/usr/ /bin:/usr/sbin:/usr/bin:/sbin:/bin - name: TERM value: xterm - name: HOSTNAME - name: container value: podman - name: NODE_VERSION value: 10.19.0 - name: YARN_VERSION value: 1.21.1 - name: NUXT_HOST value: 0.0.0.0 - name: NUXT_PORT value: image: quay.io/andreipope/podman-nuxtjs-demo:podman name: objectiveneumann ports: - containerPort: 3000 hostPort: 3000 protocol: TCP resources: {} securityContext: allowPrivilegeEscalation: capabilities: {} privileged: readOnlyRootFilesystem: tty: workingDir: /usr/src/nuxt-app imagePullSecrets: - name: andreipope-pull-secret status: {} # Generation of Kubernetes YAML is still under development! # # Save the output of this file and use kubectl create -f to import # it into Kubernetes. # # Created with podman-1.6.4 "2020-02-12T05:24:44Z" command local local "3000" true false false true Create a Kubernetes Cluster with Kind (Optional) Kind is a tool for running local Kubernetes clusters using Docker container "nodes". Follow the steps in this section if you don't have a running Kubernetes cluster: Create a file called with the following content: cluster.yaml kind create cluster --config cluster.yaml kind: Cluster apiVersion: kind.x-k8s.io/v1alpha4 nodes: - role: control-plane - role: worker - role: worker # three node (two workers) cluster config 2. Apply the spec: kind create cluster --config cluster.yaml Creating cluster ... ✓ Ensuring node image (kindest/node:v1.16.3) 🖼 ✓ Preparing nodes 📦 ✓ Writing configuration 📜 ✓ Starting control-plane 🕹️ ✓ Installing CNI 🔌 ✓ Installing StorageClass 💾 ✓ Joining worker nodes 🚜 Set kubectl context to You can now use your cluster with: "kind" "kind-kind" This creates a Kubernetes cluster with a control plane and two worker nodes. Deploying to Kubernetes 1. Apply your Kubernetes pull secrets spec. Enter the command specifying: kubectl create The flag with the name of the file (our example uses a file named ) -f andreipope-secret.yml The flag with the name of your namespace (we're using the default namespace) --namespace kubectl create -f andreipope-secret.yml --namespace=default secret/andreipope-pull-secret created 2. Now you're ready to apply the spec: podman-nuxt-js-demo kubectl apply -f podman-nuxt-js-demo.yaml pod/podman-nuxtjs-demo created 3. Monitor the status of your installation with: kubectl get pods NAME READY STATUS RESTARTS AGE podman-nuxtjs-demo 0/1 ContainerCreating 0 85s 4. You can retrieve more details about the status of your installation by entering the followed by the name of your Pod: kubectl describe pod kubectl describe pod podman-nuxtjs-demo Name: podman-nuxtjs-demo Namespace: default Priority: 0 Node: kind-worker2/172.17.0.3 Start Time: Wed, 12 Feb 2020 19:36:37 +0200 Labels: app=podman-nuxtjs-demo Annotations: kubectl.kubernetes.io/last-applied-configuration: { : , : , :{ :{}, : , :{ : quay.io/andreipope/podman-nuxtjs-demo:podman "apiVersion" "v1" "kind" "Pod" "metadata" "annotations" "creationTimestamp" "2020-02-12T05:24:44Z" "labels" "app" "podman-nuxtjs-dem... Status: Pending IP: IPs: Containers: objectiveneumann: Container ID: Image: quay.io/andreipope/podman-nuxtjs-demo:podman Image ID: Port: 3000/TCP Host Port: 3000/TCP Command: npm run dev State: Waiting Reason: ContainerCreating Ready: False Restart Count: 0 Requests: memory: 1Gi Environment: PATH: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin TERM: xterm HOSTNAME: container: podman NODE_VERSION: 10.19.0 YARN_VERSION: 1.21.1 NUXT_HOST: 0.0.0.0 NUXT_PORT: 3000 Mounts: /var/run/secrets/kubernetes.io/serviceaccount from default-token-rp6n5 (ro) Conditions: Type Status Initialized True Ready False ContainersReady False PodScheduled True Volumes: default-token-rp6n5: Type: Secret (a volume populated by a Secret) SecretName: default-token-rp6n5 Optional: false QoS Class: Burstable Node-Selectors: Tolerations: node.kubernetes.io/not-ready:NoExecute for 300s node.kubernetes.io/unreachable:NoExecute for 300s Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 57s default-scheduler Successfully assigned default/podman-nuxtjs-demo to kind-worker2 Normal Pulling 55s kubelet, kind-worker2 Pulling image " " As an alternative, you can list events with the following command: kubectl get events LAST SEEN TYPE REASON OBJECT MESSAGE 4m55s Normal RegisteredNode node/kind-control-plane Node kind-control-plane event: Registered Node kind-control-plane Controller 4m37s Normal Starting node/kind-control-plane Starting kube-proxy. 4m36s Normal NodeHasSufficientMemory node/kind-worker Node kind-worker status is now: NodeHasSufficientMemory 4m36s Normal NodeHasNoDiskPressure node/kind-worker Node kind-worker status is now: NodeHasNoDiskPressure 4m36s Normal NodeHasSufficientPID node/kind-worker Node kind-worker status is now: NodeHasSufficientPID 4m35s Normal RegisteredNode node/kind-worker Node kind-worker event: Registered Node kind-worker Controller 4m15s Normal Starting node/kind-worker Starting kube-proxy. 3m36s Normal NodeReady node/kind-worker Node kind-worker status is now: NodeReady 4m34s Normal NodeHasSufficientMemory node/kind-worker2 Node kind-worker2 status is now: NodeHasSufficientMemory 4m34s Normal NodeHasNoDiskPressure node/kind-worker2 Node kind-worker2 status is now: NodeHasNoDiskPressure 4m34s Normal NodeHasSufficientPID node/kind-worker2 Node kind-worker2 status is now: NodeHasSufficientPID 4m30s Normal RegisteredNode node/kind-worker2 Node kind-worker2 event: Registered Node kind-worker2 Controller 4m15s Normal Starting node/kind-worker2 Starting kube-proxy. 3m34s Normal NodeReady node/kind-worker2 Node kind-worker2 status is now: NodeReady 3m29s Normal Scheduled pod/podman-nuxtjs-demo Successfully assigned default/podman-nuxtjs-demo to kind-worker2 3m27s Normal Pulling pod/podman-nuxtjs-demo Pulling image in in in "quay.io/andreipope/podman-nuxtjs-demo:podman" 5. Wait a bit until the pod is created. Then, you can list all pods with: kubectl get pods NAME READY STATUS RESTARTS AGE podman-nuxtjs-demo 1/1 Running 0 7m34s 6. Now let's forward all requests made to to port 3000 on the Pod: http://localhost:3000 podman-nuxtjs-demo kubectl port-forward pod/podman-nuxtjs-demo 3000:3000 Forwarding from 127.0.0.1:3000 -> 3000 Forwarding from [::1]:3000 -> 3000 Handling connection 3000 Handling connection 3000 Handling connection 3000 Handling connection 3000 Handling connection 3000 Handling connection 3000 Handling connection 3000 for for for for for for for 7. Point your browser to . If everything works well, you should see something like the following: http://localhost:3000 Congratulations on completing this tutorial, now you know enough to use Podman as a replacement for Docker. In case you are interested, you may refer this to learn using Buildah. article Thanks for reading!