Container vs Virtual machine

Why they differ

A virtual machine carries its own full operating system; a container shares the host's kernel, which makes it lighter but less strongly separated.

Container

Containers & orchestration

A sealed-off box for one program and everything it needs, sharing the host computer's kernel instead of carrying its own.

Formal

One or more processes that the kernel keeps apart from the rest of the system - with their own view of files, network and running programs, and limits on memory and processor use - started from a container image and sharing the host's kernel.

In plain English

Like shipping containers on one cargo ship - each holds its own goods in a standard box, but they all ride on the same hull and engine.

In practice

A developer at a municipality packs the citizen booking site into a container, so the exact same box runs on a laptop, in testing and in production, ending “it worked on my machine” surprises.

Why it matters

Containers start in seconds and use little memory, but because they share one kernel, a flaw there can let one container break out and reach the others on the host.

Virtual machine

Cloud

A whole computer made in software, with its own operating system, running side by side with others on one physical machine.

Formal

A software copy of a complete computer - processor, memory, disk and network card - created by a hypervisor; it runs its own full operating system, kept apart from the other virtual machines on the same hardware.

In plain English

Like flats in one building - each has its own front door, kitchen and bathroom, even though they share the same foundations.

In practice

The IT operations manager at a water utility runs the payroll system, the file server and a test environment as three virtual machines on one large server, each with its own Windows or Linux.

Why it matters

It is the basic building block of most cloud services; strong separation between machines is what lets strangers safely share the same hardware.