EO Engineering Learning OS
PROJECT LADDER · P12
Back to map ↑
CORE PROJECT · TARGET L3 · 5 days
P12

Containers

Package application and runtime dependencies into a reproducible, constrained artifact.

01 / CONCEPT MAP

Know what the parts mean.

Learn each concept deeply enough to recognize it, place it in the system and reason about normal and failed behavior.

01

Images and layers

Define it · locate it · observe it · explain its failure mode.

02

Dockerfile

Define it · locate it · observe it · explain its failure mode.

03

Environment config

Define it · locate it · observe it · explain its failure mode.

04

Container networking

Define it · locate it · observe it · explain its failure mode.

05

Volumes

Define it · locate it · observe it · explain its failure mode.

06

Registry and scanning

Define it · locate it · observe it · explain its failure mode.

02 / SYSTEM FLOW

Trace it end to end.

Source→image build→registry→container→port→external services

For every transition: identify input, output, identity, protocol, state, trust boundary, evidence and owner.

03 / GUIDED BUILD

Build, observe and explain.

Documentation and AI are allowed. The engineer must review every output and demonstrate the result from direct evidence.

  1. 01Write minimal Dockerfile
  2. 02Run as non-root
  3. 03Externalize config
  4. 04Add health check
  5. 05Scan and publish image
  6. 06Run with database and S3 dependencies
04 / INCIDENT

Container starts locally but exits in deployment due to architecture, config or filesystem assumptions.

Required investigation

State impact → collect evidence → form competing hypotheses → test the cheapest discriminator → isolate root cause → contain → correct → verify.

Evidence pack

Timeline, relevant logs/metrics, failed assumptions, root cause, correction, verification and one prevention action.

AI ownership

AI may suggest causes and commands. The engineer must explain why each check is safe, what result is expected and how the result changes the hypothesis.

05 / DESIGN CHALLENGE

Defend the decision.

Define what belongs in image, configuration, secret and persistent storage.

06 / VERIFY, SUBMIT & REVIEW

Submission evidence

Architecture review

  • Explain containers without relying on memorized commands.
  • Draw the flow and name what crosses every arrow.
  • Identify the most likely, highest-impact and hardest-to-detect failure.
  • Show the evidence that proves the solution works.
  • Defend one security, reliability and cost trade-off.

Definition of Done

  • Acceptance criteria pass
  • Flow is drawn and explained
  • Security implications considered
  • Logs/metrics checked
  • Failure is tested
  • AI output is understood
  • Runbook is reusable
  • Mentor review passes
07 / MENTOR GUIDE

Do not score memory. Score the engineer’s ability to form a model, collect evidence, make a safe change and defend the trade-off.

1 Cannot explain2 Understands with gaps3 Implements and troubleshoots4 Designs and reviews