4 ms·
For those utterly confused by this story, CoreOS is for running Containers. Containers can be thought of as way of packaging an entire runtime environment whic
by srgseg 13y ago
For those utterly confused by this story, CoreOS is for running Containers.
Containers can be thought of as way of packaging an entire runtime environment which is more lightweight and more universally deployable than creating a virtual machine image.
This one slide explains it well: http://www.docker.io/static/img/about/docker_vm.jpg http://www.docker.io/static/img/about/docker_vm.jpg
- stephengillie 13y agoLooking at the slide, the Microsoft equivalent seems to be app pools running in IIS.
- dman 13y agoHow does the "appropriate" sharing of bins / libs take place?
- FooBarWidget 13y agoNothing is shared at all between containers besides the kernel. Inside a container, apps share libraries and binaries.
- jtgeibel 13y agoThe containers can share a file system layer which is mounted read only. Without write access the containers can't interfere with each other and there only needs to be one copy of these shared files on the host. With something like AUFS (like what docker does) a R/W layer can be placed on top of this allowing the guest container to modify its own files without impacting the underlying shared read only layer.