Kaniko's community fork, with cross-stage cache lookahead, ran 1.6x slower than BuildKit on GitLab.com runners in a dev.to benchmark. The 15x gap still quoted against kaniko dates from 2018, so teams choosing an in-cluster builder need figures from their own Dockerfiles.
Reality
- Evidence40
- Adoption
- Insufficient
- Hype gap+30
- Incentives
- Insufficient
- Confidence35
Every Cloud Build run gets a fresh VM with an empty Docker daemon, so the only layer cache that survives a build is one exported to a registry. The documented paths reach for a published image or an archived tool instead.
Reality
- Evidence40
- Adoption
- Insufficient
- Hype gap+20
- Incentives30
- Confidence50
Two 2026 writeups measured Docker's alpine cold start at 0.31 and 1.23 seconds, a fourfold spread on the same test. The rootless networking backend a host runs moves throughput from about 40 Gbps to 3.
Reality
- Evidence40
- Adoption38
- Hype gap+12
- Incentives
- Insufficient
- Confidence45
The credential was in history[].created_by, expanded there by a RUN command that took a build argument, inside a Harbor project anyone could pull anonymously. Baseten rotated it about 17 hours after the disclosure email.
Reality
- Evidence62
- Adoption35
- Hype gap+22
- Incentives60
- Confidence55
A dev.to write-up traces a build that fails only on enterprise-kernel servers to three correct components meeting badly. The seccomp profile that fixes it stays inert until the build runs on Docker's classic engine.
Reality
- Evidence50
- Adoption12
- Hype gap−15
- Incentives55
- Confidence55
Reading soit-ai/soit v1.0.0 out of ghcr.io by hand shows how far a container signature reaches. It covers one digest, and the release tag survives as a string in the build predicate that nothing compares for you.
Reality
- Evidence62
- Adoption20
- Hype gap+25
- Incentives55
- Confidence60
A two-part dev.to series walks through the Buildx subcommand that collapses multi-target image builds into HCL files, where the variables live in a separate file and a print flag shows the fully interpolated configuration before anything is pushed.
Reality
- Evidence52
- Adoption30
- Hype gap+12
- Incentives45
- Confidence58
A dev.to teardown argues the 11-minute CI build that runs in 20 seconds locally is a cache-miss problem, and that one run with --progress=plain will prove it before you pay for bigger runners.
Reality
- Evidence55
- Adoption
- Insufficient
- Hype gap+12
- Incentives45
- Confidence52