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.0 KiB
Markdown
25 lines
1.0 KiB
Markdown
# Reflection: A Small Distinction With Large Consequences
|
|
|
|
## Reflection questions
|
|
|
|
1. Before this module, would you have known why `docker rm` and `docker rmi` are two separate
|
|
commands? Does it make sense now?
|
|
2. Where else in ROOT_ have you seen this exact "artifact vs. running instance" pattern before?
|
|
(Hint: think back to ROOT 01.)
|
|
|
|
## Real Ops takeaway
|
|
|
|
**Precise vocabulary prevents real mistakes.** Confusing "stop the container" with "delete the
|
|
image," or assuming `latest` means "the current version," are genuine, common sources of
|
|
production incidents — not just semantic nitpicking. The image/container distinction you just
|
|
solidified is the foundation every command in the rest of this course builds on.
|
|
|
|
This module is complete. Continue to the next module.
|
|
|
|
## Instructor Notes
|
|
|
|
**Discussion questions for a live classroom:** question 2's intended answer is "program vs.
|
|
process," from ROOT 01 — a good moment to explicitly connect the two courses.
|
|
|
|
**Approximate timing:** 5-8 minutes live discussion; 5 minutes self-paced writing.
|