minikube: Error creating host:: sudo systemctl -f restart docker: Process exited with status 1

Environment:

Minikube version: minikube version: v0.22.1

  • OS: Windows 10 64-bit (15063.540) with latest updates
  • VM Driver: virtualbox
  • ISO version: v0.23.3
  • Install tools:
  • Others:

What happened:

I ran minikube start and it produced a series of errors:

$ minikube start
Starting local Kubernetes v1.7.5 cluster...
Starting VM...
Downloading Minikube ISO
 106.36 MB / 106.36 MB [============================================] 100.00% 0s
E0912 11:51:06.694413   14284 start.go:143] Error starting host: Error creating host: Error executing step: Provisioning VM.
: Temporary Error: ssh command error:
command : sudo systemctl -f restart docker
err     : Process exited with status 1
output  : Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.

Temporary Error: ssh command error:
command : sudo systemctl -f restart docker
err     : Process exited with status 1
output  : Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.

Temporary Error: ssh command error:
command : sudo systemctl -f restart docker
err     : Process exited with status 1
output  : Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.

Temporary Error: ssh command error:
command : sudo systemctl -f restart docker
err     : Process exited with status 1
output  : Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.

Temporary Error: ssh command error:
command : sudo systemctl -f restart docker
err     : Process exited with status 1
output  : Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.
.

 Retrying.
E0912 11:51:06.698319   14284 start.go:149] Error starting host:  Error creating host: Error executing step: Provisioning VM.
: Temporary Error: ssh command error:
command : sudo systemctl -f restart docker
err     : Process exited with status 1
output  : Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.

Temporary Error: ssh command error:
command : sudo systemctl -f restart docker
err     : Process exited with status 1
output  : Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.

Temporary Error: ssh command error:
command : sudo systemctl -f restart docker
err     : Process exited with status 1
output  : Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.

Temporary Error: ssh command error:
command : sudo systemctl -f restart docker
err     : Process exited with status 1
output  : Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.

Temporary Error: ssh command error:
command : sudo systemctl -f restart docker
err     : Process exited with status 1
output  : Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.

================================================================================
An error has occurred. Would you like to opt in to sending anonymized crash
information to minikube to help prevent future errors?
To opt out of these messages, run the command:
        minikube config set WantReportErrorPrompt false
================================================================================
Please enter your response [Y/n]:

I then ran minikube delete and minikube start again:

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

$ minikube start
Starting local Kubernetes v1.7.5 cluster...
Starting VM...
E0912 12:23:24.297049   13440 start.go:143] Error starting host: Error creating host: Error executing step: Provisioning VM.
: Temporary Error: ssh command error:
command : sudo systemctl -f restart docker
err     : Process exited with status 1
output  : Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.

Temporary Error: ssh command error:
command : sudo systemctl -f restart docker
err     : Process exited with status 1
output  : Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.

Temporary Error: ssh command error:
command : sudo systemctl -f restart docker
err     : Process exited with status 1
output  : Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.

Temporary Error: ssh command error:
command : sudo systemctl -f restart docker
err     : Process exited with status 1
output  : Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.

Temporary Error: ssh command error:
command : sudo systemctl -f restart docker
err     : Process exited with status 1
output  : Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.
.

 Retrying.
E0912 12:23:24.305838   13440 start.go:149] Error starting host:  Error creating host: Error executing step: Provisioning VM.
: Temporary Error: ssh command error:
command : sudo systemctl -f restart docker
err     : Process exited with status 1
output  : Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.

Temporary Error: ssh command error:
command : sudo systemctl -f restart docker
err     : Process exited with status 1
output  : Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.

Temporary Error: ssh command error:
command : sudo systemctl -f restart docker
err     : Process exited with status 1
output  : Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.

Temporary Error: ssh command error:
command : sudo systemctl -f restart docker
err     : Process exited with status 1
output  : Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.

Temporary Error: ssh command error:
command : sudo systemctl -f restart docker
err     : Process exited with status 1
output  : Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.

================================================================================
An error has occurred. Would you like to opt in to sending anonymized crash
information to minikube to help prevent future errors?
To opt out of these messages, run the command:
        minikube config set WantReportErrorPrompt false
================================================================================
Please enter your response [Y/n]:

What you expected to happen: Minikube should start a kubernetes cluster correctly

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

Output of minikube logs (if applicable):

$ minikube logs
F0912 12:25:08.382533   12512 logs.go:50] Error getting cluster bootstrapper: getting localkube bootstrapper: getting ssh client: Error dialing tcp via ssh client: dial tcp 127.0.0.1:22: connectex: No connection could be made because the target machine actively refused it.

Anything else do we need to know:

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Comments: 27 (6 by maintainers)

Most upvoted comments

This should be fixed by #1959

Similar with mac OSX high sierra.

minikube delete returns…

Deleting local Kubernetes cluster...
Machine deleted.
Error deleting machine profile config

and then starting minikube results in…

Starting local Kubernetes v1.8.0 cluster...
Starting VM...
E0105 17:43:20.160776   20194 start.go:150] Error starting host: Error starting stopped host: IP address never found in dhcp leases file Temporary Error: Could not find an IP address for b2:56:5:c4:6e:21```

Check if docker service is running properly. I ran in same issue. Following were the steps followed

  1. Restarted docker service
  2. Created a docker machine with a virtualbox driver. [any driver that you will be using for Kubernetes] with following command docker-machine create -d virtualbox default
  3. now stop the docker instance docker-machine stop default
  4. remove the docker instance docker-machine rm default
  5. Now retry minikube start --vm-driver=virtualbox it should probably work .

Same problem using a mac… update:nm … just had to do minikube delete for my problem

I’m getting the same error, the log from systemctl status docker.service is

[[0;1;31m●[[0m docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; disabled; vendor preset: enabled)
   Active: [[0;1;31mfailed[[0m (Result: exit-code) since Tue 2017-09-12 08:52:21 UTC; 2min 13s ago
     Docs: https://docs.docker.com
  Process: 3545 ExecStart=/usr/bin/docker daemon -H tcp://0.0.0.0:2376 -H unix:///var/run/docker.sock --tlsverify --tlscacert /etc/docker/ca.pem --tlscert /etc/docker/server.pem --tlskey /e
tc/docker/server-key.pem --label provider=hyperv --label provider=hyperv --label provider=hyperv --label provider=hyperv --label provider=hyperv --insecure-registry 10.0.0.0/24 [[0;1;31m(co
de=exited, status=1/FAILURE)[[0m
 Main PID: 3545 (code=exited, status=1/FAILURE)
      CPU: 77ms

Sep 12 08:52:21 minikube systemd[1]: Starting Docker Application Container Engine...
Sep 12 08:52:21 minikube docker[3545]: time="2017-09-12T08:52:21.825996200Z" level=fatal msg="Could not load X509 key pair (cert: \"/etc/docker/server.pem\", key: \"/etc/docker/server-key.p
em\"): open /etc/docker/server.pem: no such file or directory"
Sep 12 08:52:21 minikube systemd[1]: [[0;1;39mdocker.service: Main process exited, code=exited, status=1/FAILURE[[0m
Sep 12 08:52:21 minikube systemd[1]: [[0;1;31mFailed to start Docker Application Container Engine.[[0m
Sep 12 08:52:21 minikube systemd[1]: [[0;1;39mdocker.service: Unit entered failed state.[[0m
Sep 12 08:52:21 minikube systemd[1]: [[0;1;39mdocker.service: Failed with result 'exit-code'.[[0m

When I ssh into minikube I can’t see anything in /etc/docker

Update: I think that is a configuration problem on Windows10 using HyperV, I have my problem solved following this article: (https://medium.com/@JockDaRock/minikube-on-windows-10-with-hyper-v-6ef0f4dc158c)

minikube -v10 start

i used this ,fix it, hope help you, my friend