3 ms·
> Think of them as processes with additional isolation from each other. That's true, but as VMs also isolate processes from each other, this can confuse others
by nailer 7y ago
> Think of them as processes with additional isolation from each other.
That's true, but as VMs also isolate processes from each other, this can confuse others. Let's be more exact:
A VM = isolated kernel and userspace.
- Advantages: security
- Disadvantages: speed
A container = isolated userspace only. Shared kernel.
- Advantages: speed, size
- Disadvantages: security
Both can have pre-created images to avoid the problem of recreating workspace. Docker did not invent orchestration.
- notyourday 7y ago> - Disadvantages: speed Nuh? Of starting, sure. Of running? A margin of error.
- nailer 7y agoRunning an app inside a container on bare metal is way faster than running an app in a VM on bare metal. - Containers in this case: userspace on kernel on hardware - VMs in this case: userspace on kernel on virtual hardware on kernel on hardware. There are very fast VMs (the Firecracker MIcroVM) but they're not in popular use.
- notyourday 7y agoYou are hopelessly out of date. VMs are not Xen with emulation. Neither are they the original VMware. Nor are they QEMU without acceleration. VMs are qemu-system-x86_64 -machine accel=kvm or whatever is the platform specific way to run a VM under a hypervisor. This has been the case since hypervisors showed up on the scene, aka right after what was the predecessor of Virtuozzo
- nailer 7y agoXen was never an emulator. That's technically incorrect. Not does the definition of VM change because of hardware acceleration. That's also technically incorrect.
- notyourday 7y agoIt should have been VMware with emulation, not Xen. You are correct The overhead of running a VM absolutely changes depending on whether it is a type 1 hypervisor or a type 2 hypervisor or if the runner/monitor supports acceleration. You can run a VM with QEMU without accel=kvm and it will be dog slow. Try it.
- nailer 7y agoI know re qemu and hypervisor types. VMware was never an emulator, but TBH we agree more than we disagree - have a good weekend
- KaiserPro 7y agospeed, possibly, possibly not. For CPU/memory, yes. For network, possibly (lots of iptables re-writes) for disk, not so much, docker(depending on what driver you have) suffers from write amplification.