Docker and Containers roadmap
Build, ship and run containers the way production teams do.
6 to 8 weeks at 6 to 8 hours a week6 stages28 topicsBeginner friendly
All roadmapsContainers package an application with everything it needs so it behaves the same on your laptop, in CI and in production. This path takes you from running your first container to building small, secure images and shipping them through a pipeline.
Where you will end up
Confidence to containerise any typical web application, run it with its dependencies using Compose, publish a small and non-root image to a registry, and explain the choices you made.
Before you start
- Basic Linux command line
- Any application you can run locally, in any language
Roles it leads to
- Junior DevOps Engineer
- Backend Developer
- Cloud Support Engineer
- 1
Container concepts
1 week0 of 4 done
Explain what a container is, what it is not, and how it differs from a virtual machine.
Prove it
Run and inspect a container
Pull a public image, run it, open a shell inside it, change a file, remove the container and show what survived and what did not.
- 2
Running containers
1 week0 of 5 done
Operate containers day to day: ports, environment, storage, logs and cleanup.
Prove it
Database that survives
Run a database container with a named volume, add data, destroy and recreate the container, and prove the data is still there.
- 3
Building images
2 weeks0 of 5 done
Write Dockerfiles that build quickly, produce small images and are easy to maintain.
Prove it
Shrink an image
Take a naive Dockerfile for a real app and improve it with caching and a multi-stage build. Record the before and after size and build time.
- 4
Multi-container apps with Compose
1 to 2 weeks0 of 4 done
Describe a whole application stack in one file and start it with one command.
Prove it
App, database and cache
Compose a web app, a database and a cache with health checks and persistent data. A new teammate should be productive after cloning and running one command.
- 5
Production practices
2 weeks0 of 6 done
Ship images you would be comfortable running in front of real users.
Prove it
Production-ready image
Harden your image: non-root, scanned, pinned base, small, tagged by version. List what a scanner found and what you changed in response.
- 6
Shipping and next steps
1 to 2 weeks0 of 3 done
Build and publish images automatically, then run them somewhere real.
Prove it
From commit to running container
A pipeline that builds, scans and publishes your image, and a deployment that pulls it and serves traffic. Then move on to the Kubernetes roadmap.
Certifications that fit
Optional, and never a substitute for projects. Exam details change, so confirm on the official page before you book.
- Kubernetes and Cloud Native Associate (KCNA)AssociateMultiple choice, online proctored, 90 minutes. A natural first credential once you are comfortable with containers.
- Certified Kubernetes Application Developer (CKAD)ProfessionalHands-on, two hours, for people who build and deploy containerised applications.
The honest part
Docker itself is quick to learn. What separates a beginner from a professional is judgement: image size, security and how the image behaves in a pipeline. Spend your time on the milestones, and keep your Dockerfiles in a public repository so others can see how you think.
Checked against
Written by CloudIskole and reviewed against the official sources below. Last verified November 2026. Spotted something out of date? Tell us and we will fix it.
These roadmaps are our own work. For another community view of learning paths, see roadmap.sh, which inspired the idea of a visual guide.


