A
A
Anton2018-03-18 18:33:00
Continuous Integration
Anton, 2018-03-18 18:33:00

How to fix gitlab-ci-multi-runner Couldn't resolve host if host is pinged?

Good afternoon!
How to fix gitlab-ci-multi-runner Couldn't resolve host if host is pinged?
Installed gitlab, gitlab-ci-multi-runner
Running with gitlab-ci-multi-runner 9.5.1 (96b34cc)
on gitlab.paa (ed7ddf0c)
Using Docker executor with image alpine ...
....
fatal: unable to access ' http://gitlab-ci-token:[email protected] ': Couldn't resolve host 'gitlab.paa'
But the specified host
resolves ping gitlab.paa
PING gitlab.paa (192.168.88.245) 56(84) bytes of data.
64 bytes from gitlab.paa (192.168.88.245): icmp_seq=1 ttl=64 time=0.041 ms
nslookup gitlab.paa
Server: 192.168.88.1
Address: 192.168.88.1#53
Non-authoritative answer:
Name: gitlab.paa
Address: 192.168.88.245
I know about extra_hosts
https://stackoverflow.com/questions/34242634/add-h...
But it should probably resolve in docker if it resolves on the server?

Answer the question

In order to leave comments, you need to log in

1 answer(s)
A
Anton, 2018-03-19
Patsev @chemtech

you need to
add
extra_hosts=["dns-domain:ip-dns"] to the /etc/gitlab-runner/config.toml file
as described here
https://gitlab.com/gitlab-org/gitlab-runner/issues...

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question