Difference between LXC and libcontainer [closed]

纵饮孤独 提交于 2019-11-30 06:25:40

That means Docker is abstracting itself from its original implementation, allowing other vendors (like CoreOS) to implement their own version of containers.


Note: since then (What’s the difference between runc, containerd, docker?) shows:

In 2016 the container space was booming and docker decided to split the monolith into separate parts, some of which other projects can even build on — that’s how containerd happened. That was Docker 1.11 (so pretty much ancient history).
Containerd is a daemon that acts as API facade for various container runtimes and OS. When using containerd, you no longer work with syscalls, instead you work with higher-level entities like snapshot and container — the rest is abstracted away.
If you want to understand containerd even more in depth, there’s a design documentation in their GitHub repo.
Under the hood, containerd uses runc to do all the linux work.

See more at "How containerd compares to runC"

I would rather recommend you to go through this link to have a complete understanding of why Docker started libcontainer

http://www.zdnet.com/article/docker-libcontainer-unifies-linux-container-powers/

As I am aware.. LXC was default execution driver for docker engine to execute its container/namespace and other. Docker developed 'libcontainer' and added to their docker engine. Correct me if I am wrong.

标签
易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!