-
Notifications
You must be signed in to change notification settings - Fork 5k
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
High Sierra: Error in driver during machine creation: hyperkit crashed! #6079
Comments
Probably related: #5780 Do you mind sharing the output of My bet is that upgrading to the latest of whatever installed hyperkit (Docker or homebrew) will fix this. |
I reinstalled hyperkit and It worked.
Thanks
…On Monday, December 16, 2019, Thomas Strömberg ***@***.***> wrote:
Probably related: #5780
<#5780>
Do you mind sharing the output of hyperkit -version and ls -la
/usr/local/bin/hyperkit?
My bet is that upgrading to the latest of whatever installed hyperkit
(Docker or homebrew) will fix this.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#6079?email_source=notifications&email_token=ADMYUYXQXDHPWJAU253UFWDQY7A7ZA5CNFSM4J2B4OMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEG7TMDQ#issuecomment-566179342>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADMYUYTVCQZ6AHIU3UOGNJDQY7A7ZANCNFSM4J2B4OMA>
.
|
Great news. Thank you for the update! |
seems like although latest version is installed, minikube is still using an old one? brew upgrade hyperkit Warning: hyperkit 0.20190802 already installed
💡 Tip: Use 'minikube start -p ' to create a new cluster, or 'minikube delete' to delete this one. 💣 Unable to start VM. Please investigate and run 'minikube delete' if possible 😿 If the above advice does not help, please let us know: |
I had the same issues on Mac OS, though resolved it by simply updating Docker (since I had skipped multiple updates in the past). |
This is still an issue. OS: Mac Sonoma. Uninstalled/reinstalled hyperkit: crash. Restart system: crash. |
We can use the default Docker driver for Minikube on macOS Apple Silicon chips. To do this, we need to install the arm64 version of Minikube and start it with the default Docker driver.
The above setup works on macOS Sequoia Version 15.0.1, Apple M2 Chip. |
The exact command to reproduce the issue:
The full output of the command that failed:
when i am trying to start minikube with minikube start --vm-driver=hyperkit command ,i am getting below error.
minikube v1.6.1 on Darwin 10.13.6
✨ Selecting 'hyperkit' driver from existing profile (alternates: [])
🔥 Creating hyperkit VM (CPUs=2, Memory=2000MB, Disk=20000MB) ...
🔄 Retriable failure: create: Error creating machine: Error in driver during machine creation: hyperkit crashed! command line:
hyperkit loglevel=3 console=ttyS0 console=tty0 noembed nomodeset norestore waitusb=10 systemd.legacy_systemd_cgroup_controller=yes random.trust_cpu=on hw_rng_model=virtio base host=minikube
🔥 Deleting "minikube" in hyperkit ...
Please guide
The output of the
minikube logs
command:The operating system version:
The text was updated successfully, but these errors were encountered: