|
| 1 | +--- |
| 2 | +title: About Docker Cloud |
| 3 | +linktitle: About |
| 4 | +weight: 15 |
| 5 | +description: Learn about Docker Cloud, its features, and how it works. |
| 6 | +keywords: cloud, build, remote builder |
| 7 | +--- |
| 8 | + |
| 9 | +Docker Cloud 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 Cloud 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 | +You can use Docker Cloud in following ways: |
| 21 | + |
| 22 | +- In Cloud mode, where you use Docker Desktop with cloud-based resources. This |
| 23 | + is ideal for virtual desktop environments (VDIs) where nested virtualization |
| 24 | + isn't supported, or when you need more CPU, memory, or GPU than your local |
| 25 | + machine can provide. In this mode, both builds and container runs happen in |
| 26 | + the cloud, but Docker Desktop maintains a local-like experience. To get |
| 27 | + started, see [Docker Cloud quickstart](/cloud/quickstart/). |
| 28 | + |
| 29 | +- For only builds, without running containers in the cloud. This lets you offload image |
| 30 | + builds to Docker Cloud while continuing to run containers locally. It's useful |
| 31 | + when you want faster, consistent builds but don’t need to run containers in |
| 32 | + the cloud. To get started, see [Build with Docker Cloud](/cloud/build/). |
| 33 | + |
| 34 | +- In CI environments where builds are performed entirely in the cloud. This lets |
| 35 | + you have fast, consistent, and scalable builds without the need to manage your |
| 36 | + own runners or infrastructure. To get started, see [Use Docker Cloud in |
| 37 | + CI](/cloud/ci-build/). |
| 38 | + |
| 39 | +## Key features |
| 40 | + |
| 41 | +Docker Cloud includes the following capabilities to support modern container |
| 42 | +workflows: |
| 43 | + |
| 44 | +- Cloud-based builds: Execute builds on remote, fully managed BuildKit instances |
| 45 | + with native support for multi-platform output. |
| 46 | +- GPU acceleration: Use NVIDIA L4 GPU-backed environments for machine learning, |
| 47 | + media processing, and other compute-intensive workloads. |
| 48 | +- Ephemeral cloud runners: Automatically provision and tear down cloud |
| 49 | + environments for each container session. |
| 50 | +- Shared build cache: Speed up build times across machines and teammates with a |
| 51 | + smart, shared cache layer. |
| 52 | +- Hybrid workflows: Seamlessly transition between local and remote execution |
| 53 | + using Docker Desktop, CLI, or CI tools. |
| 54 | +- Secure communication: Use encrypted tunnels between Docker Desktop and cloud |
| 55 | + environments with support for secure secrets and image pulling. |
| 56 | +- CI/CD integration: Trigger builds in CI pipelines using Buildx, GitHub |
| 57 | + Actions, or prebuilt integrations. |
| 58 | +- Port forwarding and bind mounts: Retain a local development experience even |
| 59 | + when running containers in the cloud. |
| 60 | +- VDI-friendly: Use Docker Cloud in virtual desktop environments or systems that |
| 61 | + don't support nested virtualization. |
| 62 | + |
| 63 | +## Why use Docker Cloud? |
| 64 | + |
| 65 | +Docker Cloud is designed to support modern development teams working across |
| 66 | +local and cloud environments. It helps you: |
| 67 | + |
| 68 | +- Use the same Docker workflows locally and in the cloud |
| 69 | +- Offload builds to fast, high-performance infrastructure |
| 70 | +- Run containers that require more CPU, memory, or GPU than your local setup can |
| 71 | + provide |
| 72 | +- Run Docker Desktop in environments that don't support nested virtualization |
| 73 | +- Speed up feedback loops by reducing wait times for builds and testing |
| 74 | + environments |
| 75 | +- Avoid managing custom infrastructure while retaining full control over how |
| 76 | + containers are built and executed |
| 77 | +- Ensure consistent, clean environments for every build or test |
| 78 | +- Integrate easily with any CI system using simple scripts or prebuilt actions |
| 79 | + |
| 80 | +Docker Cloud is ideal for hybrid teams that want to iterate quickly, test |
| 81 | +reliably, and scale efficiently without compromising on developer experience. |
| 82 | + |
| 83 | +## How Docker Cloud works |
| 84 | + |
| 85 | +Docker Cloud replaces the need to build or run containers locally by connecting |
| 86 | +Docker Desktop and your CI pipelines to secure, dedicated cloud resources. |
| 87 | + |
| 88 | +### Building with Docker Cloud |
| 89 | + |
| 90 | +When you use Docker Cloud for builds, the `docker buildx build` command sends |
| 91 | +the build request to a remote BuildKit instance in the cloud, instead of |
| 92 | +executing it locally. Your workflow stays the same, only the execution |
| 93 | +environment changes. |
| 94 | + |
| 95 | +The build runs on infrastructure provisioned and managed by Docker: |
| 96 | + |
| 97 | +- Each cloud builder is an isolated Amazon EC2 instance with its own EBS volume |
| 98 | +- Remote builders use a shared cache to speed up builds across machines and |
| 99 | + teammates |
| 100 | +- Builds support native multi-platform output (for example, `linux/amd64`, |
| 101 | + `linux/arm64`) |
| 102 | +- Build results are encrypted in transit and sent to your specified destination |
| 103 | + (such as a registry or local image store) |
| 104 | + |
| 105 | +Docker Cloud manages the lifecycle of builders automatically. There's no need to |
| 106 | +provision or maintain infrastructure. |
| 107 | + |
| 108 | +> [!NOTE] |
| 109 | +> |
| 110 | +> Docker Cloud builders are currently hosted in the US East region. Users in |
| 111 | +> other regions may experience increased latency. |
| 112 | +
|
| 113 | +### Running containers with Docker Cloud |
| 114 | + |
| 115 | +When you use Docker Cloud to run containers, a Docker Desktop creates a secure |
| 116 | +SSH tunnel to a Docker daemon running in the cloud. Your containers are started |
| 117 | +and managed entirely in that remote environment. |
| 118 | + |
| 119 | +Here's what happens: |
| 120 | + |
| 121 | +1. Docker Desktop connects to the cloud and triggers container creation. |
| 122 | +2. Docker Cloud pulls the required images and starts containers in the cloud. |
| 123 | +3. The connection stays open while the containers run. |
| 124 | +4. When the containers stop running, the environment shuts down and is cleaned |
| 125 | + up automatically. |
| 126 | + |
| 127 | +This setup avoids the overhead of running containers locally and enables fast, |
| 128 | +reliable containers even on low-powered machines, including machines that do not |
| 129 | +support nested virtualization. This makes Docker Cloud ideal for developers |
| 130 | +using environments such as virtual desktops, cloud-hosted development machines, |
| 131 | +or older hardware. |
| 132 | + |
| 133 | +Docker Cloud also supports GPU-accelerated workloads. Containers that require |
| 134 | +GPU access can run on cloud instances provisioned with NVIDIA L4 GPUs for |
| 135 | +efficient AI inferencing, media processing, and general-purpose GPU |
| 136 | +acceleration. This enables compute-heavy workflows such as model evaluation, |
| 137 | +image processing, and hardware-accelerated CI tests to run seamlessly in the |
| 138 | +cloud. |
| 139 | + |
| 140 | +Despite running remotely, features like bind mounts and port forwarding continue |
| 141 | +to work seamlessly, providing a local-like experience from within Docker Desktop |
| 142 | +and the CLI. |
| 143 | + |
| 144 | +Docker Cloud provisions an ephemeral cloud environment for each session. The |
| 145 | +environment remains active while you are interacting with Docker Desktop or |
| 146 | +actively using containers. If no activity is detected for about 30 minutes, the |
| 147 | +session shuts down automatically. This includes any containers, images, or |
| 148 | +volumes in that environment, which are deleted when the session ends. |
| 149 | + |
| 150 | +## What's next |
| 151 | + |
| 152 | +Get hands-on with Docker Cloud by following the [Docker Cloud quickstart](/cloud/quickstart/). |
0 commit comments