Docker for DevOps Roadmap
From containers vs VMs all the way to CI/CD registries — the full Docker path a practising DevOps engineer needs.
0%
0 of 14 topics complete
- Done
- To do
- Optional
Tick a topic as you finish — saved in this browser only.
-
Foundations
Understand why containers exist and how Docker fits in.
-
Why containers won the infra argument.
-
The daemon, client, and registry model.
-
Get Docker running on Ubuntu 24.04.
-
-
Images
Images are the unit of deployment. Master them.
-
How layers stack and why cache order matters.
-
pull, tag, inspect, prune.
-
Build
Author Dockerfiles that are fast, small, and reproducible.
-
Layer hygiene, .dockerignore, BuildKit.
-
Shrink production images by leaving build tooling behind.
-
Runtime
Run containers reliably with proper networking, storage, and composition.
-
Bridge, host, overlay, and port mapping.
-
Named volumes, bind mounts, and tmpfs.
-
Define multi-container stacks declaratively.
-
-
Ship & prepare
Push images to registries and get interview-ready.
-
Docker Hub, ECR, GitHub Packages, and automated pushes.
- Practice interview questions optional
Scenario and concept questions asked in real DevOps interviews.
-
Why this order.
Docker is easy to use and hard to use well, and the gap between those shows up as builds that take four minutes when they should take ten seconds, images that ship your AWS keys in a layer nobody looks at, and a container that runs on your laptop and not in CI.
The order here follows how the abstraction is built. Images and layers first, because the layer cache explains most of what is otherwise mysterious about build times and image size — including why reordering two lines in a Dockerfile can change a rebuild from minutes to seconds.
Networking and volumes come before Compose, because Compose is mostly a declarative wrapper over exactly those two things plus process ordering. Learning Compose first gives you a file you can edit but not debug.
Registries and CI come last, since pushing an image is the easy part once the image is right.