Small Containers? or Small Images?
summary
Shows how a tiny static site that started in a 2.36 MB source ends up packaged in a 606 MB Docker image using an Ubuntu base and full dev toolchain, then progressively reduces image size by switching to an Alpine nginx base and using multi-stage builds with a Node builder to reach ~23.8 MB (app ≈2.4 MB). Then demonstrates compiling a static web server and moving to scratch or minimal assembly-language bases to shrink artifacts to ~5.24 MB and finally ~2.36 MB, and discusses concrete steps, exact image sizes and the tradeoffs between optimization and maintainability.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:17Qui suis-je ?
- 1:20Mon environnement local
- 1:59Image de base ubuntu
- 3:07Image de base nginx alpine
- 4:54utiliser un conteneur de build
- 6:49Utiliser un binaire statique
- 8:29MUSL c'est trop lourd
- 9:43A retenir
related talks
35mOptimizing Containers for Security and Scaling
55mRecipes and Runtimes: Making Sense of Containers in 2026
27mDocker Image Journey - How to Shrink a Docker Image
40m"Willy Wonka and the Secure Container Factory"
40mBuilding Smaller Container Images
29mDockerfile: the best practices
43mContainer images anti-patterns
01h 01m.NET and Containers - each layer of abstraction indistinguishable from magic
