From 12f13bfba2b5e2c9c2edece52846a5d7f52d6b05 Mon Sep 17 00:00:00 2001 From: Sarah Sanders Date: Tue, 1 Jul 2025 14:27:34 -0400 Subject: [PATCH 1/4] fix: typos in insights.md (#22974) ## Description - Noticed a grammar typo in insights.md, fixed a few others as well ## Related issues or tickets https://docker.atlassian.net/browse/ENGDOCS-2802 ## Reviews - [ ] Technical review - [ ] Editorial review - [ ] Product review --- content/manuals/admin/organization/insights.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/content/manuals/admin/organization/insights.md b/content/manuals/admin/organization/insights.md index f06a0a5fb52b..05ed1d1a54e5 100644 --- a/content/manuals/admin/organization/insights.md +++ b/content/manuals/admin/organization/insights.md @@ -68,9 +68,9 @@ The chart contains the following data: | Data | Description | |:-----------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Active user | The number of users that have actively used Docker Desktop and either signed in with a Docker account that has a license in your organization or signed in to a Docker account with an email address from a domain associated with your organization.

Users who don’t sign in to an account associated with your organization are not represented in the data. To ensure users sign in with an account associated with your organization, you can [enforce sign-in](/security/for-admins/enforce-sign-in/). | -| Total organization members | The number of users that have used Docker Desktop, regardless of their Insights activity. | -| Users opted out of analytics | The number of users that are a member of your organization that have opted out of sending analytics.

When users opt out of sending analytics, you won't see any of their data in Insights. To ensure that the data includes all users, you can use [Settings Management](/desktop/hardened-desktop/settings-management/) to set `analyticsEnabled` for all your users. | +| Active user | The number of users who have actively used Docker Desktop and either signed in with a Docker account that has a license in your organization or signed in to a Docker account with an email address from a domain associated with your organization.

Users who don’t sign in to an account associated with your organization are not represented in the data. To ensure users sign in with an account associated with your organization, you can [enforce sign-in](/security/for-admins/enforce-sign-in/). | +| Total organization members | The number of users who have used Docker Desktop, regardless of their Insights activity. | +| Users opted out of analytics | The number of users who are members of your organization that have opted out of sending analytics.

When users opt out of sending analytics, you won't see any of their data in Insights. To ensure that the data includes all users, you can use [Settings Management](/desktop/hardened-desktop/settings-management/) to set `analyticsEnabled` for all your users. | | Active users (graph) | The view over time for total active users. | @@ -142,7 +142,7 @@ The chart contains the following data: ### Extensions Monitor extension installation activity with this chart. It provides visibility -into the Docker Desktop extensions your team are using, letting you track +into the Docker Desktop extensions your teams are using, letting you track adoption and identify popular tools that enhance productivity. The chart contains the following data: @@ -180,7 +180,7 @@ A Docker Desktop user export file contains the following data points: member of - Date Joined: The date the user joined your organization - Last Logged-In Date: The last date the user logged into Docker using -their web browser (this include Docker Hub and Docker Home) +their web browser (this includes Docker Hub and Docker Home) - Docker Desktop Version: The version of Docker Desktop the user has installed - Last Seen Date: The last date the user used the Docker Desktop application @@ -206,11 +206,11 @@ solutions to resolve common problems. Management](/desktop/hardened-desktop/settings-management/) and enable the `analyticsEnabled` setting. -- Ensure that users are using Docker Desktop and aren't using the standalone +- Ensure users use Docker Desktop and aren't using the standalone version of Docker Engine. - Only Docker Desktop can provide data for Insights. If a user installs and - uses Docker Engine outside of Docker Desktop, Docker Engine won't provide + Only Docker Desktop can provide data for Insights. If a user installs Docker + Engine outside of Docker Desktop, Docker Engine won't provide data for that user. - Ensure that users are signing in to an account associated with your From b6833c2b1d1220e8b25374bca7dedb1efecc6ef9 Mon Sep 17 00:00:00 2001 From: Sebastiaan van Stijn Date: Wed, 2 Jul 2025 08:58:44 +0200 Subject: [PATCH 2/4] Merge pull request #22731 from thaJeztah/vale_bgp vale: add "BGP" (Border Gateway Protocol) to acronyms --- _vale/Docker/Acronyms.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/_vale/Docker/Acronyms.yml b/_vale/Docker/Acronyms.yml index 3d8eb1e86760..d6d9fdde6bde 100644 --- a/_vale/Docker/Acronyms.yml +++ b/_vale/Docker/Acronyms.yml @@ -17,6 +17,7 @@ exceptions: - ASP - AUFS - AWS + - BGP # Border Gateway Protocol - BIOS - BPF - BSD From 1d5fb9e0946d558778869a4b01d5e21ab3b93463 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Pawe=C5=82=20Gronowski?= Date: Wed, 2 Jul 2025 09:10:29 +0200 Subject: [PATCH 3/4] docs: Add warning about using btrfs storage driver (#22621) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit ## Description This has been a source of confusion for many users. Recommend to use overlay2 and clarify that using btrfs filesystem doesn't require using the btrfs storage driver. ## Related issues or tickets - https://github.com/moby/moby/issues/27653 ## Reviews - [ ] Technical review - [ ] Editorial review - [ ] Product review --------- Signed-off-by: Paweł Gronowski Co-authored-by: Allie Sadler <102604716+aevesdocker@users.noreply.github.com> --- .../engine/storage/drivers/btrfs-driver.md | 9 ++++++++ .../storage/drivers/select-storage-driver.md | 21 ++++++++++++------- 2 files changed, 23 insertions(+), 7 deletions(-) diff --git a/content/manuals/engine/storage/drivers/btrfs-driver.md b/content/manuals/engine/storage/drivers/btrfs-driver.md index 720f6d59be8f..ecfa3179ea34 100644 --- a/content/manuals/engine/storage/drivers/btrfs-driver.md +++ b/content/manuals/engine/storage/drivers/btrfs-driver.md @@ -6,6 +6,15 @@ aliases: - /storage/storagedriver/btrfs-driver/ --- +> [!IMPORTANT] +> +> In most cases you should use the `overlay2` storage driver - it's not +> required to use the `btrfs` storage driver simply because your system uses +> Btrfs as its root filesystem. +> +> Btrfs driver has known issues. See [Moby issue #27653](https://github.com/moby/moby/issues/27653) +> for more information. + Btrfs is a copy-on-write filesystem that supports many advanced storage technologies, making it a good fit for Docker. Btrfs is included in the mainline Linux kernel. diff --git a/content/manuals/engine/storage/drivers/select-storage-driver.md b/content/manuals/engine/storage/drivers/select-storage-driver.md index fe441ce5fc83..18785775c510 100644 --- a/content/manuals/engine/storage/drivers/select-storage-driver.md +++ b/content/manuals/engine/storage/drivers/select-storage-driver.md @@ -108,13 +108,20 @@ With regard to Docker, the backing filesystem is the filesystem where `/var/lib/docker/` is located. Some storage drivers only work with specific backing filesystems. -| Storage driver | Supported backing filesystems | -| :--------------- | :---------------------------- | -| `overlay2` | `xfs` with ftype=1, `ext4` | -| `fuse-overlayfs` | any filesystem | -| `btrfs` | `btrfs` | -| `zfs` | `zfs` | -| `vfs` | any filesystem | +| Storage driver | Supported backing filesystems | +| :--------------- | :-----------------------------------------------------| +| `overlay2` | `xfs` with ftype=1, `ext4`, `btrfs`, (and more) | +| `fuse-overlayfs` | any filesystem | +| `btrfs` | `btrfs` | +| `zfs` | `zfs` | +| `vfs` | any filesystem | + +> [!NOTE] +> +> Most filesystems should work if they have the required features. +> Consult [OverlayFS](https://www.kernel.org/doc/html/latest/filesystems/overlayfs.html) +> for more information. + ## Other considerations From a96c7a7f2cd4ef513bd6c58b0feb1e6253b88618 Mon Sep 17 00:00:00 2001 From: Nicolas Beck Date: Wed, 2 Jul 2025 09:15:15 +0200 Subject: [PATCH 4/4] docs(ci): clarify builder and credential variables for CI setup (#22706) ## Description This PR updates the Docker Build Cloud CI documentation to clarify the use of builder and credential variables. **Key changes:** - Standardizes the use of `DOCKER_ACCOUNT`, `DOCKER_ACCESS_TOKEN`, and `CLOUD_BUILDER_NAME` in all CI/CD examples. - Updates template string syntax for builder endpoints (e.g., `${{ vars.DOCKER_ACCOUNT }}/${{ vars.CLOUD_BUILDER_NAME }}` in GitHub Actions). - Adds explicit call outs that the cloud builder has to be created first. - Improves instructions for naming and referencing cloud builders in both the dashboard and CLI steps. - Ensures all code comments and documentation are consistent and clear for users setting up Docker Build Cloud in CI. These changes make it easier for users to configure their CI/CD pipelines correctly and reduce confusion around builder and credential setup. ## Related issues or tickets https://docker.atlassian.net/browse/DCL-248 ## Reviews - [ ] Technical review - [ ] Editorial review - [ ] Product review --------- Co-authored-by: Allie Sadler <102604716+aevesdocker@users.noreply.github.com> --- content/manuals/build-cloud/ci.md | 101 ++++++++++++++------------- content/manuals/build-cloud/setup.md | 15 +++- 2 files changed, 63 insertions(+), 53 deletions(-) diff --git a/content/manuals/build-cloud/ci.md b/content/manuals/build-cloud/ci.md index f51931381830..6d18d8f37d0b 100644 --- a/content/manuals/build-cloud/ci.md +++ b/content/manuals/build-cloud/ci.md @@ -36,8 +36,8 @@ See [Loading build results](./usage/#loading-build-results) for details. To enable your CI/CD system to build and push images using Docker Build Cloud, provide both an access token and a username. The type of token and the username you use depend on your account type and permissions. -- If you are an organization administrator or have permission to create [organization access tokens (OAT)](../security/for-admins/access-tokens.md), use an OAT and set `DOCKER_USER` to your Docker Hub organization name. -- If you do not have permission to create OATs or are using a personal account, use a [personal access token (PAT)](/security/for-developers/access-tokens/) and set `DOCKER_USER` to your Docker Hub username. +- If you are an organization administrator or have permission to create [organization access tokens (OAT)](../security/for-admins/access-tokens.md), use an OAT and set `DOCKER_ACCOUNT` to your Docker Hub organization name. +- If you do not have permission to create OATs or are using a personal account, use a [personal access token (PAT)](/security/for-developers/access-tokens/) and set `DOCKER_ACCOUNT` to your Docker Hub username. ### Creating access tokens @@ -45,14 +45,13 @@ To enable your CI/CD system to build and push images using Docker Build Cloud, p If you are an organization administrator: -1. Create an [organization access token (OAT)](../security/for-admins/access-tokens.md): - - The token must have these permissions: - - **cloud-connect** scope - - **Read public repositories** permission - - **Repository access** with **Image push** permission for the target repository: - - Expand the **Repository** drop-down. - - Select **Add repository** and choose your target repository. - - Set the **Image push** permission for the repository. +- Create an [organization access token (OAT)](../security/for-admins/access-tokens.md). The token must have these permissions: + 1. **cloud-connect** scope + 2. **Read public repositories** permission + 3. **Repository access** with **Image push** permission for the target repository: + - Expand the **Repository** drop-down. + - Select **Add repository** and choose your target repository. + - Set the **Image push** permission for the repository. If you are not an organization administrator: @@ -60,18 +59,19 @@ If you are not an organization administrator: #### For personal accounts -1. Create a [personal access token (PAT)](/security/for-developers/access-tokens/): - - Create a new token with **Read & write** access. - - Note: Building with Docker Build Cloud only requires read access, but you need write access to push images to a Docker Hub repository. +- Create a [personal access token (PAT)](/security/for-developers/access-tokens/) with the following permissions: + 1. **Read & write** access. + - Note: Building with Docker Build Cloud only requires read access, but you need write access to push images to a Docker Hub repository. ## CI platform examples > [!NOTE] > -> In your CI/CD configuration, set the following variables: -> - `DOCKER_PAT` — your access token (PAT or OAT) -> - `DOCKER_USER` — your Docker Hub username (for PAT) or organization name (for OAT) +> In your CI/CD configuration, set the following variables/secrets: +> - `DOCKER_ACCESS_TOKEN` — your access token (PAT or OAT). Use a secret to store the token. +> - `DOCKER_ACCOUNT` — your Docker Hub organization name (for OAT) or username (for PAT) +> - `CLOUD_BUILDER_NAME` — the name of the cloud builder you created in the [Docker Build Cloud Dashboard](https://app.docker.com/build/) > > This ensures your builds authenticate correctly with Docker Build Cloud. @@ -92,20 +92,20 @@ jobs: - name: Login to Docker Hub uses: docker/login-action@v3 with: - username: ${{ vars.DOCKER_USER }} - password: ${{ secrets.DOCKER_PAT }} + username: ${{ vars.DOCKER_ACCOUNT }} + password: ${{ secrets.DOCKER_ACCESS_TOKEN }} - name: Set up Docker Buildx uses: docker/setup-buildx-action@v3 with: driver: cloud - endpoint: "/default" + endpoint: "${{ vars.DOCKER_ACCOUNT }}/${{ vars.CLOUD_BUILDER_NAME }}" # for example, "acme/default" install: true - name: Build and push uses: docker/build-push-action@v6 with: - tags: "" + tags: "" # for example, "acme/my-image:latest" # For pull requests, export results to the build cache. # Otherwise, push to a registry. outputs: ${{ github.event_name == 'pull_request' && 'type=cacheonly' || 'type=registry' }} @@ -120,7 +120,7 @@ default: - docker:24-dind before_script: - docker info - - echo "$DOCKER_PAT" | docker login --username "$DOCKER_USER" --password-stdin + - echo "$DOCKER_ACCESS_TOKEN" | docker login --username "$DOCKER_ACCOUNT" --password-stdin - | apk add curl jq ARCH=${CI_RUNNER_EXECUTABLE_ARCH#*/} @@ -128,11 +128,12 @@ default: mkdir -vp ~/.docker/cli-plugins/ curl --silent -L --output ~/.docker/cli-plugins/docker-buildx $BUILDX_URL chmod a+x ~/.docker/cli-plugins/docker-buildx - - docker buildx create --use --driver cloud ${DOCKER_ORG}/default + - docker buildx create --use --driver cloud ${DOCKER_ACCOUNT}/${CLOUD_BUILDER_NAME} variables: IMAGE_NAME: - DOCKER_ORG: + DOCKER_ACCOUNT: # your Docker Hub organization name (or username when using a personal account) + CLOUD_BUILDER_NAME: # the name of the cloud builder you created in the [Docker Build Cloud Dashboard](https://app.docker.com/build/) # Build multi-platform image and push to a registry build_push: @@ -176,8 +177,8 @@ jobs: curl --silent -L --output ~/.docker/cli-plugins/docker-buildx $BUILDX_URL chmod a+x ~/.docker/cli-plugins/docker-buildx - - run: echo "$DOCKER_PAT" | docker login --username $DOCKER_USER --password-stdin - - run: docker buildx create --use --driver cloud "/default" + - run: echo "$DOCKER_ACCESS_TOKEN" | docker login --username $DOCKER_ --password-stdin + - run: docker buildx create --use --driver cloud "${DOCKER_ACCOUNT}/${CLOUD_BUILDER_NAME}" - run: | docker buildx build \ @@ -199,8 +200,8 @@ jobs: curl --silent -L --output ~/.docker/cli-plugins/docker-buildx $BUILDX_URL chmod a+x ~/.docker/cli-plugins/docker-buildx - - run: echo "$DOCKER_PAT" | docker login --username $DOCKER_USER --password-stdin - - run: docker buildx create --use --driver cloud "/default" + - run: echo "$DOCKER_ACCESS_TOKEN" | docker login --username $DOCKER_ --password-stdin + - run: docker buildx create --use --driver cloud "${DOCKER_ACCOUNT}/${CLOUD_BUILDER_NAME}" - run: | docker buildx build \ @@ -231,7 +232,7 @@ Add the following `environment` hook agent's hook directory: set -euo pipefail if [[ "$BUILDKITE_PIPELINE_NAME" == "build-push-docker" ]]; then - export DOCKER_PAT="" + export DOCKER_ACCESS_TOKEN="" fi ``` @@ -239,7 +240,8 @@ Create a `pipeline.yml` that uses the `docker-login` plugin: ```yaml env: - DOCKER_ORG: + DOCKER_ACCOUNT: # your Docker Hub organization name (or username when using a personal account) + CLOUD_BUILDER_NAME: # the name of the cloud builder you created in the [Docker Build Cloud Dashboard](https://app.docker.com/build/) IMAGE_NAME: steps: @@ -247,8 +249,8 @@ steps: key: build-push plugins: - docker-login#v2.1.0: - username: - password-env: DOCKER_PAT # the variable name in the environment hook + username: DOCKER_ACCOUNT + password-env: DOCKER_ACCESS_TOKEN # the variable name in the environment hook ``` Create the `build.sh` script: @@ -277,7 +279,7 @@ curl --silent -L --output $DOCKER_DIR/cli-plugins/docker-buildx $BUILDX_URL chmod a+x ~/.docker/cli-plugins/docker-buildx # Connect to your builder and set it as the default builder -docker buildx create --use --driver cloud "$DOCKER_ORG/default" +docker buildx create --use --driver cloud "${DOCKER_ACCOUNT}/${CLOUD_BUILDER_NAME}" # Cache-only image build docker buildx build \ @@ -302,9 +304,9 @@ pipeline { environment { ARCH = 'amd64' - DOCKER_PAT = credentials('docker-personal-access-token') - DOCKER_USER = credentials('docker-username') - DOCKER_ORG = '' + DOCKER_ACCESS_TOKEN = credentials('docker-access-token') + DOCKER_ACCOUNT = credentials('docker-account') + CLOUD_BUILDER_NAME = '' IMAGE_NAME = '' } @@ -317,8 +319,8 @@ pipeline { sh 'mkdir -vp ~/.docker/cli-plugins/' sh 'curl --silent -L --output ~/.docker/cli-plugins/docker-buildx $BUILDX_URL' sh 'chmod a+x ~/.docker/cli-plugins/docker-buildx' - sh 'echo "$DOCKER_PAT" | docker login --username $DOCKER_USER --password-stdin' - sh 'docker buildx create --use --driver cloud "$DOCKER_ORG/default"' + sh 'echo "$DOCKER_ACCESS_TOKEN" | docker login --username $DOCKER_ACCOUNT --password-stdin' + sh 'docker buildx create --use --driver cloud "${DOCKER_ACCOUNT}/${CLOUD_BUILDER_NAME}"' // Cache-only build sh 'docker buildx build --platform linux/amd64,linux/arm64 --tag "$IMAGE_NAME" --output type=cacheonly .' // Build and push a multi-platform image @@ -340,10 +342,10 @@ services: env: global: - - IMAGE_NAME=username/repo + - IMAGE_NAME= # for example, "acme/my-image:latest" before_install: | - echo "$DOCKER_PAT" | docker login --username "$DOCKER_USER" --password-stdin + echo "$DOCKER_ACCESS_TOKEN" | docker login --username "$DOCKER_ACCOUNT" --password-stdin install: | set -e @@ -351,7 +353,7 @@ install: | mkdir -vp ~/.docker/cli-plugins/ curl --silent -L --output ~/.docker/cli-plugins/docker-buildx $BUILDX_URL chmod a+x ~/.docker/cli-plugins/docker-buildx - docker buildx create --use --driver cloud "/default" + docker buildx create --use --driver cloud "${DOCKER_ACCOUNT}/${CLOUD_BUILDER_NAME}" script: | docker buildx build \ @@ -363,9 +365,8 @@ script: | ### BitBucket Pipelines ```yaml -# Prerequisites: $DOCKER_USER, $DOCKER_PAT setup as deployment variables +# Prerequisites: $DOCKER_ACCOUNT, $CLOUD_BUILDER_NAME, $DOCKER_ACCESS_TOKEN setup as deployment variables # This pipeline assumes $BITBUCKET_REPO_SLUG as the image name -# Replace in the `docker buildx create` command with your Docker org image: atlassian/default-image:3 @@ -379,8 +380,8 @@ pipelines: - BUILDX_URL=$(curl -s https://raw.githubusercontent.com/docker/actions-toolkit/main/.github/buildx-lab-releases.json | jq -r ".latest.assets[] | select(endswith(\"linux-$ARCH\"))") - curl --silent -L --output ~/.docker/cli-plugins/docker-buildx $BUILDX_URL - chmod a+x ~/.docker/cli-plugins/docker-buildx - - echo "$DOCKER_PAT" | docker login --username $DOCKER_USER --password-stdin - - docker buildx create --use --driver cloud "/default" + - echo "$DOCKER_ACCESS_TOKEN" | docker login --username $DOCKER_ACCOUNT --password-stdin + - docker buildx create --use --driver cloud "${DOCKER_ACCOUNT}/${CLOUD_BUILDER_NAME}" - IMAGE_NAME=$BITBUCKET_REPO_SLUG - docker buildx build --platform linux/amd64,linux/arm64 @@ -404,11 +405,11 @@ mkdir -vp ~/.docker/cli-plugins/ curl --silent -L --output ~/.docker/cli-plugins/docker-buildx $BUILDX_URL chmod a+x ~/.docker/cli-plugins/docker-buildx -# Login to Docker Hub. For security reasons $DOCKER_PAT should be a Personal Access Token. See https://docs.docker.com/build-cloud/ci/#creating-access-tokens -echo "$DOCKER_PAT" | docker login --username $DOCKER_USER --password-stdin +# Login to Docker Hub with an access token. See https://docs.docker.com/build-cloud/ci/#creating-access-tokens +echo "$DOCKER_ACCESS_TOKEN" | docker login --username $DOCKER_ACCOUNT --password-stdin # Connect to your builder and set it as the default builder -docker buildx create --use --driver cloud "/default" +docker buildx create --use --driver cloud "${DOCKER_ACCOUNT}/${CLOUD_BUILDER_NAME}" # Cache-only image build docker buildx build \ @@ -449,11 +450,11 @@ curl --silent -L --output ~/.docker/cli-plugins/docker-compose $COMPOSE_URL chmod a+x ~/.docker/cli-plugins/docker-buildx chmod a+x ~/.docker/cli-plugins/docker-compose -# Login to Docker Hub. For security reasons $DOCKER_PAT should be a Personal Access Token. See https://docs.docker.com/build-cloud/ci/#creating-access-tokens -echo "$DOCKER_PAT" | docker login --username $DOCKER_USER --password-stdin +# Login to Docker Hub with an access token. See https://docs.docker.com/build-cloud/ci/#creating-access-tokens +echo "$DOCKER_ACCESS_TOKEN" | docker login --username $DOCKER_ACCOUNT --password-stdin # Connect to your builder and set it as the default builder -docker buildx create --use --driver cloud "/default" +docker buildx create --use --driver cloud "${DOCKER_ACCOUNT}/${CLOUD_BUILDER_NAME}" # Build the image build docker compose build diff --git a/content/manuals/build-cloud/setup.md b/content/manuals/build-cloud/setup.md index 57c2e366314d..56f78180c42d 100644 --- a/content/manuals/build-cloud/setup.md +++ b/content/manuals/build-cloud/setup.md @@ -16,7 +16,8 @@ environment. To get started with Docker Build Cloud, you need to: - Download and install Docker Desktop version 4.26.0 or later. -- Sign up for a Docker Build Cloud subscription in the [Docker Build Cloud Dashboard](https://app.docker.com/build/). +- Create a cloud builder on the [Docker Build Cloud Dashboard](https://app.docker.com/build/). + - When you create the builder, choose a name for it (for example, `default`). You will use this name as `BUILDER_NAME` in the CLI steps below. ### Use Docker Build Cloud without Docker Desktop @@ -50,9 +51,17 @@ command, or using the Docker Desktop settings GUI. $ docker buildx create --driver cloud / ``` - Replace `ORG` with the Docker Hub namespace of your Docker organization. + Replace `` with the Docker Hub namespace of your Docker organization (or your username if you are using a personal account), and `` with the name you chose when creating the builder in the dashboard. + + This creates a local instance of the cloud builder named `cloud-ORG-BUILDER_NAME`. + + > [!NOTE] + > + > If your organization is `acme` and you named your builder `default`, use: + > ```console + > $ docker buildx create --driver cloud acme/default + > ``` -This creates a builder named `cloud-ORG-BUILDER_NAME`. {{< /tab >}} {{< tab name="Docker Desktop" >}}