0 to production-ready: a best-practices process for Docker packaging
summary
A concrete iterative process appears: first get a working image, then fix security (for example don't run as root and remove build-time secrets), then automate CI builds and tag per branch, then ensure reproducible artifacts by pinning deps and using bases like python:3.9-slim-buster, then add operational fixes (faulthandler, precompiled pyc), and finally optimize build time and size (avoid Alpine for heavy Python wheels). The uploader claims over 70+ best practices collected and many are implemented as small reproducible steps.
AI-written summary · about
chapters (16)
- 0:00Intro
- 0:33Why Docker packaging is
- 1:56The problem: too much to cover
- 2:24Today: learn the big picture
- 3:28An iterative Dockerizing process
- 4:57Get something working
- 7:06Example: don't run as root
- 8:472. Process: Security updates
- 10:34Automated builds/CI
- 13:32Operational correctness and debuggability
- 14:054. Example: Tracebacks on crashes in C code
- 15:384. Example: Pre-compile bytecode
- 16:40Reproducibility
- 20:20Faster builds and smaller images
- 22:37Dockerizing is not just about artifacts
- 23:19Thank you! Free resources on my website
related talks
29mZero to production-ready: a best-practices process for Docker packaging
43mZero to production ready: a best practices process for Docker packaging
16mSimplifying the Journey of Your Containerized Application from Dev to Production
29m5 Security Best Practices For Production Ready Containers
29m5 Best Security Practices for your Production-Ready Containers
30mPython Containers: Best Practices
33mBest Practices for Production-ready .NET Docker Images
40mDocker and Python: making them play nicely and securely for Data Science and ML