You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
9
+
The **Builds** view provides an interactive interface for inspecting build history, monitoring active builds, and managing builders directly in Docker Desktop.
10
10
11
-
12
-
e **Builds** view lets you inspect your build history and manage builders. By default, it displays a list of all your ongoing and completed builds. [Explore builds](builds.md).
13
-
14
-
The **Builds** view is a simple interface that lets you inspect your build
15
-
history and manage builders using Docker Desktop.
16
-
17
-
Opening the **Builds** view in Docker Desktop displays a list of completed builds.
18
-
By default, the list is sorted by date, showing the most recent builds at the top.
19
-
You can switch to **Active builds** to view any ongoing builds.
20
-
21
-
11
+
By default, the **Build history** tab displays a list of completed builds, sorted by date (newest first). Switch to the **Active builds** tab to view ongoing builds.
22
12
23
13
If you're connected to a cloud builder through [Docker Build Cloud](../../build-cloud/_index.md),
24
14
the Builds view also lists any active or completed cloud builds by other team members
25
15
connected to the same cloud builder.
26
16
27
17
## Show build list
28
18
29
-
Select the **Builds** view in the Docker Desktop Dashboard to open the build list.
19
+
Open the **Builds** view from the Docker Dashboard to access:
30
20
31
-
The build list shows your completed and ongoing builds. The **Build history**
32
-
tab shows completed historical builds, and from here you can inspect the build
33
-
logs, dependencies, traces, and more. The **Active builds** tab shows builds
34
-
that are currently running.
21
+
-**Build history**: Completed builds with access to logs, dependencies, traces, and more
22
+
-**Active builds**: Builds currently in progress
35
23
36
-
The list shows builds for your active, running builders. It doesn't list builds
37
-
for inactive builders: builders that you've removed from your system, or
38
-
builders that have been stopped.
24
+
Only builds from active, running builders are listed. Builds from removed or stopped builders are not shown.
39
25
40
26
### Builder settings
41
27
@@ -50,7 +36,9 @@ Docker Desktop settings.
50
36
The **Import builds** button lets you import build records for builds by other
51
37
people, or builds in a CI environment. When you've imported a build record, it
52
38
gives you full access to the logs, traces, and other data for that build,
53
-
directly in Docker Desktop. The [build summary](/manuals/build/ci/github-actions/build-summary.md)
39
+
directly in Docker Desktop.
40
+
41
+
The [build summary](/manuals/build/ci/github-actions/build-summary.md)
54
42
for the `docker/build-push-action` and `docker/bake-action` GitHub Actions
55
43
includes a link to download the build records, for inspecting CI jobs with
56
44
Docker Desktop.
@@ -66,8 +54,6 @@ If you're inspecting a multi-platform build, the drop-down menu in the
66
54
top-right of this tab lets you filter the information down to a specific
Copy file name to clipboardExpand all lines: content/manuals/desktop/use-desktop/container.md
+3-38Lines changed: 3 additions & 38 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,7 @@ When you [inspect a container](#inspect-a-container), the **Stats** tab displays
31
31
32
32
You can obtain detailed information about the container when you select it.
33
33
34
-
From here, you can use the quick action buttons to perform various actions such as pause, resume, start or stop, or explore the **Logs**, **Inspect**, **Bind mounts**, **Exec**, **Files**, and **Stats** tabs.
34
+
From here, you can use the quick action buttons to perform various actions such as pause, resume, start or stop, or explore the **Logs**, **Inspect**, **Bind mounts**, **Debug**, **Files**, and **Stats** tabs.
35
35
36
36
### Logs
37
37
@@ -53,40 +53,7 @@ Select **Logs** to see logs from the container. You can also:
53
53
54
54
Select **Inspect** to view low-level information about the container. It displays the local path, version number of the image, SHA-256, port mapping, and other details.
55
55
56
-
### Integrated terminal
57
-
58
-
From the **Exec** tab, you can use the integrated terminal, on a running
59
-
container, directly within Docker Desktop. You are able to quickly run commands
60
-
within your container so you can understand its current state or debug when
61
-
something goes wrong.
62
-
63
-
Using the integrated terminal is the same as running one of the following commands:
64
-
65
-
-`docker exec -it <container-id> /bin/sh`
66
-
-`docker exec -it <container-id> cmd.exe` when accessing Windows containers
67
-
-`docker debug <container-id>` when using debug mode
68
-
69
-
The integrated terminal:
70
-
71
-
- Persists your session and **Debug mode** setting if you navigate to another
72
-
part of the Docker Desktop Dashboard and then return.
73
-
- Supports copy, paste, search, and clearing your session.
74
-
- When not using debug mode, it automatically detects the default user for a
75
-
running container from the image's Dockerfile. If no user is specified, or
76
-
you're using debug mode, it defaults to `root`.
77
-
78
-
#### Open the integrated terminal
79
-
80
-
To open the integrated terminal, either:
81
-
82
-
- Hover over your running container and under the **Actions** column, select the **Show container actions**
83
-
menu. From the drop-down menu, select **Open in terminal**.
84
-
- Or, select the container and then select the **Exec** tab.
85
-
86
-
To use your external terminal, navigate to the **General** tab in **Settings**
87
-
and select the **System default** option under **Choose your terminal**.
88
-
89
-
#### Open the integrated terminal in debug mode
56
+
### Debug
90
57
91
58
Debug mode requires a [Pro, Team, or Business subscription](/subscription/details/). Debug mode has several advantages, such as:
92
59
@@ -103,9 +70,7 @@ To open the integrated terminal in debug mode:
103
70
104
71
- Hover over your running container and under the **Actions** column, select the **Show container actions**
105
72
menu. From the drop-down menu, select **Use Docker Debug**.
106
-
- Or, select the container and then select the **Debug** tab. If the
107
-
**Debug** tab isn't visible, select the **Exec** tab and then enable the
108
-
**Debug mode** setting.
73
+
- Or, select the container and then select the **Debug** tab.
109
74
110
75
To use debug mode by default when accessing the integrated terminal, navigate to
111
76
the **General** tab in **Settings** and select the **Enable Docker Debug by
0 commit comments