inline cache storage backend is the simplest way to get an external cache
and is easy to get started using if you're already building and pushing an
The downside of inline cache is that it doesn't scale with multi-stage builds as well as the other drivers do. It also doesn't offer separation between your output artifacts and your cache output. This means that if you're using a particularly complex build flow, or not exporting your images directly to a registry, then you may want to consider the registry cache.
$ docker buildx build --push -t <registry>/<image> \ --cache-to type=inline \ --cache-from type=registry,ref=<registry>/<image> .
No additional parameters are supported for the
To export cache using
inline storage, pass
type=inline to the
$ docker buildx build --push -t <registry>/<image> \ --cache-to type=inline .
Alternatively, you can also export inline cache by setting the build argument
BUILDKIT_INLINE_CACHE=1, instead of using the
$ docker buildx build --push -t <registry>/<image> \ --build-arg BUILDKIT_INLINE_CACHE=1 .
To import the resulting cache on a future build, pass
--cache-from which lets you extract the cache from inside a Docker image in
the specified registry:
$ docker buildx build --push -t <registry>/<image> \ --cache-from type=registry,ref=<registry>/<image> .
For an introduction to caching see Optimizing builds with cache.
For more information on the
inline cache backend, see the