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]>
37 lines
1.1 KiB
Markdown
37 lines
1.1 KiB
Markdown
# Guided Exercise: Translate a Compose File Back Into Plain `docker run`
|
|
|
|
This is a paper exercise — commit to your translation before checking it in the Lab.
|
|
|
|
## Your task
|
|
|
|
Given this Compose service definition, write the equivalent plain `docker run` command by hand:
|
|
|
|
```yaml
|
|
services:
|
|
web:
|
|
image: nginx:alpine
|
|
ports:
|
|
- "8080:80"
|
|
```
|
|
|
|
Then explain: what would you ALSO need to do manually (that Compose does automatically) if two
|
|
services needed to reach each other by name?
|
|
|
|
## A worked shape to check yourself against
|
|
|
|
```
|
|
docker run -d -p 8080:80 nginx:alpine
|
|
```
|
|
|
|
For two services to reach each other by name manually, you'd need to `docker network create` a
|
|
shared network yourself, then add `--network <that-network>` to EACH container's `docker run`
|
|
command — exactly the manual step Compose eliminates.
|
|
|
|
## Instructor Notes
|
|
|
|
**Facilitation:** This exercise is the clearest possible proof that Compose isn't new magic —
|
|
being able to translate it back to `docker run` confirms genuine understanding, not just
|
|
familiarity with YAML syntax.
|
|
|
|
**Approximate timing:** 8-10 minutes live discussion; 5 minutes self-paced.
|