docker - LXC 和 libcontainer 的区别

Question

关闭。这个问题需要更多 focused .它目前不接受答案。

---

想要改进这个问题吗？ 更新问题，使其只关注一个问题 editing this post .

关闭 3 年前。

Improve this question

在浏览 docker 文档时，我发现 docker 现在使用的是 libcontainer 而不是 LXC。有没有人知道 libcontainer 如何比 LXC 更好(如果是这样..)？

Answer 1

• Linux Containers (LXC) 在 docker 0.9 之前使用(在 March 13, 2014, with the release of version 0.9 上，Docker 放弃了 LXC 作为默认执行环境，并用自己的 libcontainer 库替换它)作为 docker 的一个执行驱动程序，并为 Linux 内核包含提供了一个用户空间接口(interface)特征。它非常特定于 Linux

• libcontainer(现为 opencontainers/runc )是一种抽象，以支持更广泛的隔离技术，如 described in this article

这意味着 Docker 将自己从其原始实现中抽象出来，允许其他供应商(如 CoreOS)实现自己的容器版本。

---

注意:从那时起(What’s the difference between runc, containerd, docker?)显示:

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.

在“How containerd compares to runC”查看更多信息