-
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
HYPERKIT_CRASHED #7841
Comments
Hello. Could you try following commands?
If the problem remains, could you mind sharing the output of above |
➜ ~ minikube delete --all ❌ [HYPERKIT_CRASHED] Failed to start hyperkit VM. "minikube start" may fix it. creating host: create: Error creating machine: Error in driver during machine creation: hyperkit crashed! command line: |
➜ ~ minikube delete --all I0422 14:50:09.511430 71857 kubelet.go:43] stopping kubelet ... stderr: stderr: stderr: ❌ [CREATE_TIMEOUT] Failed to start docker container. "minikube start" may fix it. recreate: creating host: create host timed out in 120.000000 seconds |
Thank you for sharing your tried result.
It looks failed cannot accessing or writing home directory files.
|
|
Thank you for sharing. This looks no error log about starting machine... In above log, docker driver time outed.
However, maybe it's best to be able to get the Docker driver working on your machine I'm sorry many times. What is your docker's version?
If it's not latest, please consider upgrading your docker version. |
|
Thank you sharing. Now it looks there is a problem which cannot access artifact repository.
Could you check if you can access
If you cannot access with your proxy, please try once more |
yes. I got 401
If I Use proxy env variable NO_PROXY == 'localhost,127.0.0.1,10.96.0.0/12,192.168.99.0/24,192.168.39.0/24,gcr.io' |
I got this msg
in the latest log
|
The above error is returned the Could you check Or if the root cause is filesystem something, |
|
Thank you sharing. Now I don't understand what is root cause but I think this is bug or this is missing more detail of error.
I relabled this issue. |
If you can share more verbose output, please share the following command output?
|
The download took all night and still failed. Now 🏄 Done! kubectl is now configured to use "minikube" It's all about the proxy. Thank you very much for your help and your time these days. |
Thank you for sharing. |
$ hyperkit -versio
hyperkit: v0.20190802-4-g97f091
Homepage: https://github.com/docker/hyperkit
License: BSD
$ ls -la /usr/local/bin/hyperkit
lrwxr-xr-x 1 root admin 67 Apr 22 10:20 /usr/local/bin/hyperkit -> /Applications/Docker.app/Contents/Resources/bin/com.docker.hyperkit
$ minikube delete
$ minikube start --driver=hyperkit
😄 minikube v1.9.2 on Darwin 10.15.4
✨ Using the hyperkit driver based on user configuration
👍 Starting control plane node m01 in cluster minikube
🔥 Creating hyperkit VM (CPUs=2, Memory=4000MB, Disk=20000MB) ...
🤦 StartHost failed, but will try again: creating host: 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 ...
🔥 Creating hyperkit VM (CPUs=2, Memory=4000MB, Disk=20000MB) ...
❌ [HYPERKIT_CRASHED] Failed to start hyperkit VM. "minikube start" may fix it. creating host: 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
Upgrade to the latest hyperkit version
$ hyperkit -v
hyperkit: 0.20200224
$ ls -la /usr/local/bin/hyperkit
lrwxr-xr-x 1 yves admin 42 Apr 22 11:18 /usr/local/bin/hyperkit -> ../Cellar/hyperkit/0.20200224/bin/hyperkit
➔ ~ minikube delete
🔥 Deleting "minikube" in hyperkit ...
💀 Removed all traces of the "minikube" cluster.
➔ ~ minikube start --driver=hyperkit
😄 minikube v1.9.2 on Darwin 10.15.4
✨ Using the hyperkit driver based on user configuration
👍 Starting control plane node m01 in cluster minikube
🔥 Creating hyperkit VM (CPUs=2, Memory=4000MB, Disk=20000MB) ...
🤦 StartHost failed, but will try again: creating host: 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 ...
🔥 Creating hyperkit VM (CPUs=2, Memory=4000MB, Disk=20000MB) ...
❌ [HYPERKIT_CRASHED] Failed to start hyperkit VM. "minikube start" may fix it. creating host: 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
choose an alternate --driver virtualbox
➜ ~ minikube delete
🔥 Removing /Users/yves/.minikube/machines/minikube ...
💀 Removed all traces of the "minikube" cluster.
➔ ~ minikube start --driver=virtualbox
😄 minikube v1.9.2 on Darwin 10.15.4
✨ Using the virtualbox driver based on user configuration
👍 Starting control plane node m01 in cluster minikube
🔥 Creating virtualbox VM (CPUs=2, Memory=4000MB, Disk=20000MB) ...
🤦 StartHost failed, but will try again: creating host: create: creating: /usr/local/bin/VBoxManage storageattach minikube --storagectl SATA --port 0 --device 0 --type dvddrive --medium /Users/yves/.minikube/machines/minikube/boot2docker.iso failed:
VBoxManage: error: Could not get the storage format of the medium '/Users/yves/.minikube/machines/minikube/boot2docker.iso' (VERR_NOT_SUPPORTED)
VBoxManage: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component MediumWrap, interface IMedium, callee nsISupports
VBoxManage: error: Context: "OpenMedium(Bstr(pszFilenameOrUuid).raw(), enmDevType, enmAccessMode, fForceNewUuidOnOpen, pMedium.asOutParam())" at line 191 of file VBoxManageDisk.cpp
VBoxManage: error: Invalid UUID or filename "/Users/yves/.minikube/machines/minikube/boot2docker.iso"
🔥 Deleting "minikube" in virtualbox ...
🔥 Creating virtualbox VM (CPUs=2, Memory=4000MB, Disk=20000MB) ...
💣 Failed to start virtualbox VM. "minikube start" may fix it.: creating host: create: creating: /usr/local/bin/VBoxManage storageattach minikube --storagectl SATA --port 0 --device 0 --type dvddrive --medium /Users/yves/.minikube/machines/minikube/boot2docker.iso failed:
VBoxManage: error: Could not get the storage format of the medium '/Users/yves/.minikube/machines/minikube/boot2docker.iso' (VERR_NOT_SUPPORTED)
VBoxManage: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component MediumWrap, interface IMedium, callee nsISupports
VBoxManage: error: Context: "OpenMedium(Bstr(pszFilenameOrUuid).raw(), enmDevType, enmAccessMode, fForceNewUuidOnOpen, pMedium.asOutParam())" at line 191 of file VBoxManageDisk.cpp
VBoxManage: error: Invalid UUID or filename "/Users/yves/.minikube/machines/minikube/boot2docker.iso"
😿 minikube is exiting due to an error. If the above message is not useful, open an issue:
👉 https://github.com/kubernetes/minikube/issues/new/choose
choose an alternate --driver docker
➜ ~ minikube delete
🔥 Deleting "minikube" in virtualbox ...
💀 Removed all traces of the "minikube" cluster.
➔ ~ minikube start --driver=docker
😄 minikube v1.9.2 on Darwin 10.15.4
✨ Using the docker driver based on user configuration
👍 Starting control plane node m01 in cluster minikube
🚜 Pulling base image ...
E0422 11:40:23.244391 28666 cache.go:114] Error downloading kic artifacts: getting remote image: Get "https://gcr.io/v2/": dial tcp 108.177.97.82:443: i/o timeout
🔥 Creating Kubernetes in docker container with (CPUs=2) (4 available), Memory=1989MB (1989MB available) ...
🤦 StartHost failed, but will try again: creating host: create host timed out in 120.000000 seconds
🤷 docker "minikube" container is missing, will recreate.
🔥 Creating Kubernetes in docker container with (CPUs=2) (4 available), Memory=1989MB (1989MB available) ...
❌ [CREATE_TIMEOUT] Failed to start docker container. "minikube start" may fix it. recreate: creating host: create host timed out in 120.000000 seconds
The text was updated successfully, but these errors were encountered: