Building containers without DockerFile
summary
Claims that containers can be built without a Dokerfile using buildpacks and JIB and demonstrates building with pack build and pushing to Google Artifact Registry and Cloud Run, producing a working Java service locally and on Cloud Run. Shows image sizes (214 MB for JIB, ~700 MB for default buildpack) and ~72 reported vulnerabilities, explains rebase updates base layers without rebuilding the app, and shows image signing with cosign backed by KMS to enforce signed deployments.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:57Dockerfile problems
- 12:26JIB alternative
- 17:33Build packs explained
- 21:16Advantages and disadvantages of build packs
- 23:21When to use build packs
- 26:33Build packs in Cloud Run
- 32:51Securing images with cosign
- 40:57Q&A
related talks
51mJava applications containerized and deployed, make your buildpack edition
49mDockerfiles, Jib ..., what's the best way to run your Java code in Containers?
46mDockerfiles, Buildpacks, Jib and more, best way to run Java code in Containers?
49mJava Container Mastery: Optimizing Images Across Build Tools
45mBuilding & Managing Container Images at Scale with Cloud Native Buildpacks
30mSpeedy build for your java application images with JIB!
32mDockerfile vs Jib vs Pack vs Native Image: Which Is the Best Image Build Method?
25mCommit to Excellence - Java in Containers