A cache that stays
Each project's layers are kept between builds. The builder stops after 10 idle minutes. The cache stays.
- Per project, per team
- Least recently used layers go first
- Build secrets are never stored in it
BuildKit on our machines, with a layer cache kept per project. A second build of the same Dockerfile reuses every layer that did not change.
8 vCPU builder·$0.011 a minute·Every plan
Each project's layers are kept between builds. The builder stops after 10 idle minutes. The cache stays.
Takes the flags of docker build. It prints the steps and, at the end, how many came from the cache.
One step before docker/build-push-action, which works unchanged. On Groundbox runners, GitHub-hosted runners and your own. Remove cache-from and cache-to: the builder keeps the cache.
No other team's build can read it or write to it. Build secrets go through BuildKit secrets.
| Build | Empty cache · after a code change · no change |
|---|---|
| Our API image, remote builder | 15.4 s · 9.5 s · 3.4 s |
| A Next.js app, remote builder | 12.6 s · 6.7 s · 3.4 s |
| Our API image, plain docker on a fresh VM | 17 to 19 s every time |
| A Next.js app, plain docker on a fresh VM | 17 to 23 s every time |
| Builder start, from stopped | 4.2 s |
One run each, in production, from a laptop through the API to a 8 vCPU builder. Plain docker ran on a fresh VM of a runner's size.
| Setting | Value |
|---|---|
| Builder | 8 vCPU, 16 GB |
| Builder time | $0.011 a minute, by the second, from its start to its stop |
| Cache | up to 50 GB per project, included |
| Platforms | linux/amd64 natively; linux/arm64 under emulation, slowly |
| One build | an hour at most |
| Plan | Paid |