Setting up GitLab on my home server, decided to put a docker gitlab-runner inside of a VM. Calling home seems to work fine, so does accepting jobs, but attempts to git clone outright fail stating it can’t resolve the host.
Okay, networking issues you’d think…except I can access the host and internet just fine. If I manually start a ubuntu:16.04 container everything works fine as well. Worse, I can even ping the host in a pre-clone script.
I’m very, very confused right now.
Running with gitlab-ci-multi-runner 9.1.1 (6104325) on Standard Ubuntu 17.04 (53dd69f5) Using Docker executor with image ubuntu:16.04 ... Using docker image sha256:3919c87cf29a786c9d1c6252cc38befddccb4163eccffb847e0d1a73648602e4 for predefined container... Pulling docker image ubuntu:16.04 ... Using docker image ubuntu:16.04 ID=sha256:f7b3f317ec734a73deca91b34c2b1e3dd7454650da9c8ef3047d29a873865178 for build container... Running on runner-53dd69f5-project-3-concurrent-0 via VM-GitlabRunner... $ cat /etc/resolv.conf nameserver 220.127.116.11 $ cat /etc/hosts 127.0.0.1 localhost ::1 localhost ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters 172.17.0.2 runner-53dd69f5-project-3-concurrent-0 $ ping -c 5 gitlab.[REDACTED].it PING gitlab.[REDACTED].it ([REDACTED]): 56 data bytes 64 bytes from [REDACTED]: seq=0 ttl=62 time=0.597 ms 64 bytes from [REDACTED]: seq=1 ttl=62 time=0.482 ms 64 bytes from [REDACTED]: seq=2 ttl=62 time=0.901 ms 64 bytes from [REDACTED]: seq=3 ttl=62 time=0.828 ms 64 bytes from [REDACTED]: seq=4 ttl=62 time=0.988 ms --- gitlab.[REDACTED].it ping statistics --- 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max = 0.482/0.759/0.988 ms Cloning repository... Cloning into '/builds/[REDACTED]/[REDACTED]'... fatal: unable to access 'https://\gitlab.[REDACTED].it\/[REDACTED]/[REDACTED].git/': Couldn't resolve host '\gitlab.[REDACTED].it\' ERROR: Job failed: exit code 1