Container
Let's see how the container solves the Virtual Machine's weight and boot-time problem by dropping the one thing a VM never gives up: its own private kernel.
Browse every article by subject.
Let's see how the container solves the Virtual Machine's weight and boot-time problem by dropping the one thing a VM never gives up: its own private kernel.
With containers now scattered across dozens or hundreds of machines, who decides which one runs where, restarts it when it dies, or scales it up under load? That's the exact job Kubernetes was built for — let's map out what's actually inside a cluster.
Before getting anywhere near Kubernetes itself, the story has to start with the one piece of software everything else in this series is built on top of: the Linux kernel. If you've never really sat down and thought about what a kernel does, what a driver is, or what "sandbox" actually means in Linux, this article is for you.
What does a physical server actually look like, and why can't we just keep deploying more onto the same one?
Let's see how the Virtual Machine solves the physical server's "one machine, one environment" problem, and the downsides of this approach.