Run a website in a container
Serve a static website from an official web server image on your own port.
Package applications into containers that run the same on every laptop and server.
You have reached the end of the beginner stages. Prove what you learned with a project.
You have reached the end of the intermediate stages. Prove what you learned with a project.
You have reached the end of the advanced stages. Prove what you learned with a project.
Serve a static website from an official web server image on your own port.
Run PostgreSQL in a container, add data, remove the container and get the data back.
Write a Dockerfile for a small app you built and make the image as small as you can.
Run an app, its database and an admin tool together with one Compose file.
Build, scan and push an image to a registry on every push to main.
Deploy your containerised app to a free or low-cost cloud container service.
The same roadmap as a reading list: every stage, what each topic covers, and which ones are optional.
An isolated, portable package of an app and everything it needs to run.
Install Docker Desktop or Docker Engine and run your first container.
An image is the template; a container is a running copy of it.
Docker is mostly used from a terminal. Get comfortable there.
Start, stop, list, inspect and remove containers.
Find trusted images and pick the right version tag.
Reach a container from your browser and let containers talk to each other.
Keep data when a container is removed.
Describe step by step how to build an image for your app.
Small, cache-friendly images that rebuild fast.
Build in one stage and ship only what is needed to run.
Send only the files the build needs, and never your secrets.
Run an app, its database and its cache together with one file.
Change settings per environment without rebuilding the image.
Run PostgreSQL or MySQL locally with persistent volumes.
Read logs, open a shell inside a container and find what went wrong.
Run as a non-root user, keep images small and patched.
Version your images and push them to a registry.
Build and push images automatically when code changes.
Find known vulnerabilities in your images before you ship.
Run many containers across many machines with self-healing and scaling.
A daemonless alternative that runs most Docker commands.
Run containers on managed cloud services without managing servers.
Give every developer the same ready-to-use environment.
It removes "works on my machine" problems: the same container runs on a laptop, a test server and production.
No. Containers share the host's operating system kernel, so they start in seconds and use far less memory than virtual machines.
Yes. Kubernetes runs containers, so understanding images, containers, networking and volumes comes first.
© 2026 KamerLink. All rights reserved.