"ko: The Only Good Way to Build Go Containers"
summary
ko runs go build to produce a binary, stitches it onto a tiny base image, and pushes the image with registry HTTP APIs so there is no Docker daemon required. It reuses Go’s build cache to skip work, avoids pushing unchanged artifacts, emits build-time SBOMs, supports cross‑compilation and multi‑platform images, and integrates with Kubernetes, GitHub Actions and a Terraform provider. Claim: simpler, faster, smaller Go container images; status: accepted into CNCF and actively used.
AI-written summary · about
chapters (8)
- 0:00Introduction to ko
- 1:03Multi-stage Dockerfiles problems
- 3:30ko simplifies Go builds
- 5:34What ko does under the hood
- 7:21Benefits of ko
- 9:51Advanced features
- 13:17Why Go and simplicity
- 14:45Other tools inspired by ko
related talks
23mko - zero-config tool for deploying Go app on k8s
25mBuilding Docker Images Without Docker
21mMaking Docker GO: Why One of the Fastest Growing Open Source Projects
35mDeveloping Go apps with Docker
01h 03mGo Microservices in Containers
46mBuilding Kubernetes [a Go binary] with Bazel
58mOptions Galore to Get from Source Code to Container
28mCompiling Containers