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

build(cloud): move build cloud cache description from faq to usage 

Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
This commit is contained in:
David Karlsson 2024-02-08 22:50:30 +01:00
parent 8cb196a8cb
commit 526e361298
2 changed files with 18 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
content/build/cloud/faq.md
View File

@ -15,24 +15,6 @@ aliases:
- [Can I use Docker Build Cloud with a registry behind a VPN?](#can-i-use-docker-build-cloud-with-a-registry-behind-a-vpn)
<!--toc:end-->
### How do I manage the build cache with Docker Build Cloud?
You don't need to manage the builder's cache manually. The system manages it
for you through [garbage collection](/build/cache/garbage-collection/).
Old cache is automatically removed if you hit your storage limit. You can check
your current cache state using the
[`docker buildx du` command](/engine/reference/commandline/buildx_du/).
To clear the builder's cache manually, you can use the
[`docker buildx prune` command](/engine/reference/commandline/buildx_prune/)
command. This works like pruning the cache for any other builder.
> **Note**
>
> Pruning a cloud builder's cache also removes the cache for other team members
> using the same builder.
### Can I use Docker Build Cloud with a registry behind a VPN?
No, you can't use Docker Build Cloud with a private registry or registry mirror

18
content/build/cloud/usage.md
View File

@ -152,6 +152,24 @@ For more information, refer to:
- [`docker buildx build --secret`](/engine/reference/commandline/buildx_build/#secret)
- [`docker buildx build --ssh`](/engine/reference/commandline/buildx_build/#ssh)
## Managing build cache
You don't need to manage Docker Build Cloud cache manually.
The system manages it for you through [garbage collection](/build/cache/garbage-collection/).
Old cache is automatically removed if you hit your storage limit.
You can check your current cache state using the
[`docker buildx du` command](/engine/reference/commandline/buildx_du/).
To clear the builder's cache manually,
use the [`docker buildx prune` command](/engine/reference/commandline/buildx_prune/).
This works like pruning the cache for any other builder.
> **Warning**
>
> Pruning a cloud builder's cache also removes the cache for other team members
> using the same builder.
{ .warning }
## Unset Docker Build Cloud as the default builder