Docker and Docker Compose for Developers Who Ship
by Tom Eriksen
Pipelines that run fast, cache correctly and fail for reasons you can actually read.
TE Created by Tom Eriksen
Every bullet below is something you will have built, shipped or be able to explain by the time you finish the last lesson.
6 modules · 48 lessons · 6h 25m of material
8 lessons running 1h in total. Each lesson ships with the finished source files and a short written recap, so you can follow along in your own editor and skim the module again later.
Lesson-by-lesson titles, code downloads and exercises live inside the course library you get access to straight after checkout.
8 lessons running 1h 4m in total. Each lesson ships with the finished source files and a short written recap, so you can follow along in your own editor and skim the module again later.
Lesson-by-lesson titles, code downloads and exercises live inside the course library you get access to straight after checkout.
8 lessons running 1h 8m in total. Each lesson ships with the finished source files and a short written recap, so you can follow along in your own editor and skim the module again later.
Lesson-by-lesson titles, code downloads and exercises live inside the course library you get access to straight after checkout.
8 lessons running 1h 8m in total. Each lesson ships with the finished source files and a short written recap, so you can follow along in your own editor and skim the module again later.
Lesson-by-lesson titles, code downloads and exercises live inside the course library you get access to straight after checkout.
8 lessons running 1h 4m in total. Each lesson ships with the finished source files and a short written recap, so you can follow along in your own editor and skim the module again later.
Lesson-by-lesson titles, code downloads and exercises live inside the course library you get access to straight after checkout.
8 lessons running 1h 1m in total. Each lesson ships with the finished source files and a short written recap, so you can follow along in your own editor and skim the module again later.
Lesson-by-lesson titles, code downloads and exercises live inside the course library you get access to straight after checkout.
6 modules · 48 lessons
6h 25m total length
Short list, and deliberately so. If you meet these you can start today.
Continuous integration is either the thing that catches problems before your users do, or the thing everyone reruns twice and eventually ignores. The difference is engineering, and it is almost entirely learnable.
The course starts with the execution model, because most confusion comes from not knowing it. Events and their payloads, the difference between pull request and pull request target and why that difference is a security boundary, jobs and steps, runners and what is already installed on them, contexts and expressions, and where each piece of state actually lives. You will write workflows that do exactly what you intended rather than approximately.
Then speed, which is what makes a pipeline get used. Caching dependencies correctly including the key design that decides whether you ever get a hit, Docker layer caching in a build, matrix builds without a combinatorial explosion, splitting a slow test suite across parallel jobs, and skipping work that no change could have affected.
The rest covers correctness and safety: reusable workflows and composite actions to stop copy-paste sprawl, secrets and environment protection rules, OpenID Connect for cloud credentials so you stop storing long-lived keys, concurrency groups that cancel superseded runs, deployment gates with approvals, and debugging techniques for the failure that only ever happens on the runner.
Still unsure about something? Write to misteryjj100@gmail.com and a human answers, usually the same working day.
Reviews are written by people who bought this course. We publish the critical ones too.
4.0
Rated 4.0 out of 5Course rating · 2 reviews
Hassan Farouk
DevOps engineer
Ours had a timestamp baked into the key, so it never once restored and nobody had noticed. The explanation of how the fallback keys are actually matched found it in ten minutes. Only real complaint is that the OIDC material is written AWS-first and I am on Azure.
Katarzyna Wójcik
Platform engineer
The execution model and reusable workflow chapters are the clearest explanation of either that I have seen, and neither will date. A few of the interface walkthroughs no longer match what is on my screen, and one referenced action version has since been deprecated. Nothing that actually stopped me, but be prepared to translate.
Platform engineer and DevOps instructor
Tom has built delivery pipelines for teams of three and teams of three hundred, and openly prefers the smaller ones. He teaches Docker, Kubernetes and CI/CD outward from a single commit, so nothing ever appears by magic, and he treats the test suite as part of the pipeline rather than a separate subject. Every course includes a deliberate outage that you have to diagnose from logs and metrics before you can continue. He is a CNCF contributor and a reluctant but formidable YAML expert.
One-time payment · lifetime access