title: kubeadm init shows kubelet isn't running or healthy
body: <p>I am trying to run Kubernetes and trying to use <code>sudo kubeadm init</code>.
  Swap is off as recommended by official doc.</p>
  
  <p>The issue is it displays the warning:</p>
  
  <pre><code>[kubelet-check] It seems like the kubelet isn't running or healthy.
  [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: 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:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: 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:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: 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:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: 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:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: 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)
              - No internet connection is available so the kubelet cannot pull or find the following control plane images:
                  - k8s.gcr.io/kube-apiserver-amd64:v1.11.2
                  - k8s.gcr.io/kube-controller-manager-amd64:v1.11.2
                  - k8s.gcr.io/kube-scheduler-amd64:v1.11.2
                  - k8s.gcr.io/etcd-amd64:3.2.18
                  - You can check or miligate this in beforehand with "kubeadm config images pull" to make sure the images
                    are downloaded locally and cached.
  
          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'
  
          Additionally, a control plane component may have crashed or exited when started by the container runtime.
          To troubleshoot, list all containers using your preferred container runtimes CLI, e.g. docker.
          Here is one example how you may list all Kubernetes containers running in docker:
              - 'docker ps -a | grep kube | grep -v pause'
              Once you have found the failing container, you can inspect its logs with:
              - 'docker logs CONTAINERID'
  couldn't initialize a Kubernetes cluster
  </code></pre>
  
  <p>The docker version I am using is <code>Docker version 17.03.2-ce, build f5ec1e2</code>
  I m using Ubuntu 16.04 LTS 64bit</p>
  
  <p>The docker images shows the following images:</p>
  
  <pre><code>REPOSITORY                                 TAG                 IMAGE ID            CREATED             SIZE
  k8s.gcr.io/kube-apiserver-amd64            v1.11.2             821507941e9c        3 weeks ago         187 MB
  k8s.gcr.io/kube-controller-manager-amd64   v1.11.2             38521457c799        3 weeks ago         155 MB
  k8s.gcr.io/kube-proxy-amd64                v1.11.2             46a3cd725628        3 weeks ago         97.8 MB
  k8s.gcr.io/kube-scheduler-amd64            v1.11.2             37a1403e6c1a        3 weeks ago         56.8 MB
  k8s.gcr.io/coredns                         1.1.3               b3b94275d97c        3 months ago        45.6 MB
  k8s.gcr.io/etcd-amd64                      3.2.18              b8df3b177be2        4 months ago        219 MB
  k8s.gcr.io/pause                           3.1                 da86e6ba6ca1        8 months ago        742 kB
  </code></pre>
  
  <p>Full logs can be found here :
  <a href="https://pastebin.com/T5V0taE3" rel="noreferrer">https://pastebin.com/T5V0taE3</a></p>
  
  <p>I didn't found any solution on internet.</p>
  
  <p><strong>EDIT:</strong></p>
  
  <p><em>docker ps -a</em> output:</p>
  
  <pre><code>ubuntu@ubuntu-HP-Pavilion-15-Notebook-PC:~$ docker ps -a
  CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS
  </code></pre>
  
  <p><em>journalctl -xeu kubelet</em> output:</p>
  
  <pre><code>journalctl -xeu kubelet
  -- Subject: Unit kubelet.service has finished shutting down
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  -- 
  -- Unit kubelet.service has finished shutting down.
  Sep 01 10:40:05 ubuntu-HP-Pavilion-15-Notebook-PC systemd[1]: Started kubelet: T
  -- Subject: Unit kubelet.service has finished start-up
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  -- 
  -- Unit kubelet.service has finished starting up.
  -- 
  -- The start-up result is done.
  Sep 01 10:40:06 ubuntu-HP-Pavilion-15-Notebook-PC kubelet[9107]: Flag --cgroup-d
  Sep 01 10:40:06 ubuntu-HP-Pavilion-15-Notebook-PC kubelet[9107]: Flag --cgroup-d
  Sep 01 10:40:06 ubuntu-HP-Pavilion-15-Notebook-PC kubelet[9107]: I0901 10:40:06.
  Sep 01 10:40:06 ubuntu-HP-Pavilion-15-Notebook-PC kubelet[9107]: I0901 10:40:06.
  Sep 01 10:40:06 ubuntu-HP-Pavilion-15-Notebook-PC kubelet[9107]: I0901 10:40:06.
  Sep 01 10:40:06 ubuntu-HP-Pavilion-15-Notebook-PC kubelet[9107]: I0901 10:40:06.
  Sep 01 10:40:06 ubuntu-HP-Pavilion-15-Notebook-PC kubelet[9107]: F0901 10:40:06.
  Sep 01 10:40:06 ubuntu-HP-Pavilion-15-Notebook-PC systemd[1]: kubelet.service: M
  Sep 01 10:40:06 ubuntu-HP-Pavilion-15-Notebook-PC systemd[1]: kubelet.service: U
  Sep 01 10:40:06 ubuntu-HP-Pavilion-15-Notebook-PC systemd[1]: kubelet.service: F
  lines 788-810/810 (END)
  -- Subject: Unit kubelet.service has finished shutting down
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  -- 
  -- Unit kubelet.service has finished shutting down.
  Sep 01 10:40:05 ubuntu-HP-Pavilion-15-Notebook-PC systemd[1]: Started kubelet: The Kubernetes Node Agent.
  -- Subject: Unit kubelet.service has finished start-up
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  -- 
  -- Unit kubelet.service has finished starting up.
  -- 
  -- The start-up result is done.
  Sep 01 10:40:06 ubuntu-HP-Pavilion-15-Notebook-PC kubelet[9107]: Flag --cgroup-driver has been deprecated, This parameter should be set via the
  Sep 01 10:40:06 ubuntu-HP-Pavilion-15-Notebook-PC kubelet[9107]: Flag --cgroup-driver has been deprecated, This parameter should be set via the
  Sep 01 10:40:06 ubuntu-HP-Pavilion-15-Notebook-PC kubelet[9107]: I0901 10:40:06.117131    9107 server.go:408] Version: v1.11.2
  Sep 01 10:40:06 ubuntu-HP-Pavilion-15-Notebook-PC kubelet[9107]: I0901 10:40:06.117406    9107 plugins.go:97] No cloud provider specified.
  Sep 01 10:40:06 ubuntu-HP-Pavilion-15-Notebook-PC kubelet[9107]: I0901 10:40:06.121192    9107 certificate_store.go:131] Loading cert/key pair 
  Sep 01 10:40:06 ubuntu-HP-Pavilion-15-Notebook-PC kubelet[9107]: I0901 10:40:06.145720    9107 server.go:648] --cgroups-per-qos enabled, but --
  Sep 01 10:40:06 ubuntu-HP-Pavilion-15-Notebook-PC kubelet[9107]: F0901 10:40:06.146074    9107 server.go:262] failed to run Kubelet: Running wi
  Sep 01 10:40:06 ubuntu-HP-Pavilion-15-Notebook-PC systemd[1]: kubelet.service: Main process exited, code=exited, status=255/n/a
  Sep 01 10:40:06 ubuntu-HP-Pavilion-15-Notebook-PC systemd[1]: kubelet.service: Unit entered failed state.
  Sep 01 10:40:06 ubuntu-HP-Pavilion-15-Notebook-PC systemd[1]: kubelet.service: Failed with result 'exit-code'.
  ~
  
  
            PORTS               NAMES
  </code></pre>
  
  <p>Any help/suggestion/comment would be appreciated.</p>