diff --git a/content/manuals/admin/organization/manage-products.md b/content/manuals/admin/organization/manage-products.md index 40125f86b2af..60274fef17f0 100644 --- a/content/manuals/admin/organization/manage-products.md +++ b/content/manuals/admin/organization/manage-products.md @@ -16,6 +16,7 @@ product, including how to set up and configure them, see the following manuals: - [Docker Build Cloud](../../build-cloud/_index.md) - [Docker Scout](../../scout/_index.md) - [Testcontainers Cloud](https://testcontainers.com/cloud/docs/#getting-started) +- [Docker Offload](../../offload/_index.md) ## Manage product access for your organization @@ -98,6 +99,18 @@ To manage access to Testcontainers Cloud: select **Account**. 1. Select **Settings**, then **Lock access to Testcontainers Cloud**. +{{< /tab >}} +{{< tab name="Docker Offload" >}} + +### Manage Docker Offload access + +Docker Offload access is set inside the Docker Desktop Dashboard. To manage Docker Desktop settings for your +organization, you can use Setttings Management. + +Follow the instructions at [Configure Settings Management with the Admin +Console](/enterprise/security/hardened-desktop/settings-management/configure-admin-console/) and set the **Enable Docker +Offload** setting to your desired value. + {{< /tab >}} {{< /tabs >}} @@ -110,6 +123,7 @@ To view usage for Docker products: - Docker Build Cloud: View the **Build minutes** page in [Docker Build Cloud](http://app.docker.com/build). - Docker Scout: View the [**Repository settings** page](https://scout.docker.com/settings/repos) in Docker Scout. - Testcontainers Cloud: View the [**Billing** page](https://app.testcontainers.cloud/dashboard/billing) in Testcontainers Cloud. +- Docker Offload: View the **Docker Offload** > **Usage summary** page in [Docker Billing](https://app.docker.com/billing). If your usage or seat count exceeds your subscription amount, you can [scale your subscription](../../subscription/scale.md) to meet your needs. diff --git a/content/manuals/desktop/setup/vm-vdi.md b/content/manuals/desktop/setup/vm-vdi.md index e99c02c5e4e3..33e5f2e73462 100644 --- a/content/manuals/desktop/setup/vm-vdi.md +++ b/content/manuals/desktop/setup/vm-vdi.md @@ -24,10 +24,9 @@ depending on whether nested virtualization is supported: Docker Offload lets you offload container workloads to a high-performance, fully 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 -relying on local virtualization. +Docker Offload is useful in virtual desktop environments where nested virtualization isn't supported. In these +environments, Docker Desktop can use Docker Offload to ensure you can still build and run containers without relying on +local virtualization. Docker Offload decouples the Docker Desktop client from the Docker Engine, allowing the Docker CLI and Docker Desktop Dashboard to interact with diff --git a/content/manuals/offload/_index.md b/content/manuals/offload/_index.md index cea387365598..a7f0172b3abf 100644 --- a/content/manuals/offload/_index.md +++ b/content/manuals/offload/_index.md @@ -2,13 +2,10 @@ 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 +keywords: cloud, offload, vdi params: sidebar: group: Products - badge: - color: blue - text: Beta grid: @@ -53,12 +50,11 @@ 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 extends [Docker Desktop](/desktop/) to build and run containers in the +cloud. For developers working in virtual desktop infrastructure (VDI) or on systems that don't support +nested virtualization, it enables full Docker functionality without the need for local compute resources. -In the following topics, learn about Docker Offload, how to set it up, use it -for your workflows, and troubleshoot common issues. +In the following topics, learn about Docker Offload, how to set it up, use it for your workflows, and troubleshoot +common issues. {{< grid >}} \ No newline at end of file diff --git a/content/manuals/offload/about.md b/content/manuals/offload/about.md index 8f6c9a804a14..f0f56807bd7e 100644 --- a/content/manuals/offload/about.md +++ b/content/manuals/offload/about.md @@ -3,124 +3,54 @@ 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, vdi, 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 also supports GPU-accelerated instances, allowing you to -containerize and run compute-intensive workloads such as Docker Model Runner and -other machine learning or data processing tasks that benefit from GPU. +Docker Offload is a fully managed service designed for developers working in virtual +desktop infrastructure (VDI) environments or on systems that don't support nested +virtualization. It lets you use Docker Desktop to build and run containers in +the cloud, providing full Docker functionality without the need for local compute +resources or nested virtualization support. ## Key features -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 - environments with support for secure secrets and image pulling. -- Port forwarding and bind mounts: Retain a local development experience even - when running containers in the cloud. -- VDI-friendly: Use Docker Offload in virtual desktop environments or systems that - don't support nested virtualization. - -## Why use Docker Offload? - -Docker Offload is designed to support modern development teams working across -local and cloud environments. It helps you: +Docker Offload includes the following capabilities to support modern container workflows: -- 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 -- Use Docker Compose to manage complex, multi-service apps that need cloud - resources -- Maintain consistent environments without managing custom infrastructure -- Develop efficiently in restricted or low-powered environments like VDIs - -Docker Offload is ideal for high-velocity development workflows -that need the flexibility of the cloud without sacrificing the simplicity of -local tools. +- VDI-friendly: [Run Docker Desktop for Windows in a VM or VDI environment](/desktop/setup/vm-vdi/) without nested + virtualization. +- Ephemeral cloud runners: Automatically provision and tear down cloud environments for each container session. +- Secure communication: Use encrypted tunnels between Docker Desktop and the cloud environment. +- Port forwarding and bind mounts: Retain a local development experience even when running containers in the cloud. ## 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. +Docker Offload replaces the need to build or run containers locally by connecting Docker Desktop to secure, dedicated +cloud resources. -The build runs on infrastructure provisioned and managed by Docker: +When you use Docker Offload to build images or run containers, Docker Desktop creates a secure SSH tunnel to a Docker +daemon running in the cloud. Your images are built and containers are started and managed entirely in that remote +environment. -- 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. - -### Running containers with Docker Offload - -When you use Docker Offload to run containers, a Docker Desktop creates a secure -SSH tunnel to a Docker daemon running in the cloud. Your containers are started -and managed entirely in that remote environment. - -Here's what happens: +Here's what happens when you run containers: 1. Docker Desktop connects to the cloud and triggers container creation. -2. Docker Offload pulls the required images and starts containers in the cloud. +2. Docker Offload pulls or builds the required images and starts containers in the cloud. 3. The connection stays open while the containers run. -4. When the containers stop running, the environment shuts down and is cleaned - up automatically. - -This setup avoids the overhead of running containers locally and enables fast, -reliable containers even on low-powered machines, including machines that do not -support nested virtualization. This makes Docker Offload ideal for developers -using environments such as virtual desktops, cloud-hosted development machines, -or older hardware. +4. When the containers stop running, the environment shuts down and is cleaned up automatically. -Docker Offload also supports GPU-accelerated workloads. Containers that require -GPU access can run on cloud instances provisioned with NVIDIA L4 GPUs for -efficient AI inferencing, media processing, and general-purpose GPU -acceleration. This enables compute-heavy workflows such as model evaluation, -image processing, and hardware-accelerated CI tests to run seamlessly in the -cloud. +This setup avoids the overhead of running containers locally and enables fast, reliable containers even on low-powered +machines, including machines that do not support nested virtualization. This makes Docker Offload ideal for developers +using environments such as virtual desktops, cloud-hosted development machines, or older hardware. -Despite running remotely, features like bind mounts and port forwarding continue -to work seamlessly, providing a local-like experience from within Docker Desktop -and the CLI. +Despite running remotely, features like bind mounts and port forwarding continue to work seamlessly, providing a +local-like experience from within Docker Desktop and the CLI. -Docker Offload provisions an ephemeral cloud environment for each session. The -environment remains active while you are interacting with Docker Desktop or -actively using containers. If no activity is detected for about 5 minutes, the -session shuts down automatically. This includes any containers, images, or -volumes in that environment, which are deleted when the session ends. +Docker Offload provisions an ephemeral cloud environment for each session. The environment remains active while you are +interacting with Docker Desktop or actively using containers. If no activity is detected for about 5 minutes, the +session shuts down automatically. This includes any containers, images, or volumes in that environment, which are +deleted when the session ends. ## What's next -Get hands-on with Docker Offload by following the [Docker Offload quickstart](/offload/quickstart/). \ No newline at end of file +[Contact sales](https://www.docker.com/pricing/contact-sales/) to subscribe to Docker Offload, and [get +started](/offload/quickstart) using it. \ No newline at end of file diff --git a/content/manuals/offload/configuration.md b/content/manuals/offload/configuration.md index 0af088a11bfd..3c907847a2e8 100644 --- a/content/manuals/offload/configuration.md +++ b/content/manuals/offload/configuration.md @@ -3,102 +3,33 @@ title: Configure Docker Offload linktitle: Configure weight: 20 description: Learn how to configure build settings for Docker Offload. -keywords: cloud, configuration, settings, cloud builder, GPU, disk allocation, private resources, firewall +keywords: cloud, configuration, settings, offload, idle, timeout --- -To use Docker Offload, you must start it in Docker Desktop. For more details, -see the [Docker Offload quickstart](/offload/quickstart/). - -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. +{{< summary-bar feature_name="Docker Offload" >}} > [!NOTE] > -> To view usage and configure billing for Docker Offload, see [Docker Offload -> usage and billing](/offload/usage/). - -## Offload settings - -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: - -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] +> All free trial usage granted for the Docker Offload Beta expire after 90 days from the time they are granted. To +> continue using Docker Offload Beta after your usage expires, you can enable on-demand usage at [Docker Home +> Billing](https://app.docker.com/billing). > -> If you build very large images, consider allocating less storage for caching. - -### Build cache space - -Your subscription includes the following Build cache space: - -| Subscription | Build cache space | -|--------------|-------------------| -| Personal | N/A | -| Pro | 50GB | -| Team | 100GB | -| Business | 200GB | - -To get more Build cache space, [upgrade your subscription](/manuals/subscription/change.md). - -### 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. +> Implementation and settings for the Docker Offload Beta may differ from the General Availability (GA) release. The +> following topic describes the user experience for the GA release. -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. +For organization owners, you can manage Docker Offload settings for all users in your organization. For more details, +see [Manage Docker products](../admin/organization/manage-products.md). To view usage and configure billing for Docker +Offload, see [Docker Offload usage and billing](/offload/usage/). -```console -$ echo $DOCKER_PAT | docker login docker.io -u --password-stdin -$ echo $REGISTRY_PASSWORD | docker login registry.example.com -u --password-stdin -$ docker build --builder --tag registry.example.com/ --push . -``` -### Firewall +For developers, you can manage Docker Offload settings in Docker Desktop. To manage settings: -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. Open the Docker Desktop Dashboard and sign in. +2. Select the settings icon in the Docker Desktop Dashboard header. +3. In **Settings**, select **Docker Offload**. -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. + Here you can: + - Enable or disable Docker Offload. + - Select the idle timeout. This is the duration of inactivity after which Docker Offload enters idle mode and no + longer incurs usage. The default is 5 minutes. \ No newline at end of file diff --git a/content/manuals/offload/feedback.md b/content/manuals/offload/feedback.md index afa5f36b296d..aa990ee8304f 100644 --- a/content/manuals/offload/feedback.md +++ b/content/manuals/offload/feedback.md @@ -5,7 +5,6 @@ title: Give feedback weight: 900 --- - There are several ways you can provide feedback on Docker Offload. ## Quick survey diff --git a/content/manuals/offload/images/offload-toggle.png b/content/manuals/offload/images/offload-toggle.png new file mode 100644 index 000000000000..4342a5003ad2 Binary files /dev/null and b/content/manuals/offload/images/offload-toggle.png differ diff --git a/content/manuals/offload/optimize.md b/content/manuals/offload/optimize.md index 259f1db6db44..d466f96da712 100644 --- a/content/manuals/offload/optimize.md +++ b/content/manuals/offload/optimize.md @@ -11,15 +11,10 @@ build. This means that files must be transferred from your local system to the cloud over the network. Transferring files over the network introduces higher latency and lower -bandwidth compared to local transfers. To reduce these effects, Docker Offload -includes several performance optimizations: +bandwidth compared to local transfers. -- It uses attached storage volumes for build cache, which makes reading and writing cache fast. -- When pulling build results back to your local machine, it only transfers layers that changed since the previous build. - -Even with these optimizations, large projects or slower network connections can -lead to longer transfer times. Here are several ways to optimize your build -setup for Docker Offload: +Large projects or slower network connections can lead to longer transfer times. Here are several ways to optimize your +build setup for Docker Offload: - [Use `.dockerignore` files](#dockerignore-files) - [Choose slim base images](#slim-base-images) diff --git a/content/manuals/offload/quickstart.md b/content/manuals/offload/quickstart.md index 2a6ce97f7bfe..c7a5bd9a0362 100644 --- a/content/manuals/offload/quickstart.md +++ b/content/manuals/offload/quickstart.md @@ -8,25 +8,32 @@ keywords: cloud, quickstart, cloud mode, Docker Desktop, GPU support, cloud buil {{< summary-bar feature_name="Docker Offload" >}} -This quickstart helps you get started with Docker Offload. Docker Offload lets -you build and run container images faster by offloading resource-intensive tasks -to the cloud. It provides a cloud-based environment that mirrors your local -Docker Desktop experience. +This quickstart covers the steps developers need to get started with [Docker Offload](./about.md). If you're an +organization owner, see [Manage Docker products](../admin/organization/manage-products.md) to learn how to manage access +for the developers in your organization. -## Step 1: Sign up and subscribe to Docker Offload for access +## Prerequisites -To access Docker Offload, you must [sign -up](https://www.docker.com/products/docker-offload/) and subscribe. +- You must have [Docker Desktop](/desktop/) installed. Docker Offload works with Docker Desktop version 4.50.0 or later. -## Step 2: Start Docker Offload +## Step 1: Verify access to Docker Offload + +To access Docker Offload, you must be part of an organization that has subscribed to Docker Offload. As a developer, you +can verify this by checking if the Docker Offload toggle appears in the Docker Desktop Dashboard header. + +1. Start Docker Desktop and sign in. +2. In the Docker Desktop Dashboard header, look for the Docker Offload toggle. -> [!NOTE] -> -> After subscribing to Docker Offload, the first time you start Docker Desktop -> and sign in, you may be prompted to start Docker Offload. If you start Docker -> Offload via this prompt, you can skip the following steps. Note that you can -> use the following steps to start Docker Offload at any time. +![Offload toggle](./images/offload-toggle.png) + +If you see the Docker Offload toggle, you have access to Docker Offload and can proceed to the next step. If you don't +see the Docker Offload toggle, contact your administrator to verify that your organization has subscribed to Docker +Offload. + +## Step 2: Start Docker Offload +You can start Docker Offload from the CLI or in the header of the Docker Desktop Dashboard. The following steps describe +how to start Docker Offload using the CLI. 1. Start Docker Desktop and sign in. 2. Open a terminal and run the following command to start Docker Offload: @@ -35,23 +42,10 @@ up](https://www.docker.com/products/docker-offload/) and subscribe. $ docker offload start ``` -3. When prompted, select your account to use for Docker Offload. This account - will consume Docker Offload usage. - -4. When prompted, select whether to enable GPU support. If you choose to enable - GPU support, Docker Offload will run in an instance with an NVIDIA L4 GPU, - which is useful for machine learning or compute-intensive workloads. - - > [!NOTE] - > - > Enabling GPU support consumes more budget. For more details, see [Docker - > Offload usage](/offload/usage/). - -When Docker Offload is started, you'll see a cloud icon ({{< inline-image -src="./images/cloud-mode.png" alt="Offload mode icon" >}}) -in the Docker Desktop Dashboard header, and the Docker Desktop Dashboard appears purple. -You can run `docker offload status` in a terminal to check the status of -Docker Offload. +When Docker Offload is started, you'll see a cloud icon +({{< inline-image src="./images/cloud-mode.png" alt="Offload mode icon" >}}) +in the Docker Desktop Dashboard header, and the Docker Desktop Dashboard appears purple. You can run +`docker offload status` in a terminal to check the status of Docker Offload. ## Step 3: Run a container with Docker Offload @@ -65,18 +59,16 @@ To verify that Docker Offload is working, run a container: $ docker run --rm hello-world ``` -If you enabled GPU support, you can also run a GPU-enabled container: +If Docker Offload is working, you'll see `Hello from Docker!` in the terminal output. -```console -$ docker run --rm --gpus all hello-world -``` +## Step 4: Monitor your Offload usage -If Docker Offload is working, you'll see `Hello from Docker!` in the terminal output. +You can see your current Offload session duration in the Docker Desktop Dashboard footer. To view detailed information, +in the Docker Desktop Dashboard left navigation select **Offload** > **Insights** when Docker Offload is running. -## Step 4: Stop Docker Offload +## Step 5: Stop Docker Offload -When you're done using Docker Offload, you can stop it. When stopped, you build -images and run containers locally. +Docker Offload automatically idles after a period of inactivity. You can stop it at any time. To stop Docker Offload: ```console $ docker offload stop @@ -86,6 +78,5 @@ To start Docker Offload again, run the `docker offload start` command. ## What's next -- [Configure Docker Offload](configuration.md). -- Try [Docker Model Runner](../ai/model-runner/_index.md) or - [Compose](../ai/compose/models-and-compose.md) to run AI models using Docker Offload. \ No newline at end of file +Configure Docker Offload settings in Docker Desktop. For more information, see [Configure Docker +Offload](/offload/configuration/). \ No newline at end of file diff --git a/content/manuals/offload/troubleshoot.md b/content/manuals/offload/troubleshoot.md index 802063cb0385..275bdb6a090a 100644 --- a/content/manuals/offload/troubleshoot.md +++ b/content/manuals/offload/troubleshoot.md @@ -3,7 +3,7 @@ title: Troubleshoot Docker Offload linktitle: Troubleshoot weight: 800 description: Learn how to troubleshoot issues with Docker Offload. -keywords: cloud, troubleshooting, cloud mode, Docker Desktop, cloud builder, usage +keywords: cloud, troubleshooting, cloud mode, Docker Desktop, offload, usage tags: [Troubleshooting] --- @@ -12,8 +12,8 @@ Docker Offload requires: - Authentication - An active internet connection - No restrictive proxy or firewall blocking traffic to Docker Cloud -- Beta access to Docker Offload -- Docker Desktop 4.43 or later +- A Docker Offload subscription +- Docker Desktop 4.50.0 or later Docker Desktop uses Offload to run both builds and containers in the cloud. If builds or containers are failing to run, falling back to local, or reporting @@ -22,8 +22,8 @@ session errors, use the following steps to help resolve the issue. 1. Ensure Docker Offload is enabled in Docker Desktop: 1. Open Docker Desktop and sign in. - 2. Go to **Settings** > **Beta features**. - 3. Ensure that **Docker Offload** is checked. + 2. Go to **Settings** > **Docker Offload**. + 3. Ensure that **Enable Docker Offload** is enabled. 2. Use the following command to check if the connection is active: diff --git a/content/manuals/offload/usage.md b/content/manuals/offload/usage.md index d061f765e84d..d26a4f6a274b 100644 --- a/content/manuals/offload/usage.md +++ b/content/manuals/offload/usage.md @@ -10,10 +10,12 @@ keywords: cloud, usage, cloud minutes, shared cache, top repositories, cloud bui > [!NOTE] > -> All free trial usage granted for the Docker Offload Beta expire after 90 -> days from the time they are granted. To continue using Docker Offload after -> your usage expires, you can enable on-demand usage at [Docker Home +> All free trial usage granted for the Docker Offload Beta expire after 90 days from the time they are granted. To +> continue using Docker Offload Beta after your usage expires, you can enable on-demand usage at [Docker Home > Billing](https://app.docker.com/billing). +> +> Implementation and settings for the Docker Offload Beta may differ from the General Availability (GA) release. The +> following topic describes the user experience for the GA release. ## Docker Offload billing @@ -21,67 +23,41 @@ For Docker Offload, you can view and configure billing on the **Docker Offload** page in [Docker Home Billing](https://app.docker.com/billing). On this page, you can: -- View your included usage +- View your committed usage - View rates for cloud resources -- Enable or disable on-demand usage +- Manage on-demand billing +- Track your organization's Docker Offload usage - Add or change payment methods -For more general information about billing, see [Billing](../billing/_index.md). +You must be an organization owner to manage billing. For more general information about billing, see +[Billing](../billing/_index.md). ## Docker Offload overview -The Docker Offload overview page in Docker Home provides visibility into -how you or your team is using cloud resources to build and run containers. +The **Offload overview** page in Docker Home provides visibility into +how you are using cloud resources to build and run containers. To view the **Overview** page: 1. Sign in to [Docker Home](https://app.docker.com/). 2. Select the account for which you want to manage Docker Offload. -3. Select **Offload** > **Overview**. - -The following sections describe the available widgets on **Overview**. - -### Offload minutes - -This widget shows the total number of offload minutes used over time. Offload -minutes represent the time spent running builds and containers in the Offload -environment. You can use this chart to: - -- Track your Offload usage trends over time. -- Spot spikes in usage, which may indicate CI changes or build issues. -- Estimate usage against your subscription limits. - -### Build cache usage +3. Select **Offload** > **Offload overview**. -This widget displays data about cache re-use across all builds, helping you -understand how effectively Docker Offload is using the build cache. It -provides insight into: +The following widgets are available: -- The percentage of cache hits vs. misses. -- How much estimated build time is saved by reusing cache layers. -- Opportunities to improve cache efficiency by tuning your Dockerfiles or build - strategy. +- My recent sessions: This widget shows your total session time as well as a break down of your most recent sessions' + duration. +- My top 10 images: This widget shows the top 10 images used in Docker Offload in run sessions. It provides insight into + which images are most frequently used, helping you understand your container usage patterns. +- My active sessions: This widget displays any currently active Docker Offload sessions. -### Top repositories built +## Docker Offload recent activity -This widget highlights the repositories with the highest build activity for -Docker Offload. This widget helps you understand which projects consume the most -cloud resources and how efficiently they're being built. +The **Recent activity** page in Docker Home provides detailed information about your recent Docker Offload sessions. +This includes session ID, start date and time, duration, and number of containers. -It includes both aggregated metrics and per-repository details to give you a -comprehensive view. +To view the **Recent activity** page: -Use this widget to: - -- Identify build hotspots: See which repositories are consuming the most build - time and resources. -- Spot trends: Monitor how build activity evolves across your projects. -- Evaluate efficiency: Check which repositories benefit most from cache re-use. -- Target improvements: Flag repositories with low cache hits or high failure - rates for optimization. - -### Top 10 images - -This widget shows the top 10 images used in Docker Offload in run sessions. It -provides insight into which images are most frequently used, helping you -understand your team's container usage patterns. +1. Sign in to [Docker Home](https://app.docker.com/). +2. Select the account for which you want to manage Docker Offload. +3. Select **Offload** > **Recent activity**. \ No newline at end of file diff --git a/data/summary.yaml b/data/summary.yaml index 191626357e5f..0dcea1254cc6 100644 --- a/data/summary.yaml +++ b/data/summary.yaml @@ -150,8 +150,8 @@ Docker Build Cloud: Docker CLI OpenTelemetry: requires: Docker Engine [26.1.0](/manuals/engine/release-notes/26.1.md#2610) and later Docker Offload: - availability: Beta - requires: Docker Desktop 4.43 and later + subscription: [Docker Offload] + requires: Docker Desktop 4.50 and later docker compose alpha: availability: Experimental Docker Debug: diff --git a/layouts/shortcodes/summary-bar.html b/layouts/shortcodes/summary-bar.html index 172f81c61966..77e588071795 100644 --- a/layouts/shortcodes/summary-bar.html +++ b/layouts/shortcodes/summary-bar.html @@ -11,6 +11,7 @@ "Personal" "person" "Available to all" "public" "Docker Hardened Images" "/icons/dhi.svg" + "Docker Offload" "cloud" }} {{ $availabilityIcons := dict "Experimental" "science"