Source2Image Intro
summary
About 25 competing sessions run at the same time but the session lays out concrete options: traditional docker build requires a Docker socket, while s2i enforces nonroot, builder-image workflows and bilder/img implement daemonless dockerfile execution by launching containers and committing images (often as a single layer) to improve security and on‑cluster builds. Techniques like FTL/Jib and Bazel produce incremental layers for faster pushes; a Kanico/Conoco PR adds multi‑stage support so curated build→runtime separation is feasible.
AI-written summary · about
chapters (6)
- 0:00Start
- 2:44What is it?
- 4:15Why do I want it?
- 4:52Approaches - Docker Daemon
- 5:57Approaches - Daemon-less Dockerfile Builds
- 20:52Observations
related talks
19mHow OpenShift Builds Container Images
34mUnprivileged Image Builds: What are the Challenges and Where are we Today?
33mDocker Container Lifecycles – Problem or Opportunity?
41mGoogle Container Tools: Develop Efficiently [...]
27mDocker Image Journey - How to Shrink a Docker Image
35mBuilding Container Images In Kubernetes: It’s Been a Journey!
46mThe Environments Inside Your Containers
52mAdding containers to your CI/CD pipeline