Why We Delay Container Week

Early cohorts begged for containers in week one. We tried it once and watched learners mask missing fundamentals with copy-pasted run flags. Now container week sits behind filesystem and cgroup literacy on purpose.

The delayed start lets us draw parallels between bind mounts and volume maps without rushing. Learners sketch diagrams first, then translate them into podman commands with mentors challenging hidden root assumptions.

We still surface Kubernetes vocabulary, but only as a map of what peers might mention in meetings—not as something we configure. That honesty keeps expectations aligned with the job titles most learners actually hold.

Assessment stays rooted in host skills: if someone cannot explain a bind mount, we pause container grading until the gap is documented—not hidden behind YAML prettiness.