My VPS has only an IPv6 address, but I’m using Dan Win’s github IPv6 proxy: I can ping github.com, I successfully cloned discourse_docker.git, and I can clone the exact same discourse.git from the command line on the same VPS. But when the same command is executed by discourse-setup, it cannot resolve github.com and fails.
A previous post recommended setting mtu=1400 in my docker.service file, which I did, but it didn’t change anything.
I first assumed this was an IPv6 problem, but the fact that my VPS can access github and clone the package has me confused… I don’t know what the setup is doing differently. I wish there were some way to tell discourse-setup that github.git is already on the server or just to use the server’s default settings that worked.
I’ve hit issues with Docker on IPv6 only systems in the past related to the lack of NAT, since Docker often uses IP addresses that are only accessible from the host but NAT is not automatically configured by Docker for IPv6.