Defence Against the Docker Arts
summary
Explains why a Dockerfile forces fragile, cache‑dependent image builds (examples: a 112‑line RUN, almost 2,500 OpenJDK tags, top‑10 images with 30+ vulnerabilities) and compares alternatives: low‑level build kit (Go API), Java‑native jib (Maven/Gradle plugin that builds images without a daemon), and Cloud Native Buildpacks with pack rebase that updates stacks in seconds so thousands of app images avoid full rebuilds and shrink patch time from months/years to hours.
AI-written summary · about
chapters (6)
- 0:00Start
- 12:31Buildkit is for tool developers
- 15:36Jib is for application developers
- 20:38Pack CLI
- 24:39Buildpack API
- 29:48ABI Compatibility
related talks
46mDockerfiles, Buildpacks, Jib and more, best way to run Java code in Containers?
46mWrite Once, Run Anywhere? Building Perfect Docker Images for Java Apps
50mHowto: Options Galore to Get from Source Code to Container
54mHowto: Options Galore to Get from Source Code to Container
58mOptions Galore to Get from Source Code to Container
25mBuilding Docker Images Without Docker
51mJava applications containerized and deployed, make your buildpack edition
01h 15mEvaluation of OSS Options to Build Container Images