search

kubernetes / minikube

Run Kubernetes locally
https://minikube.sigs.k8s.io/
Apache License 2.0
29.45k stars 4.88k forks source link

Unable to download kubeadm: write udp host->srv:53: write: host is down #4506

Closed eduardo4jesus closed 5 years ago

eduardo4jesus commented 5 years ago

I installed kubectl and minikube and using brew install and brew cask install, respectively. Just opened VirtualBox, and the minikube VM shows as running.

The exact command to reproduce the issue: minikube start

The full output of the command that failed:

😄  minikube v1.1.1 on darwin (amd64)
💡  Tip: Use 'minikube start -p <name>' to create a new cluster, or 'minikube delete' to delete this one.
🏃  Re-using the currently running virtualbox VM for "minikube" ...
⌛  Waiting for SSH access ...
🐳  Configuring environment for Kubernetes v1.14.3 on Docker 18.09.6
💾  Downloading kubelet v1.14.3
💾  Downloading kubeadm v1.14.3

💣  Failed to update cluster: downloading binaries: downloading kubeadm: Error downloading kubeadm v1.14.3: failed to download: failed to download to temp file: download failed: 5 error(s) occurred:

* Temporary download error: Get https://storage.googleapis.com/kubernetes-release/release/v1.14.3/bin/linux/amd64/kubeadm: dial tcp: lookup storage.googleapis.com on 192.168.99.12:53: write udp 192.168.99.1:55906->192.168.99.12:53: write: host is down
* Temporary download error: Get https://storage.googleapis.com/kubernetes-release/release/v1.14.3/bin/linux/amd64/kubeadm: dial tcp: lookup storage.googleapis.com on 192.168.99.12:53: write udp 192.168.99.1:62018->192.168.99.12:53: write: host is down
* Temporary download error: Get https://storage.googleapis.com/kubernetes-release/release/v1.14.3/bin/linux/amd64/kubeadm: dial tcp: lookup storage.googleapis.com on 192.168.99.12:53: write udp 192.168.99.1:60351->192.168.99.12:53: write: host is down
* Temporary download error: Get https://storage.googleapis.com/kubernetes-release/release/v1.14.3/bin/linux/amd64/kubeadm: dial tcp: lookup storage.googleapis.com on 192.168.99.12:53: write udp 192.168.99.1:65519->192.168.99.12:53: write: host is down
* Temporary download error: Get https://storage.googleapis.com/kubernetes-release/release/v1.14.3/bin/linux/amd64/kubeadm: dial tcp: lookup storage.googleapis.com on 192.168.99.12:53: write udp 192.168.99.1:59189->192.168.99.12:53: write: host is down

😿  Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
👉  https://github.com/kubernetes/minikube/issues/new

The output of the minikube logs command:

==> dmesg <==
[  +5.016387] hpet1: lost 319 rtc interrupts
[  +4.996475] hpet1: lost 319 rtc interrupts
[  +5.001314] hpet1: lost 318 rtc interrupts
[Jun16 22:24] hpet1: lost 318 rtc interrupts
[  +5.000369] hpet1: lost 319 rtc interrupts
[  +5.021442] hpet1: lost 321 rtc interrupts
[  +4.989294] hpet1: lost 317 rtc interrupts
[  +5.003016] hpet1: lost 318 rtc interrupts
[  +5.001207] hpet1: lost 318 rtc interrupts
[  +5.002933] hpet1: lost 318 rtc interrupts
[  +4.999683] hpet1: lost 318 rtc interrupts
[  +5.002901] hpet1: lost 320 rtc interrupts
[  +5.003908] hpet1: lost 318 rtc interrupts
[  +4.999168] hpet1: lost 319 rtc interrupts
[  +5.003794] hpet1: lost 318 rtc interrupts
[Jun16 22:25] hpet1: lost 319 rtc interrupts
[  +5.003432] hpet1: lost 318 rtc interrupts
[  +5.004398] hpet1: lost 319 rtc interrupts
[  +5.004077] hpet1: lost 318 rtc interrupts
[  +5.002706] hpet1: lost 318 rtc interrupts
[  +5.000295] hpet1: lost 318 rtc interrupts
[  +5.003799] hpet1: lost 318 rtc interrupts
[  +5.003023] hpet1: lost 320 rtc interrupts
[  +5.002983] hpet1: lost 318 rtc interrupts
[  +5.004555] hpet1: lost 318 rtc interrupts
[  +5.001519] hpet1: lost 318 rtc interrupts
[  +5.003233] hpet1: lost 318 rtc interrupts
[Jun16 22:26] hpet1: lost 318 rtc interrupts
[  +5.002123] hpet1: lost 319 rtc interrupts
[  +5.001409] hpet1: lost 318 rtc interrupts
[  +5.003383] hpet1: lost 318 rtc interrupts
[  +5.002690] hpet1: lost 319 rtc interrupts
[  +5.002221] hpet1: lost 318 rtc interrupts
[  +5.001601] hpet1: lost 318 rtc interrupts
[  +5.001961] hpet1: lost 318 rtc interrupts
[  +5.002348] hpet1: lost 319 rtc interrupts
[  +5.006178] hpet1: lost 318 rtc interrupts
[  +5.138782] hpet1: lost 327 rtc interrupts
[  +4.994981] hpet1: lost 318 rtc interrupts
[Jun16 22:27] hpet1: lost 318 rtc interrupts
[  +5.003863] hpet1: lost 318 rtc interrupts
[  +5.002642] hpet1: lost 318 rtc interrupts
[  +5.000609] hpet1: lost 318 rtc interrupts
[  +5.004011] hpet1: lost 318 rtc interrupts
[  +5.001319] hpet1: lost 318 rtc interrupts
[  +5.001817] hpet1: lost 319 rtc interrupts
[  +5.004002] hpet1: lost 318 rtc interrupts
[  +5.004261] hpet1: lost 319 rtc interrupts
[  +5.002855] hpet1: lost 318 rtc interrupts
[  +5.002795] hpet1: lost 318 rtc interrupts

==> kernel <==
 22:27:53 up 23 min,  0 users,  load average: 0.00, 0.05, 0.22
Linux minikube 4.15.0 #1 SMP Thu Jun 6 15:07:18 PDT 2019 x86_64 GNU/Linux

==> kubelet <==
-- Logs begin at Sun 2019-06-16 22:04:54 UTC, end at Sun 2019-06-16 22:27:53 UTC. --
-- No entries --

The operating system version: MacOS Mojave Version 10.14.4 (18E226)

medyagh commented 5 years ago

Thank you for taking the time to create this issue, I am curious if you are behind a proxy or vpn ?

simonMoisselin commented 5 years ago

I have exactly the same issue. Waiting for updates !

eduardo4jesus commented 5 years ago

@medyagh , I am not sure if there is a proxy on my network. I am under an university's network. I could download these files and manually put in a cache folder inside .minibuke. But that didn't work to. Let me know what informations I could provide.

tstromberg commented 5 years ago

@eduardo4jesus - This error is raised because DNS queries to 192.168.99.12 are failing. It isn't clear if it's a general network failure, or just a failure to resolve a DNS. Do you have any idea what that IP points to?

Some commands which may help:

host 192.168.99.12 route get 192.168.99.12 scutil --dns | grep 192.168.99.12

Worst case, you should be able to work around the issue by running curl -O on the binaries, and storing them in ~/.minikube/cache/v1.14.3

medyagh commented 5 years ago

@@eduardo4jesus are you still facing this issue ?