Shulou(Shulou.com)06/01 Report--

This article will explain in detail how to use the podman container tool. The editor thinks it is very practical, so I share it with you as a reference. I hope you can get something after reading this article.

Introduction to podman

Podman is an open source project that can be used on most Linux platforms and open source on GitHub. Podman is a daemon-free container engine for developing, managing, and running Open Container Initiative (OCI) containers and container images on Linux systems. Podman provides a command line front end compatible with Docker, which can simply be used as a Docker cli. Simply put, you can simply add the alias: alias docker = podman to use podman.

Containers under the control of Podman can be run by root users or by non-privileged users. Podman manages the entire ecosystem of containers, including pod, containers, container images, and container volumes using libpod library. Podman focuses on helping you maintain and modify all the commands and functions of the OCI container image, such as pulling and tagging. It allows you to create, run, and maintain containers created from these images in a production environment.

Official website: https://podman.io/

Installation documentation: https://github.com/containers/libpod/blob/master/install.md

Configuration reference: https://github.com/containers/image/blob/master/docs/containers-registries.conf.5.md

What are the main differences between Podman and Docker?

When dockers implements CRI, it needs a daemon, and then it needs to run as root, so this also brings security risks.

Podman does not require daemons and does not require root users to run, which is more reasonable than docker in terms of logical architecture.

In the running system of docker, multiple daemon are needed to call the implementation RunC of OCI.

In container-managed links, the implementation of Docker Engine is dockerd

Daemon, which needs to run as root in linux, and dockerd calls containerd,containerd to call containerd-shim before runC can be called. As the name implies, shim acts as a "gasket" to prevent the parent process from withdrawing from affecting the operation and training of the container.

Podman calls OCI,runtime (runC) directly, using common as the management tool for the container process, but does not require a daemon like dockerd, which runs as root.

In the podman system, there is a daemon called common, whose running path is usually / usr/libexec/podman/conmon, which is the parent of each container process, each container has one, and the parent of common is usually process 1. Common in podman is actually equivalent to containerd-shim in docker system.

Podman installation and use

Install using the centos official yum source

$yum install-y podman$ podman versionVersion: 1.4.4RemoteAPI Version: 1Go Version: go1.10.3OS/Arch: linux/amd64 configure Image acceleration

The Aliyun mirror accelerator is used here.

Cp / etc/containers/registries.conf {, .bak} cat > / etc/containers/registries.conf > .bashrc $source .bashrc $docker ps-aCONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES1fc033bb2209 docker.io/library/centos:latest sleep 3600 7 minutes ago Up 7 minutes ago test this article on "how to use podman Container tools" ends here. I hope the above content can be of some help to you. So that you can learn more knowledge, if you think the article is good, please share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.