Score:0

docker stats reports the same memory usage for each container

cn flag

On our server with 16 GB RAM, docker stats --no-stream reports the same MEM USAGE value for each container:

docker stats --no-stream
CONTAINER ID   NAME                 CPU %     MEM USAGE / LIMIT     MEM %     NET I/O           BLOCK I/O       PIDS
1ee032e01189   webprotege           9.42%     7.211GiB / 15.63GiB   46.14%    1.73MB / 6.92MB   3.86GB / 40GB   454
9432aa1e98d9   webprotege-mongodb   9.72%     7.211GiB / 15.63GiB   46.14%    726kB / 430kB     3.86GB / 40GB   454
60430227a719   clever_kare          9.74%     7.211GiB / 15.63GiB   46.14%    2.73kB / 1.36kB   3.86GB / 40GB   454
ee945035014f   ols-ols-web-1        9.54%     7.211GiB / 15.63GiB   46.14%    158MB / 146MB     3.86GB / 40GB   454
cbde532970d5   ols-mongo-1          9.58%     7.211GiB / 15.63GiB   46.14%    112MB / 157MB     3.86GB / 40GB   454
dfb2b7ad76fe   ols-solr-1           15.13%    7.211GiB / 15.63GiB   46.14%    4.16MB / 627kB    3.86GB / 40GB   454

However htop only reports that 4.74GB/15.6GB RAM is used. How can I see the memory stats for each container separately? Docker has version 20.10.17, build 100c701 and runs rootless on a Linux VM.

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.