4 ms·
Good read, but "The tool that really runs your containers" isn't quite right either. Bocker (docker runtime in ~100 lines of bash) does a good job showing what
by tyingq 7y ago
Good read, but "The tool that really runs your containers" isn't quite right either.
Bocker (docker runtime in ~100 lines of bash) does a good job showing what's really happening. Basically namespaces and cgroups, both of which come with Linux. The source is probably the best "deep dive" on containers I've found.
https://github.com/p8952/bocker https://github.com/p8952/bocker
Docker thrives because of the repository of images, a great name, and some marketing. Runc thrives because it provides a nice wrapper around namespaces, mounts, cgroups, virtual network interfaces, etc. Neither really provides the magic, though...it's already there.
- monocasa 7y agoNamespaces and cgroups are orthogonal to OCI and runc. gvisor is an example that runs containers via runc without all that, using the same scheme as User Mode Linux instead.
- mav3rick 7y agoThese are at different abstraction levels.
- fodoj 7y agoI agree that the final “thing” that runs containers and provides isolation is Linux kernel, it’s also pointed out in the article :-) Thanks for the feedback! Bocker looks like a fun little project indeed