Adds all 8 ROOT 04 modules (why containers exist, images & containers, Docker CLI, container networking, container storage, Dockerfile & image build, Docker Compose, containers → Kubernetes) — 43 activities, using the nested Docker Engine Phase 6D built and tested. Modules 1, 2, and 8 are conceptual (no lab by design) — the honest bridge module (M8) explicitly names what Kubernetes adds beyond what this course already taught, without re-teaching Kubernetes itself. Adds 5 new hands-on Docker scenarios plus 2 MCQs, all against the real nested Docker Engine: docker-cli-basics (run/exec/inspect a real container), docker-container-networking (a genuine "works internally, unreachable from host" port-publishing failure, diagnosed and fixed by recreating the container with the correct `-p` flag), docker-container-storage (a real destroy/recreate cycle proving named-volume persistence, not just described), docker-build-image (a real Dockerfile, a real build, a real custom image run), and docker-compose-multiservice (a real two-service Compose application with a real published port). All tested end-to-end via the real scenario-validation API, including negative tests. Wires rootnode-containers-assessment (2 required + 4 random-draw scenarios) using the existing Phase 3B assessment engine. This completes the entire ROOT_ Foundations sequence (ROOT 01-04) — see docs/PHASE6E_ROOT_FOUNDATIONS_COMPLETION.md. Co-Authored-By: Claude Sonnet 5 <[email protected]>
1.2 KiB
Reflection: You Now Know What Problem You're About to Solve, Hands-On
Reflection questions
- Think back to ROOT 01's "how computers run software" module. How does today's lesson refine your understanding of what a "process" actually is?
- Do you expect containers to make the Linux/process/networking skills from ROOT 01-02 less relevant, or MORE relevant? Why?
Real Ops takeaway
Every skill from ROOT 01-02 — processes, filesystems, networking — transfers directly into containers, because a container is built from exactly those same primitives, just isolated differently. You are not about to learn an unrelated new subject; you're about to see the Linux fundamentals you already have applied through Docker's specific tooling. Module 2 starts that translation.
This module is complete. Continue to the next module.
Instructor Notes
Discussion questions for a live classroom: question 2's honest answer is "more relevant" — worth stating explicitly, since students sometimes assume containers are an alternative to Linux fundamentals rather than built directly on top of them.
Approximate timing: 5-8 minutes live discussion; 5 minutes self-paced writing.