Simplifying the Journey of Your Containerized Application from Dev to Production
summary
Demonstrates how to get a production-ready container without endless manual work by applying concrete fixes: pin base images, use npm ci, delete caches in the same RUN, separate dependency install, run as non-root, add init for proper signal handling, and use multi-stage builds. Compares buildpacks (pack / Waypoint), multi-stage + distroless and alpine approaches and shows Docker Slim shrinking a ~945 MB Node image down to ~80 MB while producing hardened, reproducible images.
AI-written summary · about
chapters (11)
- 0:00Start
- 0:28What's the Problem
- 2:20Build and Deploy Times
- 3:15What's Wrong with the Image and Its Docker File
- 3:56Reproducibility
- 4:49Common Gotchas
- 6:53Installing the Application Dependencies Separately from the Application
- 10:02Multi-Stage Builds
- 12:52Build Packs
- 14:28Optimizing Container Images
- 15:57Takeaways
related talks
29mZero to production-ready: a best-practices process for Docker packaging
25m0 to production-ready: a best-practices process for Docker packaging
43mDocker: From Development to Production
27mDocker Image Journey - How to Shrink a Docker Image
58mOptions Galore to Get from Source Code to Container
43mZero to production ready: a best practices process for Docker packaging
54mHowto: Options Galore to Get from Source Code to Container
44mSpeeding Up Deployment of JavaScript and Node.js Applications