We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
CPU utilisation should not be impaired with Docker NOT running
System process constantly runs at around 35% after docker has been started, then stopped
The image below show docker VM not running, yet System CPU utilisation still at 35%
The only way I am able to return to normal is to uninstall docker then reboot the machine
The text was updated successfully, but these errors were encountered:
Likely - https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/high-cpu-utilisation-after-running-a-hyper-v-vm/053ed1ff-c737-4dab-96d4-29ffa663cd49?auth=1
Sorry, something went wrong.
Thanks for reporting! I suspect this is a dupe of #220, so closing.
Please re-open if that's not the case.
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
No branches or pull requests
Expected behavior
CPU utilisation should not be impaired with Docker NOT running
Actual behavior
System process constantly runs at around 35% after docker has been started, then stopped
Information
The image below show docker VM not running, yet System CPU utilisation still at 35%
The only way I am able to return to normal is to uninstall docker then reboot the machine
Steps to reproduce the behavior
The text was updated successfully, but these errors were encountered: