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

[viartemev]

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT (minikube start failed, reason: _Failed to restart crio.service: Unit crio.service not found._)

Please provide the following details:

Environment:

Minikube version (use minikube version):

• OS: MacOS Sierra version 10.12.6
• VM Driver: virtualbox
• ISO version: minikube-v0.23.4.iso
• Install tools: -na-
• Others: -na-

What happened:
An error occurred during minikube startup.

What you expected to happen:
Minikube should start.

How to reproduce it (as minimally and precisely as possible):
minikube start

Output of minikube logs (if applicable):
minikube start
Starting local Kubernetes v1.8.0 cluster...
Starting VM...
E1029 14:30:42.234439 18732 start.go:150] Error starting host: Temporary Error: Error configuring auth on host: ssh command error: command : sudo systemctl -f restart crio err : Process exited with status 5 output : Failed to restart crio.service: Unit crio.service not found.

Anything else do we need to know:
minikube status
minikube: Running
cluster: Stopped
kubectl: Correctly Configured: pointing to minikube-vm at 192.168.99.100

[kugelr]

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

[JoshArmi]

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

Doing minikube delete && minikube start fixed the issue

[trstringer]

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.

[angshuman]

same issue with "minikube start" on windows.

[Sylvain-Delafoy]

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.

[kwaazaar]

Minikube delete did not work for me. This is my log:

C:\WINDOWS\system32> minikube start --vm-driver=hyperv
Starting local Kubernetes v1.8.0 cluster...
Starting VM...
E1107 21:05:01.258934 16028 start.go:150] Error starting host: Temporary Error: Error configuring auth on host: ssh co
mmand 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.
E1107 21:05:20.640822 16028 start.go:150] Error starting host: Temporary Error: Error configuring auth on host: ssh co
mmand 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.
E1107 21:05:38.955350 16028 start.go:150] Error starting host: Temporary Error: Error configuring auth on host: ssh co
mmand 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.
E1107 21:05:57.695839 16028 start.go:150] Error starting host: Temporary Error: Error configuring auth on host: ssh co
mmand 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 first started it in a Powershell windows that was not running with Administrator-rights. Also, I already had kubectl locally, including config file.

[r2d4]

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

[kwaazaar]

@r2d4 Check the first line of my comment: "Minikube delete did not work for me".
Btw: delete also returns an error: "Error deleting machine profile config".

[msnelling]

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.

[rbq]

Same here:

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

[knaepel]

Same Issue here:

PS C:\Users\knaepel\Documents> .\minikube.exe delete; .\minikube.exe start --vm-driver=hyperv
Deleting local Kubernetes cluster...
Machine deleted.
Error deleting machine profile config
Starting local Kubernetes v1.8.0 cluster...
Starting VM...
E1113 09:42:48.440279   10904 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.

[knaepel]

I'm switched from hyperv to virtualbox, works fine ...

[rafaelgaldencio]

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>

[seniorquico]

I can second what @rafaelgaldencio posted _for Windows 10 users_ (not sure if anything related exists for OP). I was able to get minikube running after setting up a new, external virtual switch using the notes in the documentation.

[rbq]

I use xhyve on macOS and minikube delete && minikube start actually fixed it, even without deleting the config or anything else.

[vladimirvivien]

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

Works for me on OSX

[sunanxiang]

minikube delete will have errors, then goto the vm to delete minikube file, finally goto the terminal minikube delete and minikube start will work.

[robertluwang]

delete and recreate minikube cluster working for me.

I have minikube v.0.22.2 before and created default vm minikube in virtualbox, after upgraded to v0.24.1 I directly to start minikube, got these errors:

$ minikube start
Starting local Kubernetes v1.8.0 cluster...
Starting VM...
E1209 12:10:07.451560 13164 start.go:150] Error starting host: Temporary Error: Error configuring auth on host: ssh command error:
command : sudo systemctl -f restart crio
err : Process exited with status 5
output : Failed to restart crio.service: Unit crio.service not found

deleted old cluster then start again, it created new cluster in new vm, then everything working fine:

$ minikube status
minikube: Running
cluster: Running
kubectl: Correctly Configured: pointing to minikube-vm at 192.168.99.101

[hendrakwong]

I also have the problem starting minikube using hyperv. I had win7 with virtualbox and I was able to run minikube fine. After I upgraded to win10 with hyperv, I had the same error as reported.

[zsfarkas]

The same here. :-( Windows 10 / Minikube v0.24.1 / kubectl v1.9.0

With Hyper-V, behind corporate proxy.

minikube stop && minikube delete does not help.

It also does not solve the problem, if I create a virtual switch (external as mentioned before) in Hyper-V-Manager.

Is there anybody, who manages to start minikube with the above circumstances?

[iszekely]

@zsfarkas Windows 10 / Minikube v0.24.1 / kubectl v1.9.1
The only difference is that I don't have a proxy.

I started to play with Minikube two weeks ago. It worked without a virtual switch. I ended up with a lot of deployments, pods, etc. and wanted to have a clean system, so I deleted everything. Minikube stopped working.

I created a virtual switch and it solved my issue. I have no idea why it worked without the switch first and then stopped working. Maybe the .iso was updated.

Please have a look at #2181

[jevy-wangfei]

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.

[nlachmann]

Had the same issue with win10, minikube version: v0.25.0 but it actually helped to:

• create a new virtual, extern switch in Hyper-V-Manager named "Primary Virtual Switch" (pick whatever you like)
• delete the old minikube vm
• remove %USERPROFILE%/.minikube

start over (run a cmd with Admin permission)

minikube stop
minikube delete
minikube start --vm-driver=hyperv --hyperv-virtual-switch="Primary Virtual Switch"
minikube status

[s-leonard]

I had the same issue as most people on here with Hyper-V on windows 10.

@rafaelgaldencio fix worked for me.
Creating a new External virtual switch in Hyper-V Manager

minikube stop
minikube delete
minikube start --vm-driver=hyperv --hyperv-virtual-switch=<your-custom-virtual-switch-name>

[jevy-wangfei]

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.

[NajeebArif]

i fixed this issue on Windows 10 by creating a hyperv external switch from hyperv-management
https://blogs.msdn.microsoft.com/wasimbloch/2017/01/23/setting-up-kubernetes-on-windows10-laptop-with-minikube/

This link helped me get through this coz i had already tried minikube delete && start but it did not work.

[asbjornu]

I just experienced this on macOS 10.12.6, minikube v0.25.0, kubectl version:

Client Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.4", GitCommit:"9befc2b8928a9426501d3bf62f72849d5cbcd5a3", GitTreeState:"clean", BuildDate:"2017-11-20T05:28:34Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"darwin/amd64"}

minikube delete and reinstall of minikube did not help.

[jueast08]

@kugelr MVP
Thanks for the fix. Worked perfectly on Ubuntu 17.10.1

[ryaz]

I was able to fix it by deleting VM from virtualbox and then minikube delete && minikube start

[wilddylan]

Hi, i Meet some questions, start with error:

➜  Desktop sudo minikube start
Starting local Kubernetes v1.10.0 cluster...
Starting VM...
Getting VM IP address...
Moving files into cluster...
Setting up certs...
Connecting to cluster...
Setting up kubeconfig...
Starting cluster components...
E0621 02:36:40.920379   43134 start.go:294] Error starting cluster:  kubeadm init error sudo /usr/bin/kubeadm init --config /var/lib/kubeadm.yaml --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests --ignore-preflight-errors=DirAvailable--data-minikube --ignore-preflight-errors=Port-10250 --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-etcd.yaml --ignore-preflight-errors=Swap --ignore-preflight-errors=CRI  running command: : running command: sudo /usr/bin/kubeadm init --config /var/lib/kubeadm.yaml --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests --ignore-preflight-errors=DirAvailable--data-minikube --ignore-preflight-errors=Port-10250 --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-etcd.yaml --ignore-preflight-errors=Swap --ignore-preflight-errors=CRI
.: Process exited with status 1
E0621 02:36:40.993075   43134 util.go:151] Error uploading error message: : Post https://clouderrorreporting.googleapis.com/v1beta1/projects/k8s-minikube/events:report?key=AIzaSyACUwzG0dEPcl-eOgpDKnyKoUFgHdfoFuA: read tcp 192.168.0.11:63055->172.217.27.138:443: read: connection reset by peer

Who can help me ?

OSX 10.13.6
minikube version: v0.28.0

[progsri]

minikube version: v0.28.0
minikube delete
minikube start
Above 2 commands ...worked for me as well.

[shridharmanvi]

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

[sandeep450]

can anyone help me with this error
[root@localhost ~]# minikube start --vm-driver=vmwarefusion
Starting local Kubernetes v1.10.0 cluster...
Starting VM...
E0917 19:06:32.353439 4086 start.go:174] Error starting host: Error starting stopped host: Maximum number of retries (5) exceeded.
Retrying.
E0917 19:06:32.695382 4086 start.go:180] Error starting host: Error starting stopped host: Maximum number of retries (5) exceeded
[root@localhost ~]#

[tstromberg]

Many of these comments represent issues other than the original person. I suspect the original issue is very obsolete ("Failed to restart crio.service: Unit crio.service not found."). Please open any other issues as new ones. Thanks!

[BIG-CHENG]

I got similar problem.

Take above suggestion to:

1. minikube delete
2. (no reinstall minikube (version: v0.33.1))
3. rm ~/.minikube
4. minikube start

Worked !! Thanks for suggestion.