2.5.0.1 High CPU usage

[Nuru]

• I have tried with the latest version of my channel (Stable or Edge)
• I have uploaded Diagnostics
• Diagnostics ID: 7DDDF979-417F-442C-B930-719FC131249A/20201130184239

Actual behavior

I have several containers running which mount my home directory into the containers with --volume=$HOME:/local. Running a shell script from a host terminal (that presumably obtained some sort of file lock on the directory) in one of those directories sent Hyperkit into > 300% CPU usage.

Information

• macOS Version: macOS 10.15.7 (19H15) (Catalina)
• Use gRPC FUSE for file sharing enabled

My guess is that #5044 is actually several issues in one and this is one of them.

Diagnostic logs

Docker for Mac: 2.5.0.1 (49550)

[stephen-turner]

I guess the question is what the shell script actually does. If it does a lot of file changes, then it wouldn't surprise me that hyperkit gets very busy as everything has to be sync'ed across the VM boundary. But if there's something particular that the shell script is doing that confuses hyperkit, then that's a bug that could be fixed.

[Nuru]

@stephen-turner As it turns out, the script had a bug, and it was just running an infinite recursive loop. Should not have been doing anything to the file system, just eating up CPU and memory.

function foo() { foo bar baz; }

[kumarunster]

similar issue here. After upgrade docker for mac to the version 2.5.0.1 I see relatively high cpu time on com.docker.hypervisor process. It is incredibly how fast the battery is empty. as well it seems to be the cause for running fans on my macbook.

For me it looks as the same issue from 2019, closed few weeks ago: #4981

Containers itself are idle, nearly zero cpu usage, but docker engine is running incredible high amount of cpu.

PID file analytics:
Analyse von „com.docker.hyperkit“.txt

[stephen-turner]

Could you both try the most recent build pasted in #5044? We discovered a regression in the latest Linux kernel. That build reverts the kernel to an earlier version, and most users say it has solved their CPU problems.

[kumarunster]

@stephen-turner many thanks for the link in #5044 ! seems that the new version reduced the load by half now. will keep one eye on it.

[retrodude]

I tried different offcial versions 2.5.0.1, 2.4.0, 2.3.0.4 but with all of them, hyperkit had very high CPU > 600% (without any running containers) on my system.
Luckily I found the Link to Version 2.4.2 in this thread which workes for me! (CPU 8%).

Addendum: the new Version 2.5.4 workes too!

MacOS 10.14.6, MacBook Pro 3,1 Ghz i7 (4 Cores, 8 Hyperthreads) 16GB
Docker configured Resources: CPU: 6, Memory: 10 GB, Swap 4 GB.

[n13]

I tried different offcial versions 2.5.0.1, 2.4.0, 2.3.0.4 but with all of them, hyperkit had very high CPU > 600% (without any running containers) on my system.
Luckily I found the Link to Version 2.4.2 in this thread which workes for me! (CPU 8%).

Addendum: the new Version 2.5.4 workes too!

MacOS 10.14.6, MacBook Pro 3,1 Ghz i7 (4 Cores, 8 Hyperthreads) 16GB
Docker configured Resources: CPU: 6, Memory: 10 GB, Swap 4 GB.

Where - on what official page - can this 2.5.4 release be found? I only see up to 2.5.3 on the "edge" releases on the Docker page.

I need to verify it's an actual legitimate build before letting it run wild on my system (I really need VMs running OS X...)

@retrodude

[stephen-turner]

2.5.4 is not released yet. We're expecting to release it later today, but it might not be that exact build.

[n13]

Great thanks ! Would be very nice. Edit - its up now on the official page, thanks! https://docs.docker.com/docker-for-mac/edge-release-notes/

[stephen-turner]

Yup, 2.5.4 (build 50534) is now released and fixes this bug, so I'll close this ticket.

If you're on the Stable channel, we're planning a release including this later this week.

[n13]

This build dropped CPU of com.docker.hyperkit to 2% with 1 core assigned to Docker (8 core i9)- much better than before, still less than ideal but I guess on par with what it was before. I don't understand why it's using any CPU when no containers are running.

[stephen-turner]

The VM is always running and may use a little bit of CPU.

[Niek]

I can confirm that upgrading to 2.5.4 fixed high idle CPU for me.

[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