Best Practices for Production-Ready Docker Packaging

Best Practices for Production-Ready Docker Packaging

EuroPython Conference via YouTube Direct link

Security Before you can deploy anything publicly, it reeds to be secure . So we do that net

6 of 21

6 of 21

Security Before you can deploy anything publicly, it reeds to be secure . So we do that net

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

Never Stop Learning.

Get personalized course recommendations, track subjects and courses with reminders, and more.

Someone learning on their laptop while sitting on the floor.