Panel Discussion: Buildpacks and Containers for Cloud Foundry
summary
Debate over whether Cloud Foundry should treat containers as packaged images or as kernel-level process isolation focuses on concrete tradeoffs: buildpacks produce a portable droplet that can move between spaces without restaging, Dockerfiles give fast onboarding but create opaque images with many layers and a growing Docker graph cache to manage. Panel covers staging, restage-for-vuln problems, filesystem layering bugs (permission quirks across dozens of layers), Kubernetes pods versus single containers, and when to enforce curated buildpacks versus allowing arbitrary containers.
AI-written summary · about
chapters (9)
- 0:00Introduction of panelists
- 2:49Defining containers and images
- 7:08Buildpacks vs containers spectrum
- 13:38User experience and abstraction goals
- 17:31Cloud Foundry push vs Docker ease
- 23:05Governance and build pack complexity
- 26:46Layered file systems challenges
- 29:36Cloud Foundry’s layered approach
- 30:05Closing remarks
related talks
28mDelivering Heterogeneous Architectures
30mPanel: Cloud Foundry and Kubernetes - The Blending Continues
18mLightning Talk: Multi-Buildpack Hacks
24mA Cloud Native Foundation For Developer/Application Platforms
24mBringing Cloud Native Buildpacks to Cloud Foundry
33mDocker and Cloud Foundry: The 3 Use Cases
46mPanel Discussion: The number of orche
36mClosing the Developer Experience Gap of your Container Platforms