|
1 | 1 | --- |
2 | 2 | title: Configure Docker Offload |
3 | | -linktitle: Configure |
| 3 | +linktitle: Configuration & billing |
4 | 4 | weight: 20 |
5 | | -description: Learn how to configure build settings for Docker Offload. |
6 | | -keywords: cloud, configuration, settings, cloud builder, GPU, disk allocation, private resources, firewall |
| 5 | +description: Learn how to configure settings for Docker Offload. |
| 6 | +keywords: cloud, configuration, settings, GPU |
7 | 7 | --- |
8 | 8 |
|
9 | | -To use Docker Offload, you must start it in Docker Desktop. For more details, |
10 | | -see the [Docker Offload quickstart](/offload/quickstart/). |
| 9 | +The following Docker Offload settings can be configured: |
11 | 10 |
|
12 | | -Settings for the cloud builders in Docker Offload can be further configured, in |
13 | | -addition to settings for an entire organization, through **Offload settings** in |
14 | | -the Docker Offload dashboard. |
| 11 | + - [Run settings](#run-settings): Configure tenancy and data settings for |
| 12 | + Docker Offload in your organization. |
| 13 | + - [Offload access](#offload-access): Configure Offload availability for |
| 14 | + members of your organization. |
| 15 | + - [Offload billing](#offload-billing): View and configure billing for Docker |
| 16 | + Offload. |
15 | 17 |
|
16 | | -> [!NOTE] |
17 | | -> |
18 | | -> To view usage and configure billing for Docker Offload, see [Docker Offload |
19 | | -> usage and billing](/offload/usage/). |
20 | | -
|
21 | | -## Offload settings |
| 18 | +## Run settings |
22 | 19 |
|
23 | | -The **Offload settings** page in Docker Home lets you configure disk |
24 | | -allocation, private resource access, and firewall settings for your cloud |
25 | | -builders in your organization. |
| 20 | +The **Run settings** page in Docker Home lets you configure tenancy and data |
| 21 | +settings for Docker Offload in your organization. |
26 | 22 |
|
27 | | -To view the **Offload settings** page: |
| 23 | +To view the **Run settings** page: |
28 | 24 |
|
29 | 25 | 1. Go to [Docker Home](https://app.docker.com/). |
30 | 26 | 2. Select the account for which you want to manage Docker Offload. |
31 | | -3. Select **Offload** > **Offload settings**. |
32 | | - |
33 | | -The following sections describe the available settings. |
34 | | - |
35 | | -### Disk allocation |
36 | | - |
37 | | -The **Disk allocation** setting lets you control how much of the available |
38 | | -storage is dedicated to the build cache. A lower allocation increases storage |
39 | | -available for active builds. |
40 | | - |
41 | | -Adjust the **Disk allocation** slider to specify the percentage of storage used |
42 | | -for build caching. |
43 | | - |
44 | | -Any changes take effect immediately. |
45 | | - |
46 | | -> [!TIP] |
47 | | -> |
48 | | -> If you build very large images, consider allocating less storage for caching. |
| 27 | +3. Select **Offload** > **Run settings**. |
49 | 28 |
|
50 | | -### Build cache space |
| 29 | +## Offload access |
51 | 30 |
|
52 | | -Your subscription includes the following Build cache space: |
| 31 | +The **Offload access** page in Docker Home lets you configure Offload |
| 32 | +availability for members of your organization. By default, Offload is disabled |
| 33 | +for all members of an organization. An organization owner must enable Offload |
| 34 | +access for the organization. To configure Docker Offload access as an |
| 35 | +organization owner: |
53 | 36 |
|
54 | | -| Subscription | Build cache space | |
55 | | -|--------------|-------------------| |
56 | | -| Personal | N/A | |
57 | | -| Pro | 50GB | |
58 | | -| Team | 100GB | |
59 | | -| Business | 200GB | |
60 | | - |
61 | | -To get more Build cache space, [upgrade your subscription](/manuals/subscription/change.md). |
62 | | - |
63 | | -### Private resource access |
64 | | - |
65 | | -Private resource access lets cloud builders pull images and packages from |
66 | | -private resources. This feature is useful when builds rely on self-hosted |
67 | | -artifact repositories or private OCI registries. |
68 | | - |
69 | | -For example, if your organization hosts a private [PyPI](https://pypi.org/) |
70 | | -repository on a private network, Docker Build Cloud would not be able to access |
71 | | -it by default, since the cloud builder is not connected to your private network. |
72 | | - |
73 | | -To enable your cloud builders to access your private resources, enter the host |
74 | | -name and port of your private resource and then select **Add**. |
75 | | - |
76 | | -#### Authentication |
| 37 | +1. Sign in to [Docker Home](https://app.docker.com/) as an organization owner. |
| 38 | +2. Select the account for which you want to manage Docker Offload. |
| 39 | +3. Select **Admin Console** > **Offload access**. |
| 40 | +4. Select whether to enable or disable Offload access for all members of the |
| 41 | + organization as well as allow or disallow GPU access. |
77 | 42 |
|
78 | | -If your internal artifacts require authentication, make sure that you |
79 | | -authenticate with the repository either before or during the build. For internal |
80 | | -package repositories for npm or PyPI, use [build |
81 | | -secrets](/manuals/build/building/secrets.md) to authenticate during the build. |
82 | | -For internal OCI registries, use `docker login` to authenticate before building. |
| 43 | + > [!NOTE] |
| 44 | + > |
| 45 | + > If you enable Offload access, all members of the organization can use |
| 46 | + > Docker Offload. Members of the organization can choose to start or stop |
| 47 | + > Offload in Docker Desktop. |
83 | 48 |
|
84 | | -Note that if you use a private registry that requires authentication, you will |
85 | | -need to authenticate with `docker login` twice before building. This is because |
86 | | -the cloud builder needs to authenticate with Docker to use the cloud builder, |
87 | | -and then again to authenticate with the private registry. |
88 | 49 |
|
89 | | -```console |
90 | | -$ echo $DOCKER_PAT | docker login docker.io -u <username> --password-stdin |
91 | | -$ echo $REGISTRY_PASSWORD | docker login registry.example.com -u <username> --password-stdin |
92 | | -$ docker build --builder <cloud-builder> --tag registry.example.com/<image> --push . |
93 | | -``` |
| 50 | +## Offload billing |
94 | 51 |
|
95 | | -### Firewall |
| 52 | +> [!NOTE] |
| 53 | +> |
| 54 | +> All free trial credits granted for the Docker Offload Beta expire after 90 |
| 55 | +> days from the time they are granted. To continue using Docker Offload after |
| 56 | +> your credits expire, you can enable on-demand usage at [Docker Home |
| 57 | +> Billing](https://app.docker.com/billing). |
96 | 58 |
|
97 | | -Firewall settings let you restrict cloud builder egress traffic to specific IP |
98 | | -addresses. This helps enhance security by limiting external network egress from |
99 | | -the builder. |
| 59 | +For Docker Offload, you can view and configure billing on the **Docker Offload** |
| 60 | +page in [Docker Home Billing](https://app.docker.com/billing). In Docker Home |
| 61 | +Billing, you can: |
100 | 62 |
|
101 | | -1. Select **Enable firewall: Restrict cloud builder egress to specific public IP address**. |
102 | | -2. Enter the IP address you want to allow. |
103 | | -3. Select **Add** to apply the restriction. |
| 63 | +- View your Docker Offload usage summary |
| 64 | +- View rates for cloud resources |
| 65 | +- Manage on-demand usage |
| 66 | +- Add or change payment methods |
104 | 67 |
|
| 68 | +For more general information about billing, see [Billing](../billing/_index.md). |
0 commit comments