Open piontec opened 7 years ago
@piontec Thanks for your feedback.
Just to double check that the docker daemon unresponsive
means all API calls unresponsive or docker ps
unresponsive?
And can you give some hints how to make the processes in container turn to state "D"?
Description Our monitoring detected docker performance problems rising slowly - checked with
docker ps
,docker info
anddocker run
calls. At the same time about 100 processes with "D" state were detected in the system. Increasing number of "D" processes eventually renders docker daemon unresponsive. This was confirmed on multiple occasions (at least 5 times).Steps to reproduce the issue:
Describe the results you received: Docker API response time grow and eventually render the whole daemon unresponsive.
Additional information you deem important (e.g. issue happens only occasionally): Is repeatable, happens every time the number of "D" processes on the host rises.
Output of
docker version
:Output of
docker info
:Additional environment details (AWS, VirtualBox, physical, etc.):
Linux ip-10-69-11-89 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux