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

docker/mac: high cpu usage and unresponsive on wake #316

Closed
mhat opened this issue Aug 17, 2016 · 5 comments
Closed

docker/mac: high cpu usage and unresponsive on wake #316

mhat opened this issue Aug 17, 2016 · 5 comments

Comments

@mhat
Copy link

mhat commented Aug 17, 2016

Steps to reproduce

  1. Have Docker running along with some container.
  2. Close Laptop.
  3. Go Home or Go to the Office.
  4. Open Laptop.
  5. Watch com.docker.hyperkit consume a majority of CPU until it's killed/restarted.

This has been going on since the private-beta. I assume it's not all that common or y'all would have fixed it by now. One possibility is that it's related to openvpn and having a active/open connection before closing the laptop. Then post-commute, on wake, the laptop is on a new network, openvpn shuts down the connection, etc.

It happens about twice a day. I'll update the issue tomorrow after I try to isolate if having the vpn up is really a factor or not.

Expected behavior

That com.docker.hyperkit doesn't consume all CPU when the laptop wakes up.

Actual behavior

com.docker.hyperkit consumes a majority of CPU until it is killed/restarted.

Information

Diagnostic ID: FB4CED9F-EB70-4E7C-81DE-6C1C5302EFDE
Docker for Mac: 1.12.0-beta22 (Build 11222)
macOS: Version 10.10.5 (Build 14F1808)
[ERROR]  docker-cli
         docker ps failed
[OK]     dns
[OK]     moby-syslog
[OK]     app
[OK]     disk
[OK]     system
[OK]     virtualization
[OK]     osxfs
[OK]     menubar
[OK]     db
[OK]     slirp
[OK]     logs
[OK]     moby-console
[OK]     vmnetd
[OK]     env
[OK]     moby
[OK]     driver.amd64-linux
@mhat
Copy link
Author

mhat commented Aug 17, 2016

screen shot 2016-08-16 at 8 06 18 pm

@mhat
Copy link
Author

mhat commented Aug 18, 2016

It seems to at least casually correlate to when I: have a vpn connection, close my laptop, and then hours later open my laptop in a new location on a new network with a different address range. E.g. commuting from home to the office and vice versa.

Also, I'm now running Version 1.12.1-rc1-beta23 (build: 11375)
2f0427ac7d4d47c705934ae141c3a248ed7fff40.

@shusugmt
Copy link

Hi I'm also facing the exact same problem and looking for a solution.
Tentatively going back to use docker-machine w/VirtualBox.

Version 1.12.0-a (build: 11213)
ad6ab836187e4111082447b7c0a6a74d01929a5c

@mchiang0610
Copy link

Merging with #82

@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 Jun 19, 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

5 participants