@@ -6,46 +6,31 @@ description: Learn about Docker Offload, its features, and how it works.
66keywords : cloud, offload, vdi
77---
88
9+ {{< summary-bar feature_name="Docker Offload" >}}
10+
911Docker Offload is a fully managed service for building and running containers in
1012the cloud using the Docker tools you already know, including Docker Desktop, the
1113Docker CLI, and Docker Compose. It extends your local development workflow into a
1214scalable, cloud-powered environment, enabling developers to work efficiently even
1315in virtual desktop infrastructure (VDI) environments or systems that don't support
1416nested virtualization.
1517
16-
17-
1818## Key features
1919
2020Docker Offload includes the following capabilities to support modern container
2121workflows:
2222
2323- Ephemeral cloud runners: Automatically provision and tear down cloud
2424 environments for each container session.
25- - Hybrid workflows: Seamlessly transition between local and remote execution
26- using Docker Desktop or CLI.
2725- Secure communication: Use encrypted tunnels between Docker Desktop and cloud
2826 environments with support for secure secrets and image pulling.
2927- Port forwarding and bind mounts: Retain a local development experience even
3028 when running containers in the cloud.
31- - VDI-friendly: [ Use Docker Desktop] ( ../desktop/setup/vm-vdi.md ) in virtual desktop environments or systems that
32- don't support nested virtualization.
33-
34- ## Why use Docker Offload?
35-
36- Docker Offload is designed to support modern development teams working across
37- local and cloud environments. It helps you:
38-
39- - Offload heavy builds and runs to fast, scalable infrastructure
40- - Run containers that require more resources than your local setup can provide
41- - Use Docker Compose to manage complex, multi-service apps that need cloud
42- resources
43- - Maintain consistent environments without managing custom infrastructure
44- - Develop efficiently in restricted or low-powered environments like VDIs
29+ - VDI-friendly: [ Use Docker Desktop] ( ../desktop/setup/vm-vdi.md ) in virtual
30+ desktop environments or systems that don't support nested virtualization.
4531
46- Docker Offload is ideal for high-velocity development workflows
47- that need the flexibility of the cloud without sacrificing the simplicity of
48- local tools.
32+ For more information, see the [ Docker Offload product
33+ page] ( https://www.docker.com/products/docker-offload/ ) .
4934
5035## How Docker Offload works
5136
@@ -54,15 +39,15 @@ Docker Desktop to secure, dedicated cloud resources.
5439
5540### Running containers with Docker Offload
5641
57- When you use Docker Offload to build or run containers, a Docker Desktop creates a secure
42+ When you use Docker Offload to build or run containers, Docker Desktop creates a secure
5843SSH tunnel to a Docker daemon running in the cloud. Your containers are started
5944and managed entirely in that remote environment.
6045
6146Here's what happens:
6247
63481 . Docker Desktop connects to the cloud and triggers container creation.
64492 . Docker Offload builds or pulls the required images and starts containers in the cloud.
65- 3 . The connection stays open while the containers run.
50+ 3 . The connection stays open while the containers run and you remain active .
66514 . When the containers stop running, the environment shuts down and is cleaned
6752 up automatically.
6853
@@ -76,11 +61,36 @@ Despite running remotely, features like bind mounts and port forwarding continue
7661to work seamlessly, providing a local-like experience from within Docker Desktop
7762and the CLI.
7863
79- Docker Offload automatically transitions between active and idle states based on
80- usage. You're only charged when actively building or running containers. When
81- idle for more than 5 minutes, the session ends and resources are cleaned up. For
82- details about how this works and how to configure idle timeout, see [ Active and
83- idle states] ( configuration.md#understand-active-and-idle-states ) .
64+ ### Cloud resources
65+
66+ Docker Offload uses cloud hosts with 4 vCPUs and 8 GiB of memory. If you have
67+ different requirements, [ contact
68+ Docker] ( https://www.docker.com/pricing/contact-sales/ ) to explore options.
69+
70+ ### Session management and idle state
71+
72+ Docker Offload implements session management and idle state policies to ensure
73+ fair use across all users.
74+
75+ Here's how session management works:
76+
77+ 1 . You start a new Docker Offload session. You can only have one session active
78+ at a time.
79+ 2 . You receive periodic prompts (every 1 to 3 hours) in the Docker Desktop Dashboard
80+ to determine if you are still active. When the prompt appears, you can choose to:
81+ - Select ** Resume** in the prompt to confirm you're still active and
82+ continue your session.
83+ - Do nothing, select ** Cancel** , or dismiss the prompt. You have a
84+ 5-minute grace period. After the grace period, if you still haven't
85+ responded, your session enters a 5-minute idle timeout period. During
86+ either period, you can select ** Resume** to continue your session and
87+ preserve all containers, images, and volumes.
88+ 3 . If the idle timeout period exceeds 5 minutes without resuming, the session
89+ is suspended (the remote connection is suspended and containers stop
90+ running).
91+ 4 . After 8 hours of cumulative usage, the periodic prompts become more frequent.
92+ If you do not respond to a prompt and the idle timeout expires, your session
93+ ends and any containers, images, or volumes are deleted.
8494
8595## What's next
8696
0 commit comments