When running ./discourse-setup it continues to fail with the error: cd /pups && git pull && /pups/bin/pups --stdin fatal: unable to access 'https://github.com/discourse/pups.git/': Could not resolve host: github.com fe7a66f6321f948dd840124da1f0165db18807367b4419e1cc9906eb7f71a0a8 ** FAILED TO BOOTSTRAP ** I have tried like at least 3 different solutions to this problem that I could find from this forum and around GitHub, including some Docker stack overflow answers for “lack of internet” and “DNS problems” within docker. I have tried following like at least 2 different tutorials I could find for setting the Discourse forum software up, the official one and some other one. Things like setting up a daemon.json file with DNS’ configured. Setting the docker0 interface into promiscuous mode. After all that I still get the same problem. I am using an Ubuntu 20.04 server hosted by OVH. I am able to ping github.com and get a response on the host, just not within the Docker setup. Anyone able to help? Edit: after hacking together a manual entry in the/etc/hosts file of the container environment for github’s IP address, it now says “connection timed out” instead of “unable to resolve github.com”.

This is at least the second report in recent days. [image] After upgrade, docker cannot communicate with the outside world Self-hosting Honestly, I think the best approach at this point is to reinstall and copy your data over. You have a broken system for Mysterious Reasons, and the installation process is rather quick. It’s likely the best use of your time. We’ll take a look at the process.

[image] pfaffman: How’d you install docker? I think the first time I ran /discourse-setup it installed Docker for me. And after hacking together a manual entry in the/etc/hosts file of the container environment for github’s IP address, it now says “connection timed out” instead of “unable to resolve github.com”. So it seems like it might be an internet connection problem in general and not just a DNS thing. I even tried running it with the --network host option and it still didn’t work even though it does work on my host. If I run a simple test Docker container, I am able to reach the internet from it. It just seems like the Discourse container is not connecting out.

Just as a note, it seems to be working fine on a DigitalOcean droplet (as recommended by the README). However this problem still persists on my existing Ubuntu 20.04 server.

I am having the same issue with a default digital ocean droplet based on ubuntu 20.04. Did you find a solution yet? seems to work now, see After upgrade, docker cannot communicate with the outside world - #24 by niels-anders

./discourse-setup: could not resolve host: github.com

Product Support

supermathie (Michael Brown) December 5, 2020, 1:29am 2

This is at least the second report in recent days.

We’ll take a look at the process.

After upgrade, docker cannot communicate with the outside world

Topic		Replies	Views
After upgrade, docker cannot communicate with the outside world Self-hosting	26	3929	February 1, 2021
Discourse docker container has trouble reaching DNS Self-hosting	10	4590	April 30, 2018
Restore from a server image that contain discourse, but rebuild error Product Support	6	649	September 13, 2020
Unable to install on ubuntu Self-hosting	6	395	May 18, 2024
Failed to Bootstrap Ping is working to github Self-hosting	11	5462	December 4, 2020

./discourse-setup: could not resolve host: github.com

Related topics