build(cloud): describe builder isolation on index page

Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
This commit is contained in:
David Karlsson 2024-02-08 22:39:06 +01:00
parent 86cf54be0b
commit 312584c2d9
2 changed files with 4 additions and 7 deletions

View File

@ -34,6 +34,10 @@ Docker Build Cloud provides several benefits over local builds:
And the best part: you don't need to worry about managing builders or
infrastructure. Just connect to your builders, and start building.
Each cloud builder provisioned to an organization is completely
isolated to a single Amazon EC2 instance, with a dedicated EBS volume for build
cache, and end-to-end encryption. That means there are no shared processes or
data between cloud builders.
> **Note**
>

View File

@ -15,13 +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-->
### Are builders shared between organizations?
No. Each cloud builder provisioned to an organization is completely
isolated to a single Amazon EC2 instance, with a dedicated EBS volume for build
cache, and end-to-end encryption. That means there are no shared processes or
data between cloud builders.
### Do I need to add my secrets to the builder to access private resources?
No. Your interface to Docker Build Cloud is Buildx, and you can use the existing