Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

High CPU Load without running a single container #5636

Closed
2 of 3 tasks
ceelian opened this issue Apr 28, 2021 · 2 comments
Closed
2 of 3 tasks

High CPU Load without running a single container #5636

ceelian opened this issue Apr 28, 2021 · 2 comments

Comments

@ceelian
Copy link

ceelian commented Apr 28, 2021

  • I have tried with the latest version of Docker Desktop
  • I have tried disabling enabled experimental features
  • I have uploaded Diagnostics
  • Diagnostics ID: F384ADE4-F5EF-4664-8EA2-22EC0A099D81/20210428152258

Expected behavior

com.docker.hyperkit does not use 100% CPU when no container is running.

Actual behavior

com.docker.hyperkit uses 100% CPU even without having a single container running.

Information

The fans are constantly running on a macbook pro 2,4 GHz 8-Core Intel Core i9 with 64GB memory without having a single docker container running.

Docker Ressources Settings:

  • 8 "CPU Cores" (out of the 16) are dedicated to docker
  • 32 GB memory is dedicated to docker
  • 1GB Swap
  • 128 GB Disk Image Size (currently 37GB used)

Further information:

  • Is it reproducible?
    yes
  • Is the problem new?
    yes
  • Did the problem appear with an update?
    yes, updating to the most recent docker desktop version, not sure which one I'd used before

System :

  • macOS Version: 11.2.3 (20D91)
  • Intel chip or Apple chip: Intel
  • Docker Desktop Version: 3.3.1 (63152)

Steps to reproduce the behavior

  1. start docker desktop and make sure no container is running in the docker desktop dashboard
  2. check the macOS activity monitor look for the cpu load of com.docker.hyperkit
  3. stop docker desktop
  4. check the macOS activity monitor again look for the cpu load of com.docker.hyperkit
@ceelian
Copy link
Author

ceelian commented Apr 28, 2021

might be a duplicate of #5116

@ceelian ceelian closed this as completed Apr 28, 2021
@docker-robott
Copy link
Collaborator

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

@docker docker locked and limited conversation to collaborators May 28, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants