BuildKit supports multiple cache exporters

Related to https://github.com/docker/docs/issues/18590
This commit is contained in:
Lorenz Vanthillo 2025-04-10 10:55:47 +02:00 committed by GitHub
parent 6057a7b51f
commit 09fabd2fa0
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 5 additions and 6 deletions

View File

@ -81,12 +81,11 @@ $ docker buildx build --push -t <registry>/<image> \
## Multiple caches
BuildKit currently only supports
[a single cache exporter](https://github.com/moby/buildkit/pull/3024). But you
can import from as many remote caches as you like. For example, a common pattern
is to use the cache of both the current branch and the main branch. The
following example shows importing cache from multiple locations using the
registry cache backend:
BuildKit supports multiple cache exporters, allowing you to push cache to more
than one destination. You can also import from as many remote caches as you'd
like. For example, a common pattern is to use the cache of both the current
branch and the main branch. The following example shows importing cache from
multiple locations using the registry cache backend:
```console
$ docker buildx build --push -t <registry>/<image> \