4 ms·
So it uses xhyve...does this mean Docker runs up a full hypervisor per Docker process you run? That seems a bit excessive.
by smegel 11y ago
So it uses xhyve...does this mean Docker runs up a full hypervisor per Docker process you run? That seems a bit excessive.
- friism 11y agoThat's not the case - there's only one virtual machine shared by all containers.
- smegel 11y agoOh...that's interesting. That would even be useful on Linux to enable greater resource separation between processes...say being able to lock all Docker processes down to 1-2 cores on a machine and with a hard memory limit they can't exceed.
- pritambaral 11y agoThat's already possible with cgroups. Adding a virtualization layer even on Linux would be wasteful, since Docker runs natively on Linux anyway.
- zenlikethat 11y agoWhat you mention is a major reason why Linux containers were invented, and is already possible with Docker today. Take a look at the '--mem-limit' or '--cpu-shares' flags for 'docker run', for instance.
- cstrahan 11y agoI would bet money that it does not. The Virtualbox based solutions all create one VM and run all containers there -- why would they stop doing that just because they're using a different means of virtualization?
- smegel 11y agoWell part of me hoped this was actually Docker for Mac, not just running Docker inside a Linux VM. Guess what? I can do that on Windows 10 too and it works like a charm.