-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
MacOS/virtualbox w/ VPN: stuck on "Starting cluster components..." #3503
Comments
I am also facing the same issue. |
I tried the same steps like @viveks4grps, I even reinstalled virtualbox.. Still no luck. |
+1 |
Any tips on how to debug this? |
Not sure If I am seeing the same issue - but dns resolution on the minikube guest fails. The nameserver seems to be incorrect, or perhaps virtualbox 6.x has some kind of dns / host network issue. |
I ran into the same issue as above, I went through deleting the VM, removing ~/.minikube and such as well. The fix was to remove the virtualbox network and have minikube/virtualbox create a new one on boot. |
Hi @mikesplain, can you tell more detailed what you did?
then deleted the network vboxnet0 from the virtual box gui, rebooted my mac and run:
there it still got stuck. The logs show a diffrent error though:
|
Personal tip: disconnect to any VPN you might be connected to. Depending on the VPN client, you might even need to completely close it (this was the case with Cisco AnyConnect for me). |
@TheKangaroo my solution involved actually deleting the network in virtualbox as well (as seen in this photo). |
okay, @mikesplain, I did the same thing but it didn't help. |
I think @mikesplain, you are spot on. I rebooted my Mac Book too, and then everything started working. |
Correct, when I reboot my mac, the following happens:
So I guess AnyConnect configures something when connecting to a VPN, but does not properly reset it after disconnecting. A reboot of the system resets it. |
@TheKangaroo that might be the DNS cache. Try running |
flushing the dns cache after disconnecting from AnyConnect didn't solve the issue for me |
I have the same issue but this is on version 1.13.2. I have done everything mentioned in this thread but am curious if anyone has any other suggestions. I have my log below and man it's full of, well, errors. Thx much |
Related: #3145 |
@douglascamata Thanks for suggestion regarding Cisco AnyConnect. I would NEVER have thought having it open without a VPN connection would cause this issue, but alas... |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@douglascamata Thanks so much ! Killing the Cisco Any Connect App worked for me. |
Is this a BUG REPORT or FEATURE REQUEST?: Bug report
Please provide the following details:
Environment:
What happened:
I try to start minikube on my newly set up MacBook. I installed virtualbox and minikube via brew cask.
When I run
minikube start
it starts the virtualbox VM and start to configure stuff, but it got stuck at this point:At this point, it hangs forever.
How to reproduce it:
I just installed virtualbox and minikube via brew cask on a fresh installation of MacOS.
Next I ran
minikube start
and the issue occured.Output of
minikube logs
(if applicable):Anything else do we need to know:
If I can provide more information, let me know.
The text was updated successfully, but these errors were encountered: