mirror of https://github.com/docker/docs.git
ENGDOCS-1527 (#17860)
* ENGDOCS-1527 * tweak * review edits --------- Co-authored-by: aevesdocker <alliesadler@f693mt7fh6.home>
This commit is contained in:
parent
cddb7fa6d1
commit
ba8228a804
|
@ -10,35 +10,28 @@ The **Containers** view lists all your running containers and applications. You
|
|||
|
||||
Use the **Search** field to search for any specific container.
|
||||
|
||||
From the **Containers** view you can perform the following actions on one or more containers at once:
|
||||
From the **Containers** view you can perform the following actions:
|
||||
- Pause/Resume
|
||||
- Stop/Start
|
||||
- Stop/Start/Restart
|
||||
- View image packages and CVEs
|
||||
- Delete
|
||||
- Open the application in VS code
|
||||
- Open the port exposed by the container in a browser
|
||||
- Copy docker run. This allows you to easily share container run details or modify certain parameters
|
||||
- Copy docker run. This lets you share container run details or modify certain parameters.
|
||||
|
||||
### Integrated terminal
|
||||
## Resource usage
|
||||
|
||||
You also have the option to open an integrated terminal, on a running container, directly within Docker Desktop. This allows you to quickly run commands within your container so you can understand its current state or debug when something goes wrong.
|
||||
From the **Containers** view you can monitor your containers' CPU and memory usage over time. This can help you understand if something is wrong with your containers or if you need to allocate additional resources.
|
||||
|
||||
Using the integrated terminal is the same as running `docker exec -it <container-id> /bin/sh`, or `docker exec -it <container-id> cmd.exe` if you are using Windows containers, in your external terminal. It also:
|
||||
|
||||
- Automatically detects the default user for a running container from the image's Dockerfile. If no use is specified it defaults to `root`.
|
||||
- Persists your session if you navigate to another part of the Docker Dashboard and then return.
|
||||
- Supports copy, paste, search, and clearing your session.
|
||||
|
||||
To open the integrated terminal, either:
|
||||
- Hover over your running container and select the **Show container actions** menu. From the drop-down menu, select **Open in terminal**.
|
||||
- Select the container and then select the **Terminal** tab.
|
||||
|
||||
To use your external terminal, change your settings.
|
||||
When you [inspect a container](#inspect-a-container), the **Stats** tab displays further information about a container's resource utilization. You can see how much CPU, memory, network and disk space your container is using over time.
|
||||
|
||||
## Inspect a container
|
||||
|
||||
You can obtain detailed information about the container when you select a container.
|
||||
You can obtain detailed information about the container when you select it.
|
||||
|
||||
The **container view** displays **Logs**, **Inspect**, **Terminal**, **Files**, and **Stats** tabs and provides quick action buttons to perform various actions.
|
||||
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**, **Terminal**, **Files**, and **Stats** tabs.
|
||||
|
||||
### Logs
|
||||
|
||||
- Select **Logs** to see logs from the container. You can also:
|
||||
- Use `Cmd + f`/`Ctrl + f` to open the search bar and find specific entries. Search matches are highlighted in yellow.
|
||||
|
@ -48,7 +41,27 @@ The **container view** displays **Logs**, **Inspect**, **Terminal**, **Files**,
|
|||
- Use the **Clear terminal** icon in the top right-hand corner to clear the logs terminal.
|
||||
- Select and view external links that may be in your logs.
|
||||
|
||||
- Select **Inspect** to view low-level information about the container. You can see the local path, version number of the image, SHA-256, port mapping, and other details.
|
||||
### Inspect
|
||||
|
||||
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.
|
||||
|
||||
### Integrated terminal
|
||||
|
||||
From the **Terminal** tab, lets you use the integrated terminal, on a running container, directly within Docker Desktop. You are able to quickly run commands within your container so you can understand its current state or debug when something goes wrong.
|
||||
|
||||
Using the integrated terminal is the same as running `docker exec -it <container-id> /bin/sh`, or `docker exec -it <container-id> cmd.exe` if you are using Windows containers, in your external terminal. It also:
|
||||
|
||||
- Automatically detects the default user for a running container from the image's Dockerfile. If no user is specified it defaults to `root`.
|
||||
- Persists your session if you navigate to another part of the Docker Dashboard and then return.
|
||||
- Supports copy, paste, search, and clearing your session.
|
||||
|
||||
To open the integrated terminal, either:
|
||||
- Hover over your running container and select the **Show container actions** menu. From the drop-down menu, select **Open in terminal**.
|
||||
- Select the container and then select the **Terminal** tab.
|
||||
|
||||
To use your external terminal, navigate to the **General** tab in **Settings** and select the **System default** option under **Choose your terminal**.
|
||||
|
||||
### Files
|
||||
|
||||
- Select **Files** to explore the filesystem of running or stopped containers. You can also:
|
||||
- See which files have been recently added, modified, or deleted
|
||||
|
@ -56,5 +69,3 @@ The **container view** displays **Logs**, **Inspect**, **Terminal**, **Files**,
|
|||
- Drag and drop files and folders between the host and the container
|
||||
- Delete unnecessary files when you right-click on a file
|
||||
- Download file and folders from the container straight to the host
|
||||
|
||||
- Select **Stats** to view information about the container resource utilization. You can see the amount of CPU, disk I/O, memory, and network I/O used by the container.
|
||||
|
|
Loading…
Reference in New Issue