mirror of
https://gitea.com/Lydanne/buildx.git
synced 2025-07-09 21:17:09 +08:00
docs: refactored file and directory structure
Signed-off-by: David Karlsson <david.karlsson@docker.com>
This commit is contained in:
14
docs/manuals/README.md
Normal file
14
docs/manuals/README.md
Normal file
@ -0,0 +1,14 @@
|
||||
# Buildx manuals 📚
|
||||
|
||||
This directory contains a bunch of useful docs for how to use Buildx features.
|
||||
|
||||
> **Note**
|
||||
>
|
||||
> The markdown files in this directory (excluding this README) are reused
|
||||
> downstream by the
|
||||
> [Docker documentation repository](https://github.com/docker/docs).
|
||||
>
|
||||
> If you wish to contribute to these docs, be sure to first review the
|
||||
> [documentation contribution guidelines](https://docs.docker.com/contribute/overview/).
|
||||
>
|
||||
> Thank you!
|
@ -50,7 +50,7 @@ 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](https://docs.docker.com/build/building/drivers/).
|
||||
[select an alternative Buildx driver](../../drivers/index.md).
|
||||
|
||||
Example `buildx` command using the `registry` backend, using import and export
|
||||
cache:
|
||||
@ -127,10 +127,8 @@ with both parameters to find the results that work best for you.
|
||||
|
||||
### Cache compression
|
||||
|
||||
<!-- TODO: change this link to a local link -->
|
||||
|
||||
The cache compression options are the same as the
|
||||
[exporter compression options](https://docs.docker.com/build/building/exporters/#compression).
|
||||
[exporter compression options](../../exporters/index.md#compression).
|
||||
|
||||
For example, to compress the `registry` cache with `zstd` compression:
|
||||
|
||||
@ -142,10 +140,8 @@ $ docker buildx build --push -t <registry>/<image> \
|
||||
|
||||
### OCI media types
|
||||
|
||||
<!-- TODO: change this link to a local link -->
|
||||
|
||||
The cache OCI options are the same as the
|
||||
[exporter OCI options](https://docs.docker.com/build/building/exporters/#oci-media-types).
|
||||
[exporter OCI options](../../exporters/index.md#oci-media-types).
|
||||
|
||||
For example, to export OCI media type cache, use the `oci-mediatypes` property:
|
||||
|
@ -9,7 +9,7 @@ Docker driver. For example:
|
||||
- Specify custom BuildKit versions to use.
|
||||
- Build multi-arch images, see [QEMU](#qemu)
|
||||
- Advanced options for
|
||||
[cache import and export](https://docs.docker.com/build/building/cache/)
|
||||
[cache import and export](../cache/backends/index.md)
|
||||
|
||||
## Synopsis
|
||||
|
@ -144,8 +144,9 @@ $ docker buildx build --output type=tar,dest=<path/to/output> .
|
||||
```
|
||||
|
||||
The `local` exporter is useful in
|
||||
[multi-stage builds](/build/building/multi-stage/) since it allows you to export
|
||||
only a minimal number of build artifacts. For example, self-contained binaries.
|
||||
[multi-stage builds](https://docs.docker.com/build/building/multi-stage/) since
|
||||
it allows you to export only a minimal number of build artifacts. For example,
|
||||
self-contained binaries.
|
||||
|
||||
### Cache-only export
|
||||
|
Reference in New Issue
Block a user