Skip to content

Commit 78f189b

Browse files
feedback1
Signed-off-by: Craig <[email protected]>
1 parent 6be613f commit 78f189b

File tree

3 files changed

+14
-18
lines changed

3 files changed

+14
-18
lines changed

content/manuals/offload/configuration.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -61,10 +61,6 @@ Your subscription includes the following Build cache space:
6161

6262
To get more Build cache space, [upgrade your subscription](/manuals/subscription/change.md).
6363

64-
> [!TIP]
65-
>
66-
> If you build large images, consider allocating less storage for caching.
67-
6864
### Private resource access
6965

7066
Private resource access lets cloud builders pull images and packages from

content/manuals/offload/quickstart.md

Lines changed: 2 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -48,17 +48,11 @@ up](https://www.docker.com/products/docker-offload/) and subscribe.
4848
> Offload usage](/offload/usage/).
4949
5050
When Docker Offload is started, you'll see a cloud icon ({{< inline-image
51-
src="./images/cloud-mode.png" alt="Offload mode icon"
52-
>}}), and the Docker Desktop Dashboard appears purple.
51+
src="./images/cloud-mode.png" alt="Offload mode icon" >}})
52+
in the Docker Desktop Dashboard header, and the Docker Desktop Dashboard appears purple.
5353
You can run `docker offload status` in a terminal to check the status of
5454
Docker Offload.
5555

56-
> [!NOTE]
57-
>
58-
> If you're unable to start Docker Offload, ensure you have the latest
59-
> version of Docker Desktop installed, you're signed in, and that Docker
60-
> Offload is enabled in **Settings** > **Beta features**.
61-
6256
## Step 3: Run a container with Docker Offload
6357

6458
After starting Docker Offload, Docker Desktop connects to a secure cloud environment

content/manuals/offload/troubleshoot.md

Lines changed: 12 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -19,31 +19,37 @@ Docker Desktop uses Offload to run both builds and containers in the cloud.
1919
If builds or containers are failing to run, falling back to local, or reporting
2020
session errors, use the following steps to help resolve the issue.
2121

22-
1. Use the following command to check if the connection is active:
22+
1. Ensure Docker Offload is enabled in Docker Desktop:
23+
24+
1. Open Docker Desktop and sign in.
25+
2. Go to **Settings** > **Beta features**.
26+
3. Ensure that **Docker Offload** is checked.
27+
28+
2. Use the following command to check if the connection is active:
2329

2430
```console
2531
$ docker offload status
2632
```
2733

28-
2. To get more information, run the following command:
34+
3. To get more information, run the following command:
2935

3036
```console
3137
$ docker offload diagnose
3238
```
3339

34-
3. If you're not connected, start a new session:
40+
4. If you're not connected, start a new session:
3541

3642
```console
3743
$ docker offload start
3844
```
3945

40-
4. Verify authentication with `docker login`.
46+
5. Verify authentication with `docker login`.
4147

42-
5. If needed, you can sign out and then sign in again:
48+
6. If needed, you can sign out and then sign in again:
4349

4450
```console
4551
$ docker logout
4652
$ docker login
4753
```
4854

49-
6. Verify your usage and billing. For more information, see [Docker Offload usage](/offload/usage/).
55+
7. Verify your usage and billing. For more information, see [Docker Offload usage](/offload/usage/).

0 commit comments

Comments
 (0)