From 09fabd2fa0f57277130f13146541598529501962 Mon Sep 17 00:00:00 2001 From: Lorenz Vanthillo Date: Thu, 10 Apr 2025 10:55:47 +0200 Subject: [PATCH] BuildKit supports multiple cache exporters Related to https://github.com/docker/docs/issues/18590 --- content/manuals/build/cache/backends/_index.md | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/content/manuals/build/cache/backends/_index.md b/content/manuals/build/cache/backends/_index.md index 6dd4a8a9de..de54ea0f6c 100644 --- a/content/manuals/build/cache/backends/_index.md +++ b/content/manuals/build/cache/backends/_index.md @@ -81,12 +81,11 @@ $ docker buildx build --push -t / \ ## 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 / \