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

Exiting due to GUEST_START #18506

Open
rsergio07 opened this issue Mar 25, 2024 · 2 comments
Open

Exiting due to GUEST_START #18506

rsergio07 opened this issue Mar 25, 2024 · 2 comments
Labels
kind/support Categorizes issue or PR as a support question. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. long-term-support Long-term support issues that can't be fixed in code

Comments

@rsergio07
Copy link

What Happened?

I was following along the "https://kubernetes.io/docs/tutorials/hello-minikube/," but I got this message: ❌ Exiting due to MK_UNIMPLEMENTED: minikube service is not currently implemented with the builtin network on QEMU, try starting minikube with '--network=socket_vmnet' when trying the following command: minikube service hello-node

So, I tried to start the minikube service again following the recommendation made by the system: minikube start --network=socket_vmnet but I got a new error:

❌ Exiting due to GUEST_START: failed to start node: wait 6m0s for node: wait for healthy API server: apiserver healthz never reported healthy: context deadline exceeded

Attach the log file

logs.txt

Operating System

macOS (Default)

Driver

QEMU

@Ritikaa96
Copy link

/kind support

@k8s-ci-robot k8s-ci-robot added the kind/support Categorizes issue or PR as a support question. label Apr 8, 2024
@spowelljr spowelljr added the long-term-support Long-term support issues that can't be fixed in code label Jun 5, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/support Categorizes issue or PR as a support question. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. long-term-support Long-term support issues that can't be fixed in code
Projects
None yet
Development

No branches or pull requests

5 participants