minikube: Failed to restart crio.service: Unit crio.service not found.

Ran into the same issue. However I am working on Linux. The following steps did the trick for me:

1. Uninstall/delete all minikube related files 1.1. minikube delete 1.2. rm /usr/local/minikube 1.3. rm -rf ~/.minikube

2. Reinstall minikube 2.1. (For Linux) curl -Lo minikube https://storage.googleapis.com/minikube/releases/v0.23.0/minikube-linux-amd64 && chmod +x minikube && sudo mv minikube /usr/local/bin/ 2.2. minikube start

Had the same issue present on my mac running similar set up.

Doing minikube delete && minikube start fixed the issue

Those using Windows with Hyper-V try creating a new external virtual switch in Hyper-V Manager, then start Minikube with minikube start --vm-driver=hyperv --hyperv-virtual-switch=<your-custom-virtual-switch-name>

Same here:

$ minikube delete && minikube start
Deleting local Kubernetes cluster...
Machine deleted.
Error deleting machine profile config

minikube stop # ensure its not still running
minikube delete && minikube start

Works for me on OSX

In my situation, it is caused by network.

Problem analysing:

• During the starting of Minikube, it requires to connect public network to download some packages from inside the VM machine.
• On my machine, it could not get an ipv4 address from DHCP server, and a ipv6 ip was obtained by Minikube instead. Because my network does not support ipv6, the VM could not access network.
• Minikube seems need a DHCP server to allocate its instances IPs (I am not sure yet.)

Solution:

• Create a Hyper-v Virtual Switch using Internet Network connection type.
• At the host machine network connections interface, right click the Hyper-V virtual adaptor and ensure that:
  • Automatically obtain IP address
  • Advanced -> DHCP is on
• At the host machine, sharing the connected network to the new internet virtual switch
• Start minikube: minikube start --vm-driver hyperv --hyperv-virtual-switch internal-switch-name -v7
• Monitor and ensure your VM abstained an ipv4 address correctly.
• If your VM still get an ipv6 address, try something else to ensure your VM could obtain an ipv4 address from a DHCP server.

Problem of restart minikube and solution

• Some time, after restart you host machine, your minikube may not work.
• Stop minikube and check your minikube VM ip address.
• If it changed to ipv6 again, trying stop the network sharing from host machine, and re-sharing network. Ensure your Hyper-V Virtual adopter could identify your network.

Same issue here. except status is 1:

C:\Users\PC>bin\minikube.exe start --vm-driver hyperv
Starting local Kubernetes v1.8.0 cluster...
Starting VM...
E1103 10:48:59.321083   15840 start.go:150] Error starting host: Error creating host: Error executing step: Provisioning VM.
: ssh command error:
command : sudo systemctl -f restart crio
err     : Process exited with status 1
output  : Job for crio.service failed because the control process exited with error code.
See "systemctl status crio.service" and "journalctl -xe" for details.
.

 Retrying.
E1103 10:48:59.330088   15840 start.go:156] Error starting host:  Error creating host: Error executing step: Provisioning VM.
: ssh command error:
command : sudo systemctl -f restart crio
err     : Process exited with status 1
output  : Job for crio.service failed because the control process exited with error code.
See "systemctl status crio.service" and "journalctl -xe" for details.

I am also getting this error with minikube v0.23.0 on Windows 10 1709. minikube delete didn’t help me either, neither did removing all trace of .minikube and .kube directories and rebooting.

@kwaazaar you should run minikube delete and a minikube start to fix that issue after upgrading.

Ran into same issue. I had to run the following commands: rm /usr/local/bin/minikube && brew cask install minikube

If ssh error, try this: Minikube uses system ssh by default. But windows system don’t have a ssh by default. Try using git bash as terminal have try. If it is not work, try re-install git bash as system ssh client.

same issue with “minikube start” on windows.

I’m on Linux (Fedora 26) and ran into the same issue. @JoshArmi’s solution worked in my environment too, $ minikube delete && minikube start. Then it was working perfectly.