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.

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

Error downloading kubelet: A connection attempt failed because the connected party did not properly respond #6109

Closed
NikhilSarda opened this issue Dec 17, 2019 · 5 comments
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.

Comments

@NikhilSarda
Copy link

The exact command to reproduce the issue: minikube start --vm-driver=virtualbox

The full output of the command that failed:

  • minikube v1.5.2 on Microsoft Windows 10 Enterprise 10.0.17134 Build 17134
  • Creating virtualbox VM (CPUs=2, Memory=2000MB, Disk=20000MB) ...
    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
  • Preparing Kubernetes v1.16.2 on Docker '18.09.9' ...
    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
  • Unable to load cached images: loading cached images: loading image C:\Users\Nikhil.minikube\cache\images\k8
    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.
  • Downloading kubelet v1.16.2

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

@tstromberg tstromberg changed the title minikube crashes Error downloading kubelet: A connection attempt failed because the connected party did not properly respond Dec 19, 2019
@tstromberg
Copy link
Contributor

minikube needs access to the internet to download the required images and binaries the first time.

Does your machine require an HTTP proxy to access the internet? If so, you will need to configure it: https://minikube.sigs.k8s.io/docs/reference/networking/proxy/

@tstromberg tstromberg added 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. labels Dec 19, 2019
@priyawadhwa
Copy link

Hey @NikhilSarda are you still seeing this issue?

@NikhilSarda
Copy link
Author

@priyawadhwa Haven't checked yet. Will check and let you know soon.

@priyawadhwa
Copy link

Hey @NikhilSarda any updates here?

@priyawadhwa
Copy link

Hey @NikhilSarda --

Hopefully it's OK if I close this, as some time has already passed. If you are able to provide additional details, you may reopen it at any point by adding /reopen to your comment.

Thank you for sharing your experience!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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.
Projects
None yet
Development

No branches or pull requests

3 participants