dockerd vs docker-containerd vs docker-runc vs docker-containerd-ctr vs docker-containerd-shim [英] dockerd vs docker-containerd vs docker-runc vs docker-containerd-ctr vs docker-containerd-shim
问题描述
这些东西现在真的变得混乱了.有人可以解释发生了什么吗?只是直线的一线差异.
This stuff is really getting confused now. Can someone please explain what's going on. Just the straight one liner difference.
-
dockerd
-
libcontainerd
-
containerd
-
docker-containerd
-
docker-runc
-
docker-containerd-ctr
-
docker-containerd-shim
dockerd
libcontainerd
containerd
docker-containerd
docker-runc
docker-containerd-ctr
docker-containerd-shim
谢谢
推荐答案
dockerd -Docker守护程序本身.列表中最高级的组件,也是列出的唯一"Docker"产品.提供Docker的所有出色的UX功能.
dockerd - The Docker daemon itself. The highest level component in your list and also the only 'Docker' product listed. Provides all the nice UX features of Docker.
(docker-)containerd -还有一个守护程序,在Unix套接字上侦听,公开gRPC端点.处理所有底层容器管理任务,存储,图像分发,网络附件等...
(docker-)containerd - Also a daemon, listening on a Unix socket, exposes gRPC endpoints. Handles all the low-level container management tasks, storage, image distribution, network attachment, etc...
(docker-)containerd-ctr -一种直接与容器通信的轻量级CLI.可以将其视为码头工人"对码头工人"的方式.
(docker-)containerd-ctr - A lightweight CLI to directly communicate with containerd. Think of it as how 'docker' is to 'dockerd'.
(docker-)runc -用于实际运行容器的轻量级二进制文件.处理与Linux功能(例如cgroup,名称空间等)的低级接口.
(docker-)runc - A lightweight binary for actually running containers. Deals with the low-level interfacing with Linux capabilities like cgroups, namespaces, etc...
(docker-)containerd-shim -在runC实际运行容器之后,它退出(这使我们不再对容器负责任何长时间运行的进程).垫片是位于容器和runc之间的组件,以方便此操作.
(docker-)containerd-shim - After runC actually runs the container, it exits (allowing us to not have any long-running processes responsible for our containers). The shim is the component which sits between containerd and runc to facilitate this.
这篇关于dockerd vs docker-containerd vs docker-runc vs docker-containerd-ctr vs docker-containerd-shim的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!