Also failing on Windows 10 1709 64-bit and VirtualBox 5.2.6 here, but for a different reason:

$ minikube start --kubernetes-version=v1.9.2 --bootstrapper=kubeadm
Starting local Kubernetes v1.9.2 cluster...
Starting VM...
Getting VM IP address...
Moving files into cluster...
Setting up certs...
Connecting to cluster...
Setting up kubeconfig...
Starting cluster components...
E0201 10:01:27.044252    9948 start.go:281] Error restarting cluster:  restarting kube-proxy: waiting for kube-proxy to be up for configmap update: timed out waiting for the condition
================================================================================
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]:

F21 on 1 Feb 2018

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"}

asbjornu on 14 Mar 2018

👍2

Seems related to #2131.

asbjornu on 14 Mar 2018

Faced this issue on arch linux
kernel: 4.15.9-1-ARCH
minikube version: v0.25.2
```
$ minikube start --memory=3000 -b kubeadm --kubernetes-version
Starting local Kubernetes v1.9.1 cluster...
Starting VM...
Getting VM IP address...
Moving files into cluster...
Setting up certs...
Connecting to cluster...
Setting up kubeconfig...
Starting cluster components...

E0328 21:54:51.600728 7358 start.go:276] Error starting cluster: kubeadm init error running command: sudo /usr/bin/kubeadm init --config /var/lib/kubeadm.yaml --skip-preflight-checks: Process exited with status 1

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]:
```

rohan47 on 29 Mar 2018

Same issue on Windows 10
````
Starting cluster components...

E0328 21:54:51.600728 7358 start.go:276] Error starting cluster: kubeadm init error running command: sudo /usr/bin/kubeadm init --config /var/lib/kubeadm.yaml --skip-preflight-checks: Process exited with status 1

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]:
````

After rerunning now i got this

`
```
Starting cluster components...

E0412 18:04:43.797557 34012 start.go:281] Error restarting cluster: restarting kube-proxy: waiting for kube-proxy to be up for configmap update: timed out waiting for the condition

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]:
y
````

pawankr on 12 Apr 2018

👍2

Hi. I am also having the same issue when trying to install All-in-one-node Kubernetes cluster with minikube. It seems like an issue when starting the cluster. Below are the details:
OS: Windows 10
VM Driver: Oracle Virtualbox
Minikube version: v0.26.0
Install tools:
Others:

Starting cluster components...
E0415 19:48:14.362282   13916 start.go:276] 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 --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  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 --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
 output: [init] Using Kubernetes version: v1.10.0
[init] Using Authorization modes: [Node RBAC]
[preflight] Running pre-flight checks.
[certificates] Using the existing ca certificate and key.
                                                                                                        [WARNING Swap]: running with swap on is not supported. Please disable swap
Flag --admission-control has been deprecated, Use --enable-admission-plugins or --disable-admission-plugins instead. Will be removed in a future version.
                                                          [certificates] Using the existing apiserver certificate and key.
[certificates] Generated apiserver-kubelet-client certificate and key.
[certificates] Generated etcd/ca certificate and key.
[certificates] Generated etcd/server certificate and key.
[certificates] etcd/server serving cert is signed for DNS names [localhost] and IPs [127.0.0.1]
[certificates] Generated etcd/peer certificate and key.
[certificates] etcd/peer serving cert is signed for DNS names [minikube] and IPs [192.168.99.100]
[certificates] Generated etcd/healthcheck-client certificate and key.
[certificates] Generated apiserver-etcd-client certificate and key.
[certificates] Generated sa key and public key.
[certificates] Generated front-proxy-ca certificate and key.
[certificates] Generated front-proxy-client certificate and key.
[certificates] Valid certificates and keys now exist in "/var/lib/localkube/certs/"
[kubeconfig] Wrote KubeConfig file to disk: "/etc/kubernetes/admin.conf"
[kubeconfig] Wrote KubeConfig file to disk: "/etc/kubernetes/kubelet.conf"
[kubeconfig] Wrote KubeConfig file to disk: "/etc/kubernetes/controller-manager.conf"
[kubeconfig] Wrote KubeConfig file to disk: "/etc/kubernetes/scheduler.conf"
[controlplane] Wrote Static Pod manifest for component kube-apiserver to "/etc/kubernetes/manifests/kube-apiserver.yaml"
[controlplane] Wrote Static Pod manifest for component kube-controller-manager to "/etc/kubernetes/manifests/kube-controller-manager.yaml"
[controlplane] Wrote Static Pod manifest for component kube-scheduler to "/etc/kubernetes/manifests/kube-scheduler.yaml"
[etcd] Wrote Static Pod manifest for a local etcd instance to "/etc/kubernetes/manifests/etcd.yaml"
[init] Waiting for the kubelet to boot up the control plane as Static Pods from directory "/etc/kubernetes/manifests".
[init] This might take a minute or longer if the control plane images have to be pulled.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10255/healthz' failed with error: Get http://localhost:10255/healthz: dial tcp 127.0.0.1:10255: getsockopt: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10255/healthz' failed with error: Get http://localhost:10255/healthz: dial tcp 127.0.0.1:10255: getsockopt: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10255/healthz' failed with error: Get http://localhost:10255/healthz: dial tcp 127.0.0.1:10255: getsockopt: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10255/healthz/syncloop' failed with error: Get http://localhost:10255/healthz/syncloop: dial tcp 127.0.0.1:10255: getsockopt: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10255/healthz/syncloop' failed with error: Get http://localhost:10255/healthz/syncloop: dial tcp 127.0.0.1:10255: getsockopt: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10255/healthz/syncloop' failed with error: Get http://localhost:10255/healthz/syncloop: dial tcp 127.0.0.1:10255: getsockopt: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10255/healthz' failed with error: Get http://localhost:10255/healthz: dial tcp 127.0.0.1:10255: getsockopt: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10255/healthz/syncloop' failed with error: Get http://localhost:10255/healthz/syncloop: dial tcp 127.0.0.1:10255: getsockopt: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10255/healthz' failed with error: Get http://localhost:10255/healthz: dial tcp 127.0.0.1:10255: getsockopt: connection refused.

Unfortunately, an error has occurred:
        timed out waiting for the condition

This error is likely caused by:
        - The kubelet is not running
        - The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)
        - Either there is no internet connection, or imagePullPolicy is set to "Never",
          so the kubelet cannot pull or find the following control plane images:
                - k8s.gcr.io/kube-apiserver-amd64:v1.10.0
                - k8s.gcr.io/kube-controller-manager-amd64:v1.10.0
                - k8s.gcr.io/kube-scheduler-amd64:v1.10.0
                - k8s.gcr.io/etcd-amd64:3.1.12 (only if no external etcd endpoints are configured)

If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
        - 'systemctl status kubelet'
        - 'journalctl -xeu kubelet'
                                         : running command: sudo /usr/bin/kubeadm init --config /var/lib/kubeadm.yaml --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests --ignore-preflight-errors=DirAvailable--data --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
.: Process exited with status 1

I am not sure if it is related or not but running kubectl version command returns

Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.0", GitCommit:"fc32d2f3698e36b93322a3465f63a14e9f0eaead", GitTreeState:"clean", BuildDate:"2018-03-26T16:55:54Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"windows/amd64"}
Unable to connect to the server: Service Unavailable

asifmammadov on 16 Apr 2018

Hi, getting exactly the same issue as described by @asifmammadov
Using the following configuration:
OS: Windows 10
VM Driver: Oracle Virtualbox v5.2.8
Minikube version: v0.26.0

jurezz on 16 Apr 2018

Getting the same error on
OS: Windows 7
VM Driver: Oracle Virtualbox v5.2.8
Minikube version: v0.26.0

Just found related issue that solved my problem: https://github.com/kubernetes/minikube/issues/2696

chbussler on 17 Apr 2018

👍2

Get the same issue too, the logs is as following:
OS: OS X 10.12.3
Minikube: 0.26.0
VM: VirsualBox

minikube start --registry-mirror=https://registry.docker-cn.com
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...
E0417 18:23:34.065553 12866 start.go:281] Error restarting cluster: restarting kube-proxy: waiting for kube-proxy to be up for configmap update: timed out waiting for the condition
E0417 18:23:40.334590 12866 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.3.2:55296->216.58.200.234:443: read: connection reset by peer

landpy on 17 Apr 2018

👍1

Me too, same issues on unhealthy

kubeadm: v1.10.0
minikube: v0.26.0
VM: VirtaulBox 5.2.6
O/S: Windows 10 Pro 1709 m16299.371

[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10255/healthz' failed with error: Get http://localhost:10255/healthz: dial tcp 127.0.0.1:10255: getsockopt: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10255/healthz' failed with error: Get http://localhost:10255/healthz: dial tcp 127.0.0.1:10255: getsockopt: connection refused.

Jimmer-Ball on 18 Apr 2018

I faced the same issue on my laptop windows 10 minikube

minikube delete

then

minikube start

solved my issue

3miliomc on 21 Apr 2018

👍5 🎉1

Reverting to version 0.25.2 from 0.26 is a workaround for me on Windows.

Jimmer-Ball on 21 Apr 2018

👍7

Yes works when downgrading minikube to 0.25.2, hope the issues will be fixed in 0.26 soon.

jurezz on 22 Apr 2018

I tried minikube delete and start and the same problem. However, downgrading it to version 0.25.2 works, thanks!

asifmammadov on 22 Apr 2018

👍6

@asifmammadov Thanks it works for me !

linsheng9731 on 25 Apr 2018

Same issue
kubeadm: v1.10.0
minikube: v0.26.1
VM: hyperv
O/S: Windows 10 Pro

Workaround use minikube 0.25.2 work!

songpr on 25 Apr 2018

Got same issue on:
minikube version: v0.26.1
Arch linux - 4.15.14-1-ARCH

You should explicit your --vm-driver,
in my case:

 minikube start --vm-driver=virtualbox

works fine!

luizanao on 2 May 2018

I followed the approach suggested by @3miliomc and it worked! 👍

minikube delete
minikube start

O/S: Windows 10 Pro
VM: hyper-v
Minikube: v0.27.0
Kubeadm: v1.10.0

lnfnunes on 8 Jun 2018

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

fejta-bot on 6 Sep 2018

This seems to be a general case of kubeadm failures, for which we don't yet provide any additional helpful error messages. If someone sees this again, please attach the output from "minikube ssh" running the following:

sudo journalctl -u kubelet
sudo /usr/bin/kubeadm init --config /var/lib/kubeadm.yaml --skip-preflight-checks

as well as:

cat /var/lib/kubeadm.yaml

Thanks!

tstromberg on 19 Sep 2018

👍1

@tstromberg As requested ...

-- Logs begin at Wed 2018-09-19 20:32:51 UTC, end at Wed 2018-09-19 21:08:32 UTC. --
Sep 19 20:43:38 minikube systemd[1]: Started kubelet: The Kubernetes Node Agent.
Sep 19 20:43:38 minikube kubelet[2941]: Flag --cluster-dns has been deprecated, This parameter should be set via the c
onfig file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-c
onfig-file/ for more information.
Sep 19 20:43:38 minikube kubelet[2941]: Flag --authorization-mode has been deprecated, This parameter should be set vi
a the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/ku
belet-config-file/ for more information.
Sep 19 20:43:38 minikube kubelet[2941]: Flag --cadvisor-port has been deprecated, The default will change to 0 (disabl
ed) in 1.12, and the cadvisor port will be removed entirely in 1.13
Sep 19 20:43:38 minikube kubelet[2941]: Flag --cgroup-driver has been deprecated, This parameter should be set via the
 config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet
-config-file/ for more information.
Sep 19 20:43:38 minikube kubelet[2941]: Flag --fail-swap-on has been deprecated, This parameter should be set via the 
config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-
config-file/ for more information.
Sep 19 20:43:38 minikube kubelet[2941]: Flag --client-ca-file has been deprecated, This parameter should be set via th
e config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubele
t-config-file/ for more information.
Sep 19 20:43:38 minikube kubelet[2941]: Flag --pod-manifest-path has been deprecated, This parameter should be set via
 the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kub
elet-config-file/ for more information.
Sep 19 20:43:38 minikube kubelet[2941]: Flag --allow-privileged has been deprecated, will be removed in a future versi
on
Sep 19 20:43:38 minikube kubelet[2941]: Flag --cluster-domain has been deprecated, This parameter should be set via th
e config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubele
t-config-file/ for more information.
Sep 19 20:43:38 minikube kubelet[2941]: I0919 20:43:38.382437    2941 feature_gate.go:226] feature gates: &{{} map[]}
Sep 19 20:43:38 minikube kubelet[2941]: F0919 20:43:38.577343    2941 server.go:218] unable to load client CA file /va
r/lib/localkube/certs/ca.crt: open /var/lib/localkube/certs/ca.crt: no such file or directory
Sep 19 20:43:38 minikube systemd[1]: [[0;1;39m[[0;1;31m[[0;1;39mkubelet.service: Main process exited, code=exited, sta
tus=255/n/a[[0m
Sep 19 20:43:38 minikube systemd[1]: [[0;1;39m[[0;1;31m[[0;1;39mkubelet.service: Failed with result 'exit-code'.[[0m
Sep 19 20:43:48 minikube systemd[1]: kubelet.service: Service hold-off time over, scheduling restart.
Sep 19 20:43:48 minikube systemd[1]: kubelet.service: Scheduled restart job, restart counter is at 1.
standard input

$  sudo /usr/bin/kubeadm init --config /var/lib/kubeadm.yaml --skip-preflight-checks
Flag --skip-preflight-checks has been deprecated, it is now equivalent to --ignore-preflight-errors=all
[init] Using Kubernetes version: v1.10.0
[init] Using Authorization modes: [Node RBAC]
[preflight] Running pre-flight checks.
    [WARNING SystemVerification]: docker version is greater than the most recently validated version. Docker version: 17.12.1-ce. Max validated version: 17.03
    [WARNING Port-8443]: Port 8443 is in use
    [WARNING Port-10250]: Port 10250 is in use
    [WARNING Port-10251]: Port 10251 is in use
    [WARNING Port-10252]: Port 10252 is in use
    [WARNING FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml]: /etc/kubernetes/manifests/kube-apiserver.yaml already exists
    [WARNING FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml]: /etc/kubernetes/manifests/kube-controller-manager.yaml already exists
    [WARNING FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml]: /etc/kubernetes/manifests/kube-scheduler.yaml already exists
    [WARNING FileAvailable--etc-kubernetes-manifests-etcd.yaml]: /etc/kubernetes/manifests/etcd.yaml already exists
    [WARNING Swap]: running with swap on is not supported. Please disable swap
Flag --admission-control has been deprecated, Use --enable-admission-plugins or --disable-admission-plugins instead. Will be removed in a future version.
    [WARNING DirAvailable--data-minikube]: /data/minikube is not empty
[certificates] Using the existing ca certificate and key.
[certificates] Using the existing apiserver certificate and key.
[certificates] Using the existing apiserver-kubelet-client certificate and key.
[certificates] Using the existing etcd/ca certificate and key.
[certificates] Using the existing etcd/server certificate and key.
[certificates] Using the existing etcd/peer certificate and key.
[certificates] Using the existing etcd/healthcheck-client certificate and key.
[certificates] Using the existing apiserver-etcd-client certificate and key.
[certificates] Using the existing sa key.
[certificates] Using the existing front-proxy-ca certificate and key.
[certificates] Using the existing front-proxy-client certificate and key.
[certificates] Valid certificates and keys now exist in "/var/lib/localkube/certs/"
[kubeconfig] Using existing up-to-date KubeConfig file: "/etc/kubernetes/admin.conf"
[kubeconfig] Using existing up-to-date KubeConfig file: "/etc/kubernetes/kubelet.conf"
[kubeconfig] Using existing up-to-date KubeConfig file: "/etc/kubernetes/controller-manager.conf"
[kubeconfig] Using existing up-to-date KubeConfig file: "/etc/kubernetes/scheduler.conf"
[controlplane] Wrote Static Pod manifest for component kube-apiserver to "/etc/kubernetes/manifests/kube-apiserver.yaml"
[controlplane] Wrote Static Pod manifest for component kube-controller-manager to "/etc/kubernetes/manifests/kube-controller-manager.yaml"
[controlplane] Wrote Static Pod manifest for component kube-scheduler to "/etc/kubernetes/manifests/kube-scheduler.yaml"
[etcd] Wrote Static Pod manifest for a local etcd instance to "/etc/kubernetes/manifests/etcd.yaml"
[init] Waiting for the kubelet to boot up the control plane as Static Pods from directory "/etc/kubernetes/manifests".
[init] This might take a minute or longer if the control plane images have to be pulled.

$ cat /var/lib/kubeadm.yaml 
cat: /var/lib/kubeadm.yaml: Permission denied

$ sudo cat /var/lib/kubeadm.yaml
apiVersion: kubeadm.k8s.io/v1alpha1
kind: MasterConfiguration
noTaintMaster: true
api:
  advertiseAddress: 192.168.99.102
  bindPort: 8443
  controlPlaneEndpoint: localhost
kubernetesVersion: v1.10.0
certificatesDir: /var/lib/localkube/certs/
networking:
  serviceSubnet: 10.96.0.0/12
etcd:
  dataDir: /data/minikube
nodeName: minikube
apiServerExtraArgs:
  admission-control: "Initializers,NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorag

ahopkins on 19 Sep 2018

@ahopkins - This is worrying, but it's difficult to tell if the job restarted just after the logs:

F0919 20:43:38.577343    2941 server.go:218] unable to load client CA file /var/lib/localkube/certs/ca.crt: open /var/lib/localkube/certs/ca.crt: no such file or directory

However, you were able to successfully bring kubeadm up afterwards. This may be
complete red herring, or a race condition. Additionally, it's confusing that kubeadm uses the localkube certs directory, but that's backwards compatibility for you.

What was the "minikube start" line you used? And can you paste what it output in your case, along with "minikube logs?" Thanks.

tstromberg on 21 Sep 2018

this might have been a restart of an existing instance, but at the time
when moving from localkube to kubeadm
if possible, delete the instance you used and try a clean deployment.

gbraad on 21 Sep 2018

@gbraad

this might have been a restart of an existing instance, but at the time when moving from localkube to kubeadm

True. I have tried it many which ways. Start. Ctrl+C. Force shut down with virtual box.

if possible, delete the instance you used and try a clean deployment.

Yes ... I have done this. Unfortunately that is how I got into this mess. It had been working, but for some reason after about an hour it would no longer respond to requests. So, I would have to restart. I thought minikube delete and starting fresh would fix ... but it just made it so minikube start does not work at all.

It does work with --bootstrapper=localkube. BUT ... besides not being ideal since it will be deprecated, this is not workable because then kubectl hangs and does not respond.

I even went so far as to remove the minikube binaries, and ~/.minikube directory and install from scratch. Same problem.

@tstromberg

The command was simply minikube start. I have virtualbox 5.1.24 running on Ubuntu 17.10. minikube version: v0.28.2

```╭─adam@thebrewery ~
╰─$ 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...

E0921 12:32:29.702897 5220 start.go:305] Error restarting cluster: restarting kube-proxy: waiting for kube-proxy to be up for configmap update: timed out waiting for the condition

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]:
y


At the `Starting cluster components...` line ... it hangs for about 10 minutes before the error message pops up.

╭─adam@thebrewery ~
Fri 2018-09-21 09:33:06 UTC. --
The Kubernetes Node Agent.
has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.
has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.
has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.
has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.
has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.
has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.
has been deprecated, will be removed in a future version
has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.
has been deprecated, The default will change to 0 (disabled) in 1.12, and the cadvisor port will be removed entirely in 1.13
2723 feature_gate.go:226] feature gates: &{{} map[]}
2723 server.go:218] unable to load client CA file /var/lib/localkube/certs/ca.crt: open /var/lib/localkube/certs/ca.crt: no such file or directory
Main process exited, code=exited, status=255/n/a
Failed with result 'exit-code'.
Service hold-off time over, scheduling restart.
Scheduled restart job, restart counter is at 1.
The Kubernetes Node Agent.
The Kubernetes Node Agent.
has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.
has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.
has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.
has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.
has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.
has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.
has been deprecated, will be removed in a future version
has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.
has been deprecated, The default will change to 0 (disabled) in 1.12, and the cadvisor port will be removed entirely in 1.13
2799 feature_gate.go:226] feature gates: &{{} map[]}
2799 hostport_manager.go:68] The binary conntrack is not installed, this can cause failures in network connection cleanup.
2799 server.go:376] Version: v1.10.0
2799 feature_gate.go:226] feature gates: &{{} map[]}
2799 plugins.go:89] No cloud provider specified.
2799 server.go:613] --cgroups-per-qos enabled, but --cgroup-root was not specified. defaulting to /
2799 container_manager_linux.go:242] container manager verified user specified cgroup-root exists: /
2799 container_manager_linux.go:247] Creating Container Manager object based on Node Config: {RuntimeCgroupsName: SystemCgroupsName: KubeletCgroupsName: ContainerRuntime:docker CgroupsPerQOS:true CgroupRoot:/ CgroupDriver:cgroupfs KubeletRootDir:/var/lib/kubelet ProtectKernelDefaults:false NodeAllocatableConfig:{KubeReservedCgroupName: SystemReservedCgroupName: EnforceNodeAllocatable:map[pods:{}] KubeReserved:map[] SystemReserved:map[] HardEvictionThresholds:[{Signal:memory.available Operator:LessThan Value:{Quantity:100Mi Percentage:0} GracePeriod:0s MinReclaim:} {Signal:nodefs.available Operator:LessThan Value:{Quantity: Percentage:0.1} GracePeriod:0s MinReclaim:} {Signal:nodefs.inodesFree Operator:LessThan Value:{Quantity: Percentage:0.05} GracePeriod:0s MinReclaim:} {Signal:imagefs.available Operator:LessThan Value:{Quantity: Percentage:0.15} GracePeriod:0s MinReclaim:}]} ExperimentalQOSReserved:map[] ExperimentalCPUManagerPolicy:none ExperimentalCPUManagerReconcilePeriod:10s ExperimentalPodPidsLimit:-1 EnforceCPULimits:true}
2799 container_manager_linux.go:266] Creating device plugin manager: true
2799 state_mem.go:36] [cpumanager] initializing new in-memory state store
2799 state_mem.go:87] [cpumanager] updated default cpuset: ""
2799 state_mem.go:95] [cpumanager] updated cpuset assignments: "map[]"
2799 kubelet.go:272] Adding pod path: /etc/kubernetes/manifests
2799 kubelet.go:297] Watching apiserver
2799 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:460: Failed to list *v1.Node: Get https://localhost:8443/api/v1/nodes?fieldSelector=metadata.name%3Dminikube&limit=500&resourceVersion=0: dial tcp 127.0.0.1:8443: getsockopt: connection refused
2799 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:451: Failed to list *v1.Service: Get https://localhost:8443/api/v1/services?limit=500&resourceVersion=0: dial tcp 127.0.0.1:8443: getsockopt: connection refused
2799 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://localhost:8443/api/v1/pods?fieldSelector=spec.nodeName%3Dminikube&limit=500&resourceVersion=0: dial tcp 127.0.0.1:8443: getsockopt: connection refused
2799 kubelet_network.go:139] Hairpin mode set to "promiscuous-bridge" but kubenet is not enabled, falling back to "hairpin-veth"
2799 kubelet.go:556] Hairpin mode set to "hairpin-veth"
2799 client.go:75] Connecting to docker on unix:///var/run/docker.sock
2799 client.go:104] Start docker client with request timeout=2m0s
2799 hostport_manager.go:68] The binary conntrack is not installed, this can cause failures in network connection cleanup.
2799 docker_service.go:244] Docker cri networking managed by kubernetes.io/no-op
2799 docker_service.go:249] Docker Info: &{ID:QEDW:DQB5:MWND:CNHW:MFHK:GFVI:6RP7:ODNI:B2UL:WLHE:2ARX:GENQ Containers:13 ContainersRunning:12 ContainersPaused:0 ContainersStopped:1 Images:6 Driver:overlay2 DriverStatus:[[Backing Filesystem extfs] [Supports d_type true] [Native Overlay Diff true]] SystemStatus:[] Plugins:{Volume:[local] Network:[bridge host macvlan null overlay] Authorization:[] Log:[awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog]} MemoryLimit:true SwapLimit:true KernelMemory:true CPUCfsPeriod:true CPUCfsQuota:true CPUShares:true CPUSet:true IPv4Forwarding:true BridgeNfIptables:true BridgeNfIP6tables:true Debug:false NFd:22 OomKillDisable:true NGoroutines:35 SystemTime:2018-09-21T09:22:34.865689731Z LoggingDriver:json-file CgroupDriver:cgroupfs NEventsListener:0 KernelVersion:4.15.0 OperatingSystem:Buildroot 2018.05 OSType:linux Architecture:x86_64 IndexServerAddress:https://index.docker.io/v1/ RegistryConfig:0xc4201fa230 NCPU:2 MemTotal:2087550976 GenericResources:[] DockerRootDir:/var/lib/docker HTTPProxy: HTTPSProxy: NoProxy: Name:minikube Labels:[provider=virtualbox] ExperimentalBuild:false ServerVersion:17.12.1-ce ClusterStore: ClusterAdvertise: Runtimes:map[runc:{Path:docker-runc Args:[]}] DefaultRuntime:runc Swarm:{NodeID: NodeAddr: LocalNodeState:inactive ControlAvailable:false Error: RemoteManagers:[] Nodes:0 Managers:0 Cluster:} LiveRestoreEnabled:false Isolation: InitBinary:docker-init ContainerdCommit:{ID:9b55aab90508bd389d7654c4baf173a981477d55 Expected:9b55aab90508bd389d7654c4baf173a981477d55} RuncCommit:{ID:9f9c96235cc97674e935002fc3d78361b696a69e Expected:9f9c96235cc97674e935002fc3d78361b696a69e} InitCommit:{ID:N/A Expected:} SecurityOptions:[name=seccomp,profile=default]}
2799 docker_service.go:262] Setting cgroupDriver to cgroupfs
2799 remote_runtime.go:43] Connecting to runtime service unix:///var/run/dockershim.sock
2799 kuberuntime_manager.go:186] Container runtime docker initialized, version: 17.12.1-ce, apiVersion: 1.35.0
2799 probe.go:215] Flexvolume plugin directory at /usr/libexec/kubernetes/kubelet-plugins/volume/exec/ does not exist. Recreating.
2799 csi_plugin.go:61] kubernetes.io/csi: plugin initializing...
2799 kubelet.go:1277] Image garbage collection failed once. Stats initialization may not have completed yet: failed to get imageFs info: unable to find data for container /
2799 fs_resource_analyzer.go:66] Starting FS ResourceAnalyzer
2799 status_manager.go:140] Starting to sync pod status with apiserver
2799 kubelet.go:1777] Starting kubelet main sync loop.
2799 kubelet.go:1794] skipping pod synchronization - [container runtime is down PLEG is not healthy: pleg was last seen active 2562047h47m16.854775807s ago; threshold is 3m0s]
2799 server.go:129] Starting to listen on 0.0.0.0:10250
2799 server.go:299] Adding debug handlers to kubelet server.
2799 volume_manager.go:247] Starting Kubelet Volume Manager
2799 server.go:944] Started kubelet
2799 desired_state_of_world_populator.go:129] Desired state populator starts to run
2799 event.go:209] Unable to write event: 'Post https://localhost:8443/api/v1/namespaces/default/events: dial tcp 127.0.0.1:8443: getsockopt: connection refused' (may retry after sleeping)
2799 kubelet.go:1794] skipping pod synchronization - [container runtime is down]
2799 kubelet_node_status.go:271] Setting node annotation to enable volume controller attach/detach
2799 kubelet_node_status.go:82] Attempting to register node minikube
2799 kubelet_node_status.go:106] Unable to register node "minikube" with API server: Post https://localhost:8443/api/v1/nodes: dial tcp 127.0.0.1:8443: getsockopt: connection refused
2799 kubelet.go:1794] skipping pod synchronization - [container runtime is down]
2799 kubelet_node_status.go:271] Setting node annotation to enable volume controller attach/detach
2799 kubelet_node_status.go:82] Attempting to register node minikube
2799 kubelet_node_status.go:106] Unable to register node "minikube" with API server: Post https://localhost:8443/api/v1/nodes: dial tcp 127.0.0.1:8443: getsockopt: connection refused
2799 kubelet.go:1794] skipping pod synchronization - [container runtime is down]
2799 kubelet_node_status.go:271] Setting node annotation to enable volume controller attach/detach
2799 kubelet_node_status.go:82] Attempting to register node minikube
2799 kubelet_node_status.go:106] Unable to register node "minikube" with API server: Post https://localhost:8443/api/v1/nodes: dial tcp 127.0.0.1:8443: getsockopt: connection refused
2799 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:460: Failed to list *v1.Node: Get https://localhost:8443/api/v1/nodes?fieldSelector=metadata.name%3Dminikube&limit=500&resourceVersion=0: dial tcp 127.0.0.1:8443: getsockopt: connection refused
2799 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:451: Failed to list *v1.Service: Get https://localhost:8443/api/v1/services?limit=500&resourceVersion=0: dial tcp 127.0.0.1:8443: getsockopt: connection refused
2799 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://localhost:8443/api/v1/pods?fieldSelector=spec.nodeName%3Dminikube&limit=500&resourceVersion=0: dial tcp 127.0.0.1:8443: getsockopt: connection refused
2799 kubelet.go:1794] skipping pod synchronization - [container runtime is down]
2799 kubelet_node_status.go:271] Setting node annotation to enable volume controller attach/detach
2799 kubelet_node_status.go:82] Attempting to register node minikube
2799 kubelet_node_status.go:106] Unable to register node "minikube" with API server: Post https://localhost:8443/api/v1/nodes: dial tcp 127.0.0.1:8443: getsockopt: connection refused
2799 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:460: Failed to list *v1.Node: Get https://localhost:8443/api/v1/nodes?fieldSelector=metadata.name%3Dminikube&limit=500&resourceVersion=0: dial tcp 127.0.0.1:8443: getsockopt: connection refused
2799 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:451: Failed to list *v1.Service: Get https://localhost:8443/api/v1/services?limit=500&resourceVersion=0: dial tcp 127.0.0.1:8443: getsockopt: connection refused
2799 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://localhost:8443/api/v1/pods?fieldSelector=spec.nodeName%3Dminikube&limit=500&resourceVersion=0: dial tcp 127.0.0.1:8443: getsockopt: connection refused
2799 kubelet_node_status.go:271] Setting node annotation to enable volume controller attach/detach
2799 cpu_manager.go:155] [cpumanager] starting with none policy
2799 cpu_manager.go:156] [cpumanager] reconciling every 10s
2799 policy_none.go:42] [cpumanager] none policy: Start
Plugin manager
2799 eviction_manager.go:246] eviction manager: failed to get get summary stats: failed to get node info: node "minikube" not found
2799 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:460: Failed to list *v1.Node: Get https://localhost:8443/api/v1/nodes?fieldSelector=metadata.name%3Dminikube&limit=500&resourceVersion=0: dial tcp 127.0.0.1:8443: getsockopt: connection refused
2799 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:451: Failed to list *v1.Service: Get https://localhost:8443/api/v1/services?limit=500&resourceVersion=0: dial tcp 127.0.0.1:8443: getsockopt: connection refused
2799 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://localhost:8443/api/v1/pods?fieldSelector=spec.nodeName%3Dminikube&limit=500&resourceVersion=0: dial tcp 127.0.0.1:8443: getsockopt: connection refused
2799 kubelet_node_status.go:271] Setting node annotation to enable volume controller attach/detach
2799 kubelet_node_status.go:271] Setting node annotation to enable volume controller attach/detach
2799 kubelet_node_status.go:271] Setting node annotation to enable volume controller attach/detach
2799 reconciler.go:207] operationExecutor.VerifyControllerAttachedVolume started for volume "etcd-data" (UniqueName: "kubernetes.io/host-path/b8f756ea85895bda697065768b18a93a-etcd-data") pod "etcd-minikube" (UID: "b8f756ea85895bda697065768b18a93a")
2799 reconciler.go:207] operationExecutor.VerifyControllerAttachedVolume started for volume "etcd-certs" (UniqueName: "kubernetes.io/host-path/b8f756ea85895bda697065768b18a93a-etcd-certs") pod "etcd-minikube" (UID: "b8f756ea85895bda697065768b18a93a")
2799 kubelet_node_status.go:271] Setting node annotation to enable volume controller attach/detach
2799 kubelet_node_status.go:82] Attempting to register node minikube
2799 kubelet_node_status.go:106] Unable to register node "minikube" with API server: Post https://localhost:8443/api/v1/nodes: dial tcp 127.0.0.1:8443: getsockopt: connection refused
2799 status_manager.go:461] Failed to get status for pod "etcd-minikube_kube-system(b8f756ea85895bda697065768b18a93a)": Get https://localhost:8443/api/v1/namespaces/kube-system/pods/etcd-minikube: dial tcp 127.0.0.1:8443: getsockopt: connection refused
2799 kubelet_node_status.go:271] Setting node annotation to enable volume controller attach/detach
2799 kubelet_node_status.go:271] Setting node annotation to enable volume controller attach/detach
2799 status_manager.go:461] Failed to get status for pod "kube-apiserver-minikube_kube-system(f310a64a00b8dfb921ddaee9f1867742)": Get https://localhost:8443/api/v1/namespaces/kube-system/pods/kube-apiserver-minikube: dial tcp 127.0.0.1:8443: getsockopt: connection refused
2799 kubelet_node_status.go:271] Setting node annotation to enable volume controller attach/detach
2799 kubelet_node_status.go:271] Setting node annotation to enable volume controller attach/detach
2799 kubelet_node_status.go:271] Setting node annotation to enable volume controller attach/detach
2799 kubelet_node_status.go:271] Setting node annotation to enable volume controller attach/detach
2799 status_manager.go:461] Failed to get status for pod "kube-controller-manager-minikube_kube-system(190578c14f9dbb22cf9d402d93b045c3)": Get https://localhost:8443/api/v1/namespaces/kube-system/pods/kube-controller-manager-minikube: dial tcp 127.0.0.1:8443: getsockopt: connection refused
2799 status_manager.go:461] Failed to get status for pod "kube-scheduler-minikube_kube-system(31cf0ccbee286239d451edb6fb511513)": Get https://localhost:8443/api/v1/namespaces/kube-system/pods/kube-scheduler-minikube: dial tcp 127.0.0.1:8443: getsockopt: connection refused
2799 pod_container_deletor.go:77] Container "ff6a3f4cfc33a53e1b7272a145d47602d7b8ec95cd357c58b112c2aa5c7f03ad" not found in pod's containers
2799 pod_container_deletor.go:77] Container "68921dfde66a2490cce602258270a3f326b9244a1da86e8c3bfb804427e12aea" not found in pod's containers
2799 kubelet_node_status.go:271] Setting node annotation to enable volume controller attach/detach
2799 kubelet_node_status.go:271] Setting node annotation to enable volume controller attach/detach
2799 kubelet_node_status.go:271] Setting node annotation to enable volume controller attach/detach
2799 status_manager.go:461] Failed to get status for pod "kube-addon-manager-minikube_kube-system(3afaf06535cc3b85be93c31632b765da)": Get https://localhost:8443/api/v1/namespaces/kube-system/pods/kube-addon-manager-minikube: dial tcp 127.0.0.1:8443: getsockopt: connection refused
2799 pod_container_deletor.go:77] Container "32f2dc81f99d6b354f2ef65743e64eb4b0ceca0323410d155dc24b486a81a427" not found in pod's containers
2799 pod_container_deletor.go:77] Container "750d82e2b7b5ad35832a0a17ce3b211f070d61f986188889c616667383612bec" not found in pod's containers
2799 kubelet_node_status.go:271] Setting node annotation to enable volume controller attach/detach
2799 kubelet_node_status.go:271] Setting node annotation to enable volume controller attach/detach
2799 pod_container_deletor.go:77] Container "9d39e2134b26d8bda5a1a272ba6da707fdbf9d51c06bad73149743c10ebf47bf" not found in pod's containers
2799 pod_container_deletor.go:77] Container "dec383721ca8ba10ad895ea757be43662e44bcff1a1b5b3684d818284ba4eb15" not found in pod's containers
2799 pod_container_deletor.go:77] Container "c83b4bae67eb3aa901f737f4fcfd77ab10b1ac99dc792e28b3cd3071e33bebe0" not found in pod's containers
2799 pod_container_deletor.go:77] Container "d8f43c85cf9b5aacea12546e771795a39dec43f899ddca684727648b9eeed6e1" not found in pod's containers
2799 reconciler.go:207] operationExecutor.VerifyControllerAttachedVolume started for volume "k8s-certs" (UniqueName: "kubernetes.io/host-path/f310a64a00b8dfb921ddaee9f1867742-k8s-certs") pod "kube-apiserver-minikube" (UID: "f310a64a00b8dfb921ddaee9f1867742")
2799 reconciler.go:207] operationExecutor.VerifyControllerAttachedVolume started for volume "ca-certs" (UniqueName: "kubernetes.io/host-path/f310a64a00b8dfb921ddaee9f1867742-ca-certs") pod "kube-apiserver-minikube" (UID: "f310a64a00b8dfb921ddaee9f1867742")
2799 reconciler.go:207] operationExecutor.VerifyControllerAttachedVolume started for volume "ca-certs" (UniqueName: "kubernetes.io/host-path/190578c14f9dbb22cf9d402d93b045c3-ca-certs") pod "kube-controller-manager-minikube" (UID: "190578c14f9dbb22cf9d402d93b045c3")
2799 reconciler.go:207] operationExecutor.VerifyControllerAttachedVolume started for volume "kubeconfig" (UniqueName: "kubernetes.io/host-path/3afaf06535cc3b85be93c31632b765da-kubeconfig") pod "kube-addon-manager-minikube" (UID: "3afaf06535cc3b85be93c31632b765da")
2799 reconciler.go:207] operationExecutor.VerifyControllerAttachedVolume started for volume "kubeconfig" (UniqueName: "kubernetes.io/host-path/190578c14f9dbb22cf9d402d93b045c3-kubeconfig") pod "kube-controller-manager-minikube" (UID: "190578c14f9dbb22cf9d402d93b045c3")
2799 reconciler.go:207] operationExecutor.VerifyControllerAttachedVolume started for volume "kubeconfig" (UniqueName: "kubernetes.io/host-path/31cf0ccbee286239d451edb6fb511513-kubeconfig") pod "kube-scheduler-minikube" (UID: "31cf0ccbee286239d451edb6fb511513")
2799 reconciler.go:207] operationExecutor.VerifyControllerAttachedVolume started for volume "addons" (UniqueName: "kubernetes.io/host-path/3afaf06535cc3b85be93c31632b765da-addons") pod "kube-addon-manager-minikube" (UID: "3afaf06535cc3b85be93c31632b765da")
2799 reconciler.go:207] operationExecutor.VerifyControllerAttachedVolume started for volume "k8s-certs" (UniqueName: "kubernetes.io/host-path/190578c14f9dbb22cf9d402d93b045c3-k8s-certs") pod "kube-controller-manager-minikube" (UID: "190578c14f9dbb22cf9d402d93b045c3")
2799 kuberuntime_manager.go:757] checking backoff for container "kube-scheduler" in pod "kube-scheduler-minikube_kube-system(31cf0ccbee286239d451edb6fb511513)"
2799 kuberuntime_manager.go:757] checking backoff for container "kube-addon-manager" in pod "kube-addon-manager-minikube_kube-system(3afaf06535cc3b85be93c31632b765da)"
2799 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:460: Failed to list *v1.Node: Get https://localhost:8443/api/v1/nodes?fieldSelector=metadata.name%3Dminikube&limit=500&resourceVersion=0: dial tcp 127.0.0.1:8443: getsockopt: connection refused
2799 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:451: Failed to list *v1.Service: Get https://localhost:8443/api/v1/services?limit=500&resourceVersion=0: dial tcp 127.0.0.1:8443: getsockopt: connection refused
2799 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://localhost:8443/api/v1/pods?fieldSelector=spec.nodeName%3Dminikube&limit=500&resourceVersion=0: dial tcp 127.0.0.1:8443: getsockopt: connection refused
2799 kubelet_node_status.go:271] Setting node annotation to enable volume controller attach/detach
2799 status_manager.go:461] Failed to get status for pod "kube-scheduler-minikube_kube-system(31cf0ccbee286239d451edb6fb511513)": Get https://localhost:8443/api/v1/namespaces/kube-system/pods/kube-scheduler-minikube: dial tcp 127.0.0.1:8443: getsockopt: connection refused
2799 kubelet_node_status.go:271] Setting node annotation to enable volume controller attach/detach
2799 status_manager.go:461] Failed to get status for pod "kube-apiserver-minikube_kube-system(f310a64a00b8dfb921ddaee9f1867742)": Get https://localhost:8443/api/v1/namespaces/kube-system/pods/kube-apiserver-minikube: dial tcp 127.0.0.1:8443: getsockopt: connection refused
2799 kubelet_node_status.go:271] Setting node annotation to enable volume controller attach/detach
2799 status_manager.go:461] Failed to get status for pod "etcd-minikube_kube-system(b8f756ea85895bda697065768b18a93a)": Get https://localhost:8443/api/v1/namespaces/kube-system/pods/etcd-minikube: dial tcp 127.0.0.1:8443: getsockopt: connection refused
2799 kubelet_node_status.go:271] Setting node annotation to enable volume controller attach/detach
2799 status_manager.go:461] Failed to get status for pod "kube-controller-manager-minikube_kube-system(190578c14f9dbb22cf9d402d93b045c3)": Get https://localhost:8443/api/v1/namespaces/kube-system/pods/kube-controller-manager-minikube: dial tcp 127.0.0.1:8443: getsockopt: connection refused
2799 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:460: Failed to list *v1.Node: Get https://localhost:8443/api/v1/nodes?fieldSelector=metadata.name%3Dminikube&limit=500&resourceVersion=0: dial tcp 127.0.0.1:8443: getsockopt: connection refused
2799 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:451: Failed to list *v1.Service: Get https://localhost:8443/api/v1/services?limit=500&resourceVersion=0: dial tcp 127.0.0.1:8443: getsockopt: connection refused
2799 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://localhost:8443/api/v1/pods?fieldSelector=spec.nodeName%3Dminikube&limit=500&resourceVersion=0: dial tcp 127.0.0.1:8443: getsockopt: connection refused
2799 kubelet_node_status.go:271] Setting node annotation to enable volume controller attach/detach
2799 kubelet_node_status.go:271] Setting node annotation to enable volume controller attach/detach
2799 kubelet_node_status.go:271] Setting node annotation to enable volume controller attach/detach
2799 kubelet_node_status.go:271] Setting node annotation to enable volume controller attach/detach
2799 kubelet_node_status.go:271] Setting node annotation to enable volume controller attach/detach
2799 kubelet_node_status.go:271] Setting node annotation to enable volume controller attach/detach
2799 kubelet_node_status.go:82] Attempting to register node minikube
2799 kubelet_node_status.go:271] Setting node annotation to enable volume controller attach/detach
2799 kubelet.go:1602] Deleting mirror pod "etcd-minikube_kube-system(975c313f-bc57-11e8-9b63-080027824c94)" because it is outdated
2799 kubelet.go:1602] Deleting mirror pod "kube-apiserver-minikube_kube-system(9677af06-bc57-11e8-9b63-080027824c94)" because it is outdated
2799 kubelet.go:1602] Deleting mirror pod "kube-controller-manager-minikube_kube-system(9677e29f-bc57-11e8-9b63-080027824c94)" because it is outdated
2799 reconciler.go:207] operationExecutor.VerifyControllerAttachedVolume started for volume "tmp" (UniqueName: "kubernetes.io/host-path/f599affd-bc4d-11e8-8617-080027824c94-tmp") pod "storage-provisioner" (UID: "f599affd-bc4d-11e8-8617-080027824c94")
2799 reconciler.go:207] operationExecutor.VerifyControllerAttachedVolume started for volume "default-token-xjkss" (UniqueName: "kubernetes.io/secret/f59107f4-bc4d-11e8-8617-080027824c94-default-token-xjkss") pod "kubernetes-dashboard-5498ccf677-g4hqx" (UID: "f59107f4-bc4d-11e8-8617-080027824c94")
2799 reconciler.go:207] operationExecutor.VerifyControllerAttachedVolume started for volume "storage-provisioner-token-cd9hj" (UniqueName: "kubernetes.io/secret/f599affd-bc4d-11e8-8617-080027824c94-storage-provisioner-token-cd9hj") pod "storage-provisioner" (UID: "f599affd-bc4d-11e8-8617-080027824c94")
2799 reconciler.go:154] Reconciler: start to sync state
2799 kubelet_node_status.go:127] Node minikube was previously registered
2799 kubelet_node_status.go:85] Successfully registered node minikube
2799 kuberuntime_manager.go:513] Container {Name:storage-provisioner Image:gcr.io/k8s-minikube/storage-provisioner:v1.8.1 Command:[/storage-provisioner] Args:[] WorkingDir: Ports:[] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:tmp ReadOnly:false MountPath:/tmp SubPath: MountPropagation:} {Name:storage-provisioner-token-cd9hj ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:nil ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "storage-provisioner" in pod "storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:storage-provisioner Image:gcr.io/k8s-minikube/storage-provisioner:v1.8.1 Command:[/storage-provisioner] Args:[] WorkingDir: Ports:[] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:tmp ReadOnly:false MountPath:/tmp SubPath: MountPropagation:} {Name:storage-provisioner-token-cd9hj ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:nil ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "storage-provisioner" in pod "storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 10s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f599affd-bc4d-11e8-8617-080027824c94 ("storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "storage-provisioner" with CrashLoopBackOff: "Back-off 10s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:storage-provisioner Image:gcr.io/k8s-minikube/storage-provisioner:v1.8.1 Command:[/storage-provisioner] Args:[] WorkingDir: Ports:[] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:tmp ReadOnly:false MountPath:/tmp SubPath: MountPropagation:} {Name:storage-provisioner-token-cd9hj ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:nil ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "storage-provisioner" in pod "storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:kubernetes-dashboard Image:k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.1 Command:[] Args:[] WorkingDir: Ports:[{Name: HostPort:0 ContainerPort:9090 Protocol:TCP HostIP:}] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-xjkss ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:&Probe{Handler:Handler{Exec:nil,HTTPGet:&HTTPGetAction{Path:/,Port:9090,Host:,Scheme:HTTP,HTTPHeaders:[],},TCPSocket:nil,},InitialDelaySeconds:30,TimeoutSeconds:30,PeriodSeconds:10,SuccessThreshold:1,FailureThreshold:3,} ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "kubernetes-dashboard" in pod "kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:storage-provisioner Image:gcr.io/k8s-minikube/storage-provisioner:v1.8.1 Command:[/storage-provisioner] Args:[] WorkingDir: Ports:[] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:tmp ReadOnly:false MountPath:/tmp SubPath: MountPropagation:} {Name:storage-provisioner-token-cd9hj ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:nil ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "storage-provisioner" in pod "storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 20s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f599affd-bc4d-11e8-8617-080027824c94 ("storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "storage-provisioner" with CrashLoopBackOff: "Back-off 20s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:kubernetes-dashboard Image:k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.1 Command:[] Args:[] WorkingDir: Ports:[{Name: HostPort:0 ContainerPort:9090 Protocol:TCP HostIP:}] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-xjkss ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:&Probe{Handler:Handler{Exec:nil,HTTPGet:&HTTPGetAction{Path:/,Port:9090,Host:,Scheme:HTTP,HTTPHeaders:[],},TCPSocket:nil,},InitialDelaySeconds:30,TimeoutSeconds:30,PeriodSeconds:10,SuccessThreshold:1,FailureThreshold:3,} ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "kubernetes-dashboard" in pod "kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 10s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f59107f4-bc4d-11e8-8617-080027824c94 ("kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "kubernetes-dashboard" with CrashLoopBackOff: "Back-off 10s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:kubernetes-dashboard Image:k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.1 Command:[] Args:[] WorkingDir: Ports:[{Name: HostPort:0 ContainerPort:9090 Protocol:TCP HostIP:}] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-xjkss ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:&Probe{Handler:Handler{Exec:nil,HTTPGet:&HTTPGetAction{Path:/,Port:9090,Host:,Scheme:HTTP,HTTPHeaders:[],},TCPSocket:nil,},InitialDelaySeconds:30,TimeoutSeconds:30,PeriodSeconds:10,SuccessThreshold:1,FailureThreshold:3,} ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "kubernetes-dashboard" in pod "kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 10s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f59107f4-bc4d-11e8-8617-080027824c94 ("kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "kubernetes-dashboard" with CrashLoopBackOff: "Back-off 10s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:storage-provisioner Image:gcr.io/k8s-minikube/storage-provisioner:v1.8.1 Command:[/storage-provisioner] Args:[] WorkingDir: Ports:[] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:tmp ReadOnly:false MountPath:/tmp SubPath: MountPropagation:} {Name:storage-provisioner-token-cd9hj ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:nil ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "storage-provisioner" in pod "storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 20s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f599affd-bc4d-11e8-8617-080027824c94 ("storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "storage-provisioner" with CrashLoopBackOff: "Back-off 20s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:kubernetes-dashboard Image:k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.1 Command:[] Args:[] WorkingDir: Ports:[{Name: HostPort:0 ContainerPort:9090 Protocol:TCP HostIP:}] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-xjkss ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:&Probe{Handler:Handler{Exec:nil,HTTPGet:&HTTPGetAction{Path:/,Port:9090,Host:,Scheme:HTTP,HTTPHeaders:[],},TCPSocket:nil,},InitialDelaySeconds:30,TimeoutSeconds:30,PeriodSeconds:10,SuccessThreshold:1,FailureThreshold:3,} ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "kubernetes-dashboard" in pod "kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:storage-provisioner Image:gcr.io/k8s-minikube/storage-provisioner:v1.8.1 Command:[/storage-provisioner] Args:[] WorkingDir: Ports:[] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:tmp ReadOnly:false MountPath:/tmp SubPath: MountPropagation:} {Name:storage-provisioner-token-cd9hj ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:nil ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "storage-provisioner" in pod "storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:kubernetes-dashboard Image:k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.1 Command:[] Args:[] WorkingDir: Ports:[{Name: HostPort:0 ContainerPort:9090 Protocol:TCP HostIP:}] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-xjkss ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:&Probe{Handler:Handler{Exec:nil,HTTPGet:&HTTPGetAction{Path:/,Port:9090,Host:,Scheme:HTTP,HTTPHeaders:[],},TCPSocket:nil,},InitialDelaySeconds:30,TimeoutSeconds:30,PeriodSeconds:10,SuccessThreshold:1,FailureThreshold:3,} ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "kubernetes-dashboard" in pod "kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 20s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f59107f4-bc4d-11e8-8617-080027824c94 ("kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "kubernetes-dashboard" with CrashLoopBackOff: "Back-off 20s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:storage-provisioner Image:gcr.io/k8s-minikube/storage-provisioner:v1.8.1 Command:[/storage-provisioner] Args:[] WorkingDir: Ports:[] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:tmp ReadOnly:false MountPath:/tmp SubPath: MountPropagation:} {Name:storage-provisioner-token-cd9hj ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:nil ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "storage-provisioner" in pod "storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 40s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f599affd-bc4d-11e8-8617-080027824c94 ("storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "storage-provisioner" with CrashLoopBackOff: "Back-off 40s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:kubernetes-dashboard Image:k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.1 Command:[] Args:[] WorkingDir: Ports:[{Name: HostPort:0 ContainerPort:9090 Protocol:TCP HostIP:}] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-xjkss ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:&Probe{Handler:Handler{Exec:nil,HTTPGet:&HTTPGetAction{Path:/,Port:9090,Host:,Scheme:HTTP,HTTPHeaders:[],},TCPSocket:nil,},InitialDelaySeconds:30,TimeoutSeconds:30,PeriodSeconds:10,SuccessThreshold:1,FailureThreshold:3,} ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "kubernetes-dashboard" in pod "kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 20s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f59107f4-bc4d-11e8-8617-080027824c94 ("kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "kubernetes-dashboard" with CrashLoopBackOff: "Back-off 20s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:kubernetes-dashboard Image:k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.1 Command:[] Args:[] WorkingDir: Ports:[{Name: HostPort:0 ContainerPort:9090 Protocol:TCP HostIP:}] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-xjkss ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:&Probe{Handler:Handler{Exec:nil,HTTPGet:&HTTPGetAction{Path:/,Port:9090,Host:,Scheme:HTTP,HTTPHeaders:[],},TCPSocket:nil,},InitialDelaySeconds:30,TimeoutSeconds:30,PeriodSeconds:10,SuccessThreshold:1,FailureThreshold:3,} ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "kubernetes-dashboard" in pod "kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 20s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f59107f4-bc4d-11e8-8617-080027824c94 ("kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "kubernetes-dashboard" with CrashLoopBackOff: "Back-off 20s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:storage-provisioner Image:gcr.io/k8s-minikube/storage-provisioner:v1.8.1 Command:[/storage-provisioner] Args:[] WorkingDir: Ports:[] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:tmp ReadOnly:false MountPath:/tmp SubPath: MountPropagation:} {Name:storage-provisioner-token-cd9hj ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:nil ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "storage-provisioner" in pod "storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 40s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f599affd-bc4d-11e8-8617-080027824c94 ("storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "storage-provisioner" with CrashLoopBackOff: "Back-off 40s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:kubernetes-dashboard Image:k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.1 Command:[] Args:[] WorkingDir: Ports:[{Name: HostPort:0 ContainerPort:9090 Protocol:TCP HostIP:}] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-xjkss ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:&Probe{Handler:Handler{Exec:nil,HTTPGet:&HTTPGetAction{Path:/,Port:9090,Host:,Scheme:HTTP,HTTPHeaders:[],},TCPSocket:nil,},InitialDelaySeconds:30,TimeoutSeconds:30,PeriodSeconds:10,SuccessThreshold:1,FailureThreshold:3,} ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "kubernetes-dashboard" in pod "kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:storage-provisioner Image:gcr.io/k8s-minikube/storage-provisioner:v1.8.1 Command:[/storage-provisioner] Args:[] WorkingDir: Ports:[] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:tmp ReadOnly:false MountPath:/tmp SubPath: MountPropagation:} {Name:storage-provisioner-token-cd9hj ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:nil ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "storage-provisioner" in pod "storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 40s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f599affd-bc4d-11e8-8617-080027824c94 ("storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "storage-provisioner" with CrashLoopBackOff: "Back-off 40s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:storage-provisioner Image:gcr.io/k8s-minikube/storage-provisioner:v1.8.1 Command:[/storage-provisioner] Args:[] WorkingDir: Ports:[] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:tmp ReadOnly:false MountPath:/tmp SubPath: MountPropagation:} {Name:storage-provisioner-token-cd9hj ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:nil ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "storage-provisioner" in pod "storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:kubernetes-dashboard Image:k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.1 Command:[] Args:[] WorkingDir: Ports:[{Name: HostPort:0 ContainerPort:9090 Protocol:TCP HostIP:}] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-xjkss ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:&Probe{Handler:Handler{Exec:nil,HTTPGet:&HTTPGetAction{Path:/,Port:9090,Host:,Scheme:HTTP,HTTPHeaders:[],},TCPSocket:nil,},InitialDelaySeconds:30,TimeoutSeconds:30,PeriodSeconds:10,SuccessThreshold:1,FailureThreshold:3,} ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "kubernetes-dashboard" in pod "kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 40s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f59107f4-bc4d-11e8-8617-080027824c94 ("kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "kubernetes-dashboard" with CrashLoopBackOff: "Back-off 40s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:kubernetes-dashboard Image:k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.1 Command:[] Args:[] WorkingDir: Ports:[{Name: HostPort:0 ContainerPort:9090 Protocol:TCP HostIP:}] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-xjkss ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:&Probe{Handler:Handler{Exec:nil,HTTPGet:&HTTPGetAction{Path:/,Port:9090,Host:,Scheme:HTTP,HTTPHeaders:[],},TCPSocket:nil,},InitialDelaySeconds:30,TimeoutSeconds:30,PeriodSeconds:10,SuccessThreshold:1,FailureThreshold:3,} ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "kubernetes-dashboard" in pod "kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 40s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f59107f4-bc4d-11e8-8617-080027824c94 ("kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "kubernetes-dashboard" with CrashLoopBackOff: "Back-off 40s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:storage-provisioner Image:gcr.io/k8s-minikube/storage-provisioner:v1.8.1 Command:[/storage-provisioner] Args:[] WorkingDir: Ports:[] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:tmp ReadOnly:false MountPath:/tmp SubPath: MountPropagation:} {Name:storage-provisioner-token-cd9hj ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:nil ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "storage-provisioner" in pod "storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 1m20s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f599affd-bc4d-11e8-8617-080027824c94 ("storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "storage-provisioner" with CrashLoopBackOff: "Back-off 1m20s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:kubernetes-dashboard Image:k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.1 Command:[] Args:[] WorkingDir: Ports:[{Name: HostPort:0 ContainerPort:9090 Protocol:TCP HostIP:}] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-xjkss ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:&Probe{Handler:Handler{Exec:nil,HTTPGet:&HTTPGetAction{Path:/,Port:9090,Host:,Scheme:HTTP,HTTPHeaders:[],},TCPSocket:nil,},InitialDelaySeconds:30,TimeoutSeconds:30,PeriodSeconds:10,SuccessThreshold:1,FailureThreshold:3,} ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "kubernetes-dashboard" in pod "kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 40s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f59107f4-bc4d-11e8-8617-080027824c94 ("kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "kubernetes-dashboard" with CrashLoopBackOff: "Back-off 40s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:kubernetes-dashboard Image:k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.1 Command:[] Args:[] WorkingDir: Ports:[{Name: HostPort:0 ContainerPort:9090 Protocol:TCP HostIP:}] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-xjkss ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:&Probe{Handler:Handler{Exec:nil,HTTPGet:&HTTPGetAction{Path:/,Port:9090,Host:,Scheme:HTTP,HTTPHeaders:[],},TCPSocket:nil,},InitialDelaySeconds:30,TimeoutSeconds:30,PeriodSeconds:10,SuccessThreshold:1,FailureThreshold:3,} ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "kubernetes-dashboard" in pod "kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 40s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f59107f4-bc4d-11e8-8617-080027824c94 ("kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "kubernetes-dashboard" with CrashLoopBackOff: "Back-off 40s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:storage-provisioner Image:gcr.io/k8s-minikube/storage-provisioner:v1.8.1 Command:[/storage-provisioner] Args:[] WorkingDir: Ports:[] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:tmp ReadOnly:false MountPath:/tmp SubPath: MountPropagation:} {Name:storage-provisioner-token-cd9hj ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:nil ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "storage-provisioner" in pod "storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 1m20s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f599affd-bc4d-11e8-8617-080027824c94 ("storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "storage-provisioner" with CrashLoopBackOff: "Back-off 1m20s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:kubernetes-dashboard Image:k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.1 Command:[] Args:[] WorkingDir: Ports:[{Name: HostPort:0 ContainerPort:9090 Protocol:TCP HostIP:}] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-xjkss ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:&Probe{Handler:Handler{Exec:nil,HTTPGet:&HTTPGetAction{Path:/,Port:9090,Host:,Scheme:HTTP,HTTPHeaders:[],},TCPSocket:nil,},InitialDelaySeconds:30,TimeoutSeconds:30,PeriodSeconds:10,SuccessThreshold:1,FailureThreshold:3,} ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "kubernetes-dashboard" in pod "kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 40s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f59107f4-bc4d-11e8-8617-080027824c94 ("kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "kubernetes-dashboard" with CrashLoopBackOff: "Back-off 40s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:storage-provisioner Image:gcr.io/k8s-minikube/storage-provisioner:v1.8.1 Command:[/storage-provisioner] Args:[] WorkingDir: Ports:[] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:tmp ReadOnly:false MountPath:/tmp SubPath: MountPropagation:} {Name:storage-provisioner-token-cd9hj ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:nil ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "storage-provisioner" in pod "storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 1m20s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f599affd-bc4d-11e8-8617-080027824c94 ("storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "storage-provisioner" with CrashLoopBackOff: "Back-off 1m20s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:kubernetes-dashboard Image:k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.1 Command:[] Args:[] WorkingDir: Ports:[{Name: HostPort:0 ContainerPort:9090 Protocol:TCP HostIP:}] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-xjkss ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:&Probe{Handler:Handler{Exec:nil,HTTPGet:&HTTPGetAction{Path:/,Port:9090,Host:,Scheme:HTTP,HTTPHeaders:[],},TCPSocket:nil,},InitialDelaySeconds:30,TimeoutSeconds:30,PeriodSeconds:10,SuccessThreshold:1,FailureThreshold:3,} ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "kubernetes-dashboard" in pod "kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:storage-provisioner Image:gcr.io/k8s-minikube/storage-provisioner:v1.8.1 Command:[/storage-provisioner] Args:[] WorkingDir: Ports:[] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:tmp ReadOnly:false MountPath:/tmp SubPath: MountPropagation:} {Name:storage-provisioner-token-cd9hj ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:nil ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "storage-provisioner" in pod "storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 1m20s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f599affd-bc4d-11e8-8617-080027824c94 ("storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "storage-provisioner" with CrashLoopBackOff: "Back-off 1m20s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:storage-provisioner Image:gcr.io/k8s-minikube/storage-provisioner:v1.8.1 Command:[/storage-provisioner] Args:[] WorkingDir: Ports:[] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:tmp ReadOnly:false MountPath:/tmp SubPath: MountPropagation:} {Name:storage-provisioner-token-cd9hj ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:nil ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "storage-provisioner" in pod "storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 1m20s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f599affd-bc4d-11e8-8617-080027824c94 ("storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "storage-provisioner" with CrashLoopBackOff: "Back-off 1m20s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:kubernetes-dashboard Image:k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.1 Command:[] Args:[] WorkingDir: Ports:[{Name: HostPort:0 ContainerPort:9090 Protocol:TCP HostIP:}] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-xjkss ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:&Probe{Handler:Handler{Exec:nil,HTTPGet:&HTTPGetAction{Path:/,Port:9090,Host:,Scheme:HTTP,HTTPHeaders:[],},TCPSocket:nil,},InitialDelaySeconds:30,TimeoutSeconds:30,PeriodSeconds:10,SuccessThreshold:1,FailureThreshold:3,} ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "kubernetes-dashboard" in pod "kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 1m20s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f59107f4-bc4d-11e8-8617-080027824c94 ("kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "kubernetes-dashboard" with CrashLoopBackOff: "Back-off 1m20s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:kubernetes-dashboard Image:k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.1 Command:[] Args:[] WorkingDir: Ports:[{Name: HostPort:0 ContainerPort:9090 Protocol:TCP HostIP:}] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-xjkss ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:&Probe{Handler:Handler{Exec:nil,HTTPGet:&HTTPGetAction{Path:/,Port:9090,Host:,Scheme:HTTP,HTTPHeaders:[],},TCPSocket:nil,},InitialDelaySeconds:30,TimeoutSeconds:30,PeriodSeconds:10,SuccessThreshold:1,FailureThreshold:3,} ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "kubernetes-dashboard" in pod "kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 1m20s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f59107f4-bc4d-11e8-8617-080027824c94 ("kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "kubernetes-dashboard" with CrashLoopBackOff: "Back-off 1m20s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:storage-provisioner Image:gcr.io/k8s-minikube/storage-provisioner:v1.8.1 Command:[/storage-provisioner] Args:[] WorkingDir: Ports:[] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:tmp ReadOnly:false MountPath:/tmp SubPath: MountPropagation:} {Name:storage-provisioner-token-cd9hj ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:nil ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "storage-provisioner" in pod "storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 1m20s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f599affd-bc4d-11e8-8617-080027824c94 ("storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "storage-provisioner" with CrashLoopBackOff: "Back-off 1m20s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:kubernetes-dashboard Image:k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.1 Command:[] Args:[] WorkingDir: Ports:[{Name: HostPort:0 ContainerPort:9090 Protocol:TCP HostIP:}] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-xjkss ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:&Probe{Handler:Handler{Exec:nil,HTTPGet:&HTTPGetAction{Path:/,Port:9090,Host:,Scheme:HTTP,HTTPHeaders:[],},TCPSocket:nil,},InitialDelaySeconds:30,TimeoutSeconds:30,PeriodSeconds:10,SuccessThreshold:1,FailureThreshold:3,} ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "kubernetes-dashboard" in pod "kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 1m20s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f59107f4-bc4d-11e8-8617-080027824c94 ("kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "kubernetes-dashboard" with CrashLoopBackOff: "Back-off 1m20s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:storage-provisioner Image:gcr.io/k8s-minikube/storage-provisioner:v1.8.1 Command:[/storage-provisioner] Args:[] WorkingDir: Ports:[] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:tmp ReadOnly:false MountPath:/tmp SubPath: MountPropagation:} {Name:storage-provisioner-token-cd9hj ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:nil ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "storage-provisioner" in pod "storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:kubernetes-dashboard Image:k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.1 Command:[] Args:[] WorkingDir: Ports:[{Name: HostPort:0 ContainerPort:9090 Protocol:TCP HostIP:}] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-xjkss ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:&Probe{Handler:Handler{Exec:nil,HTTPGet:&HTTPGetAction{Path:/,Port:9090,Host:,Scheme:HTTP,HTTPHeaders:[],},TCPSocket:nil,},InitialDelaySeconds:30,TimeoutSeconds:30,PeriodSeconds:10,SuccessThreshold:1,FailureThreshold:3,} ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "kubernetes-dashboard" in pod "kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 1m20s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f59107f4-bc4d-11e8-8617-080027824c94 ("kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "kubernetes-dashboard" with CrashLoopBackOff: "Back-off 1m20s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:kubernetes-dashboard Image:k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.1 Command:[] Args:[] WorkingDir: Ports:[{Name: HostPort:0 ContainerPort:9090 Protocol:TCP HostIP:}] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-xjkss ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:&Probe{Handler:Handler{Exec:nil,HTTPGet:&HTTPGetAction{Path:/,Port:9090,Host:,Scheme:HTTP,HTTPHeaders:[],},TCPSocket:nil,},InitialDelaySeconds:30,TimeoutSeconds:30,PeriodSeconds:10,SuccessThreshold:1,FailureThreshold:3,} ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "kubernetes-dashboard" in pod "kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 1m20s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f59107f4-bc4d-11e8-8617-080027824c94 ("kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "kubernetes-dashboard" with CrashLoopBackOff: "Back-off 1m20s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:storage-provisioner Image:gcr.io/k8s-minikube/storage-provisioner:v1.8.1 Command:[/storage-provisioner] Args:[] WorkingDir: Ports:[] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:tmp ReadOnly:false MountPath:/tmp SubPath: MountPropagation:} {Name:storage-provisioner-token-cd9hj ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:nil ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "storage-provisioner" in pod "storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 2m40s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f599affd-bc4d-11e8-8617-080027824c94 ("storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "storage-provisioner" with CrashLoopBackOff: "Back-off 2m40s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:kubernetes-dashboard Image:k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.1 Command:[] Args:[] WorkingDir: Ports:[{Name: HostPort:0 ContainerPort:9090 Protocol:TCP HostIP:}] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-xjkss ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:&Probe{Handler:Handler{Exec:nil,HTTPGet:&HTTPGetAction{Path:/,Port:9090,Host:,Scheme:HTTP,HTTPHeaders:[],},TCPSocket:nil,},InitialDelaySeconds:30,TimeoutSeconds:30,PeriodSeconds:10,SuccessThreshold:1,FailureThreshold:3,} ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "kubernetes-dashboard" in pod "kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 1m20s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f59107f4-bc4d-11e8-8617-080027824c94 ("kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "kubernetes-dashboard" with CrashLoopBackOff: "Back-off 1m20s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:storage-provisioner Image:gcr.io/k8s-minikube/storage-provisioner:v1.8.1 Command:[/storage-provisioner] Args:[] WorkingDir: Ports:[] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:tmp ReadOnly:false MountPath:/tmp SubPath: MountPropagation:} {Name:storage-provisioner-token-cd9hj ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:nil ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "storage-provisioner" in pod "storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 2m40s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f599affd-bc4d-11e8-8617-080027824c94 ("storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "storage-provisioner" with CrashLoopBackOff: "Back-off 2m40s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:kubernetes-dashboard Image:k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.1 Command:[] Args:[] WorkingDir: Ports:[{Name: HostPort:0 ContainerPort:9090 Protocol:TCP HostIP:}] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-xjkss ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:&Probe{Handler:Handler{Exec:nil,HTTPGet:&HTTPGetAction{Path:/,Port:9090,Host:,Scheme:HTTP,HTTPHeaders:[],},TCPSocket:nil,},InitialDelaySeconds:30,TimeoutSeconds:30,PeriodSeconds:10,SuccessThreshold:1,FailureThreshold:3,} ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "kubernetes-dashboard" in pod "kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 1m20s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f59107f4-bc4d-11e8-8617-080027824c94 ("kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "kubernetes-dashboard" with CrashLoopBackOff: "Back-off 1m20s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:storage-provisioner Image:gcr.io/k8s-minikube/storage-provisioner:v1.8.1 Command:[/storage-provisioner] Args:[] WorkingDir: Ports:[] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:tmp ReadOnly:false MountPath:/tmp SubPath: MountPropagation:} {Name:storage-provisioner-token-cd9hj ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:nil ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "storage-provisioner" in pod "storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 2m40s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f599affd-bc4d-11e8-8617-080027824c94 ("storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "storage-provisioner" with CrashLoopBackOff: "Back-off 2m40s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:kubernetes-dashboard Image:k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.1 Command:[] Args:[] WorkingDir: Ports:[{Name: HostPort:0 ContainerPort:9090 Protocol:TCP HostIP:}] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-xjkss ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:&Probe{Handler:Handler{Exec:nil,HTTPGet:&HTTPGetAction{Path:/,Port:9090,Host:,Scheme:HTTP,HTTPHeaders:[],},TCPSocket:nil,},InitialDelaySeconds:30,TimeoutSeconds:30,PeriodSeconds:10,SuccessThreshold:1,FailureThreshold:3,} ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "kubernetes-dashboard" in pod "kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:storage-provisioner Image:gcr.io/k8s-minikube/storage-provisioner:v1.8.1 Command:[/storage-provisioner] Args:[] WorkingDir: Ports:[] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:tmp ReadOnly:false MountPath:/tmp SubPath: MountPropagation:} {Name:storage-provisioner-token-cd9hj ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:nil ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "storage-provisioner" in pod "storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 2m40s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f599affd-bc4d-11e8-8617-080027824c94 ("storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "storage-provisioner" with CrashLoopBackOff: "Back-off 2m40s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:storage-provisioner Image:gcr.io/k8s-minikube/storage-provisioner:v1.8.1 Command:[/storage-provisioner] Args:[] WorkingDir: Ports:[] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:tmp ReadOnly:false MountPath:/tmp SubPath: MountPropagation:} {Name:storage-provisioner-token-cd9hj ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:nil ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "storage-provisioner" in pod "storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 2m40s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f599affd-bc4d-11e8-8617-080027824c94 ("storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "storage-provisioner" with CrashLoopBackOff: "Back-off 2m40s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:kubernetes-dashboard Image:k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.1 Command:[] Args:[] WorkingDir: Ports:[{Name: HostPort:0 ContainerPort:9090 Protocol:TCP HostIP:}] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-xjkss ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:&Probe{Handler:Handler{Exec:nil,HTTPGet:&HTTPGetAction{Path:/,Port:9090,Host:,Scheme:HTTP,HTTPHeaders:[],},TCPSocket:nil,},InitialDelaySeconds:30,TimeoutSeconds:30,PeriodSeconds:10,SuccessThreshold:1,FailureThreshold:3,} ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "kubernetes-dashboard" in pod "kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 2m40s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f59107f4-bc4d-11e8-8617-080027824c94 ("kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "kubernetes-dashboard" with CrashLoopBackOff: "Back-off 2m40s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:kubernetes-dashboard Image:k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.1 Command:[] Args:[] WorkingDir: Ports:[{Name: HostPort:0 ContainerPort:9090 Protocol:TCP HostIP:}] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-xjkss ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:&Probe{Handler:Handler{Exec:nil,HTTPGet:&HTTPGetAction{Path:/,Port:9090,Host:,Scheme:HTTP,HTTPHeaders:[],},TCPSocket:nil,},InitialDelaySeconds:30,TimeoutSeconds:30,PeriodSeconds:10,SuccessThreshold:1,FailureThreshold:3,} ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "kubernetes-dashboard" in pod "kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 2m40s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f59107f4-bc4d-11e8-8617-080027824c94 ("kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "kubernetes-dashboard" with CrashLoopBackOff: "Back-off 2m40s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:storage-provisioner Image:gcr.io/k8s-minikube/storage-provisioner:v1.8.1 Command:[/storage-provisioner] Args:[] WorkingDir: Ports:[] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:tmp ReadOnly:false MountPath:/tmp SubPath: MountPropagation:} {Name:storage-provisioner-token-cd9hj ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:nil ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "storage-provisioner" in pod "storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 2m40s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f599affd-bc4d-11e8-8617-080027824c94 ("storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "storage-provisioner" with CrashLoopBackOff: "Back-off 2m40s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:kubernetes-dashboard Image:k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.1 Command:[] Args:[] WorkingDir: Ports:[{Name: HostPort:0 ContainerPort:9090 Protocol:TCP HostIP:}] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-xjkss ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:&Probe{Handler:Handler{Exec:nil,HTTPGet:&HTTPGetAction{Path:/,Port:9090,Host:,Scheme:HTTP,HTTPHeaders:[],},TCPSocket:nil,},InitialDelaySeconds:30,TimeoutSeconds:30,PeriodSeconds:10,SuccessThreshold:1,FailureThreshold:3,} ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "kubernetes-dashboard" in pod "kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 2m40s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f59107f4-bc4d-11e8-8617-080027824c94 ("kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "kubernetes-dashboard" with CrashLoopBackOff: "Back-off 2m40s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:storage-provisioner Image:gcr.io/k8s-minikube/storage-provisioner:v1.8.1 Command:[/storage-provisioner] Args:[] WorkingDir: Ports:[] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:tmp ReadOnly:false MountPath:/tmp SubPath: MountPropagation:} {Name:storage-provisioner-token-cd9hj ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:nil ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "storage-provisioner" in pod "storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 2m40s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f599affd-bc4d-11e8-8617-080027824c94 ("storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "storage-provisioner" with CrashLoopBackOff: "Back-off 2m40s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:kubernetes-dashboard Image:k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.1 Command:[] Args:[] WorkingDir: Ports:[{Name: HostPort:0 ContainerPort:9090 Protocol:TCP HostIP:}] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-xjkss ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:&Probe{Handler:Handler{Exec:nil,HTTPGet:&HTTPGetAction{Path:/,Port:9090,Host:,Scheme:HTTP,HTTPHeaders:[],},TCPSocket:nil,},InitialDelaySeconds:30,TimeoutSeconds:30,PeriodSeconds:10,SuccessThreshold:1,FailureThreshold:3,} ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "kubernetes-dashboard" in pod "kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 2m40s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f59107f4-bc4d-11e8-8617-080027824c94 ("kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "kubernetes-dashboard" with CrashLoopBackOff: "Back-off 2m40s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:storage-provisioner Image:gcr.io/k8s-minikube/storage-provisioner:v1.8.1 Command:[/storage-provisioner] Args:[] WorkingDir: Ports:[] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:tmp ReadOnly:false MountPath:/tmp SubPath: MountPropagation:} {Name:storage-provisioner-token-cd9hj ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:nil ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "storage-provisioner" in pod "storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 2m40s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f599affd-bc4d-11e8-8617-080027824c94 ("storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "storage-provisioner" with CrashLoopBackOff: "Back-off 2m40s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:kubernetes-dashboard Image:k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.1 Command:[] Args:[] WorkingDir: Ports:[{Name: HostPort:0 ContainerPort:9090 Protocol:TCP HostIP:}] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-xjkss ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:&Probe{Handler:Handler{Exec:nil,HTTPGet:&HTTPGetAction{Path:/,Port:9090,Host:,Scheme:HTTP,HTTPHeaders:[],},TCPSocket:nil,},InitialDelaySeconds:30,TimeoutSeconds:30,PeriodSeconds:10,SuccessThreshold:1,FailureThreshold:3,} ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "kubernetes-dashboard" in pod "kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 2m40s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f59107f4-bc4d-11e8-8617-080027824c94 ("kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "kubernetes-dashboard" with CrashLoopBackOff: "Back-off 2m40s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:storage-provisioner Image:gcr.io/k8s-minikube/storage-provisioner:v1.8.1 Command:[/storage-provisioner] Args:[] WorkingDir: Ports:[] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:tmp ReadOnly:false MountPath:/tmp SubPath: MountPropagation:} {Name:storage-provisioner-token-cd9hj ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:nil ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "storage-provisioner" in pod "storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 2m40s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f599affd-bc4d-11e8-8617-080027824c94 ("storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "storage-provisioner" with CrashLoopBackOff: "Back-off 2m40s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:kubernetes-dashboard Image:k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.1 Command:[] Args:[] WorkingDir: Ports:[{Name: HostPort:0 ContainerPort:9090 Protocol:TCP HostIP:}] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-xjkss ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:&Probe{Handler:Handler{Exec:nil,HTTPGet:&HTTPGetAction{Path:/,Port:9090,Host:,Scheme:HTTP,HTTPHeaders:[],},TCPSocket:nil,},InitialDelaySeconds:30,TimeoutSeconds:30,PeriodSeconds:10,SuccessThreshold:1,FailureThreshold:3,} ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "kubernetes-dashboard" in pod "kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 2m40s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f59107f4-bc4d-11e8-8617-080027824c94 ("kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "kubernetes-dashboard" with CrashLoopBackOff: "Back-off 2m40s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:storage-provisioner Image:gcr.io/k8s-minikube/storage-provisioner:v1.8.1 Command:[/storage-provisioner] Args:[] WorkingDir: Ports:[] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:tmp ReadOnly:false MountPath:/tmp SubPath: MountPropagation:} {Name:storage-provisioner-token-cd9hj ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:nil ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "storage-provisioner" in pod "storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 2m40s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f599affd-bc4d-11e8-8617-080027824c94 ("storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "storage-provisioner" with CrashLoopBackOff: "Back-off 2m40s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:storage-provisioner Image:gcr.io/k8s-minikube/storage-provisioner:v1.8.1 Command:[/storage-provisioner] Args:[] WorkingDir: Ports:[] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:tmp ReadOnly:false MountPath:/tmp SubPath: MountPropagation:} {Name:storage-provisioner-token-cd9hj ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:nil ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "storage-provisioner" in pod "storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 2m40s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f599affd-bc4d-11e8-8617-080027824c94 ("storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "storage-provisioner" with CrashLoopBackOff: "Back-off 2m40s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:kubernetes-dashboard Image:k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.1 Command:[] Args:[] WorkingDir: Ports:[{Name: HostPort:0 ContainerPort:9090 Protocol:TCP HostIP:}] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-xjkss ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:&Probe{Handler:Handler{Exec:nil,HTTPGet:&HTTPGetAction{Path:/,Port:9090,Host:,Scheme:HTTP,HTTPHeaders:[],},TCPSocket:nil,},InitialDelaySeconds:30,TimeoutSeconds:30,PeriodSeconds:10,SuccessThreshold:1,FailureThreshold:3,} ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "kubernetes-dashboard" in pod "kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 2m40s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f59107f4-bc4d-11e8-8617-080027824c94 ("kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "kubernetes-dashboard" with CrashLoopBackOff: "Back-off 2m40s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:storage-provisioner Image:gcr.io/k8s-minikube/storage-provisioner:v1.8.1 Command:[/storage-provisioner] Args:[] WorkingDir: Ports:[] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:tmp ReadOnly:false MountPath:/tmp SubPath: MountPropagation:} {Name:storage-provisioner-token-cd9hj ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:nil ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "storage-provisioner" in pod "storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 2m40s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f599affd-bc4d-11e8-8617-080027824c94 ("storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "storage-provisioner" with CrashLoopBackOff: "Back-off 2m40s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:kubernetes-dashboard Image:k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.1 Command:[] Args:[] WorkingDir: Ports:[{Name: HostPort:0 ContainerPort:9090 Protocol:TCP HostIP:}] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-xjkss ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:&Probe{Handler:Handler{Exec:nil,HTTPGet:&HTTPGetAction{Path:/,Port:9090,Host:,Scheme:HTTP,HTTPHeaders:[],},TCPSocket:nil,},InitialDelaySeconds:30,TimeoutSeconds:30,PeriodSeconds:10,SuccessThreshold:1,FailureThreshold:3,} ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "kubernetes-dashboard" in pod "kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 2m40s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f59107f4-bc4d-11e8-8617-080027824c94 ("kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "kubernetes-dashboard" with CrashLoopBackOff: "Back-off 2m40s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:storage-provisioner Image:gcr.io/k8s-minikube/storage-provisioner:v1.8.1 Command:[/storage-provisioner] Args:[] WorkingDir: Ports:[] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:tmp ReadOnly:false MountPath:/tmp SubPath: MountPropagation:} {Name:storage-provisioner-token-cd9hj ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:nil ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "storage-provisioner" in pod "storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 2m40s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f599affd-bc4d-11e8-8617-080027824c94 ("storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "storage-provisioner" with CrashLoopBackOff: "Back-off 2m40s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:kubernetes-dashboard Image:k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.1 Command:[] Args:[] WorkingDir: Ports:[{Name: HostPort:0 ContainerPort:9090 Protocol:TCP HostIP:}] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-xjkss ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:&Probe{Handler:Handler{Exec:nil,HTTPGet:&HTTPGetAction{Path:/,Port:9090,Host:,Scheme:HTTP,HTTPHeaders:[],},TCPSocket:nil,},InitialDelaySeconds:30,TimeoutSeconds:30,PeriodSeconds:10,SuccessThreshold:1,FailureThreshold:3,} ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "kubernetes-dashboard" in pod "kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 2m40s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f59107f4-bc4d-11e8-8617-080027824c94 ("kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "kubernetes-dashboard" with CrashLoopBackOff: "Back-off 2m40s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:storage-provisioner Image:gcr.io/k8s-minikube/storage-provisioner:v1.8.1 Command:[/storage-provisioner] Args:[] WorkingDir: Ports:[] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:tmp ReadOnly:false MountPath:/tmp SubPath: MountPropagation:} {Name:storage-provisioner-token-cd9hj ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:nil ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "storage-provisioner" in pod "storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:kubernetes-dashboard Image:k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.1 Command:[] Args:[] WorkingDir: Ports:[{Name: HostPort:0 ContainerPort:9090 Protocol:TCP HostIP:}] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-xjkss ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:&Probe{Handler:Handler{Exec:nil,HTTPGet:&HTTPGetAction{Path:/,Port:9090,Host:,Scheme:HTTP,HTTPHeaders:[],},TCPSocket:nil,},InitialDelaySeconds:30,TimeoutSeconds:30,PeriodSeconds:10,SuccessThreshold:1,FailureThreshold:3,} ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "kubernetes-dashboard" in pod "kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 2m40s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f59107f4-bc4d-11e8-8617-080027824c94 ("kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "kubernetes-dashboard" with CrashLoopBackOff: "Back-off 2m40s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:kubernetes-dashboard Image:k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.1 Command:[] Args:[] WorkingDir: Ports:[{Name: HostPort:0 ContainerPort:9090 Protocol:TCP HostIP:}] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-xjkss ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:&Probe{Handler:Handler{Exec:nil,HTTPGet:&HTTPGetAction{Path:/,Port:9090,Host:,Scheme:HTTP,HTTPHeaders:[],},TCPSocket:nil,},InitialDelaySeconds:30,TimeoutSeconds:30,PeriodSeconds:10,SuccessThreshold:1,FailureThreshold:3,} ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "kubernetes-dashboard" in pod "kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 2m40s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f59107f4-bc4d-11e8-8617-080027824c94 ("kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "kubernetes-dashboard" with CrashLoopBackOff: "Back-off 2m40s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:kubernetes-dashboard Image:k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.1 Command:[] Args:[] WorkingDir: Ports:[{Name: HostPort:0 ContainerPort:9090 Protocol:TCP HostIP:}] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-xjkss ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:&Probe{Handler:Handler{Exec:nil,HTTPGet:&HTTPGetAction{Path:/,Port:9090,Host:,Scheme:HTTP,HTTPHeaders:[],},TCPSocket:nil,},InitialDelaySeconds:30,TimeoutSeconds:30,PeriodSeconds:10,SuccessThreshold:1,FailureThreshold:3,} ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "kubernetes-dashboard" in pod "kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 2m40s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f59107f4-bc4d-11e8-8617-080027824c94 ("kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "kubernetes-dashboard" with CrashLoopBackOff: "Back-off 2m40s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:storage-provisioner Image:gcr.io/k8s-minikube/storage-provisioner:v1.8.1 Command:[/storage-provisioner] Args:[] WorkingDir: Ports:[] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:tmp ReadOnly:false MountPath:/tmp SubPath: MountPropagation:} {Name:storage-provisioner-token-cd9hj ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:nil ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "storage-provisioner" in pod "storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 5m0s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f599affd-bc4d-11e8-8617-080027824c94 ("storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "storage-provisioner" with CrashLoopBackOff: "Back-off 5m0s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:kubernetes-dashboard Image:k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.1 Command:[] Args:[] WorkingDir: Ports:[{Name: HostPort:0 ContainerPort:9090 Protocol:TCP HostIP:}] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-xjkss ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:&Probe{Handler:Handler{Exec:nil,HTTPGet:&HTTPGetAction{Path:/,Port:9090,Host:,Scheme:HTTP,HTTPHeaders:[],},TCPSocket:nil,},InitialDelaySeconds:30,TimeoutSeconds:30,PeriodSeconds:10,SuccessThreshold:1,FailureThreshold:3,} ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "kubernetes-dashboard" in pod "kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 2m40s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f59107f4-bc4d-11e8-8617-080027824c94 ("kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "kubernetes-dashboard" with CrashLoopBackOff: "Back-off 2m40s restarting failed container=kubernetes-dashboard pod=kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:storage-provisioner Image:gcr.io/k8s-minikube/storage-provisioner:v1.8.1 Command:[/storage-provisioner] Args:[] WorkingDir: Ports:[] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:tmp ReadOnly:false MountPath:/tmp SubPath: MountPropagation:} {Name:storage-provisioner-token-cd9hj ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:nil ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "storage-provisioner" in pod "storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 5m0s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f599affd-bc4d-11e8-8617-080027824c94 ("storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "storage-provisioner" with CrashLoopBackOff: "Back-off 5m0s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:kubernetes-dashboard Image:k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.1 Command:[] Args:[] WorkingDir: Ports:[{Name: HostPort:0 ContainerPort:9090 Protocol:TCP HostIP:}] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-xjkss ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:&Probe{Handler:Handler{Exec:nil,HTTPGet:&HTTPGetAction{Path:/,Port:9090,Host:,Scheme:HTTP,HTTPHeaders:[],},TCPSocket:nil,},InitialDelaySeconds:30,TimeoutSeconds:30,PeriodSeconds:10,SuccessThreshold:1,FailureThreshold:3,} ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "kubernetes-dashboard" in pod "kubernetes-dashboard-5498ccf677-g4hqx_kube-system(f59107f4-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:storage-provisioner Image:gcr.io/k8s-minikube/storage-provisioner:v1.8.1 Command:[/storage-provisioner] Args:[] WorkingDir: Ports:[] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:tmp ReadOnly:false MountPath:/tmp SubPath: MountPropagation:} {Name:storage-provisioner-token-cd9hj ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:nil ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "storage-provisioner" in pod "storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 5m0s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f599affd-bc4d-11e8-8617-080027824c94 ("storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "storage-provisioner" with CrashLoopBackOff: "Back-off 5m0s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:513] Container {Name:storage-provisioner Image:gcr.io/k8s-minikube/storage-provisioner:v1.8.1 Command:[/storage-provisioner] Args:[] WorkingDir: Ports:[] EnvFrom:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:tmp ReadOnly:false MountPath:/tmp SubPath: MountPropagation:} {Name:storage-provisioner-token-cd9hj ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath: MountPropagation:}] VolumeDevices:[] LivenessProbe:nil ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.
2799 kuberuntime_manager.go:757] checking backoff for container "storage-provisioner" in pod "storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"
2799 kuberuntime_manager.go:767] Back-off 5m0s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)
2799 pod_workers.go:186] Error syncing pod f599affd-bc4d-11e8-8617-080027824c94 ("storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"), skipping: failed to "StartContainer" for "storage-provisioner" with CrashLoopBackOff: "Back-off 5m0s restarting failed container=storage-provisioner pod=storage-provisioner_kube-system(f599affd-bc4d-11e8-8617-080027824c94)"

ahopkins on 21 Sep 2018

I even went so far as to remove the minikube binaries, and ~/.minikube directory and install from scratch. Same problem.

This concludes that this is a real problem and not related to old crud left behind.

gbraad on 21 Sep 2018

😕1

sadly, I have the same issue and not know how to get through this...

gqcn on 28 Sep 2018

@john-cn Sadly, I have not progressed any further 😖

ahopkins on 28 Sep 2018

Same issue using Ubuntu 18.04.1 LTS and kvm2 driver

0.25.2 works fine, 0.29 does not.

gavinB-orange on 28 Sep 2018

👍2

Windows 10 WSL. Confirmed 0.25.2 works but 0.29 doesn't on my machine.

kkimdev on 29 Sep 2018

Unfortunately, same issue here using Windows 10, VirtualBox driver, Minikube 0.30.0

eschultz-magix on 17 Oct 2018

Chiming in again - for v0.30

C:\kube\client\bin>minikube -p 0.30 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...
E1017 13:03:53.393272    5160 start.go:302] Error restarting cluster:  restarting kube-proxy: waiting for kube-proxy to be up for configmap update: timed out waiting for the condition

Env - win8.1 x64, virtualbox 5.2.12

Only 0.25.2 works. At this stage I'm ready to give up on Minikube and have stopped recommending minikube to associates :(

raghur on 17 Oct 2018

I am also seeing this issue.

Ubuntu 18.10 64bit
kernel: 4.18
Minikube 0.29

christian@robo-beaver ~ $ minikube start --vm-driver=kvm2 --cpus=2 --memory=4096 --disk-size=45GB --extra-config=apiserver.Authorization.Mode=RBAC
There is a newer version of minikube available (v0.30.0).  Download it here:
https://github.com/kubernetes/minikube/releases/tag/v0.30.0

To disable this notification, run the following:
minikube config set WantUpdateNotification false
Starting local Kubernetes v1.10.0 cluster...
Starting VM...
Downloading Minikube ISO
 170.18 MB / 170.18 MB [============================================] 100.00% 0s
Getting VM IP address...
Moving files into cluster...
Downloading kubeadm v1.10.0
Downloading kubelet v1.10.0
Finished Downloading kubelet v1.10.0
Finished Downloading kubeadm v1.10.0
Setting up certs...
Connecting to cluster...
Setting up kubeconfig...
Starting cluster components...
E1022 12:13:27.600279    9609 start.go:297] 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  &&
sudo /usr/bin/kubeadm alpha phase addon kube-dns
 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  &&
sudo /usr/bin/kubeadm alpha phase addon kube-dns

.: Process exited with status 1
================================================================================
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
================================================================================

cmbernard333 on 22 Oct 2018

👍1

Same here: Ubuntu 18.04, minikube 30, kvm2. I'm going to try regressing to 25.0 and see what happens. No Kube For You!

squillace on 30 Oct 2018

Also experiencing this issue using Minikube 30, KVM2.

emansom on 30 Oct 2018

Ubuntu 18.04, minikube version: v0.30.0 with kvm2 has the same problem.

lycheng on 8 Nov 2018

why is this still an issue? It is rendering minikube useless on arguably an important platform. Is it not worthy of someone trying to fix?

I'm curious... Is anyone looking into this? It seems all the recent messages are just further reports of it not working. I would help out myself, but I lack the knowledge to tackle this.

ahopkins on 8 Nov 2018

👍1

This seems to be network/firewall related to me. At work, if I'm connected to the secure company network, I get the exact same error as above no matter how many times I try. But If I switch to the insecure public network or I try at home I do not get the error and everything succeeds. By the way I am using minikube v0.30.0 with kubernetes version 1.12.0 on Windows 10 64bit v1709 with VirtualBox 5.2.8. Here is my configuration to start minikube:

_Make sure all the .kube and .minikube folders are deleted and the VM is also removed before running this command:_

minikube start --extra-config=apiserver.service-node-port-range=90-32000 \
    --kubernetes-version=v1.12.0 \
    --cpus 4 --memory 8192 --disk-size=50g

Starting local Kubernetes v1.12.0 cluster...
Starting VM...
Downloading Minikube ISO
 170.78 MB / 170.78 MB [============================================] 100.00% 0s
Getting VM IP address...
Moving files into cluster...
Downloading kubelet v1.12.0
Downloading kubeadm v1.12.0
Finished Downloading kubeadm v1.12.0
Finished Downloading kubelet v1.12.0
Setting up certs...
Connecting to cluster...
Setting up kubeconfig...
Starting cluster components...
Kubectl is now configured to use the cluster.
Loading cached images from config file.

herrberk on 8 Nov 2018

👍3

Similarly as @herrberk, all works fine from public networks - I only get the error behind a proxy.

danifv on 12 Nov 2018

I have the exact same problem as @herrberk and the exact same configuration

srivatss on 16 Nov 2018

Same error as @herrberk -
My versions - minikube v0.30.0 with kubernetes version 1.10.0
command - minikube start --vm-driver="hyperv" --memory=1024 --hyperv-virtual-switch="My New Switch"

If you find the solution please post here.

shresthsuman on 5 Dec 2018

I was having the very same issue, running a Mint guest VMware machine on a Win10 host.
That VM had 2GB and 2 CPUs.
In Mint, I ran this command journalctl -f when minikube was starting and noticed an error of virtual box not having enough memory.
I then added 4 more GB to the RAM, and 2 more cores, and that seemed to solve the issue. It turned out to be a lack of hardware resources

ols-dieser on 5 Dec 2018

😕1

I was having the very same issue, running a Mint guest VMware machine on a Win10 host.
That VM had 2GB and 2 CPUs.
In Mint, I ran this command journalctl -f when minikube was starting and noticed an error of virtual box not having enough memory.
I then added 4 more GB to the RAM, and 2 more cores, and that seemed to solve the issue. It turned out to be a lack of hardware resources

Hi, Thanks for your reply. I tried changing my command to "minikube start --vm-driver="hyperv" --memory=8192 --cpus=4 --hyperv-virtual-switch="My New Switch" --v=7 --alsologtostderr --kubernetes-version=v1.12.0"

But I am still stuck on

Also, error log - Setting up kubeconfig...
I1206 11:10:11.920239 14812 config.go:125] Using kubeconfig: C:\Users\shsu.kube\config
Starting cluster components...
I1206 11:10:11.922237 14812 ssh_runner.go:80] Run with output:
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 &&
sudo /usr/bin/kubeadm alpha phase addon coredns

I am on my company network.
My versions - minikube v0.30.0 with kubernetes version 1.12.0

shresthsuman on 6 Dec 2018

@shresthsuman I'm running kubernetes in a Linux Mint. I wasn't referring to the minikube hardware, but to the host hardware, Mint in my case. The thing is that I have Windows and didn't want to install a clean Mint version in a hard drive, so I created a virtual machine using vmware instead. Is the hardware of that vm I was referring to.

I'm using virtualbox driver in a Linux environment

ols-dieser on 6 Dec 2018

👍1

Same error on:

OS: OSX 10.14.1 Mojave
VM Driver: Virtualbox
Minikube version: v0.30.0

CMD:

sudo minikube delete && sudo minikube start 
\ --extra-config=apiserver.Authorization.Mode=RBAC  
\ --kubernetes-version=v1.13.0 
\ --bootstrapper=kubeadm 
\ --apiserver-ips 127.0.0.1 
\ --apiserver-name localhost 
\ --logtostderr 
\ --vm-driver=virtualbox

Log:

E1209 20:37:14.620167   97351 start.go:297] 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  &&
sudo /usr/bin/kubeadm alpha phase addon coredns
 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  &&
sudo /usr/bin/kubeadm alpha phase addon coredns

.: Process exited with status 1

viane on 10 Dec 2018

😕2

Similar error

OS: Ubuntu 18.04

$ sudo minikube start --extra-config kubelet.EnableCustomMetrics=true
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...
E1212 19:32:37.780929    3657 start.go:297] 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  &&
sudo /usr/bin/kubeadm alpha phase addon kube-dns
 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  &&
sudo /usr/bin/kubeadm alpha phase addon kube-dns

.: Process exited with status 1
================================================================================
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]: n

srinivasrk on 12 Dec 2018

Same issue here (macOS Sierra 10.12.6):

+ minikube start --bootstrapper=kubeadm --kubernetes-version=v1.13.2 --vm-driver=virtualbox --disk-size=10g
Starting local Kubernetes v1.13.2 cluster...
Starting VM...
Getting VM IP address...
Moving files into cluster...
Downloading kubelet v1.13.2
Downloading kubeadm v1.13.2
Finished Downloading kubeadm v1.13.2
Finished Downloading kubelet v1.13.2
Setting up certs...
Connecting to cluster...
Setting up kubeconfig...
Starting cluster components...
E0115 11:10:08.488050   32769 start.go:297] 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  &&
sudo /usr/bin/kubeadm alpha phase addon kube-dns
 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  &&
sudo /usr/bin/kubeadm alpha phase addon kube-dns

.: Process exited with status 1

tyranron on 15 Jan 2019

With minikube v0.33, we've presented kubeadm errors directly to the console, removing the mystery and fulfilling this bug. If you run into any further kubeadm issues, please open a new bug. Thanks!

tstromberg on 23 Jan 2019

👍2

Minikube: kubeadm init error running command: Process exited with status 1 (make error debuggable!)

Most helpful comment

All 47 comments

E0328 21:54:51.600728 7358 start.go:276] Error starting cluster: kubeadm init error running command: sudo /usr/bin/kubeadm init --config /var/lib/kubeadm.yaml --skip-preflight-checks: Process exited with status 1

minikube config set WantReportErrorPrompt false

E0328 21:54:51.600728 7358 start.go:276] Error starting cluster: kubeadm init error running command: sudo /usr/bin/kubeadm init --config /var/lib/kubeadm.yaml --skip-preflight-checks: Process exited with status 1

minikube config set WantReportErrorPrompt false

E0412 18:04:43.797557 34012 start.go:281] Error restarting cluster: restarting kube-proxy: waiting for kube-proxy to be up for configmap update: timed out waiting for the condition

minikube config set WantReportErrorPrompt false

E0921 12:32:29.702897 5220 start.go:305] Error restarting cluster: restarting kube-proxy: waiting for kube-proxy to be up for configmap update: timed out waiting for the condition

minikube config set WantReportErrorPrompt false

Related issues