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.

Sign up for GitHub

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

Jump to bottom

High CPU usage on 2.5.0.1 #5078

Closed
2 tasks done
rbranche opened this issue Nov 19, 2020 · 3 comments
Closed
2 tasks done

High CPU usage on 2.5.0.1 #5078

rbranche opened this issue Nov 19, 2020 · 3 comments
Labels
lifecycle/locked version/2.5.0.1

Comments

@rbranche
Copy link

rbranche commented Nov 19, 2020 •
edited
Loading

  • I have tried with the latest version of my channel (Stable or Edge)
  • I have uploaded Diagnostics
  • Diagnostics ID: 2435E58B-D199-4C76-BEA8-8DB1B768EBBC/20201119181559

Expected behavior

CPU usage being below 10% with no CPU usage from containers

Actual behavior

100% CPU usage with very small CPU usage from containers

Screen Shot 2020-11-19 at 10 09 24 AM

Information

  • macOS Version: macOS Big Sur

Diagnostic logs

Docker for Mac: 2.5.0.1 (49550)

Steps to reproduce the behavior

Just regular Postgres docker containers running with no CPU usage between them.
@rbranche
Copy link
Author

This is likely a duplicate of #5044

@stephen-turner
Copy link
Contributor

Yes, dupe of #5044 and #5070.

@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 Dec 20, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
lifecycle/locked version/2.5.0.1
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@rbranche @stephen-turner @docker-robott