Error downloading kubelet: A connection attempt failed because the connected party did not properly respond #6109
Labels
failed/local-networking
startup failures due to networking issues
kind/support
Categorizes issue or PR as a support question.
triage/needs-information
Indicates an issue needs more information in order to work on it.
The exact command to reproduce the issue: minikube start --vm-driver=virtualbox
The full output of the command that failed:
E1217 21:31:20.101836 13560 cache_images.go:80] CacheImage k8s.gcr.io/k8s-dns-sidecar-amd64:1.14.13 -> C:\Us
ers\Nikhil.minikube\cache\images\k8s.gcr.io\k8s-dns-sidecar-amd64_1.14.13 failed: fetching image: Get https:/
/k8s.gcr.io/v2/: dial tcp: lookup k8s.gcr.io: no such host
E1217 21:33:04.898863 13560 start.go:799] Error caching images: Caching images for kubeadm: caching images:
caching image C:\Users\Nikhil.minikube\cache\images\k8s.gcr.io\k8s-dns-sidecar-amd64_1.14.13: fetching image
: Get https://k8s.gcr.io/v2/: dial tcp: lookup k8s.gcr.io: no such host
s.gcr.io\k8s-dns-sidecar-amd64_1.14.13: CreateFile C:\Users\Nikhil.minikube\cache\images\k8s.gcr.io\k8s-dns-s
idecar-amd64_1.14.13: The system cannot find the file specified.
X Failed to update cluster: downloading binaries: downloading kubelet: Error downloading kubelet v1.16.2: fail
ed to download: failed to download to temp file: failed to copy contents: read tcp 192.168.0.106:61314->172.21
7.166.176:443: wsarecv: 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.
*
The output of the
minikube logs
command:The operating system version: windows 10
The text was updated successfully, but these errors were encountered: