Hi all - We’re enjoying discourse thus far. I’m having an issue with running a rebuild of the docker container. The container won’t rebuild because for some reason it can’t resolve github.com . I know the host system (debian jessie) can resolve at that time via dig && ping. However if I issue a s…

This is very likely the solution [изображение] Failed to Bootstrap Ping is working to github installation Edit /etc/default/docker and uncomment the following line: DOCKER_OPTS="--dns 8.8.8.8 --dns 8.8.4.4" After this, restart docker and rebuild. I had the same issue to…

Hi @sam thanks for taking the time to review. I have that option uncommented in /etc/defaults/docker, and I’ve restarted the docker service many times. To clarify, after restarting the docker service the laucher rebuild will work once, after that I have to restart the service. You can see this vi…

Same issue, I went to add the cloudflare template and when rebuilding it could not resolve github.com . I have already tried the solution of using googles DNS servers in dockers configuration file with no success. doing ping github.com works but again, it cant seem to resolve when rebuilding. Here…

This isn’t a Discourse problem, it’s a Docker problem. You’ll probably get more knowledgeable help at the Docker support forums (which, helpfully, also run Discourse).

I figured out the issue and solution to this problem at least for me. The issue was that Docker uses 8.8.8.8 and 8.8.4.4 as its DNS and I had an OVH network based firewall blocking ALL IPv4 traffic that did not match port 80, 443, and a few other specific rules. I had to authorize IPv4 traffic for …

I’m experiencing a similar issue on the latest discourse git. This started happening after performing a system update and/or discourse update via the web UI. Now when I try to rebuild the app, I get: [root@forum /var/discourse]# ./launcher rebuild app Ensuring launcher is up to date Fetching origin…

I am getting the same error as gekkonen after having attempted to upgrade to the latest Discourse version. It appears Docker can no longer access the Internet at all from the default bridge network: docker run -it --net=bridge --rm busybox ping -c 1 github.com ping: bad address 'github.com' If I …

@gekkonen I got mine running again. As a workaround, to force the Internet to work from Docker, you can configure the docker0 network to use “promiscuous” mode: [root@forum /var/discourse]# ifconfig docker0 promisc You should then be able to use the launcher to rebuild the app, and the Discourse…

Yes, that seemed to get past the issue with the DNS for now. Thank you for the suggestion.

On CentOS8 this error is due to the RHEL7 docker rpms (there are no RHEL8 ones yet) not understanding the new nftables based firewall. One has to setup masquerading by hand for the docker0 interface https://serverfault.com/questions/987686/no-network-connectivity-to-from-docker-ce-container-on-cen…

Could not resolve host: github.com for SamSaffron/pups.git

Поддержка

sam (Sam Saffron) 13.Август.2015 07:14:48 2

This is very likely the solution

3 лайка

Тема		Ответов	Просм.
Failed to Bootstrap Ping is working to github Self-hosting	11	5277	04.12.2020
Restore from a server image that contain discourse, but rebuild error Support	6	522	13.09.2020
After upgrade, docker cannot communicate with the outside world Self-hosting	27	3316	03.03.2021
Discourse docker container has trouble reaching DNS Self-hosting	10	4410	30.04.2018
Could not resolve host: github.com Support	3	198	06.10.2025

Could not resolve host: github.com for SamSaffron/pups.git

Связанные темы