b744dd3103
# To dos ~- Evaluate _index pages and standardize across account + admins category~ ~- Edit weights of topics~ - Notify TSEs, other stakeholders - TW sign off ## Summary This PR restructures the Platform documentation into a clearer Accounts, Security, and Subscription and billing information architecture, with aliases so existing URLs keep working. Work from these PRs was merged into this feature branch: - #25957 (Security IA) - #25960 (Accounts and Admin) - #25981 (Subscription and billing) ### Accounts - Moves organization, company, and admin content under Accounts. - Splits individual-account docs into their own subsection. - Removes the standalone Admin section; those pages now live under Accounts. ### Security - Publishes Security at `/security/`, matching other Platform sections. - Groups authentication (SSO, 2FA, OIDC), access tokens, provisioning, and roles under Security. - Leaves Enterprise Hardened Desktop and related enterprise security docs under Enterprise. - Restores shipped Hardened Desktop and security FAQ URLs so they match `main`. ### Subscription and billing - Merges Subscription and Billing into a single Subscription and billing section. - Drops the extra subcategory wrappers and nests billing tasks under Manage. - Shortens the billing details sidebar label. ### FAQs - Consolidates Platform FAQs onto four pages: Accounts, Security, Subscription and billing, and Platform. - Folds leftover general, container, and network/VM security FAQs into Platform FAQs. - Folds SSO enforcement FAQs into the SSO FAQ. - Templates FAQ pages with H2 topics and H3 questions, and limits the table of contents to H2. ### Navigation and follow-ups - Renames the manuals sidebar group from Platform to Accounts and admin, and updates the manuals landing heading and copy to match. - Fixes the MSI install Settings Management link after the security path move. - Updates CODEOWNERS, the labeler, and in-repo links to the new paths. --------- Co-authored-by: Cursor <cursoragent@cursor.com>
4.7 KiB
title, linktitle, weight, description, keywords
| title | linktitle | weight | description | keywords |
|---|---|---|---|---|
| Docker Offload quickstart | Quickstart | 10 | Learn how to use Docker Offload to build and run your container images in the cloud. | cloud, quickstart, Docker Desktop, offload |
{{< summary-bar feature_name="Docker Offload" >}}
Docker Offload lets you build and run containers in the cloud while using your local Docker Desktop tools and workflow. This means faster builds, access to powerful cloud resources, and a seamless development experience.
This quickstart covers the steps developers need to get started with Docker Offload.
Note
If you're an organization owner, to get started you must contact sales and subscribe your organization to use Docker Offload. After subscribing, see Manage Docker products to learn how to manage access for the developers in your organization.
Prerequisites
- You must have Docker Desktop installed. Docker recommends using the latest version of Docker Desktop to access the newest features and improvements in Docker Offload.
- You must have a Docker Business subscription and a Docker Offload subscription.
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.
- Start Docker Desktop and sign in.
- In the Docker Desktop Dashboard header, look for the Docker Offload toggle.
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, check if Docker Offload is disabled in your Docker Desktop settings, and then contact your administrator to verify that your organization has subscribed to Docker Offload and that they have enabled access for your organization.
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.
-
Start Docker Desktop and sign in.
-
Open a terminal and run the following command to start Docker Offload:
$ docker offload startTip
To learn more about the Docker Offload CLI commands, see the Docker Offload CLI reference.
-
If you are a member of multiple organizations that have access to Docker Offload, you have the option to select a profile. Your usage will be associated with the organization of the selected profile.
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
After starting Docker Offload, Docker Desktop connects to a secure cloud environment that mirrors your local experience. When you run builds or containers, they execute remotely, but behave just like local ones.
To verify that Docker Offload is working, run a container:
$ docker run --rm hello-world
If Docker Offload is working, you'll see Hello from Docker! in the terminal output.
Step 4: Monitor your Offload session
When Docker Offload is started and you have started session (for example, you've ran a container), then you can see current session duration estimate in the Docker Desktop Dashboard footer next to the hourglass icon ({{< inline-image src="./images/hourglass-icon.png" alt="Offload session duration" >}}).
Also, when Docker Offload is started, you can view detailed session information by selecting Docker Offload > Insights in the left navigation of the Docker Desktop Dashboard.
Step 5: Stop Docker Offload
Docker Offload automatically idles if you do not respond to periodic prompts that appear in the Docker Desktop Dashboard. You can stop your Docker Offload session at any time. To stop Docker Offload:
$ docker offload stop
When you stop Docker Offload, the cloud environment is terminated and all running containers and images are removed. When Docker Offload has been idle for 5 minutes, the environment is also terminated and all running containers and images are removed.
To start Docker Offload again, run the docker offload start command.