Gitlab runner failing -urgent

Hello,

I have installed Gitlab-ce and gitlab-ci-multi-runner as per standard documentation
on Ubuntu 16.04.

After registering specific runner as per below.
***************8
naman@ubuntu1604:/etc/gitlab$ sudo gitlab-ci-multi-runner register
Running in system-mode.

Please enter the gitlab-ci coordinator URL (e.g. https://gitlab.com/):
http://ci.mygitlab/ci
Please enter the gitlab-ci token for this runner:
_eZvewr_G9DyK1mxnyuD
Please enter the gitlab-ci description for this runner:
[ubuntu1604]: test-runner
Please enter the gitlab-ci tags for this runner (comma separated):
testrunner
Whether to run untagged builds [true/false]:
[false]: true
Whether to lock Runner to current project [true/false]:
[false]: false
Registering runner… succeeded runner=eZvewr
Please enter the executor: kubernetes, docker, docker-ssh, parallels, ssh, virtualbox, shell, docker+machine, docker-ssh+machine:
docker
Please enter the default Docker image (e.g. ruby:2.1):
ruby:2.1
Runner registered successfully. Feel free to start it, but if it’s running already the config should be automatically reloaded!

facing issue in building project where this runner is assigned.

Running with gitlab-ci-multi-runner 9.2.0 (adfc387)
on shared-runner (3f4bf68b)
Using Docker executor with image maven:3.3.9-jdk-8 …
Using docker image sha256:46f3e89ab33ee5b87efe78677ea252fec5bd78b77c885ec772105a38e38f1f47 for predefined container…
Pulling docker image maven:3.3.9-jdk-8 …
Using docker image maven:3.3.9-jdk-8 ID=sha256:9997d8483b2fc521a4159feab922546dda0c5c22b5084f86dfab48f123ae4364 for build container…
Running on runner-3f4bf68b-project-4-concurrent-0 via ubuntu1604…
Cloning repository…
Cloning into ‘/builds/gitlab/actuator-sample’…
fatal: unable to access ‘http://gitlab-ci-token:xxxxxxxxxxxxxxxxxxxx@ci.mygitlab/gitlab/actuator-sample.git/’: Couldn’t resolve host ‘ci.mygitlab’
ERROR: Job failed: exit code 1

I guess, this issue due to docker container is not able to know the host name of my linux vm,
so I did as below (add extra_hosts) in config.toml file

[runners.docker]
tls_verify = false
image = “ruby:2.1”
privileged = false
disable_cache = true
volumes = ["/cache"]
extra_hosts = [“ci.mygitlab:127.0.0.1”]
shm_size = 0
[runners.cache]
now error is bit different

Running with gitlab-ci-multi-runner 9.2.0 (adfc387)
on test-runner (7f9aba78)
Using Docker executor with image maven:3.3.9-jdk-8 …
Using docker image sha256:46f3e89ab33ee5b87efe78677ea252fec5bd78b77c885ec772105a38e38f1f47 for predefined container…
Pulling docker image maven:3.3.9-jdk-8 …
Using docker image maven:3.3.9-jdk-8 ID=sha256:9997d8483b2fc521a4159feab922546dda0c5c22b5084f86dfab48f123ae4364 for build container…
Running on runner-7f9aba78-project-4-concurrent-0 via ubuntu1604…
Cloning repository…
Cloning into ‘/builds/gitlab/actuator-sample’…
fatal: unable to access ‘http://gitlab-ci-token:xxxxxxxxxxxxxxxxxxxx@ci.mygitlab/gitlab/actuator-sample.git/’: Failed to connect to ci.mygitlab port 80: Connection refused
ERROR: Job failed: exit code 1

Resolved. insetad of extra_hosts = [“ci.mygitlab:127.0.0.1”] , i put extra_hosts = [“ci.mygitlab:x.x.x.x”] , ip of gitlab vm where repository is deployed.