Docker
Inline cache
Quick answer
Inline cache embeds layer cache metadata inside the pushed image so a later build can reuse layers by pulling that image.
Inline cache embeds layer cache metadata inside the pushed image so a later build can reuse layers by pulling that image.
Why it matters
It is convenient because it needs no separate cache store, but it only caches the final stage — multi-stage builds need a registry or local cache backend instead.
Your next build could be twice as fast, at half the price
Start free. Migrating away is the same one line, and we publish that diff too.
Related
Base imageA base image is the image named in a Dockerfile's FROM instruction, providing the filesystem and tooling every subsequent layer builds on.BuildKitBuildKit is Docker's build engine, providing parallel layer execution, better caching and support for build secrets and multi-platform output.BuildxBuildx is the Docker CLI plugin that exposes BuildKit features, including multi-platform builds, remote builders and advanced cache backends.Cache mountA cache mount is a BuildKit feature that persists a directory across builds without including it in the resulting image layer.