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]>
30 lines
1.1 KiB
Markdown
30 lines
1.1 KiB
Markdown
# Guided Exercise: Which Docker Command Actually Does This?
|
|
|
|
This is a paper exercise — commit to an answer before checking it in the Lab.
|
|
|
|
## Your task
|
|
|
|
For each goal, name the ONE Docker command you'd use:
|
|
|
|
1. "See every container, including ones that have stopped."
|
|
2. "Run a one-off diagnostic command inside a container that's already running."
|
|
3. "Read what a container has printed to its logs so far."
|
|
4. "Check the exact value of one specific field (like whether it's currently running) without
|
|
reading the entire inspect output."
|
|
5. "Completely remove a running container in one step, without stopping it first separately."
|
|
|
|
## A worked shape to check yourself against
|
|
|
|
1. `docker ps -a`
|
|
2. `docker exec <container> <command>`
|
|
3. `docker logs <container>`
|
|
4. `docker inspect <container> --format '{{...}}'`
|
|
5. `docker rm -f <container>`
|
|
|
|
## Instructor Notes
|
|
|
|
**Facilitation:** Have students justify why each answer fits the described GOAL specifically,
|
|
not just recite familiar syntax.
|
|
|
|
**Approximate timing:** 8-10 minutes live discussion; 5 minutes self-paced.
|