4 ms·
A container, while it can be many processes, in the case of Docker is just one process. So its just a better Operating System process... Why then is there all
by yazaddaruvala 12y ago
A container, while it can be many processes, in the case of Docker is just one process. So its just a better Operating System process...
Why then is there all this fuss about how these projects are organized? If its a good idea (which it is) won't Linus just reimplement(conform) all of these projects and move them into the kernel anyways?
- vidarh 12y ago> in the case of Docker is just one process. That is not true. It can be just one process. It does not have to be. > So its just a better Operating System process No. That's just a tiny bit of what Docker provides, and even that part of what Docker provides is largely "packaging" of cgroups functionality. That was largely there with tools like LXC The real value Docker provides is a means of building and managing images, and mediating things like capabilities and port mapping in a user friendly way > won't Linus just reimplement(conform) all of these projects and move them into the kernel anyways? Not a chance. There's no reason why these things needs to be done in kernel space. Some features that they may want, such as improvement to filesystem overlay support, or low level "plumbing" to make overlay networks more efficient, could end up in the kernel if someone comes up with something good, but there'd still be plenty to do for the userspace tools.