Book Image

Podman for DevOps

By : Alessandro Arrichiello, Gianni Salinetti
Book Image

Podman for DevOps

By: Alessandro Arrichiello, Gianni Salinetti

Overview of this book

As containers have become the new de facto standard for packaging applications and their dependencies, understanding how to implement, build, and manage them is now an essential skill for developers, system administrators, and SRE/operations teams. Podman and its companion tools Buildah and Skopeo make a great toolset to boost the development, execution, and management of containerized applications. Starting with the basic concepts of containerization and its underlying technology, this book will help you get your first container up and running with Podman. You'll explore the complete toolkit and go over the development of new containers, their lifecycle management, troubleshooting, and security aspects. Together with Podman, the book illustrates Buildah and Skopeo to complete the tools ecosystem and cover the complete workflow for building, releasing, and managing optimized container images. Podman for DevOps provides a comprehensive view of the full-stack container technology and its relationship with the operating system foundations, along with crucial topics such as networking, monitoring, and integration with systemd, docker-compose, and Kubernetes. By the end of this DevOps book, you'll have developed the skills needed to build and package your applications inside containers as well as to deploy, manage, and integrate them with system services.
Table of Contents (19 chapters)
1
Section 1: From Theory to Practice: Running Containers with Podman
7
Section 2: Building Containers from Scratch with Buildah
12
Section 3: Managing and Integrating Containers Securely

Podman commands versus Docker commands

As we saw in the previous section, as well as in Chapter 2, Comparing Podman and Docker, the Podman CLI is based on the Docker CLI. However, because Podman does not require a runtime daemon to work, some of the Docker commands may not be directly available or they could require some workarounds.

The command list is exceptionally long, so the following table only specifies a few:

As you can see, the command's name is the same as comparing the docker command with the podman command. However, even though the name is the same, due to architectural differences between Podman and Docker, some features or behaviors could be different.

Behavioral differences between Podman and Docker

The following commands were intentionally implemented in another way by the Podman development team:

  • podman volume create: This command will fail if the volume already exists. In Docker, this command is idempotent, which means...