Skip to content

build-cloud: add section on multi-architecture allocation #22849

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 17, 2025
Merged

build-cloud: add section on multi-architecture allocation #22849

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 22 additions & 5 deletions content/manuals/build-cloud/builder-settings.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,9 @@ keywords: build, cloud build, optimize, remote, local, cloud, registry, package

The **Builder settings** page in Docker Build Cloud lets you configure disk allocation, private resource access, and firewall settings for your cloud builders in your organization. These configurations help optimize storage, enable access to private registries, and secure outbound network traffic.

## Disk allocation
## Storage and cache management

### Disk allocation

The **Disk allocation** setting lets you control how much of the available
storage is dedicated to the build cache. A lower allocation increases
Expand All @@ -29,11 +31,28 @@ Your subscription includes the following Build cache space:
| Team | 100GB |
| Business | 200GB |

To get more Build cache space, [upgrade your subscription](/manuals/subscription/change.md).
### Multi-architecture storage allocation

Docker Build Cloud automatically provisions builders for both amd64 and arm64 architectures. Your total build cache space is split equally between these
two builders:

- Pro (50GB total): 25GB for amd64 builder + 25GB for arm64 builder
- Team (100GB total): 50GB for amd64 builder + 50GB for arm64 builder
- Business (200GB total): 100GB for amd64 builder + 100GB for arm64 builder

> [!IMPORTANT]
>
> If you only build for one architecture, be aware that your effective cache
space is half of your subscription's total allocation.

### Get more build cache space

To get more Build cache space, [upgrade your subscription](/manuals/subscription/scale.md).

> [!TIP]
>
> If you build large images, consider allocating less storage for caching.
> If you build large images, consider allocating less storage for caching to
leave more space for active builds.

## Private resource access

Expand Down Expand Up @@ -67,7 +86,5 @@ $ docker build --builder <cloud-builder> --tag registry.example.com/<image> --pu
Firewall settings let you restrict cloud builder egress traffic to specific IP addresses. This helps enhance security by limiting external network egress from the builder.

1. Select the **Enable firewall: Restrict cloud builder egress to specific public IP address** checkbox.

2. Enter the IP address you want to allow.

3. Select **Add** to apply the restriction.