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

Windows 10 Docker processes consuming high CPU.. #4773

Closed
1 of 2 tasks
guanxine opened this issue Sep 21, 2019 · 4 comments
Closed
1 of 2 tasks

Windows 10 Docker processes consuming high CPU.. #4773

guanxine opened this issue Sep 21, 2019 · 4 comments

Comments

@guanxine
Copy link

guanxine commented Sep 21, 2019

  • I have tried with the latest version of my channel (Stable or Edge)
  • I have uploaded Diagnostics
  • Diagnostics ID:1DB7A834-1336-4391-97B2-C5353975B824/20190921044449

Expected behavior

Actual behavior

Information

  • Windows Version: win10 18362.356
  • Docker Desktop Version: 2.1.0.1(37199)

Steps to reproduce the behavior

  1. When my computer starts.. cup high
  2. ...
@jwhipp
Copy link

jwhipp commented Dec 17, 2019

I ran into this again today but I didn't notice the CPU usage initially, I attempted to run docker build and received this error:

Error response from daemon: mkdir /var/lib/docker/tmp/docker-builder723595540: read-only file system".

Upon looking at the task manager I see the vmmem cranking the CPU. I'd guess that the VM fails to boot correctly and is in a bad state.

As always, asking docker to restart (and thus bouncing the VM) solves the issue.

Version Information:

2.1.0.5 (40693) Stable
Windows 10 1909

@docker-robott
Copy link
Collaborator

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

@hartmanjan1970
Copy link

hartmanjan1970 commented Apr 12, 2020

same issue on my laptop.
There are multiple issues but they seems to refuse to give it some attention, while the issue is going on for some years.
Is a big act of disrespect of there users!!!!!!

@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 Jul 10, 2020
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

4 participants