docker/buildx
1
0
Fork 0
mirror of https://gitea.com/Lydanne/buildx.git synced 2025-11-04 10:03:42 +08:00
Code Issues Packages Projects Releases 1 Wiki Activity

docs: final cache storage fixups

Browse Source 
Signed-off-by: Justin Chadwell <me@jedevc.com>
This commit is contained in:
Justin Chadwell
2022-09-22 10:50:59 +01:00
parent 91f0ed3fc3
commit f823d3c73c
3 changed files with 13 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/guides/cache/azblob.md vendored
View File

@@ -30,15 +30,15 @@ $ docker buildx build . --push -t <registry>/<image> \
Common parameters: Common parameters:
- `name`: the name of the cache image. - `name`: the name of the cache image.
Parameters for `--cache-to`:
- `account_url`: the base address of the blob storage account, for example: - `account_url`: the base address of the blob storage account, for example:
`https://myaccount.blob.core.windows.net`. See `https://myaccount.blob.core.windows.net`. See
[authentication](#authentication). [authentication](#authentication).
- `secret_access_key`: specifies the - `secret_access_key`: specifies the
[Azure Blob Storage account key](https://docs.microsoft.com/en-us/azure/storage/common/storage-account-keys-manage), [Azure Blob Storage account key](https://docs.microsoft.com/en-us/azure/storage/common/storage-account-keys-manage),
see [authentication](#authentication). see [authentication](#authentication).
Parameters for `--cache-to`:
- `mode`: specify cache layers to export (default: `min`), see - `mode`: specify cache layers to export (default: `min`), see
[cache mode](./index.md#cache-mode) [cache mode](./index.md#cache-mode)

17
docs/guides/cache/inline.md vendored
View File

@@ -8,6 +8,14 @@ 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 build flow, or not exporting your images directly to a registry, then you may
want to consider the [registry](./registry.md) cache. want to consider the [registry](./registry.md) cache.
## Synopsis
```console
$ docker buildx build . --push -t <registry>/<image> \
--cache-to type=inline \
--cache-from type=registry,ref=<registry>/image
```
To export cache using `inline` storage, pass `type=inline` to the `--cache-to` To export cache using `inline` storage, pass `type=inline` to the `--cache-to`
option: option:
@@ -30,15 +38,6 @@ the specified registry:
$ docker buildx build . --push -t <registry>/<image> --cache-from type=registry,ref=<registry>/<image> $ docker buildx build . --push -t <registry>/<image> --cache-from type=registry,ref=<registry>/<image>
``` ```
Most of the time, you'll want to have each build both import and export cache
from the cache store. To do this, specify both `--cache-to` and `--cache-from`:
```console
$ docker buildx build . --push -t <registry>/<image> \
--cache-to type=inline \
--cache-from type=registry,ref=<registry>/<image>
```
## Further reading ## Further reading
For an introduction to caching see For an introduction to caching see

2
docs/guides/cache/local.md vendored
View File

@@ -53,6 +53,8 @@ Parameters for `--cache-from`:
## Cache versioning ## Cache versioning
<!-- FIXME: update once https://github.com/moby/buildkit/pull/3111 is released -->
This section describes how versioning works for caches on a local filesystem, This section describes how versioning works for caches on a local filesystem,
and how you can use the `digest` parameter to use older versions of cache. and how you can use the `digest` parameter to use older versions of cache.