minikube: hyperkit: /var/db/dhcpd_leases: no such file or directory -> could not find an IP address
I have reinstalled minikube using brew and it works if the driver is virtual box. I have docker desktop working and I can select between docker desktop kubernetes and minikube if minikube is running on virtualbox.
I added a dhcpd_leases file in the /var/db directory and the error changed to: error: could not find an IP address for de:57:7:ad:86:12
The exact command to reproduce the issue: minikube start --memory 2000MB --disksize 20000MB
The full output of the command that failed:
minikube v1.6.1 on Darwin 10.14.6 ✨ Automatically selected the ‘hyperkit’ driver (alternates: [virtualbox]) 🔥 Creating hyperkit VM (CPUs=2, Memory=2000MB, Disk=20000MB) … 🔄 Retriable failure: create: Error creating machine: Error in driver during machine creation: IP address never found in dhcp leases file Temporary error: open /var/db/dhcpd_leases: no such file or directory 🔥 Deleting “minikube” in hyperkit … 🔥 Creating hyperkit VM (CPUs=2, Memory=2000MB, Disk=20000MB) … 🔄 Retriable failure: create: Error creating machine: Error in driver during machine creation: IP address never found in dhcp leases file Temporary error: open /var/db/dhcpd_leases: no such file or directory 🔥 Deleting “minikube” in hyperkit … 🔥 Creating hyperkit VM (CPUs=2, Memory=2000MB, Disk=20000MB) … 🔄 Retriable failure: create: Error creating machine: Error in driver during machine creation: IP address never found in dhcp leases file Temporary error: open /var/db/dhcpd_leases: no such file or directory 🔥 Deleting “minikube” in hyperkit …
💣 Unable to start VM: create: Error creating machine: Error in driver during machine creation: IP address never found in dhcp leases file Temporary error: open /var/db/dhcpd_leases: no such file or directory
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: macOS Mojave 10.14.6
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 2
- Comments: 18 (5 by maintainers)
I no longer have a mac and retired. I forgot about this issue. Sorry, I am closing it now.
I’m also seeing this issue when I try to use
minikube+hyperkitin a github action on github’smacos-latestaction runner image. Minikube 1.12.0:Interestingly sometimes re-running the job works.
I don’t think I am going to be very helpful in solving this issue. I did attach a file with the output of fs_usage just in case it might help. fs_usage-output.txt
I work for a healthcare company and I suspect our security folk have done something with the proxy that is causing this error. I believe minikube was working a few weeks ago, but I recently upgrade to mojave. I have not heard of any changes in our security polices, but I would not be surprised that with the update of the OS, they put in some changes to the way the mac proxy works. If this is true, I probably can’t back out the changes or make changes that could test any fixes. It does work with virtualbox and my docker desktop version of kubernetes is working.
I would be happy to try things, but I may not be able make changes to my machine that might solve this issue.