OCI Images for Droplets and Buildpacks
summary
Proposes replacing tarball droplets with OCI image spec images so buildpacks produce layered container images instead of tarballs, eliminating repeated downloads and re-extraction of large runtimes (JVM, libgmp) and using layered filesystem copy-on-write to speed app start and scale. Describes a prototype that emits OCI manifests referencing existing rootfs and droplet blobs, argues patching becomes a layer rollout, and reports experiments are in the Garden backlog to measure real performance gains.
AI-written summary · about
chapters (7)
- 0:00Introduction and build packs love
- 7:52Problems with current staging
- 10:22OCI images and layered filesystems
- 13:58OCI images for Cloud Foundry
- 17:36Patching and security with images
- 19:34First step: keep build pack model
- 23:48Q&A and closing
related talks
41mModelPack: Packaging ML models as OCI artifacts made easy
35mContain Yourself: Wasm and the OCI Spec
31mJamming with CRI-O & crun: Facilitating the Convergence of AI, WASM, and Kubernetes
36mKeynote: Revolutionize your OS deploy and management with bootc containers
39mUnikraft Has Arrived: The Lightweight, Fast, Usable Solution for Cloud Deployments
31mBuilding WebAssembly Like It's 2011
36mFetching and Running Container Images on Browsers
38mCRI-O's WASM Adventure: Challenges, Strategies, and What Lies Ahead