Minikube: hyperkit macOS catalina: getting MAC address from UUID: vmnet: error from vmnet.framework: -1

Created on 11 Oct 2019 · 21Comments · Source: kubernetes/minikube

I am unable to start minikube with hyperkit on mac OS Catalina. I was able to run minikube before upgrading to Catalina.

The exact command to reproduce the issue:

minikube stop && minikube delete && minikube start --vm-driver=hyperkit

The full output of the command that failed:

✋ Stopping "minikube" in virtualbox ...
🛑 "minikube" stopped.
🔥 Deleting "minikube" in virtualbox ...
💔 The "minikube" cluster has been deleted.
😄 minikube v1.4.0 on Darwin 10.15
🔥 Creating hyperkit VM (CPUs=4, Memory=8192MB, Disk=20000MB) ...
🔄 Retriable failure: create: Error creating machine: Error in driver during machine creation: getting MAC address from UUID: vmnet: error from vmnet.framework: -1

🔥 Deleting "minikube" in hyperkit ...
E1010 22:01:41.581336 38132 main.go:100] libmachine: (minikube) Error reading pid file: open /Users/ashkanaleali/.minikube/machines/minikube/hyperkit.json: no such file or directory
🔥 Creating hyperkit VM (CPUs=4, Memory=8192MB, Disk=20000MB) ...
🔄 Retriable failure: create: Error creating machine: Error in driver during machine creation: getting MAC address from UUID: vmnet: error from vmnet.framework: -1

🔥 Deleting "minikube" in hyperkit ...
E1010 22:01:49.012099 38132 main.go:100] libmachine: (minikube) Error reading pid file: open /Users/ashkanaleali/.minikube/machines/minikube/hyperkit.json: no such file or directory
🔥 Creating hyperkit VM (CPUs=4, Memory=8192MB, Disk=20000MB) ...
🔄 Retriable failure: create: Error creating machine: Error in driver during machine creation: getting MAC address from UUID: vmnet: error from vmnet.framework: -1

🔥 Deleting "minikube" in hyperkit ...
E1010 22:01:58.676325 38132 main.go:100] libmachine: (minikube) Error reading pid file: open /Users/ashkanaleali/.minikube/machines/minikube/hyperkit.json: no such file or directory
🔥 Creating hyperkit VM (CPUs=4, Memory=8192MB, Disk=20000MB) ...
🔄 Retriable failure: create: Error creating machine: Error in driver during machine creation: getting MAC address from UUID: vmnet: error from vmnet.framework: -1

🔥 Deleting "minikube" in hyperkit ...
E1010 22:02:14.547227 38132 main.go:100] libmachine: (minikube) Error reading pid file: open /Users/ashkanaleali/.minikube/machines/minikube/hyperkit.json: no such file or directory

💣 Unable to start VM: create: Error creating machine: Error in driver during machine creation: getting MAC address from UUID: vmnet: error from vmnet.framework: -1

😿 Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
👉 https://github.com/kubernetes/minikube/issues/new/choose

The output of the minikube logs command:

💣 api load: filestore "minikube": Docker machine "minikube" does not exist. Use "docker-machine ls" to list machines. Use "docker-machine create" to add a new one.

😿 Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
👉 https://github.com/kubernetes/minikube/issues/new/choose

The operating system version: mac OS 10.15

chyperkit help wanted kinbug lifecyclrotten prioritimportant-longterm top-10-issues

Source

ashkan-leo

Most helpful comment

Hmm... I also had internet sharing turned on and got this issue. I wonder if that's the root cause of the issue? None of my co-workers were running into it.

mglidden on 16 Mar 2020

👍3

All 21 comments

Try deleting the /Users/ashkanaleali/.minikube directory and start minikube again and see if that helps

nanikjava on 11 Oct 2019

👍1

I deleted that directory. It didn't help.

ashkan-leo on 11 Oct 2019

I suspect there is some kind of Catalina-specific permissions issue going on, but it could also be some other kind of API mismatch. I don't have a Catalina host to check against yet.

tstromberg on 16 Oct 2019

I think this is related to https://github.com/kubernetes/minikube/issues/5610
and there is a upstream PR in hyperkit that seems to be addressing hyperkit issue on catalina https://github.com/moby/hyperkit/pull/263

medyagh on 30 Oct 2019

@ashkan-leo
I myself get this error, I suspect this is related to the latest verison of Docker

 $ docker version
Client: Docker Engine - Community
 Version:           19.03.4
 API version:       1.40
 Go version:        go1.12.10
 Git commit:        9013bf5
 Built:             Thu Oct 17 23:44:48 2019
 OS/Arch:           darwin/amd64
 Experimental:      false

do you mind sharing the version of docker"

medyagh on 30 Oct 2019

@ashkan-leo @natebrunette
do you mind sharing also your hyperkit version ?

hyperkit -v

one thing I noticed brew upgrade did NOT upgrade my hyperkit version ! which made debugging this issue more complicated.

medyagh on 31 Oct 2019

@medyagh I forgot to mention, I built hyperkit from master and all of my issues are resolved (re: #5610)

$ hyperkit -v
hyperkit: v0.20190802-4-g97f091-dirty

natebrunette on 31 Oct 2019

Excellent @natebrunette thank you so much for getting back to me !

I also confirm that upgrading both my docker and hyperkit driver fixed my issue too.
here are the versions on my mac machine:

$ hyperkit -v
hyperkit: v0.20190201-11-gc0dd46

Homepage: https://github.com/docker/hyperkit
License: BSD

$ docker version

Client: Docker Engine - Community
 Version:           19.03.4
 API version:       1.40

it worth noting that brew upgrade failed to upgrade my hyperkit. so I had to manually delete it.
anyone else has the issue here are the commands :

brew uninstall hyperkit
rm $(which hyperkit)
brew install hyperkit
hyperkit -v

make sure you download latest version of docker desktop from https://www.docker.com/products/docker-desktop

Update: it worth noting for some users,
re-installing docker for desktop and restarting laptop also helped ! (see https://github.com/kubernetes/minikube/issues/5819#issuecomment-550256530)

medyagh on 31 Oct 2019

so the new release is already tagged?

natebrunette on 31 Oct 2019

Neither HyperKit version 0.20190201 nor 0.20190802 works on my machine.

Using minikube 1.5.2, hyperkit 0.20190802 and macOS 10.15.0

Update: while upgrading macOS, minikube and hyperkit didn't work, after I upgraded Docker Desktop, minikube somehow started working.

fredsted on 5 Nov 2019

Since it's been a few months now I'm trying to get a release tagged so we can get this update into Homebrew, see https://github.com/moby/hyperkit/issues/267.

mjgallag on 25 Jan 2020

New version of hyperkit with Catalina fix is finally available on Homebrew, see https://github.com/Homebrew/homebrew-core/pull/50655 & https://github.com/moby/hyperkit/issues/267 for details.

mjgallag on 10 Mar 2020

I seem to also get this problem on the latest version of hyperkit when my mac's internet sharing is turned on and in use

BoKleynen on 16 Mar 2020

👍3

Hmm... I also had internet sharing turned on and got this issue. I wonder if that's the root cause of the issue? None of my co-workers were running into it.

mglidden on 16 Mar 2020

👍3

I ran into this today, and strangely enough, re-running minikube got past the issue. This was with hyperkit: v0.20190802-4-g97f091.

tstromberg on 24 Mar 2020

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 on 22 Jun 2020

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 on 22 Jul 2020

Still having this message on the latest version (I also have internet sharing over wifi on). Any solution for this?

cglacet on 3 Aug 2020

@cglacet do you mind sharing output with latest verison of minikube?

medyagh on 12 Aug 2020

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

fejta-bot on 11 Sep 2020

@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.