top of page

Docker Stats

Docker provides a handy tool called docker stats that allows users to monitor various metrics related to running containers in real-time. In this blog post, we will explore Docker stats and how it can be utilized to gain insights into container resource usage.

Understanding Docker Stats

Docker stats provides a real-time stream of performance data for running containers. This information includes CPU usage, memory usage, network activity, and block I/O. With docker stats, you can quickly assess the health and resource utilization of your containers.


To get started, open a terminal and use the following command:

[root@siddhesh ~]# docker stats cdba0562a15c
CONTAINER           CPU %               MEM USAGE / LIMIT       MEM %               NET I/O             BLOCK I/O           PIDS
cdba0562a15c        0.00%               3.559 MiB / 15.33 GiB   0.02%               11.3 kB / 11.5 kB   0 B / 0 B           5


CONTAINER ID: The unique identifier for the container.

CPU %: The percentage of CPU usage.

MEM USAGE / LIMIT: The current memory usage and the memory limit.

MEM %: The percentage of memory usage.

NET I/O: Network Input/Output.

BLOCK I/O: Block Input/Output.

Understanding the Metrics

CPU %: This metric represents the percentage of CPU resources used by the container. A value of 100% indicates that the container is using all available CPU resources.

MEM USAGE / LIMIT: This shows the current memory usage and the memory limit set for the container. If the memory usage approaches the limit, it may lead to performance issues.

MEM %: The percentage of memory usage compared to the container's memory limit.

NET I/O: This indicates the amount of data sent and received over the network by the container.

BLOCK I/O: Represents the block input/output operations.

Docker stats is a valuable tool for troubleshooting container performance issues. If a container is exhibiting unexpected behavior or performance degradation, monitoring its resource usage with docker stats can help identify the root cause.

bottom of page