docker
/
buildx
mirror of https://github.com/docker/buildx.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #1352 from dvdksn/remove-cache-opt-link 

remove/update links to satisfy htmlproofer
This commit is contained in:
Justin Chadwell 2022-10-11 13:17:26 +01:00 committed by GitHub
parent 361c093a35 1267e0c076
commit 7add6e48b6
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
docs/guides/cache/index.md vendored
View File

@ -12,9 +12,9 @@ important to keep the runtime of image builds as low as possible.
>
> If you use secrets or credentials inside your build process, ensure you
> manipulate them using the dedicated
> [--secret](../../reference/buildx_build.md#secret) functionality instead of
> using manually `COPY`d files or build `ARG`s. Using manually managed secrets
> like this with exported cache could lead to an information leak.
> [`--secret` option](https://docs.docker.com/engine/reference/commandline/buildx_build/#secret).
> Manually managing secrets using `COPY` or `ARG` could result in leaked
> credentials.
## Backends
@ -43,14 +43,12 @@ Buildx supports the following cache storage backends:
## Command syntax
To use any of the cache backends, you first need to specify it on build with the
[`--cache-to`](../../reference/buildx_build.md#cache-to) option to export the
cache to your storage backend of choice. Then, use the
[`--cache-from`](../../reference/buildx_build.md#cache-from) option to import
the cache from the storage backend into the current build. Unlike the local
BuildKit cache (which is always enabled), all of the cache storage backends must
be explicitly exported to, and explicitly imported from. All cache exporters
except for the `inline` cache requires that you
[select an alternative Buildx driver](../drivers/index.md).
[`--cache-to` option](https://docs.docker.com/engine/reference/commandline/buildx_build/#cache-to) to export the cache to your storage backend of choice. Then,
use the [`--cache-from` option](https://docs.docker.com/engine/reference/commandline/buildx_build/#cache-from) to import the cache from the storage backend into
the current build. Unlike the local BuildKit cache (which is always enabled),
all of the cache storage backends must be explicitly exported to, and explicitly
imported from. All cache exporters except for the `inline` cache requires that
you [select an alternative Buildx driver](../drivers/index.md).
Example `buildx` command using the `registry` backend, using import and export
cache: