content/manuals/desktop/use-desktop/container.md
The Containers view lists all running and stopped containers and applications. It provides a clean interface to manage the lifecycle of your containers, interact with running applications, and inspect Docker objects—including Docker Compose apps.
Use the Search field to find a specific container by name.
From the Containers view you can:
docker run command for reuse or modificationFrom 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.
When you 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.
You can obtain detailed information about the container when you select it.
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.
Select Logs to view output from the container in real time. While viewing logs, you can:
Cmd + f/Ctrl + f to open the search bar and find specific entries.
Search matches are highlighted in yellow.Enter or Shift + Enter to jump to the next or previous search match
respectively.You can refine your view by:
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.
If you have not enabled Docker Debug in settings, the Exec tab displays. It lets you quickly run commands within your running container.
Using the Exec tab is the same as running one of the following commands:
docker exec -it <container-id> /bin/shdocker exec -it <container-id> cmd.exe when accessing Windows containersFor more details, see the docker exec CLI reference.
If you have enabled Docker Debug in settings, or toggled on Debug mode to the right of the tab options, the Debug tab displays.
Debug mode has several advantages, such as:
vim, nano, htop, and curl. For more details, see the docker debug CLI reference.To use debug mode:
To use debug mode by default, navigate to the General tab in Settings and select the Enable Docker Debug by default option.
Select Files to explore the filesystem of running or stopped containers. You can also: