# Docker Mastery: a course repository that is really a syllabus in directory form > Bret Fisher's Udemy Docker course ships its exercises as 40 top-level directories, and the section list in the README is a defensible answer to where container tooling went after Compose. **BretFisher/udemy-docker-mastery** — Docker Mastery Udemy course to build, compose, deploy, and manage containers from local development to high-availability in the cloud - Repository: https://github.com/BretFisher/udemy-docker-mastery - Website: https://www.bretfisher.com/courses - Stars: 5,804 · Forks: 6,475 - Language: JavaScript - License: MIT - Published: 2026-10-06 · Updated: 2026-10-06 · Language: en - Canonical page: https://hysenlabs.com/projects/bretfisher-udemy-docker-mastery ## Forty directories that map to the section list The repository has no code of its own worth speaking of. What it has is structure. Every top-level directory is either a `sample` or an `assignment`, and the names run in the order the course teaches them: ```text dockerfile-sample-1/ compose-sample-1/ swarm-stack-1/ k8s-yaml/ ``` Alongside those sit `bindmount-sample-1/`, `healthcheck-1/`, `registry-sample-1/`, `secrets-sample-1/`, `secrets-sample-2/`, `visualizer/`, `written-lectures/`, `references/`, `dockerfiles/`, `example-voting-app/`, `slack-chat/`, `intro/` and `k8s-yaml/`. The naming convention is the documentation. Anyone can tell which directory belongs to which section of the course without opening a single file. Two of them deserve a note. `example-voting-app/` is the Docker canonical voting application, the one every tutorial uses, which is why the repository language reads as JavaScript. `slack-chat/` is a second Node application. Neither is part of what you are learning; they are props. ## Twenty-eight sections, and what they assume The README lists the curriculum as a numbered outline of 28 sections. The first block runs from a quick start through the OS-specific setup, creating containers, building images, container lifetime with volumes, and Docker Compose. Then it moves to Swarm: an intro, a three-node cluster, basic features, and application lifecycle. The middle is production concerns. Container registries for image storage and distribution, then a Docker in Production section. After that the course changes subject. Sections 13 through 20 are Kubernetes: the what and why, architecture and install, first pods, inspecting resources, exposing ports, management techniques, and moving to declarative YAML. The tail is where a reader should apply a date. Sections 21 and 22 are automated CI workflows and GitHub Actions examples. Section 24 is Docker 19.03 release features. Section 26 is Dockerfiles and Docker images in 2022. A course outline that ends with a specific Docker release and a specific year is telling you the material was current when it was written, and that later changes to the ecosystem are not covered. Sections 23 and 25, security good defaults and DevOps clips, are the ones most likely to have degraded least. ## What a repository can tell you about a paid course There is an unusual amount of information available here for something you cannot read. The fork count is larger than the star count, which is unusual enough to be meaningful: this repository gets cloned, not just bookmarked. People download it and work through the exercises locally rather than treating it as a link to keep for later. The `references/` directory is the other useful part. One entry is `S01 Commands and Links.md`, a cheat sheet for the first section, which tells you the author expects people to be running commands alongside the video rather than passively watching. There is also a `written-lectures/` directory, so at least some of the course exists as text. There are 32 open issues and the README invites issues and pull requests specifically for problems with the examples, not for course questions. The fork-and-fix workflow is clearly anticipated. The last push was on 2026-05-18, the repository is not archived, and there are no GitHub releases at all, so you cannot tell from tags which course revision the examples match. ## The pricing and the referral links Be straightforward about what this is. The README links two Udemy courses, Docker Mastery and Swarm Mastery, each with a referral code in the URL, and it points to bretfisher.com/courses for what it calls cheapest on the internet coupon links. There is a weekly newsletter link alongside. So the honest answer to the many searches for a free download of this course is that the exercises here are free and open under MIT, while the instruction is not. The repository carries an MIT LICENSE, the Discord server linked in the header is the author's devops community, and the author is a Docker Captain, which is an official Docker community programme title. None of that changes what you are paying for. You are paying for the walkthrough, and whether that is worth it depends on how much of the material you would otherwise have to assemble yourself from Docker's own documentation. For someone who already runs containers in production, the repository alone covers most of what the course teaches about Compose and Dockerfiles. ## Where Docker went, according to this outline Read the section list as an argument rather than a curriculum. Swarm gets sections 8, 9 and 10, plus a run of six `swarm-stack-*` directories. Kubernetes gets sections 13 through 20. That ratio tells you the author's own view of the landscape, expressed through where he spent the hours. Swarm is not an incidental topic here. `swarm-app-1/`, `swarm-app-2/`, `swarm-secrets-assignment-1/`, `swarm-stack-1/` through `swarm-stack-6/` and a separate `visualizer/` directory amount to a substantial body of work on a mode Docker shipped built in and has since de-emphasised in favour of Kubernetes. Practically, that means the Swarm material is a good deal of the repository, and it is the part least likely to match what you will deploy. The Kubernetes half has the opposite problem. It stops before the ecosystem got complicated: no service mesh, no operators, no ingress controllers, no managed control plane. If you are deploying to EKS or GKE today, the `k8s-yaml/` directory is a starting point, not a reference. ## Conclusion This repository is most useful if you are already enrolled, because it is the exercise material rather than the content. As a free artifact it still holds up: the Compose, Dockerfile and Swarm examples are readable without a course in front of you, and the section list alone is a competent map of container tooling. Do not expect current Kubernetes guidance from it, since the syllabus stops at declarative YAML and GitHub Actions, and the repository language is listed as JavaScript because the bundled example apps are Node projects rather than because anything here is a JavaScript library. The last push was on 2026-05-18 and there are no GitHub releases, so nothing is versioned. Start with `compose-sample-1/` and `dockerfile-sample-1/`, which are self-contained, before touching the `swarm-stack-*` directories that assume a multi-node cluster. ## FAQ ### Is Docker still relevant in 2026? Docker the container format is not going anywhere, but this course's own outline reflects where attention moved. Swarm gets three sections and Kubernetes gets eight, ending at declarative YAML rather than anything service-mesh shaped. The Docker tooling sections on Compose, Dockerfiles, registries and secrets remain the parts of the outline that have aged best. ### Why are people moving away from Docker? The README does not argue this case, but the section ordering implies it. Swarm is covered in sections 8 to 10 and Kubernetes in 13 to 20, which places orchestration outside Docker as the destination the course is steering toward. Docker itself remains the packaging and runtime layer in both cases. ### Is the Docker Mastery course free, and what do I get from this repository? The repository is free and MIT licensed: sample and assignment directories covering Dockerfiles, Compose, Swarm stacks, registries, secrets and Kubernetes YAML. The course itself is a paid Udemy purchase, and the README links it with a referral code plus coupon links at bretfisher.com/courses. Searches for a free course download will not lead anywhere useful. ## Sources - [BretFisher/udemy-docker-mastery on GitHub](https://github.com/BretFisher/udemy-docker-mastery) - [Issues](https://github.com/BretFisher/udemy-docker-mastery/issues) - [License: MIT](https://github.com/BretFisher/udemy-docker-mastery/blob/main/LICENSE) - [Project website](https://www.bretfisher.com/courses) - [README](https://github.com/BretFisher/udemy-docker-mastery/blob/main/README.md) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/bretfisher-udemy-docker-mastery