容器与runC的比较 [英] How containerd compares to runC

问题描述

这两个如何比较？据我了解，runC是容器的运行时环境。这意味着该组件提供了运行容器的必要环境。那么，这里的集装箱的作用是什么？如果剩下的事情（网络，卷管理等）完成了，那么Doc​​ker Engine的作用是什么？集装箱垫片又如何呢？基本上，我试图了解这些组件中的每一个。

解决方案

我将简要概述一下开始：

• 
  
  

  更多链接：

  
  
  
  
  
  • 打开容器规范
  
  
  • 很棒的dockercon 2016演示文稿
  
  
  
  

  How these two compare? As far as I understand, runC is a runtime environment for containers. That means that this component provides the necessary environment to run containers. What is the role of the containerd here then? If it does the rest (networking, volume management, etc) then what is the role of the Docker Engine? And what about containerd-shim? Basically, I'm trying to understand what each of these components do.

  解决方案

  I will give a high level overview to get you started:

  • containerd is a container runtime which can manage a complete container lifecycle - from image transfer/storage to container execution, supervision and networking.
  • container-shim handle headless containers, meaning once runc initializes the containers, it exits handing the containers over to the container-shim which acts as some middleman.
  • runc is lightweight universal run time container, which abides by the OCI specification. runc is used by containerd for spawning and running containers according to OCI spec. It is also the repackaging of libcontainer.
  • grpc used for communication between containerd and docker-engine.
  • OCI maintains the OCI specification for runtime and images. The current docker versions support OCI image and runtime specs.

  More Links:

  • Open Container Specification
  • A nice dockercon 2016 presentation

  这篇关于容器与runC的比较的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！