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

minikube status take long time when paused on docker driver #15076

Closed
medyagh opened this issue Oct 5, 2022 · 1 comment · Fixed by #15077
Closed

minikube status take long time when paused on docker driver #15076

medyagh opened this issue Oct 5, 2022 · 1 comment · Fixed by #15077
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@medyagh
Copy link
Member

medyagh commented Oct 5, 2022

What Happened?

Quoting from Chris

" I've also noticed that when my cluster is paused, minikube status runs much more slowly. If the cluster is stopped, it takes around 0.15 seconds. If started, about 0.25 seconds. But if paused, it's more like 16 seconds. "

Driver

Docker Driver

@medyagh medyagh added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Oct 5, 2022
@medyagh medyagh added the kind/bug Categorizes issue or PR as related to a bug. label Oct 5, 2022
@spowelljr
Copy link
Member

spowelljr commented Oct 5, 2022

This seems to be specific to Docker driver. I tried HyperKit and KVM and for both of them the apiserver status is Paused and the status call is instant. On Docker it keeps trying to curl the apiserver and the call fails and it keeps retrying, hence why it takes so long.

The VM drivers, it uses the freezer gcroup to detect the status:
freezer state: "FROZEN"
But with Docker:
unable to find freezer cgroup: sudo egrep ^[0-9]+:freezer: /proc/1821/cgroup: Process exited with status 1
So then it tries doing the HTTP curls as a backup which makes the call take a long time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants