This is exactly what Docker containers AREN'T.
Don't think of containers like tiny VMs. Think of them as processes with additional isolation from each other.
This is exactly what Docker containers AREN'T.
Don't think of containers like tiny VMs. Think of them as processes with additional isolation from each other.
Under the hood they are simply a process isolated with namespaces, but their behavior on the outside feels like getting a VM.
Unless one is 31337-rockstar-ninja-IQ150-programmer, the uptake of new skills is painful and takes time. The pedagogical process is important. It's totally OK to not know how anything works as long as you acknowledge that and are willing to learn.
I'm mostly an ops person in outlook, although I was a programmer for over a decade and write my share of code. The software-ization of infra is a good thing; unlike some ops folks, I don't find it threatening, I find it cool.
What I find dismaying is some of the horrific stuff I catch before it gets to production, and what I do find threatening in a different way is worrying about what I miss.
Moving OS-level dependency management in to dockerfiles? Great! How are you scanning that against CVEs? If you don't know you're not running a different kernel, I have a sneaking suspicion you're... not. And so on down the list of traditional ops practices I frequently discover developers had no idea even happened.
There is nowhere in the docker-noob's workflow where the huge distinction between a docker container instance and a super light VM actually matters.
Source: I knew nearly nothing about docker a year ago. And now I'm one of my company's go-to people for docker questions. The pain is still fresh in my mind and I see noob-pain every day :)
You probably didn’t mean that they literally emulate an instruction set, because most modern hypervisors don’t emulate most instructions.
The idea of a VM is so messy these days, it's best to define what kind of VM are you talking about first. (language? system? foreign hardware?)
Aaaand that off-the-cuff statement clears up the difference between them that I've been missing for months. Containers really do just look like a VM, if you don't know the implementation details and are just using them.
If I gave a pre-Docker era engineer two terminals, one host, one in a container, they'd probably quickly figure out they are on the same physical machine. But unless they were super savvy at some very specific stuff, they'd probably conclude it was just a VM.
Every dev I've introduced to docker workflows basically treat it like a vm. The only ones that didn't already had experience with cgroups/chroot and related tools.
It's honestly better to think of Docker as "VM, but actually you use the same kernel" than "processes that are isolated".
Other poster compared it to electron models. Yes, "balls in orbits" is wrong, but kids are already familiar with planetary orbits, and that mental model works until basically Organic Chem II.
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.
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.
Nuh? Of starting, sure. Of running? A margin of error.
- 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.
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
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.