ced4568andClaude Sonnet 5
682ef2de47
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]>
25 lines
1.1 KiB
Markdown
25 lines
1.1 KiB
Markdown
# Reflection: The Whole Toolkit Was Already Familiar
|
|
|
|
## Reflection questions
|
|
|
|
1. Which Docker command in this module felt like "a new version of something I already knew"
|
|
from ROOT 01 or ROOT 02? Which felt genuinely new?
|
|
2. You ran, inspected, execed into, and removed a real container this module. What's the ONE
|
|
command you'd reach for first if a container "seemed broken" and you didn't know why yet?
|
|
|
|
## Real Ops takeaway
|
|
|
|
**Every Docker command in this module is a direct translation of a Linux skill you already
|
|
had.** `docker ps` is `ps aux`. `docker logs` is reading a log file, minus the config. `docker
|
|
exec` is reaching into a running process. This is exactly why ROOT 01-02 came before ROOT 04 —
|
|
containers don't replace Linux fundamentals, they wrap them in a specific, consistent interface.
|
|
|
|
This module is complete. Continue to the next module.
|
|
|
|
## Instructor Notes
|
|
|
|
**Discussion questions for a live classroom:** question 2's honest answer is usually `docker ps`
|
|
or `docker logs` — a good moment to connect back to ROOT 02's five-question service checklist.
|
|
|
|
**Approximate timing:** 5-8 minutes live discussion; 5 minutes self-paced writing.
|