Health checks fixed our flaky setup
Our API always crashed on first start because the database was not ready. The service_healthy lesson solved it.
Browse
Package your applications into small, secure images, run multi service projects with Docker Compose and use containers in daily development
Created by Lena Fischer
"It works on my machine" stops being a problem when your machine and every other machine run the same container. This course teaches Docker from the ground up for developers: what containers really are, how to build good images, and how to run an application with its database, cache and worker using Docker Compose.
We containerise a small web application with an API, a PostgreSQL database, a Redis cache and a background worker. You can follow along with the Python or Node.js version of the app. By the end, a new teammate can clone the repository and run the whole stack with one command.
You need Docker Desktop, Docker Engine on Linux or a compatible alternative such as OrbStack or Podman. Commands are shown for a terminal on macOS, Linux and Windows with WSL 2.
Container and Kubernetes trainer. Docker, clusters and production operations without the jargon
I run Kubernetes clusters and help development teams move their services into containers. Before that I was a backend developer, so I remember how confusing images, volumes and networking felt the first time.
My courses start from what you already know, a process on your laptop, and add one idea at a time: an image, a container, a Compose file, a Deployment, a Service. Every lesson has commands you can type and an explanation of what changed.
The advanced material comes from real incidents: crash loops, memory limits, failing probes and slow rollouts. I teach the debugging habits that help when the dashboard is red and you need answers.
Our API always crashed on first start because the database was not ready. The service_healthy lesson solved it.
The first lesson on namespaces and cgroups made everything else make sense. No magic, just processes.
Our local setup used slow bind mounts. Compose Watch with sync and rebuild rules made development much faster.
Copying requirements first, .dockerignore and multi stage builds cut our image from over a gigabyte to a fraction of that.
The 0.0.0.0 tip fixed a bug I had spent an afternoon on. The networking section was very useful.
Non root users and image scanning are covered properly, which many beginner courses skip.
Starts gently and builds up well. A few more Windows specific notes would help, but WSL 2 instructions worked.
I already knew docker run, so section one was slow for me. Sections two and four were excellent.