offload: ga updates

content/manuals/desktop/setup/vm-vdi.md

@@ -26,7 +26,7 @@ hosted cloud environment, enabling a seamless hybrid experience.
 
 Docker Offload is useful in virtual desktop environments where nested
 virtualization isn't supported. In these environments, Docker Desktop defaults
-to using Docker Offload to ensure you can still build and run containers without
+to using Docker Offload to ensure you can still run containers without
 relying on local virtualization.
 
 Docker Offload decouples the Docker Desktop client from the Docker Engine,

content/manuals/offload/_index.md

@@ -1,14 +1,11 @@
 ---
 title: Docker Offload
 weight: 15
-description: Find documentation on Docker Offload to help you build and run your container images faster, both locally and in CI
-keywords: build, cloud, cloud build, remote builder
+description: Find documentation on Docker Offload to help you run your container images faster
+keywords: cloud, cloud run, offload
 params:
   sidebar:
     group: Products
-    badge:
-      color: blue
-      text: Beta
 
 grid:
 
@@ -22,21 +19,16 @@ grid:
   icon: info
   link: /offload/about/
 
-- title: Configure
-  description: Set up and customize your cloud build environments.
+- title: Configuration
+  description: Configure settings for Docker Offload.
   icon: tune
   link: /offload/configuration/
 
-- title: Usage
+- title: Usage & billing
   description: Learn about Docker Offload usage and how to monitor your cloud resources.
   icon: monitor_heart
   link: /offload/usage/
 
-- title: Optimize
-  description: Improve performance, caching, and cost efficiency in Docker Offload.
-  icon: speed
-  link: /offload/optimize/
-
 - title: Troubleshoot
   description: Learn how to troubleshoot issues with Docker Offload.
   icon: bug_report
@@ -53,10 +45,10 @@ aliases:
 
 {{< summary-bar feature_name="Docker Offload" >}}
 
-Docker Offload is a fully managed service that lets you offload building and
-running containers to the cloud using the Docker tools you already know. It
-provides cloud infrastructure for fast, consistent builds and compute-heavy
-workloads like running LLMs or machine learning pipelines.
+Docker Offload is a fully managed service that lets you offload running
+containers to the cloud using the Docker tools you already know. It provides
+cloud infrastructure for compute-heavy workloads like running LLMs or machine
+learning pipelines.
 
 In the following topics, learn about Docker Offload, how to set it up, use it
 for your workflows, and troubleshoot common issues.

content/manuals/offload/about.md

@@ -3,15 +3,13 @@ title: About Docker Offload
 linktitle: About
 weight: 15
 description: Learn about Docker Offload, its features, and how it works.
-keywords: cloud, build, remote builder
+keywords: cloud, run, offload
 ---
 
-Docker Offload is a fully managed service for building and running containers in
-the cloud using the Docker tools you already know, including Docker Desktop, the
-Docker CLI, and Docker Compose. It extends your local development workflow into a
-scalable, cloud-powered environment, so you can offload compute-heavy tasks,
-accelerate builds, and securely manage container workloads across the software
-lifecycle.
+Docker Offload is a fully managed service for running containers in the cloud
+using the Docker tools you already know, including Docker Desktop, the Docker
+CLI, and Docker Compose. It extends your local development workflow into a
+scalable, cloud-powered environment, so you can offload compute-heavy tasks.
 
 Docker Offload also supports GPU-accelerated instances, allowing you to
 containerize and run compute-intensive workloads such as Docker Model Runner and
@@ -22,13 +20,10 @@ other machine learning or data processing tasks that benefit from GPU.
 Docker Offload includes the following capabilities to support modern container
 workflows:
 
-- Cloud-based builds: Execute builds on remote, fully managed BuildKit instances
 - GPU acceleration: Use NVIDIA L4 GPU-backed environments for machine learning,
   media processing, and other compute-intensive workloads.
 - Ephemeral cloud runners: Automatically provision and tear down cloud
   environments for each container session.
-- Shared build cache: Speed up build times across machines and teammates with a
-  smart, shared cache layer.
 - Hybrid workflows: Seamlessly transition between local and remote execution
   using Docker Desktop or CLI.
 - Secure communication: Use encrypted tunnels between Docker Desktop and cloud
@@ -43,10 +38,9 @@ workflows:
 Docker Offload is designed to support modern development teams working across
 local and cloud environments. It helps you:
 
-- Offload heavy builds and runs to fast, scalable infrastructure
 - Accelerate feedback loops in development and testing
 - Run containers that require more resources than your local setup can provide
-- Build and run AI apps with instant access to GPU-powered environments
+- Run AI apps with instant access to GPU-powered environments
 - Use Docker Compose to manage complex, multi-service apps that need cloud
   resources
 - Maintain consistent environments without managing custom infrastructure
@@ -58,31 +52,8 @@ local tools.
 
 ## How Docker Offload works
 
-Docker Offload replaces the need to build or run containers locally by connecting
-Docker Desktop to secure, dedicated cloud resources.
-
-### Building with Docker Offload
-
-When you use Docker Offload for builds, the `docker buildx build` command sends
-the build request to a remote BuildKit instance in the cloud, instead of
-executing it locally. Your workflow stays the same, only the execution
-environment changes.
-
-The build runs on infrastructure provisioned and managed by Docker:
-
-- Each cloud builder is an isolated Amazon EC2 instance with its own EBS volume
-- Remote builders use a shared cache to speed up builds across machines and
-  teammates
-- Build results are encrypted in transit and sent to your specified destination
-  (such as a registry or local image store)
-
-Docker Offload manages the lifecycle of builders automatically. There's no need to
-provision or maintain infrastructure.
-
-> [!NOTE]
->
-> Docker Offload builders are currently hosted in the United States East region. Users in
-> other regions may experience increased latency.
+Docker Offload replaces the need to run containers locally by connecting Docker
+Desktop to secure, dedicated cloud resources.
 
 ### Running containers with Docker Offload
 

content/manuals/offload/configuration.md

@@ -1,104 +1,47 @@
 ---
 title: Configure Docker Offload
-linktitle: Configure
+linktitle: Configuration
 weight: 20
-description: Learn how to configure build settings for Docker Offload.
-keywords: cloud, configuration, settings, cloud builder, GPU, disk allocation, private resources, firewall
+description: Learn how to configure settings for Docker Offload.
+keywords: cloud, configuration, settings, GPU
 ---
 
-To use Docker Offload, you must start it in Docker Desktop. For more details,
-see the [Docker Offload quickstart](/offload/quickstart/).
+The following Docker Offload settings can be configured:
 
-Settings for the cloud builders in Docker Offload can be further configured, in
-addition to settings for an entire organization, through **Offload settings** in
-the Docker Offload dashboard.
+   - [Run settings](#run-settings): Configure tenancy and data settings for
+     Docker Offload in your organization.
+   - [Offload access](#offload-access): Configure Offload availability for
+     members of your organization.
 
-> [!NOTE]
->
-> To view usage and configure billing for Docker Offload, see [Docker Offload
-> usage and billing](/offload/usage/).
+## Run settings
 
-## Offload settings
+The **Run settings** page in Docker Home lets you configure tenancy and data
+settings for Docker Offload in your organization.
 
-The **Offload settings** page in Docker Home lets you configure disk
-allocation, private resource access, and firewall settings for your cloud
-builders in your organization.
-
-To view the **Offload settings** page:
+To view the **Run settings** page:
 
 1. Go to [Docker Home](https://app.docker.com/).
 2. Select the account for which you want to manage Docker Offload.
-3. Select **Offload** > **Offload settings**.
-
-The following sections describe the available settings.
-
-### 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 storage
-available for active builds.
-
-Adjust the **Disk allocation** slider to specify the percentage of storage used
-for build caching.
-
-Any changes take effect immediately.
-
-> [!TIP]
->
-> If you build very large images, consider allocating less storage for caching.
-
-### Build cache space
-
-Your subscription includes the following Build cache space:
+3. Select **Offload** > **Run settings**.
 
-| Subscription | Build cache space |
-|--------------|-------------------|
-| Personal     | N/A               |
-| Pro          | 50GB              |
-| Team         | 100GB             |
-| Business     | 200GB             |
+## Offload access
 
-To get more Build cache space, [upgrade your subscription](/manuals/subscription/change.md).
+The **Offload access** page in Docker Home lets you configure Offload
+availability for members of your organization. By default, Offload is disabled
+for all members of an organization. An organization owner must enable Offload
+access for the organization. To configure Docker Offload access as an
+organization owner:
 
-### Private resource access
-
-Private resource access lets cloud builders pull images and packages from
-private resources. This feature is useful when builds rely on self-hosted
-artifact repositories or private OCI registries.
-
-For example, if your organization hosts a private [PyPI](https://pypi.org/)
-repository on a private network, Docker Build Cloud would not be able to access
-it by default, since the cloud builder is not connected to your private network.
-
-To enable your cloud builders to access your private resources, enter the host
-name and port of your private resource and then select **Add**.
-
-#### Authentication
-
-If your internal artifacts require authentication, make sure that you
-authenticate with the repository either before or during the build. For internal
-package repositories for npm or PyPI, use [build
-secrets](/manuals/build/building/secrets.md) to authenticate during the build.
-For internal OCI registries, use `docker login` to authenticate before building.
-
-Note that if you use a private registry that requires authentication, you will
-need to authenticate with `docker login` twice before building. This is because
-the cloud builder needs to authenticate with Docker to use the cloud builder,
-and then again to authenticate with the private registry.
-
-```console
-$ echo $DOCKER_PAT | docker login docker.io -u <username> --password-stdin
-$ echo $REGISTRY_PASSWORD | docker login registry.example.com -u <username> --password-stdin
-$ docker build --builder <cloud-builder> --tag registry.example.com/<image> --push .
-```
-
-### Firewall
+1. Sign in to [Docker Home](https://app.docker.com/) as an organization owner.
+2. Select the account for which you want to manage Docker Offload.
+3. Select **Admin Console** > **Offload access**.
+4. Select whether to enable or disable Offload access for all members of the
+   organization as well as allow or disallow GPU access.
 
-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.
+   > [!NOTE]
+   >
+   > If you enable Offload access, all members of the organization can use
+   > Docker Offload. Members of the organization can choose to start or stop
+   > Offload in Docker Desktop.
 
-1. Select **Enable firewall: Restrict cloud builder egress to specific public IP address**.
-2. Enter the IP address you want to allow.
-3. Select **Add** to apply the restriction.