Containerization explained from first principles. Learn images, the Dockerfile, volumes, networking and Docker Compose — the foundation for Kubernetes and modern deployment — remembered with spaced repetition.
Docker packages an application together with everything it needs to run — code, runtime, libraries — into a portable image. Run that image and you get a container: an isolated, reproducible process that behaves the same on your laptop and in production. No more "works on my machine".
This track covers the building blocks: the difference between images and containers, writing a Dockerfile, persisting data with volumes, connecting containers over networks, and orchestrating multi-container apps with Docker Compose.
It uses spaced repetition so the commands and concepts stick — and it is the natural foundation before Kubernetes, which orchestrates containers at scale.
Each module is a set of practice cards — 62 in total. Answer, review, and watch your knowledge grow from seed to full bloom.
Docker fundamentals — containers, images, layers, lifecycle, and registries
13 cardsBuilding images — instructions, layers, caching, multi-stage builds, and optimization
12 cardsData persistence — volumes, bind mounts, tmpfs, backup, and sharing
10 cardsContainer communication — drivers, CNM, DNS discovery, port mapping, and network isolation
15 cardsMulti-container apps — services, networking, volumes, environment, and lifecycle
12 cardsA taste of the real cards. Pick an answer, then reveal the explanation.
What is Docker?
What is a Dockerfile?
What are the three types of mounts available in Docker?
What is Docker Compose used for?
Each card is one practical concept with multiple options. Pick what you think is right.
See the correct option plus a clear explanation, and a link to deeper docs when one is available.
A spaced-repetition engine (SM-2 or FSRS) resurfaces each card just before you would forget it.
Containers are how software ships today. Docker fluency is table stakes for backend and DevOps work.
Reproducible images mean the same behaviour on every laptop, CI runner and server.
Kubernetes orchestrates containers — understanding Docker first makes it click far faster.
Spin up databases and services in seconds with Compose instead of installing them by hand.
No. The track starts from what an image and a container actually are and builds up from there.
About 10 minutes a day. Spaced repetition means short, frequent sessions beat long cramming, so the commands and concepts stick.
Yes, completely free. No registration or credit card is required, and all your progress is stored locally in your browser.
Yes. Kubernetes orchestrates containers, so a solid grasp of Docker makes the Kubernetes tracks much easier.
Plant your first seed today. Ten minutes a day is all it takes to grow real, lasting container skills.