Skip to content

Commit 6be613f

Browse files
craig-osterhoutcraig-osterhout
committed
cloud: add initial docs
Signed-off-by: Craig <[email protected]> fix link Signed-off-by: Craig <[email protected]> polish troubleshoot Signed-off-by: Craig <[email protected]> polish config Signed-off-by: Craig <[email protected]>
1 parent 9635287 commit 6be613f

28 files changed

+822
-70
lines changed

‎_vale/config/vocabularies/Docker/accept.txt

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -68,6 +68,7 @@ Grafana
6868
Gravatar
6969
gRPC
7070
HyperKit
71+
inferencing
7172
inotify
7273
Intel
7374
Intune

‎content/manuals/_index.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -53,6 +53,10 @@ params:
5353
description: Secure, minimal images for trusted software delivery.
5454
icon: /icons/dhi.svg
5555
link: /dhi/
56+
- title: Docker Offload
57+
description: Build and run containers in the cloud.
58+
icon: cloud
59+
link: /offload/
5660
- title: Build Cloud
5761
description: Build your images faster in the cloud.
5862
icon: /icons/logo-build-cloud.svg

‎content/manuals/desktop/setup/images/cloud-mode.png

-457 Bytes
Binary file not shown.

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

Lines changed: 14 additions & 67 deletions
Original file line numberDiff line numberDiff line change
@@ -16,82 +16,29 @@ depending on whether nested virtualization is supported:
1616

1717
- If your environment supports nested virtualization, you can run Docker Desktop
1818
with its default local Linux VM.
19-
- If nested virtualization is not supported, Docker recommends using Docker
20-
Cloud. To join the beta, contact Docker at `[email protected]`.
19+
- If nested virtualization is not supported, Docker recommends using [Docker
20+
Offload](/offload/).
2121

22-
## Use Docker Cloud
22+
## Use Docker Offload
2323

24-
{{< summary-bar feature_name="Docker Cloud" >}}
24+
Docker Offload lets you offload container workloads to a high-performance, fully
25+
hosted cloud environment, enabling a seamless hybrid experience.
2526

26-
Docker Cloud lets you offload container workloads to a high-performance,
27-
fully hosted cloud environment, enabling a seamless hybrid experience. It
28-
includes an insights dashboard that offers performance metrics and environment
29-
management to help optimize your development workflow.
27+
Docker Offload is useful in virtual desktop environments where nested
28+
virtualization isn't supported. In these environments, Docker Desktop defaults
29+
to using Docker Offload to ensure you can still build and run containers without
30+
relying on local virtualization.
3031

31-
This mode is useful in virtual desktop environments where nested virtualization
32-
isn't supported. In these environments, Docker Desktop defaults to using
33-
cloud mode to ensure you can still build and run containers without relying on
34-
local virtualization.
35-
36-
Docker Cloud decouples the Docker Desktop client from the Docker Engine,
32+
Docker Offload decouples the Docker Desktop client from the Docker Engine,
3733
allowing the Docker CLI and Docker Desktop Dashboard to interact with
3834
cloud-based resources as if they were local. When you run a container, Docker
3935
provisions a secure, isolated, and ephemeral cloud environment connected to
4036
Docker Desktop via an SSH tunnel. Despite running remotely, features like bind
4137
mounts and port forwarding continue to work seamlessly, providing a local-like
42-
experience. To use Docker Cloud:
43-
44-
1. Contact Docker at `[email protected]` to activate the feature for your
45-
account.
46-
2. [Install Docker Desktop](/manuals/desktop/setup/install/windows-install.md#install-docker-desktop-on-windows)
47-
version 4.42 or later on your Windows virtual desktop.
48-
3. [Start Docker Desktop](/manuals/desktop/setup/install/windows-install.md#start-docker-desktop).
49-
4. Sign in to Docker Desktop.
50-
51-
After you sign in, Docker Cloud is enabled by default and cannot be
52-
disabled. When enabled, Docker Desktop's Dashboard header appears purple and the
53-
cloud-mode toggle is a cloud icon ({{< inline-image
54-
src="./images/cloud-mode.png" alt="Cloud mode icon" >}}).
55-
56-
In this mode, Docker Desktop mirrors your cloud environment, providing
57-
a seamless view of your containers and resources running on Docker Cloud. You
58-
can verify that Docker Cloud is working by running a simple container. In a
59-
terminal on your virtual desktop, run the following command:
60-
61-
```console
62-
$ docker run hello-world
63-
```
64-
65-
In the terminal, you will see `Hello from Docker!` if everything is working
66-
correctly.
67-
68-
### View insights and manage Docker Cloud
69-
70-
For insights and management, use the [Docker Cloud
71-
Dashboard](https://app.docker.com/cloud). It provides visibility into your
72-
builds, runs, and cloud resource usage. Key features include:
73-
74-
- Overview: Monitor cloud usage, build cache, and top repositories built.
75-
- Build history: Review past builds with filtering and sorting options.
76-
- Run history: Track container runs and sort by various options.
77-
- Integrations: Learn how to set up cloud builders and runners for your CI
78-
pipeline.
79-
- Settings: Manage cloud builders, usage, and account settings.
80-
81-
Access the Docker Cloud Dashboard at https://app.docker.com/cloud.
82-
83-
### Limitations
84-
85-
The following limitations apply when using Docker Cloud:
86-
87-
- Persistence: Containers are launched in a cloud engine that remains available
88-
as long as you interact with and consume the containers' output. After closing
89-
Docker Desktop, or about 30 minutes of inactivity, the engine is shut down and
90-
becomes inaccessible, along with any data stored in it, including images,
91-
containers, and volumes. A new engine is provisioned for any new workloads.
92-
- Usage and billing: During beta, no charges are incurred for using Docker Cloud
93-
resources. Docker enforces a usage cap and reserves the right to disable
94-
Docker Cloud access at any time.
38+
experience. To use Docker Offload:
39+
40+
To get started using Docker Offload, see the [Docker Offload
41+
quickstart](/offload/quickstart/).
9542

9643
## Virtual desktop support when using nested virtualization
9744

‎content/manuals/offload/_index.md

Lines changed: 57 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,57 @@
1+
---
2+
title: Docker Offload
3+
weight: 15
4+
description: Find documentation on Docker Offload to help you build and run your container images faster, both locally and in CI
5+
keywords: build, cloud, cloud build, remote builder
6+
params:
7+
sidebar:
8+
group: Products
9+
badge:
10+
color: blue
11+
text: Beta
12+
13+
grid:
14+
15+
- title: Quickstart
16+
description: Get up and running with Docker Offload in just a few steps.
17+
icon: rocket_launch
18+
link: /offload/quickstart/
19+
20+
- title: About
21+
description: Learn about Docker Offload and how it works.
22+
icon: info
23+
link: /offload/about/
24+
25+
- title: Configure
26+
description: Set up and customize your cloud build environments.
27+
icon: tune
28+
link: /offload/configuration/
29+
30+
- title: Usage
31+
description: Learn about Docker Offload usage and how to monitor your cloud resources.
32+
icon: monitor_heart
33+
link: /offload/usage/
34+
35+
- title: Optimize
36+
description: Improve performance, caching, and cost efficiency in Docker Offload.
37+
icon: speed
38+
link: /offload/optimize/
39+
40+
- title: Troubleshoot
41+
description: Learn how to troubleshoot issues with Docker Offload.
42+
icon: bug_report
43+
link: /offload/troubleshoot/
44+
45+
---
46+
47+
{{< summary-bar feature_name="Docker Offload" >}}
48+
49+
Docker Offload is a fully managed service that lets you offload building and
50+
running containers to the cloud using the Docker tools you already know. It
51+
provides cloud infrastructure for fast, consistent builds and compute-heavy
52+
workloads like running LLMs or machine learning pipelines.
53+
54+
In the following topics, learn about Docker Offload, how to set it up, use it
55+
for your workflows, and troubleshoot common issues.
56+
57+
{{< grid >}}

‎content/manuals/offload/about.md

Lines changed: 129 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,129 @@
1+
---
2+
title: About Docker Offload
3+
linktitle: About
4+
weight: 15
5+
description: Learn about Docker Offload, its features, and how it works.
6+
keywords: cloud, build, remote builder
7+
---
8+
9+
Docker Offload is a fully managed service for building and running containers in
10+
the cloud using the Docker tools you already know, including Docker Desktop, the
11+
Docker CLI, and Docker Compose. It extends your local development workflow into a
12+
scalable, cloud-powered environment, so you can offload compute-heavy tasks,
13+
accelerate builds, and securely manage container workloads across the software
14+
lifecycle.
15+
16+
Docker Offload also supports GPU-accelerated instances, allowing you to
17+
containerize and run compute-intensive workloads such as Docker Model Runner and
18+
other machine learning or data processing tasks that benefit from GPU.
19+
20+
## Key features
21+
22+
Docker Offload includes the following capabilities to support modern container
23+
workflows:
24+
25+
- Cloud-based builds: Execute builds on remote, fully managed BuildKit instances
26+
with native support for multi-platform output.
27+
- GPU acceleration: Use NVIDIA L4 GPU-backed environments for machine learning,
28+
media processing, and other compute-intensive workloads.
29+
- Ephemeral cloud runners: Automatically provision and tear down cloud
30+
environments for each container session.
31+
- Shared build cache: Speed up build times across machines and teammates with a
32+
smart, shared cache layer.
33+
- Hybrid workflows: Seamlessly transition between local and remote execution
34+
using Docker Desktop or CLI.
35+
- Secure communication: Use encrypted tunnels between Docker Desktop and cloud
36+
environments with support for secure secrets and image pulling.
37+
- Port forwarding and bind mounts: Retain a local development experience even
38+
when running containers in the cloud.
39+
- VDI-friendly: Use Docker Offload in virtual desktop environments or systems that
40+
don't support nested virtualization.
41+
42+
## Why use Docker Offload?
43+
44+
Docker Offload is designed to support modern development teams working across
45+
local and cloud environments. It helps you:
46+
47+
- Offload heavy builds and runs to fast, scalable infrastructure
48+
- Accelerate feedback loops in development and testing
49+
- Run containers that require more resources than your local setup can provide
50+
- Build and run AI apps with instant access to GPU-powered environments
51+
- Use Docker Compose to manage complex, multi-service apps that need cloud
52+
resources
53+
- Maintain consistent environments without managing custom infrastructure
54+
- Develop efficiently in restricted or low-powered environments like VDIs
55+
56+
Docker Offload is ideal for high-velocity development workflows
57+
that need the flexibility of the cloud without sacrificing the simplicity of
58+
local tools.
59+
60+
## How Docker Offload works
61+
62+
Docker Offload replaces the need to build or run containers locally by connecting
63+
Docker Desktop to secure, dedicated cloud resources.
64+
65+
### Building with Docker Offload
66+
67+
When you use Docker Offload for builds, the `docker buildx build` command sends
68+
the build request to a remote BuildKit instance in the cloud, instead of
69+
executing it locally. Your workflow stays the same, only the execution
70+
environment changes.
71+
72+
The build runs on infrastructure provisioned and managed by Docker:
73+
74+
- Each cloud builder is an isolated Amazon EC2 instance with its own EBS volume
75+
- Remote builders use a shared cache to speed up builds across machines and
76+
teammates
77+
- Builds support native multi-platform output (for example, `linux/amd64`,
78+
`linux/arm64`)
79+
- Build results are encrypted in transit and sent to your specified destination
80+
(such as a registry or local image store)
81+
82+
Docker Offload manages the lifecycle of builders automatically. There's no need to
83+
provision or maintain infrastructure.
84+
85+
> [!NOTE]
86+
>
87+
> Docker Offload builders are currently hosted in the United States East region. Users in
88+
> other regions may experience increased latency.
89+
90+
### Running containers with Docker Offload
91+
92+
When you use Docker Offload to run containers, a Docker Desktop creates a secure
93+
SSH tunnel to a Docker daemon running in the cloud. Your containers are started
94+
and managed entirely in that remote environment.
95+
96+
Here's what happens:
97+
98+
1. Docker Desktop connects to the cloud and triggers container creation.
99+
2. Docker Offload pulls the required images and starts containers in the cloud.
100+
3. The connection stays open while the containers run.
101+
4. When the containers stop running, the environment shuts down and is cleaned
102+
up automatically.
103+
104+
This setup avoids the overhead of running containers locally and enables fast,
105+
reliable containers even on low-powered machines, including machines that do not
106+
support nested virtualization. This makes Docker Offload ideal for developers
107+
using environments such as virtual desktops, cloud-hosted development machines,
108+
or older hardware.
109+
110+
Docker Offload also supports GPU-accelerated workloads. Containers that require
111+
GPU access can run on cloud instances provisioned with NVIDIA L4 GPUs for
112+
efficient AI inferencing, media processing, and general-purpose GPU
113+
acceleration. This enables compute-heavy workflows such as model evaluation,
114+
image processing, and hardware-accelerated CI tests to run seamlessly in the
115+
cloud.
116+
117+
Despite running remotely, features like bind mounts and port forwarding continue
118+
to work seamlessly, providing a local-like experience from within Docker Desktop
119+
and the CLI.
120+
121+
Docker Offload provisions an ephemeral cloud environment for each session. The
122+
environment remains active while you are interacting with Docker Desktop or
123+
actively using containers. If no activity is detected for about 30 minutes, the
124+
session shuts down automatically. This includes any containers, images, or
125+
volumes in that environment, which are deleted when the session ends.
126+
127+
## What's next
128+
129+
Get hands-on with Docker Offload by following the [Docker Offload quickstart](/offload/quickstart/).

0 commit comments

Comments
 (0)