-
Notifications
You must be signed in to change notification settings - Fork 45
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
Could not resolve host: get.docker.com #14
Comments
RPi not responding to SSH, so might be PSU issue or network. |
This does sound like a network related issue that is not caused by the script itself. |
I was able to reach that site with my Mac, so not a firewall issue. RPi won't boot now, so starting from scratch again. Everything was fine up to that line, so I'm thinking my PSU might've been marginal in terms of supplying enough current and I was using Wifi. Will try with Ethernet next as well. |
I'm still getting the same issue - different PSU (but still on wifi) and failed at the same spot. I'm using CloudFlare DNS (1.1.1.1), so not sure if that is an issue but I can resolve the host on other machines, so maybe Stretch lite is doing something strange with DNS? Edit: re-imaged SD card and before running script tested DNS/network:
Edit-2: Re-ran on ethernet and script ran to completion. I'm guessing that wifi is the issue and that the docker container cannot access network via the host OS. |
Same. Could not resolve host : get.docker.com when using WiFi. Reflashed, connected to ethernet (after only enabling SSH, not WiFi), and it worked. |
Sadly i can’t use ehternet...any workaround? |
Added a PR to document this issue in the README. |
Same issue for me while installing docker as rootless (curl: (6) Could not resolve host: get.docker.com). For me "ping get.docker.com" is giving reply. I am running windows 11 but i am not able to install OpenSSH through App->Optional features. Any other workarounds? |
Script failed at
Edit: Using
2018-04-18-raspbian-stretch-lite
on a RPi 3B+ booting in headless mode connecting via wifi (using thewpa_supplicant.conf
file method).The text was updated successfully, but these errors were encountered: