Completed
Why Docker packaging is complicated
Class Central Classrooms beta
YouTube videos curated by Class Central.
Classroom Contents
Best Practices for Production-Ready Docker Packaging
Automatically move to the next video in the Classroom when playback concludes
- 1 Intro
- 2 Why Docker packaging is complicated
- 3 The problem: too much to cover
- 4 Today: learn a process
- 5 An iterative process
- 6 Security Before you can deploy anything publicly, it reeds to be secure . So we do that net
- 7 Security: Don't run as root
- 8 Security: Other best practices
- 9 CI: Tag based on branch . You want to build image for feature branch 123 . You want production not to be impacted.
- 10 CI: Other best practices . Once a week, rebuild without caching--pull
- 11 Make it debuggable You've started automatically building and probably deploying
- 12 Debuggable: Tracebacks on crashes in C code
- 13 Debuggable: Other best practices
- 14 Improve operational correctness
- 15 Operational correctness: Pre- compile bytecode
- 16 Reproducible builds: Choose a good base image
- 17 Reproducible builds: More best practices
- 18 Faster builds: Don't use Alpine Linux
- 19 Faster builds: More best practices
- 20 Smaller images: Disable pip's caching
- 21 Smaller images: Other best practices
