Docker Bootcamp
A two-week sprint to be production-ready with Docker - images, security, compose, registries.
Bootcamp plan
EXAMPLE
# Docker bootcamp - 10 working days Day 1 - Tooling: Docker Desktop, CLI, contexts, basic ps/run/exec. Day 2 - Images + layers: cache behaviour, multi-stage, distroless. Day 3 - Volumes + networks: bind mount vs named volume, bridge vs host. Day 4 - Compose: depends_on, healthchecks, env files, profiles. Day 5 - BuildKit + buildx: cache mounts, multi-platform builds, secrets at build time. Weekend project: containerise a 3-tier app (api + db + cache) with compose. Day 6 - Security: rootless containers, capabilities, seccomp, USER non-root. Day 7 - Registries + signing: push to ECR/GHCR, cosign + sigstore for signed images. Day 8 - Image scanning: docker scout, trivy, grype - wire one into CI. Day 9 - OCI + runtimes: rootless runtimes (Podman, containerd), CRI for K8s. Day 10 - Observability: logging drivers, JSON logs, healthcheck + readiness for orchestrators. Capstone: ship a signed, scanned, multi-arch image to a public registry, deployed to a small cloud (Fly, Render). ## Tips - Pin base images to SHA in production - Always non-root user; always HEALTHCHECK; always graceful shutdown - Compose profiles let you keep dev + integration + perf services in one file - Sign every release image and verify in your deploy pipeline
Why it matters
Docker is no longer enough on its own at scale - you graduate to a real registry, a real scanner, and signature verification before you trust a deploy. The bootcamp pace gives you a working pipeline by Friday of week two.
Tip: Tweak the snippet with Try it Yourself », then sit the quiz at the bottom of the page.
Discussion
Loading…