Why Docker?
Images, containers, layers, and why containers are lighter than virtual machines.
Transcript
It works on my machine, but breaks on the server, because the environment is different.
A Docker image packs the app together with its runtime, libraries and settings.
Run an image and you get a container: an isolated process with its own files and network.
Containers share the host kernel, so they start in milliseconds and are far lighter than virtual machines.
Images are built in layers, so unchanged layers are cached and shared between images.
Ship the same image to a laptop, a test server or the cloud, and it runs the same way everywhere.
Package. Isolate. Ship.
More in this series
2:212Why container runtimes?
Docker is one way to run containers, not the only container runtime: the OCI standards, high-level (containerd, CRI-O) vs low-level (runc) runtimes, Podman, and which runtime Kubernetes uses by default.
1:283Why Kubernetes?
Why we orchestrate containers: declarative desired state, scheduling, self-healing, scaling, rolling updates and services.