Docker for Mac 100% CPU consumption

[oscarrenalias]

Expected behavior

CPU consumption is very low, or zero, when no containers are running.

Actual behavior

Docker for Mac is currently consuming 100% of CPU (1 full core) on a 4-core mid-2014 Retina MBP 15". There are no containers running, and even old containers that were in stopped status have been removed.

Information

Diagnostic ID DF2FCECB-CD24-4209-BF81-04FCDC2D55D3.

Steps to reproduce the behavior

No clear steps available. Docker for Mac has been running for some time, always successfully, but a couple of hours ago started to show high CPU consumption. Tried restarting but the problem does not go away.

[jjjjw]

I think I am having the same problem.

I am running OSX Yosemite (10.10.5) on a mid-2014 MBP, and whenever I start docker the CPU is more or less immediately pinned at 100% with no containers running. The process primarily consuming the CPU is com.docker.hyperkit.

Docker version 17.03.1-ce, build c6d412e

Diagnostic ID: 9E2A24E0-970D-4B07-97E8-3CB72F9ABF7F

[egglang]

I am also having the same on Mid-2012 MBP.

[mizuluffyhwang]

I have the same issue with my 2016 MBP 15 with touch bar when running dockeredge. Had a look at the Activity Monitor, find "Hyperkit" had more than 200% CPU utilization even without any workload.

[AlbertoBarba]

Same issue on my mid 2014 MBP 15

[wolraich]

Same issue on mid-2012 MBP 15, El Capitan 10.11.6.

With no containers running, com.docker.hyperkit bursts over 150% cpu, and com.docker.osxfs runs up to 90%.

[wolraich]

Follow-up: I upgraded to Sierra 10.12.5 but still see the issue. Com.docker.hyperkit jumped us high as 298% with no containers. I try to avoid using docker with battery because it drains very quickly.

[jedie]

I can confirm this, and many other users, too, see: many "confirm" posts here: https://forums.docker.com/t/com-docker-hyperkit-up-cpu-to-340/13057

or:
moby/hyperkit#58
#1759

Any work-a-round?

[aurea-vijay]

Force killing the hyperkit process and restarting docker seems to have fixed the problem for me.

YMMV.

[akimd]

Please try a more recent version of Docker for Mac.

[docker-robott]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

[glyph]

/remove-lifecycle stale

[glyph]

I have this same issue. Not only does it use 100% CPU and murder my battery, it also seems to be preventing sleep, causing my laptop to get very hot and then hibernate with the lid closed.

[glyph]

Diagnostic ID: 1D83BF2B-37CD-4516-9408-59A7F75F39AB/20180527-230130

[pwaterz]

Same here running 18.05.0-ce-mac66 (24545).

I was running the pervious version and not having this issue.

[henryqhl]

Same. Version 18.03.0-ce-mac60 (23751)
Diagnostic ID: A94EC7C5-B2D2-4CE5-A6F6-50BDFCBB8076

[docker-robott]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

[rrdlpl]

its 2020 is there any fix for this?

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked