Howto: Options Galore to Get from Source Code to Container
summary
Live demo compares Dockerfile variants (simple, multi-stage Dockerfiles, BuildKit with BuildKit cache mounts), Cloud-Native Buildpacks (paketo/pack) and Google’s JIB/ChaP plus Source2Image, measuring build time, final image layers and security/standardization tradeoffs. Shows splitting Spring Boot jars into dependency/resource/class layers to shrink updates, BuildKit parallel stages and cache to avoid repeated downloads, pack/paketo rebasing for OS patching, and a ChaP/JIB workflow that builds and pushes in ~20–30s without a Docker daemon.
AI-written summary · about
chapters (12)
- 0:00Start
- 1:34Situation
- 1:52Options
- 13:54Frontend Images - Versions
- 15:01Frontend Image - Experimental
- 15:37Mount Cache
- 23:03Jib
- 26:04Buildpacks idea
- 26:58History
- 29:44Rebase
- 34:11Flow
- 37:10Lab Repo
related talks
50mHowto: Options Galore to Get from Source Code to Container
58mOptions Galore to Get from Source Code to Container
01h 15mEvaluation of OSS Options to Build Container Images
46mDockerfiles, Buildpacks, Jib and more, best way to run Java code in Containers?
51mJava applications containerized and deployed, make your buildpack edition
46mWrite Once, Run Anywhere? Building Perfect Docker Images for Java Apps
34mDefence Against the Docker Arts
29mHow to Improve Your Image Builds Using Advance Docker Build