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

Merge pull request #19415 from docker/nicks/e2e 

build(cloud): rephrase conn encryption
This commit is contained in:
David Karlsson 2024-02-15 14:51:39 +01:00 committed by GitHub
parent 20e9030be4 06b710d24a
commit 9d3d153014
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/build/cloud/_index.md
View File

@ -37,7 +37,7 @@ And the best part: you don't need to worry about managing builders or
infrastructure. Just connect to your builders, and start building. infrastructure. Just connect to your builders, and start building.
Each cloud builder provisioned to an organization is completely Each cloud builder provisioned to an organization is completely
isolated to a single Amazon EC2 instance, with a dedicated EBS volume for build 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 cache, and encryption in transit. That means there are no shared processes or
data between cloud builders. data between cloud builders.
> **Note** > **Note**

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

@ -136,7 +136,7 @@ and forth between each other.
To use build secrets with Docker Build Cloud, To use build secrets with Docker Build Cloud,
such as authentication credentials or tokens, such as authentication credentials or tokens,
use the `--secret` and `--ssh` CLI flags for the `docker buildx` command. use the `--secret` and `--ssh` CLI flags for the `docker buildx` command.
The traffic is end-to-end encrypted and secrets are never stored in the build cache. The traffic is encrypted and secrets are never stored in the build cache.
> **Warning** > **Warning**
> >