Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Error starting cluster: kubelet config: error: open /var/lib/kubelet/config.yaml: no such file or directory #5947

Closed
ShangCunShanFu opened this issue Nov 19, 2019 · 4 comments
Closed

Error starting cluster: kubelet config: error: open /var/lib/kubelet/config.yaml: no such file or directory #5947

ShangCunShanFu opened this issue Nov 19, 2019 · 4 comments
Labels
kind/support Categorizes issue or PR as a support question. l/zh-CN Issues in or relating to Chinese

Comments

@ShangCunShanFu
Copy link

重现问题所需的命令：
minikube start --vm-driver=virtualbox

失败的命令的完整输出：

  • Microsoft Windows 10 Enterprise LTSC 2019 10.0.17763 Build 17763 上的 minikube v1.5.2
  • 正在下载 VM boot image...

    minikube-v1.5.1.iso.sha256: 65 B / 65 B [--------------] 100.00% ? p/s 0s
    minikube-v1.5.1.iso: 143.76 MiB / 143.76 MiB [-] 100.00% 8.97 MiB p/s 16s

  • 正在创建 virtualbox 虚拟机（CPUs=2，Memory=2000MB, Disk=20000MB）...
    E1119 19:41:47.505983 30868 cache_images.go:80] CacheImage gcr.io/k8s-minikube/storage-provisioner:v1.8.1 -> C:\Users\wangkaige.minikube\cache\images\gcr.io\k8s-minikube\storage-provisioner_v1.8.1 failed: fetching image: Get https://gcr.io/v2/: dial tcp 64.233.189.82:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
    E1119 19:41:47.556747 30868 cache_images.go:80] CacheImage k8s.gcr.io/k8s-dns-kube-dns-amd64:1.14.13 -> C:\Users\wangkaige.minikube\cache\images\k8s.gcr.io\k8s-dns-kube-dns-amd64_1.14.13 failed: fetching image: Get https://k8s.gcr.io/v2/: dial tcp 74.125.203.82:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
    E1119 19:41:47.557745 30868 cache_images.go:80] CacheImage k8s.gcr.io/etcd:3.3.15-0 -> C:\Users\wangkaige.minikube\cache\images\k8s.gcr.io\etcd_3.3.15-0 failed: fetching image: Get https://k8s.gcr.io/v2/: dial tcp 74.125.203.82:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
    E1119 19:41:47.559697 30868 cache_images.go:80] CacheImage k8s.gcr.io/k8s-dns-sidecar-amd64:1.14.13 -> C:\Users\wangkaige.minikube\cache\images\k8s.gcr.io\k8s-dns-sidecar-amd64_1.14.13 failed: fetching image: Get https://k8s.gcr.io/v2/: dial tcp 74.125.203.82:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
    E1119 19:41:47.559697 30868 cache_images.go:80] CacheImage k8s.gcr.io/kube-controller-manager:v1.16.2 -> C:\Users\wangkaige.minikube\cache\images\k8s.gcr.io\kube-controller-manager_v1.16.2 failed: fetching image: Get https://k8s.gcr.io/v2/: dial tcp 74.125.203.82:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
    E1119 19:41:47.561641 30868 cache_images.go:80] CacheImage k8s.gcr.io/coredns:1.6.2 -> C:\Users\wangkaige.minikube\cache\images\k8s.gcr.io\coredns_1.6.2 failed: fetching image: Get https://k8s.gcr.io/v2/: dial tcp 74.125.203.82:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
    E1119 19:41:47.561641 30868 cache_images.go:80] CacheImage k8s.gcr.io/kube-proxy:v1.16.2 -> C:\Users\wangkaige.minikube\cache\images\k8s.gcr.io\kube-proxy_v1.16.2 failed: fetching image: Get https://k8s.gcr.io/v2/: dial tcp 74.125.203.82:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
    E1119 19:41:47.565552 30868 cache_images.go:80] CacheImage k8s.gcr.io/kube-apiserver:v1.16.2 -> C:\Users\wangkaige.minikube\cache\images\k8s.gcr.io\kube-apiserver_v1.16.2 failed: fetching image: Get https://k8s.gcr.io/v2/: dial tcp 74.125.203.82:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
    E1119 19:41:47.613379 30868 cache_images.go:80] CacheImage k8s.gcr.io/kube-addon-manager:v9.0 -> C:\Users\wangkaige.minikube\cache\images\k8s.gcr.io\kube-addon-manager_v9.0 failed: fetching image: Get https://k8s.gcr.io/v2/: dial tcp 74.125.203.82:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
    E1119 19:41:47.618257 30868 cache_images.go:80] CacheImage k8s.gcr.io/k8s-dns-dnsmasq-nanny-amd64:1.14.13 -> C:\Users\wangkaige.minikube\cache\images\k8s.gcr.io\k8s-dns-dnsmasq-nanny-amd64_1.14.13 failed: fetching image: Get https://k8s.gcr.io/v2/: dial tcp 74.125.203.82:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
    E1119 19:41:47.673852 30868 cache_images.go:80] CacheImage k8s.gcr.io/kubernetes-dashboard-amd64:v1.10.1 -> C:\Users\wangkaige.minikube\cache\images\k8s.gcr.io\kubernetes-dashboard-amd64_v1.10.1 failed: fetching image: Get https://k8s.gcr.io/v2/: dial tcp 74.125.203.82:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
    E1119 19:41:47.685564 30868 cache_images.go:80] CacheImage k8s.gcr.io/pause:3.1 -> C:\Users\wangkaige.minikube\cache\images\k8s.gcr.io\pause_3.1 failed: fetching image: Get https://k8s.gcr.io/v2/: dial tcp 74.125.203.82:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
    E1119 19:41:47.689442 30868 cache_images.go:80] CacheImage k8s.gcr.io/kube-scheduler:v1.16.2 -> C:\Users\wangkaige.minikube\cache\images\k8s.gcr.io\kube-scheduler_v1.16.2 failed: fetching image: Get https://k8s.gcr.io/v2/: dial tcp 74.125.203.82:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
    ! VM is unable to access k8s.gcr.io, you may need to configure a proxy or set --image-repository
  • 正在 Docker '18.09.9' 中准备 Kubernetes v1.16.2…
    E1119 19:44:36.301839 30868 start.go:799] Error caching images: Caching images for kubeadm: caching images: caching image C:\Users\wangkaige.minikube\cache\images\gcr.io\k8s-minikube\storage-provisioner_v1.8.1: fetching image: Get https://gcr.io/v2/: dial tcp 64.233.189.82:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
  • Unable to load cached images: loading cached images: loading image C:\Users\wangkaige.minikube\cache\images\gcr.io\k8s-minikube\storage-provisioner_v1.8.1: CreateFile C:\Users\wangkaige.minikube\cache\images\gcr.io\k8s-minikube\storage-provisioner_v1.8.1: The system cannot find the file specified.
  • 正在下载 kubeadm v1.16.2
  • 正在下载 kubelet v1.16.2
  • 拉取镜像 ...
  • 无法拉取映像，有可能是正常状况：running cmd: "/bin/bash -c "sudo env PATH=/var/lib/minikube/binaries/v1.16.2:$PATH kubeadm config images pull --config /var/tmp/minikube/kubeadm.yaml"": Process exited with status 1
  • 正在启动 Kubernetes ...

X 开启 cluster 时出错: init failed. cmd: "/bin/bash -c "sudo env PATH=/var/lib/minikube/binaries/v1.16.2:$PATH kubeadm init --config /var/tmp/minikube/kubeadm.yaml --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests,DirAvailable--var-lib-minikube,FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml,FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml,FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml,FileAvailable--etc-kubernetes-manifests-etcd.yaml,Port-10250,Swap"": Process exited with status 1
*

minikube logs命令的输出：

  • ==> Docker <==
  • -- Logs begin at Tue 2019-11-19 11:42:10 UTC, end at Tue 2019-11-19 11:51:17 UTC. --
  • Nov 19 11:44:36 minikube dockerd[2422]: time="2019-11-19T11:44:36.038758835Z" level=info msg="parsed scheme: "unix"" module=grpc
  • Nov 19 11:44:36 minikube dockerd[2422]: time="2019-11-19T11:44:36.038815271Z" level=info msg="scheme "unix" not registered, fallback to default scheme" module=grpc
  • Nov 19 11:44:36 minikube dockerd[2422]: time="2019-11-19T11:44:36.038972337Z" level=info msg="ccResolverWrapper: sending new addresses to cc: [{unix:///var/run/docker/containerd/containerd.sock 0 }]" module=grpc
  • Nov 19 11:44:36 minikube dockerd[2422]: time="2019-11-19T11:44:36.039003871Z" level=info msg="ClientConn switching balancer to "pick_first"" module=grpc
  • Nov 19 11:44:36 minikube dockerd[2422]: time="2019-11-19T11:44:36.039074992Z" level=info msg="pickfirstBalancer: HandleSubConnStateChange: 0xc000737460, CONNECTING" module=grpc
  • Nov 19 11:44:36 minikube dockerd[2422]: time="2019-11-19T11:44:36.039332916Z" level=info msg="pickfirstBalancer: HandleSubConnStateChange: 0xc000737460, READY" module=grpc
  • Nov 19 11:44:36 minikube dockerd[2422]: time="2019-11-19T11:44:36.039449641Z" level=info msg="ccResolverWrapper: sending new addresses to cc: [{unix:///var/run/docker/containerd/containerd.sock 0 }]" module=grpc
  • Nov 19 11:44:36 minikube dockerd[2422]: time="2019-11-19T11:44:36.039523036Z" level=info msg="ClientConn switching balancer to "pick_first"" module=grpc
  • Nov 19 11:44:36 minikube dockerd[2422]: time="2019-11-19T11:44:36.039604650Z" level=info msg="pickfirstBalancer: HandleSubConnStateChange: 0xc000737740, CONNECTING" module=grpc
  • Nov 19 11:44:36 minikube dockerd[2422]: time="2019-11-19T11:44:36.039855413Z" level=info msg="pickfirstBalancer: HandleSubConnStateChange: 0xc000737740, READY" module=grpc
  • Nov 19 11:44:36 minikube dockerd[2422]: time="2019-11-19T11:44:36.054338136Z" level=info msg="Graph migration to content-addressability took 0.00 seconds"
  • Nov 19 11:44:36 minikube dockerd[2422]: time="2019-11-19T11:44:36.054727655Z" level=warning msg="Your kernel does not support cgroup blkio weight"
  • Nov 19 11:44:36 minikube dockerd[2422]: time="2019-11-19T11:44:36.054792326Z" level=warning msg="Your kernel does not support cgroup blkio weight_device"
  • Nov 19 11:44:36 minikube dockerd[2422]: time="2019-11-19T11:44:36.054840827Z" level=warning msg="Your kernel does not support cgroup blkio throttle.read_bps_device"
  • Nov 19 11:44:36 minikube dockerd[2422]: time="2019-11-19T11:44:36.054891886Z" level=warning msg="Your kernel does not support cgroup blkio throttle.write_bps_device"
  • Nov 19 11:44:36 minikube dockerd[2422]: time="2019-11-19T11:44:36.054938666Z" level=warning msg="Your kernel does not support cgroup blkio throttle.read_iops_device"
  • Nov 19 11:44:36 minikube dockerd[2422]: time="2019-11-19T11:44:36.054984581Z" level=warning msg="Your kernel does not support cgroup blkio throttle.write_iops_device"
  • Nov 19 11:44:36 minikube dockerd[2422]: time="2019-11-19T11:44:36.055351384Z" level=info msg="Loading containers: start."
  • Nov 19 11:44:36 minikube dockerd[2422]: time="2019-11-19T11:44:36.119572681Z" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address"
  • Nov 19 11:44:36 minikube dockerd[2422]: time="2019-11-19T11:44:36.160732662Z" level=info msg="Loading containers: done."
  • Nov 19 11:44:36 minikube dockerd[2422]: time="2019-11-19T11:44:36.174367638Z" level=warning msg="failed to retrieve runc version: unknown output format: runc version commit: 425e105d5a03fabd737a126ad93d62a9eeede87f\nspec: 1.0.1-dev\n"
  • Nov 19 11:44:36 minikube dockerd[2422]: time="2019-11-19T11:44:36.186118076Z" level=info msg="Docker daemon" commit=039a7df9ba graphdriver(s)=overlay2 version=18.09.9
  • Nov 19 11:44:36 minikube dockerd[2422]: time="2019-11-19T11:44:36.186356790Z" level=info msg="Daemon has completed initialization"
  • Nov 19 11:44:36 minikube dockerd[2422]: time="2019-11-19T11:44:36.196638603Z" level=info msg="API listen on /var/run/docker.sock"
  • Nov 19 11:44:36 minikube dockerd[2422]: time="2019-11-19T11:44:36.196647584Z" level=info msg="API listen on [::]:2376"
  • Nov 19 11:44:36 minikube systemd[1]: Started Docker Application Container Engine.
  • Nov 19 11:45:45 minikube dockerd[2422]: time="2019-11-19T11:45:45.658877574Z" level=warning msg="Error getting v2 registry: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
  • Nov 19 11:45:45 minikube dockerd[2422]: time="2019-11-19T11:45:45.660176011Z" level=info msg="Attempting next endpoint for pull after error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
  • Nov 19 11:45:45 minikube dockerd[2422]: time="2019-11-19T11:45:45.660325027Z" level=error msg="Handler for POST /v1.39/images/create returned error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
  • Nov 19 11:45:45 minikube dockerd[2422]: time="2019-11-19T11:45:45.790940050Z" level=warning msg="failed to retrieve runc version: unknown output format: runc version commit: 425e105d5a03fabd737a126ad93d62a9eeede87f\nspec: 1.0.1-dev\n"
  • Nov 19 11:45:45 minikube dockerd[2422]: time="2019-11-19T11:45:45.841979523Z" level=warning msg="failed to retrieve runc version: unknown output format: runc version commit: 425e105d5a03fabd737a126ad93d62a9eeede87f\nspec: 1.0.1-dev\n"
  • Nov 19 11:45:45 minikube dockerd[2422]: time="2019-11-19T11:45:45.880721100Z" level=warning msg="failed to retrieve runc version: unknown output format: runc version commit: 425e105d5a03fabd737a126ad93d62a9eeede87f\nspec: 1.0.1-dev\n"
  • Nov 19 11:45:46 minikube dockerd[2422]: time="2019-11-19T11:45:46.023336017Z" level=warning msg="failed to retrieve runc version: unknown output format: runc version commit: 425e105d5a03fabd737a126ad93d62a9eeede87f\nspec: 1.0.1-dev\n"
  • Nov 19 11:46:01 minikube dockerd[2422]: time="2019-11-19T11:46:01.055092818Z" level=warning msg="Error getting v2 registry: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
  • Nov 19 11:46:01 minikube dockerd[2422]: time="2019-11-19T11:46:01.062835111Z" level=info msg="Attempting next endpoint for pull after error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
  • Nov 19 11:46:01 minikube dockerd[2422]: time="2019-11-19T11:46:01.062932380Z" level=error msg="Handler for POST /v1.39/images/create returned error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
  • Nov 19 11:46:01 minikube dockerd[2422]: time="2019-11-19T11:46:01.109199610Z" level=warning msg="failed to retrieve runc version: unknown output format: runc version commit: 425e105d5a03fabd737a126ad93d62a9eeede87f\nspec: 1.0.1-dev\n"
  • Nov 19 11:46:16 minikube dockerd[2422]: time="2019-11-19T11:46:16.143831924Z" level=warning msg="Error getting v2 registry: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
  • Nov 19 11:46:16 minikube dockerd[2422]: time="2019-11-19T11:46:16.143867164Z" level=info msg="Attempting next endpoint for pull after error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
  • Nov 19 11:46:16 minikube dockerd[2422]: time="2019-11-19T11:46:16.143896277Z" level=error msg="Handler for POST /v1.39/images/create returned error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
  • Nov 19 11:46:16 minikube dockerd[2422]: time="2019-11-19T11:46:16.181822803Z" level=warning msg="failed to retrieve runc version: unknown output format: runc version commit: 425e105d5a03fabd737a126ad93d62a9eeede87f\nspec: 1.0.1-dev\n"
  • Nov 19 11:46:31 minikube dockerd[2422]: time="2019-11-19T11:46:31.287964238Z" level=warning msg="Error getting v2 registry: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
  • Nov 19 11:46:31 minikube dockerd[2422]: time="2019-11-19T11:46:31.287992636Z" level=info msg="Attempting next endpoint for pull after error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
  • Nov 19 11:46:31 minikube dockerd[2422]: time="2019-11-19T11:46:31.288034194Z" level=error msg="Handler for POST /v1.39/images/create returned error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
  • Nov 19 11:46:31 minikube dockerd[2422]: time="2019-11-19T11:46:31.327702246Z" level=warning msg="failed to retrieve runc version: unknown output format: runc version commit: 425e105d5a03fabd737a126ad93d62a9eeede87f\nspec: 1.0.1-dev\n"
  • Nov 19 11:46:46 minikube dockerd[2422]: time="2019-11-19T11:46:46.356057665Z" level=warning msg="Error getting v2 registry: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
  • Nov 19 11:46:46 minikube dockerd[2422]: time="2019-11-19T11:46:46.356096559Z" level=info msg="Attempting next endpoint for pull after error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
  • Nov 19 11:46:46 minikube dockerd[2422]: time="2019-11-19T11:46:46.356127020Z" level=error msg="Handler for POST /v1.39/images/create returned error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
  • Nov 19 11:46:46 minikube dockerd[2422]: time="2019-11-19T11:46:46.410659000Z" level=warning msg="failed to retrieve runc version: unknown output format: runc version commit: 425e105d5a03fabd737a126ad93d62a9eeede87f\nspec: 1.0.1-dev\n"
  • Nov 19 11:47:01 minikube dockerd[2422]: time="2019-11-19T11:47:01.449243393Z" level=warning msg="Error getting v2 registry: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
  • Nov 19 11:47:01 minikube dockerd[2422]: time="2019-11-19T11:47:01.449290855Z" level=info msg="Attempting next endpoint for pull after error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
  • Nov 19 11:47:01 minikube dockerd[2422]: time="2019-11-19T11:47:01.449460511Z" level=error msg="Handler for POST /v1.39/images/create returned error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
  • Nov 19 11:47:01 minikube dockerd[2422]: time="2019-11-19T11:47:01.491271188Z" level=warning msg="failed to retrieve runc version: unknown output format: runc version commit: 425e105d5a03fabd737a126ad93d62a9eeede87f\nspec: 1.0.1-dev\n"
  • Nov 19 11:47:16 minikube dockerd[2422]: time="2019-11-19T11:47:16.542775605Z" level=warning msg="Error getting v2 registry: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
  • Nov 19 11:47:16 minikube dockerd[2422]: time="2019-11-19T11:47:16.542843881Z" level=info msg="Attempting next endpoint for pull after error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
  • Nov 19 11:47:16 minikube dockerd[2422]: time="2019-11-19T11:47:16.542876829Z" level=error msg="Handler for POST /v1.39/images/create returned error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
  • Nov 19 11:47:16 minikube dockerd[2422]: time="2019-11-19T11:47:16.579753180Z" level=warning msg="failed to retrieve runc version: unknown output format: runc version commit: 425e105d5a03fabd737a126ad93d62a9eeede87f\nspec: 1.0.1-dev\n"
  • Nov 19 11:47:31 minikube dockerd[2422]: time="2019-11-19T11:47:31.632370221Z" level=warning msg="Error getting v2 registry: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
  • Nov 19 11:47:31 minikube dockerd[2422]: time="2019-11-19T11:47:31.632418965Z" level=info msg="Attempting next endpoint for pull after error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
  • Nov 19 11:47:31 minikube dockerd[2422]: time="2019-11-19T11:47:31.632446924Z" level=error msg="Handler for POST /v1.39/images/create returned error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
  • ==> container status <==
  • time="2019-11-19T11:51:19Z" level=fatal msg="failed to connect: failed to connect, make sure you are running as root and the runtime has been started: context deadline exceeded"
  • CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
  • ==> dmesg <==
  • [ +5.004202] hpet1: lost 318 rtc interrupts
  • [ +5.001218] hpet1: lost 318 rtc interrupts
  • [ +5.001388] hpet1: lost 318 rtc interrupts
  • [ +5.002595] hpet1: lost 318 rtc interrupts
  • [ +5.001013] hpet1: lost 318 rtc interrupts
  • [ +5.004036] hpet1: lost 319 rtc interrupts
  • [ +4.998698] hpet1: lost 318 rtc interrupts
  • [ +5.001699] hpet1: lost 318 rtc interrupts
  • [Nov19 11:47] hpet1: lost 318 rtc interrupts
  • [ +5.003916] hpet1: lost 318 rtc interrupts
  • [ +5.002062] hpet1: lost 318 rtc interrupts
  • [ +5.007779] hpet1: lost 319 rtc interrupts
  • [ +4.999536] hpet1: lost 318 rtc interrupts
  • [ +5.015203] hpet1: lost 319 rtc interrupts
  • [ +5.009401] hpet1: lost 318 rtc interrupts
  • [ +5.004167] hpet1: lost 320 rtc interrupts
  • [ +5.012413] hpet1: lost 320 rtc interrupts
  • [ +5.010686] hpet1: lost 318 rtc interrupts
  • [ +5.005131] hpet1: lost 320 rtc interrupts
  • [ +5.006528] hpet1: lost 318 rtc interrupts
  • [Nov19 11:48] hpet1: lost 320 rtc interrupts
  • [ +5.004164] hpet1: lost 318 rtc interrupts
  • [ +5.004006] hpet1: lost 318 rtc interrupts
  • [ +5.007096] hpet1: lost 319 rtc interrupts
  • [ +5.008629] hpet1: lost 318 rtc interrupts
  • [ +5.004630] hpet1: lost 318 rtc interrupts
  • [ +5.004935] hpet1: lost 319 rtc interrupts
  • [ +5.011985] hpet1: lost 318 rtc interrupts
  • [ +5.002550] hpet1: lost 319 rtc interrupts
  • [ +4.998940] hpet1: lost 318 rtc interrupts
  • [ +5.006772] hpet1: lost 318 rtc interrupts
  • [ +5.009340] hpet1: lost 319 rtc interrupts
  • [Nov19 11:49] hpet1: lost 319 rtc interrupts
  • [ +5.006958] hpet1: lost 318 rtc interrupts
  • [ +5.002891] hpet1: lost 318 rtc interrupts
  • [ +5.011264] hpet1: lost 320 rtc interrupts
  • [ +5.004222] hpet1: lost 318 rtc interrupts
  • [ +5.004929] hpet1: lost 319 rtc interrupts
  • [ +5.016705] hpet1: lost 319 rtc interrupts
  • [ +4.988667] hpet1: lost 317 rtc interrupts
  • [ +5.005119] hpet1: lost 318 rtc interrupts
  • [ +5.011002] hpet1: lost 319 rtc interrupts
  • [ +5.008422] hpet1: lost 318 rtc interrupts
  • [ +5.004273] hpet1: lost 319 rtc interrupts
  • [Nov19 11:50] hpet1: lost 318 rtc interrupts
  • [ +4.995056] hpet1: lost 318 rtc interrupts
  • [ +5.006072] hpet1: lost 318 rtc interrupts
  • [ +5.006934] hpet1: lost 319 rtc interrupts
  • [ +4.999093] hpet1: lost 318 rtc interrupts
  • [ +5.005009] hpet1: lost 318 rtc interrupts
  • [ +5.004850] hpet1: lost 318 rtc interrupts
  • [ +5.005675] hpet1: lost 319 rtc interrupts
  • [ +5.008369] hpet1: lost 318 rtc interrupts
  • [ +5.010152] hpet1: lost 319 rtc interrupts
  • [ +5.008685] hpet1: lost 318 rtc interrupts
  • [ +5.006449] hpet1: lost 319 rtc interrupts
  • [Nov19 11:51] hpet1: lost 318 rtc interrupts
  • [ +5.009633] hpet1: lost 319 rtc interrupts
  • [ +5.014726] hpet1: lost 319 rtc interrupts
  • [ +4.999324] hpet1: lost 318 rtc interrupts
  • ==> kernel <==
  • 11:51:19 up 9 min, 0 users, load average: 0.08, 0.16, 0.12
  • Linux minikube 4.19.76 Need a reliable and low latency local cluster setup for Kubernetes  #1 SMP Tue Oct 29 14:56:42 PDT 2019 x86_64 GNU/Linux
  • PRETTY_NAME="Buildroot 2019.02.6"
  • ==> kubelet <==
  • -- Logs begin at Tue 2019-11-19 11:42:10 UTC, end at Tue 2019-11-19 11:51:19 UTC. --
  • Nov 19 11:51:16 minikube kubelet[6848]: 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/kubelet-config-file/ for more information.
  • Nov 19 11:51:16 minikube kubelet[6848]: F1119 11:51:16.321843 6848 server.go:196] failed to load Kubelet config file /var/lib/kubelet/config.yaml, error failed to read kubelet config file "/var/lib/kubelet/config.yaml", error: open /var/lib/kubelet/config.yaml: no such file or directory
  • Nov 19 11:51:16 minikube systemd[1]: kubelet.service: Main process exited, code=exited, status=255/EXCEPTION
  • Nov 19 11:51:16 minikube systemd[1]: kubelet.service: Failed with result 'exit-code'.
  • Nov 19 11:51:16 minikube systemd[1]: kubelet.service: Service RestartSec=600ms expired, scheduling restart.
  • Nov 19 11:51:16 minikube systemd[1]: kubelet.service: Scheduled restart job, restart counter is at 462.
  • Nov 19 11:51:16 minikube systemd[1]: Stopped kubelet: The Kubernetes Node Agent.
  • Nov 19 11:51:16 minikube systemd[1]: Started kubelet: The Kubernetes Node Agent.
  • Nov 19 11:51:17 minikube kubelet[6868]: Flag --authorization-mode 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.
  • Nov 19 11:51:17 minikube kubelet[6868]: 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.
  • Nov 19 11:51:17 minikube kubelet[6868]: Flag --client-ca-file 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.
  • Nov 19 11:51:17 minikube kubelet[6868]: Flag --cluster-dns 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.
  • Nov 19 11:51:17 minikube kubelet[6868]: Flag --cluster-domain 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.
  • Nov 19 11:51:17 minikube kubelet[6868]: 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.
  • Nov 19 11:51:17 minikube kubelet[6868]: 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/kubelet-config-file/ for more information.
  • Nov 19 11:51:17 minikube kubelet[6868]: F1119 11:51:17.035890 6868 server.go:196] failed to load Kubelet config file /var/lib/kubelet/config.yaml, error failed to read kubelet config file "/var/lib/kubelet/config.yaml", error: open /var/lib/kubelet/config.yaml: no such file or directory
  • Nov 19 11:51:17 minikube systemd[1]: kubelet.service: Main process exited, code=exited, status=255/EXCEPTION
  • Nov 19 11:51:17 minikube systemd[1]: kubelet.service: Failed with result 'exit-code'.
  • Nov 19 11:51:17 minikube systemd[1]: kubelet.service: Service RestartSec=600ms expired, scheduling restart.
  • Nov 19 11:51:17 minikube systemd[1]: kubelet.service: Scheduled restart job, restart counter is at 463.
  • Nov 19 11:51:17 minikube systemd[1]: Stopped kubelet: The Kubernetes Node Agent.
  • Nov 19 11:51:17 minikube systemd[1]: Started kubelet: The Kubernetes Node Agent.
  • Nov 19 11:51:17 minikube kubelet[6926]: Flag --authorization-mode 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.
  • Nov 19 11:51:17 minikube kubelet[6926]: 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.
  • Nov 19 11:51:17 minikube kubelet[6926]: Flag --client-ca-file 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.
  • Nov 19 11:51:17 minikube kubelet[6926]: Flag --cluster-dns 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.
  • Nov 19 11:51:17 minikube kubelet[6926]: Flag --cluster-domain 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.
  • Nov 19 11:51:17 minikube kubelet[6926]: 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.
  • Nov 19 11:51:17 minikube kubelet[6926]: 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/kubelet-config-file/ for more information.
  • Nov 19 11:51:17 minikube kubelet[6926]: F1119 11:51:17.810221 6926 server.go:196] failed to load Kubelet config file /var/lib/kubelet/config.yaml, error failed to read kubelet config file "/var/lib/kubelet/config.yaml", error: open /var/lib/kubelet/config.yaml: no such file or directory
  • Nov 19 11:51:17 minikube systemd[1]: kubelet.service: Main process exited, code=exited, status=255/EXCEPTION
  • Nov 19 11:51:17 minikube systemd[1]: kubelet.service: Failed with result 'exit-code'.
  • Nov 19 11:51:18 minikube systemd[1]: kubelet.service: Service RestartSec=600ms expired, scheduling restart.
  • Nov 19 11:51:18 minikube systemd[1]: kubelet.service: Scheduled restart job, restart counter is at 464.
  • Nov 19 11:51:18 minikube systemd[1]: Stopped kubelet: The Kubernetes Node Agent.
  • Nov 19 11:51:18 minikube systemd[1]: Started kubelet: The Kubernetes Node Agent.
  • Nov 19 11:51:18 minikube kubelet[6934]: Flag --authorization-mode 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.
  • Nov 19 11:51:18 minikube kubelet[6934]: 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.
  • Nov 19 11:51:18 minikube kubelet[6934]: Flag --client-ca-file 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.
  • Nov 19 11:51:18 minikube kubelet[6934]: Flag --cluster-dns 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.
  • Nov 19 11:51:18 minikube kubelet[6934]: Flag --cluster-domain 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.
  • Nov 19 11:51:18 minikube kubelet[6934]: 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.
  • Nov 19 11:51:18 minikube kubelet[6934]: 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/kubelet-config-file/ for more information.
  • Nov 19 11:51:18 minikube kubelet[6934]: F1119 11:51:18.569230 6934 server.go:196] failed to load Kubelet config file /var/lib/kubelet/config.yaml, error failed to read kubelet config file "/var/lib/kubelet/config.yaml", error: open /var/lib/kubelet/config.yaml: no such file or directory
  • Nov 19 11:51:18 minikube systemd[1]: kubelet.service: Main process exited, code=exited, status=255/EXCEPTION
  • Nov 19 11:51:18 minikube systemd[1]: kubelet.service: Failed with result 'exit-code'.
  • Nov 19 11:51:19 minikube systemd[1]: kubelet.service: Service RestartSec=600ms expired, scheduling restart.
  • Nov 19 11:51:19 minikube systemd[1]: kubelet.service: Scheduled restart job, restart counter is at 465.
  • Nov 19 11:51:19 minikube systemd[1]: Stopped kubelet: The Kubernetes Node Agent.
  • Nov 19 11:51:19 minikube systemd[1]: Started kubelet: The Kubernetes Node Agent.
  • Nov 19 11:51:19 minikube kubelet[6943]: Flag --authorization-mode 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.
  • Nov 19 11:51:19 minikube kubelet[6943]: 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.
  • Nov 19 11:51:19 minikube kubelet[6943]: Flag --client-ca-file 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.
  • Nov 19 11:51:19 minikube kubelet[6943]: Flag --cluster-dns 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.
  • Nov 19 11:51:19 minikube kubelet[6943]: Flag --cluster-domain 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.
  • Nov 19 11:51:19 minikube kubelet[6943]: 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.
  • Nov 19 11:51:19 minikube kubelet[6943]: 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/kubelet-config-file/ for more information.
  • Nov 19 11:51:19 minikube kubelet[6943]: F1119 11:51:19.303124 6943 server.go:196] failed to load Kubelet config file /var/lib/kubelet/config.yaml, error failed to read kubelet config file "/var/lib/kubelet/config.yaml", error: open /var/lib/kubelet/config.yaml: no such file or directory
  • Nov 19 11:51:19 minikube systemd[1]: kubelet.service: Main process exited, code=exited, status=255/EXCEPTION
  • Nov 19 11:51:19 minikube systemd[1]: kubelet.service: Failed with result 'exit-code'.

使用的操作系统版本：
@ShangCunShanFu ShangCunShanFu added the l/zh-CN Issues in or relating to Chinese label Nov 19, 2019
@priyawadhwa priyawadhwa changed the title X 开启 cluster 时出错 Error starting cluster: unable to pull images Nov 20, 2019
@priyawadhwa priyawadhwa changed the title Error starting cluster: unable to pull images Error starting cluster: kubelet config: no such file or directory Nov 20, 2019
@priyawadhwa
Copy link

感谢您打开此问题。似乎与 #5897 有关。

您可以运行：

minikube delete

然后提供以下内容的输出：

minikube start --vm-driver=virtualbox --alsologtostderr -v = 1

谢谢！

@priyawadhwa priyawadhwa added the kind/support Categorizes issue or PR as a support question. label Nov 20, 2019
@priyawadhwa priyawadhwa changed the title Error starting cluster: kubelet config: no such file or directory Error starting cluster: kubelet config: error: open /var/lib/kubelet/config.yaml: no such file or directory Nov 20, 2019
@etuttle
Copy link

etuttle commented Nov 21, 2019

I've seen this twice now since upgrading to v1.5.2 (OSX, hyperkit driver). /var/lib/kubelet is empty! I fixed it the first time by deleting the profile and starting a new VM, which is a bummer.

By the time it happens, I haven't been able to find any clues in the start --alsologtostderr -v=8 debug output.

@etuttle
Copy link

etuttle commented Nov 21, 2019 •
edited
Loading

It looks to me like the culprit is #5697 which I picked up when I upgraded from 1.5.0 to 1.5.2.

When minikube boots, it calls kubeadm which renders out /etc/kubernetes/kubelet.config among other things. It does not render out /var/lib/kubelet/config.yaml for me. I am unclear how that file is getting created it for minikube users that have it (see discussion in #5329).

I tried adding --extra-config=kubelet.config=/etc/kubernetes/kubelet.config but that produced command line flags that made kubelet exit immediately.

I ended up downgrading to 1.5.0, deleting my profile, and starting back up. Everything works now.

@tstromberg
Copy link
Contributor

I believe we solved this issue in minikube v1.6. Please reopen if you happen to bump into it again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/support Categorizes issue or PR as a support question. l/zh-CN Issues in or relating to Chinese
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@tstromberg @etuttle @priyawadhwa @ShangCunShanFu