Minikube: not able to start minikube on mac

[anhtv08]

Hi,
I am trying to setup minikube on my mac machine

Below are environment:

nhs-MBP:~ anhtrang$ minikube version
minikube version: v0.26.1
anhs-MBP:~ anhtrang$ echo "";

anhs-MBP:~ anhtrang$ echo "OS:";
OS:
anhs-MBP:~ anhtrang$ cat /etc/os-release
cat: /etc/os-release: No such file or directory
anhs-MBP:~ anhtrang$ echo "";

anhs-MBP:~ anhtrang$ echo "VM driver":
VM driver:
anhs-MBP:~ anhtrang$ grep DriverName ~/.minikube/machines/minikube/config.json
    "DriverName": "virtualbox",
anhs-MBP:~ anhtrang$ echo "";

anhs-MBP:~ anhtrang$ echo "ISO version";
ISO version
anhs-MBP:~ anhtrang$ grep -i ISO ~/.minikube/machines/minikube/config.json
        "Boot2DockerURL": "file:///Users/anhtrang/.minikube/cache/iso/minikube-v0.26.0.iso",

Got following error:

nhs-MBP:~ anhtrang$ Starting local Kubernetes v1.10.0 cluster...
-bash: Starting: command not found
anhs-MBP:~ anhtrang$ Starting VM...
-bash: Starting: command not found
anhs-MBP:~ anhtrang$ E0420 08:24:57.963653   81977 start.go:159] Error starting host: Temporary Error: Error configuring auth on host: OS type not recognized.

Please advise

[mgdevstack]

Not able to start minikube 0.26.1 and 0.26.0:

0.26.1

0.26.0

[AishSundar]

/assignee @BenTheElder
/cc @krzyzacy

The vendors trying to write conformance tests seem to be blocked a lot on getting clusters up and running via Minikube. Is there a workaround or solution to help them be more productive. Can either of you please look at the error and advise a better developer workflow for them? Thanks.

[AishSundar]

Is there any alternative to Minikube that they can use for testing during development? Can the run their cases against a GKE cluster?

[AishSundar]

/cc @BenTheElder @krzyzacy

[AishSundar]

/priority important-soon

[anhtv08]

I am able to start minikube after upgrading the OS to Mac High Sierra, but I am not sure what exactly issue with prior High Sierra version

[mgdevstack]

@anhtv08, I'm on latest High Sierra 10.13.4, Minikube v0.25.2 is working well but not 0.26.* even after minikube delete && rm ~/.minikube .
btw I'm coping well with 0.25.2 😃

[mati865]

The same error on Arch Linux since upgrading to 0.26.x.

[johnhamelink]

I'm also experiencing this on Arch with the KVM2 driver

[fabriziocucci]

Same issue on macOS Sierra (version 10.12.6) with minikube 0.26.1.

I had to downgrade minikube to 0.25.2:

brew cask uninstall minikube
brew cask install https://raw.githubusercontent.com/caskroom/homebrew-cask/c899e526fa6e9211be92c4454ff9a7bb410622bc/Casks/minikube.rb

[nicknovitski]

I was able to start clusters with 0.26.1 and the hyperkit driver. High Sierra 10.13.4.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[hongsw]

rm -rf ~/.minikube
minikube start --logtostderr --v=3

!! DO NOT KILL minikube by CTRL-C
MUST use

minikube stop

ref. https://medium.com/@maumribeiro/troubleshooting-annoying-issues-with-minikube-34486955fc54

[charlseo]

Tried with 0.34.1 still not working so rolled back to 0.25.2 and it's fine.