Image Forge
A release must become a reproducible image and move safely through the registry.
- 8 practical command rooms
- 1 multi-step boss workflow
- Immediate explanations and safety notes
CURRICULUM // DOCKER
Docker Dockyard
Ship images, operate containers, compose services, and debug their connections.
DO48 CHALLENGES · 3 LEVELS
FOUR-ZONE PATH
From first command to incident recovery.
Each zone turns reference material into an active scenario. You will choose commands, repair mistakes, predict outcomes, and assemble complete workflows.
Container Bay
A running container needs inspection, controlled execution, and a clean shutdown.
- 8 practical command rooms
- 1 multi-step boss workflow
- Immediate explanations and safety notes
Compose District
A multi-service application must start, update, and stop as one predictable unit.
- 8 practical command rooms
- 1 multi-step boss workflow
- Immediate explanations and safety notes
Network & Storage Core
Persistent data and service communication must survive routine cleanup and redeployment.
- 8 practical command rooms
- 1 multi-step boss workflow
- Immediate explanations and safety notes
PRACTICE DESIGN
Every zone teaches a different operational decision.
The multi-step sequences below are authored workflows, while individual command rooms link to the closest available command reference.
Image Forge
Build, inspect, tag, and publish a versioned application image.
Build locally, inspect the artifact, apply the registry-qualified tag, authenticate, then publish that exact tag.
Boss incident
Rebuild a production image from an explicit Dockerfile and verify it before release. The explicit production build is inspected and its layers reviewed before tagging and publishing it.
Read the complete field guide →Container Bay
Inspect a running container, collect evidence, then stop and remove it cleanly.
Locate the running container and collect logs and metadata before stopping it; removal happens only after it stops.
Boss incident
Diagnose an unhealthy application container before replacing it. Confirm container state, inspect recent logs and internal processes, then stop and remove the failed instance.
Read the complete field guide →Compose District
Validate and launch a Compose application, then verify every service.
Validate configuration before building and starting; service state and bounded logs verify the deployment.
Boss incident
Roll out an updated Compose service and confirm the new containers are healthy. Validate, fetch referenced images, reconcile services in detached mode, then inspect state and recent logs.
Read the complete field guide →Network & Storage Core
Create persistent storage and attach it to a container before inspecting the result.
Create and inspect storage before mounting it, then inspect and locate the resulting container.
Boss incident
Create an isolated network and verify communication between two named containers. Create the network first, attach both containers, inspect network membership, then test name-based communication from the client.
Read the complete field guide →HOW THIS WORLD WAS BUILT
Source-linked commands, explicitly authored workflows.
The complete command library is public and each field guide explains prerequisites, failure modes, verification, and safety boundaries. Source-linked does not mean a command was executed on every platform.
Open the public command library →