Using Buildpacks To Reduce Container Bloat and Attack Surface
summary
87% of container vulnerabilities live in packages not used at runtime and teams waste effort patching them. Using Cloud Native Buildpacks with tiered custom builders compiles heavy dependencies once, caches runtimes, and enables OS rebasing so a single pack rebase swaps the stack layer and updates hundreds of apps in milliseconds. The result: true separation of ownership, lean runtime images, and measurable reduction from O(n) rebuilds to order one patch propagation.
AI-written summary · about
chapters (6)
- 0:00Container vulnerability waste
- 3:51Introduction to buildpacks
- 8:44Buildpacks solve patching
- 15:05Pack CLI rebase
- 19:40Security and governance benefits
- 20:42Q&A
related talks
05mProject Lightning Talk: Container Builds at Scale with Buildpacks
45mBuilding & Managing Container Images at Scale with Cloud Native Buildpacks
26mCloud Native Buildpacks: Containers for Everyone
26mIntroduction to Cloud Native Buildpacks
34mDeep Dive: Cloud Native Buildpacks
24mIntro to Cloud Native Buildpacks
06mProject Lightning Talk: Dockerfiles vs Buildpacks: What's The Cloud Native Way?
43mThe future of containerization in mature organizations