minikube: hyperv failure: sudo systemctl -f restart crio err : Process exited with status 1

If this is a BUG REPORT, please:

Fill in as much of the template below as you can. If you leave out information, we can’t help you as well.

Please provide the following details:

Environment:

minikube version: v0.24.1 OS: Windows 10 VM driver: hyperv ISO version “Boot2DockerURL”: “file://C:/Users/Andreas Höhmann/.minikube/cache/iso/minikube-v0.23.6.iso”,

What happened: I’m not be able to try a “minimal, default” minikube scenario … I read some blogs/howtos … It should be really easy (in theory) …

$ minikube start I0102 12:41:22.266728 I0102 12:41:22.635729 Starting local I0102 12:41:22.635729 Starting VM… I0102 12:41:22.635729 I0102 12:41:22.635729 I0102 12:41:22.635729 I0102 12:41:22.635729 I0102 12:41:22.635729 I0102 12:41:22.636729 I0102 12:41:22.637731 I0102 12:41:22.637731 I0102 12:41:22.637731 Downloading Creating SSH key… Creating VM… Using switch “minikube” Creating VHD Starting VM… Waiting for host to start… I0102 12:43:11.755877 I0102 12:43:11.801876 I0102 12:43:11.814881 I0102 12:43:11.819876 I0102 12:43:11.827878 I0102 12:43:11.832877 Setting Docker E0102 12:43:26.730760 : ssh command error: command : sudo err : Process exited with status 1 output : Job See “systemctl . --vm-driver=hyperv --hyperv-virtual-switch=minikube --disk-size=10g --memory=2048 --alsologtostderr --v=3 8496 notify.go:109] Checking for updates… 8496 cache_images.go:290] Attempting to cache image: gcr.io/google_containers/kubernetes-dashboard-amd64:v1.6.3 at C:\Users\Andreas Höhmann.minikube\cache\images\gcr.io\google_containers\kubernetes-dashboard-amd64_v1.6.3 Kubernetes v1.8.0 cluster… 8496 cache_images.go:290] Attempting to cache image: gcr.io/k8s-minikube/storage-provisioner:v1.8.0 at C:\Users\Andreas Höhmann.minikube\cache\images\gcr.io\k8s-minikube\storage-provisioner_v1.8.0 8496 cache_images.go:290] Attempting to cache image: gcr.io/google_containers/pause-amd64:3.0 at C:\Users\Andreas Höhmann.minikube\cache\images\gcr.io\google_containers\pause-amd64_3.0 8496 cache_images.go:290] Attempting to cache image: gcr.io/google_containers/k8s-dns-dnsmasq-nanny-amd64:1.14.5 at C:\Users\Andreas Höhmann.minikube\cache\images\gcr.io\google_containers\k8s-dns-dnsmasq-nanny-amd64_1.14.5 8496 cache_images.go:290] Attempting to cache image: gcr.io/google_containers/k8s-dns-sidecar-amd64:1.14.5 at C:\Users\Andreas Höhmann.minikube\cache\images\gcr.io\google_containers\k8s-dns-sidecar-amd64_1.14.5 8496 cache_images.go:290] Attempting to cache image: gcr.io/google-containers/kube-addon-manager:v6.4-beta.2 at C:\Users\Andreas Höhmann.minikube\cache\images\gcr.io\google-containers\kube-addon-manager_v6.4-beta.2 8496 cache_images.go:290] Attempting to cache image: gcr.io/google_containers/k8s-dns-kube-dns-amd64:1.14.5 at C:\Users\Andreas Höhmann.minikube\cache\images\gcr.io\google_containers\k8s-dns-kube-dns-amd64_1.14.5 8496 cluster.go:70] Machine does not exist… provisioning new machine 8496 cache_images.go:78] Successfully cached all images. 8496 cluster.go:71] Provisioning machine with config: {MinikubeISO:https://storage.googleapis.com/minikube/iso/minikube-v0.23.6.iso Memory:2048 CPUs:2 DiskSize:10000 VMDriver:hyperv XhyveDiskDriver:ahci-hd DockerEnv:[] InsecureRegistry:[] RegistryMirror:[] HostOnlyCIDR:192.168.99.1/24 HypervVirtualSwitch:minikube KvmNetwork:default Downloader:{} DockerOpt:[] DisableDriverMounts:false} 8496 downloader.go:56] Not caching ISO, using https://storage.googleapis.com/minikube/iso/minikube-v0.23.6.iso C:\Users\Andreas Höhmann.minikube\cache\boot2docker.iso from file://C:/Users/Andreas Höhmann/.minikube/cache/iso/minikube-v0.23.6.iso… 8496 ssh_runner.go:57] Run: sudo rm -f /etc/docker/server-key.pem 8496 ssh_runner.go:57] Run: sudo mkdir -p /etc/docker 8496 ssh_runner.go:57] Run: sudo rm -f /etc/docker/ca.pem 8496 ssh_runner.go:57] Run: sudo mkdir -p /etc/docker 8496 ssh_runner.go:57] Run: sudo rm -f /etc/docker/server.pem 8496 ssh_runner.go:57] Run: sudo mkdir -p /etc/docker configuration on the remote daemon… 8496 start.go:150] Error starting host: Error creating host: Error executing step: Provisioning VM. systemctl -f restart crio for crio.service failed because the control process exited with error code. status crio.service” and “journalctl -xe” for details.

Retrying. E0102 12:43:26.733761 8496 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.

What you expected to happen: The minikube start returns without any error 😃

How to reproduce it (as minimally and precisely as possible): see above command line

Output of minikube logs (if applicable): no entries

Anything else do we need to know: minikube ip shows me an ip (v6): fe80::215:5dff:fe00:7025 minikube ssh works inside minikube “docker info” also shows me something"

btw: is it normal that I need to run minikube commands as “administrator”?

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 19 (1 by maintainers)

Most upvoted comments

Hi @ukphillips thanks for your message. Follow up with your suggestion and change Virtual switch from Primary Virtual Switch to Default Switch try again to start minikube and it’s worked with me. AWSOME. Thanks so much 😃

trungungtoan-agilityio on Jan 25, 2018

$ minikube ssh
$ systemctl status crio.service
● crio.service - Open Container Initiative Daemon
Loaded: loaded (/lib/systemd/system/crio.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2018-01-02 11:43:24 UTC; 21min ago
Docs: https://github.com/kubernetes-incubator/cri-o
Process: 2961 ExecStart=/usr/bin/crio $CRIO_OPTIONS $CRIO_MINIKUBE_OPTIONS --root ${PERSISTENT_DIR}/var/lib/containers (code=exited, status=1/FAILURE)
Process: 2943 ExecStartPre=/bin/mkdir -p ${PERSISTENT_DIR}/var/lib/containers (code=exited, status=0/SUCCESS)
Main PID: 2961 (code=exited, status=1/FAILURE)
CPU: 161ms

Jan 02 11:43:24 minikube crio[2961]: time=“2018-01-02 11:43:24.714135600Z” level=debug msg=“[graphdriver] trying provided driver “overlay2"”
Jan 02 11:43:24 minikube crio[2961]: time=“2018-01-02 11:43:24.717706100Z” level=debug msg=“backingFs=extfs, projectQuotaSupported=false”
Jan 02 11:43:24 minikube crio[2961]: time=“2018-01-02 11:43:24.718191900Z” level=info msg=“CNI network rkt.kubernetes.io (type=bridge) is used from /etc/cni/net.d/k8s.conf”
.d/k8s.conf”:24 minikube crio[2961]: time=“2018-01-02 11:43:24.718370200Z” level=info msg="CNI network rkt.kubernetes.io (type=bridge) is used from /etc/cni/net–More–
Jan 02 11:43:24 minikube crio[2961]: time=“2018-01-02 11:43:24.724783100Z” level=debug msg=“Golang’s threads limit set to 13320”
Jan 02 11:43:24 minikube crio[2961]: time=“2018-01-02 11:43:24.725033900Z” level=fatal msg=“Unable to select an IP.”
Jan 02 11:43:24 minikube systemd[1]: crio.service: Main process exited, code=exited, status=1/FAILURE
Jan 02 11:43:24 minikube systemd[1]: Failed to start Open Container Initiative Daemon.
Jan 02 11:43:24 minikube systemd[1]: crio.service: Unit entered failed state.
Jan 02 11:43:24 minikube systemd[1]: crio.service: Failed with result ‘exit-code’.

ahoehma on Jan 2, 2018

Tried with @Dynamo6 suggest, But can not start crio.service . Waiting solution to resolve my ugly.

trungungtoan-agilityio on Jan 24, 2018

If it helps anyone, I’m running Windows 10 (with HyperV enabled) and I’ve configured the hyperv virtual switch. When that switch is first created I can start minikube without errors, however following a reboot the crio errors come back every time. At first, to get around this, I was creating a new virtual switch every day, however I’ve now found that simply disabling then re-enabling the existing switch prevents the crio errors from occurring when minikube start is run.

Dynamo6 on Jan 24, 2018