He also navigates the controversial shift away from Docker as the default Kubernetes runtime (to containerd) with clarity, explaining that the docker.sock is just an interface, and the Dockerfile remains king. With the rise of Podman, Buildah, and containerd, is a deep dive into Docker CLI still worthwhile? Grider’s course implicitly argues yes. The industry standard Dockerfile format is not going away. The mental model of namespaces, control groups (cgroups), and union file systems is universal. Learning Docker with Grider is essentially learning the lingua franca of modern cloud computing. The Verdict Stephen Grider’s Docker course is not a quick reference guide, nor is it a magic trick. It is a structured, grueling, and ultimately rewarding apprenticeship. He treats the student with respect—assuming they are smart enough to understand the kernel-level mechanics but kind enough to know they need a map.
He introduces Kubernetes by creating a "death scenario." He manually starts five Docker containers, then kills one. The developer is forced to restart it manually. "This is boring," Grider says. "This is why we need a manager." He then introduces Pods, Deployments, and Services not as abstract Google concepts, but as automated solutions to the specific manual labor the student just performed.
In the crowded ecosystem of online technical education, few instructors achieve the status of a trusted institution. For backend developers, DevOps engineers, and full-stack programmers navigating the containerization revolution, Stephen Grider has become exactly that. Specifically, his course, "Docker and Kubernetes: The Complete Guide," has transcended typical tutorial fare to become a modern rite of passage for developers grappling with the shift from monolithic architectures to microservices.
But what is it about Grider’s approach to Docker that resonates so deeply with a generation of coders tired of "It works on my machine" syndrome? Most Docker tutorials start with a definition: "A container is a lightweight, standalone, executable package of software." Grider, a software engineer and architect based in the San Francisco Bay Area, takes a radically different approach. He starts with pain.