![]() ![]() DNS is working and ping gitlab works, except inside dockers: Reproduce problem: $ sudo docker run -it alpine ping gitlabīut works with DNS given: $ sudo docker run -it -dns=172.168.0.1 alpine ping gitlabĦ4 bytes from 172.168.0.5: seq=0 ttl=63 time=0.536 msĮdit /etc/docker/daemon. Same problem but GitLab and GitLab Runner run on different machines in LAN. In case this helps others looking for this. One localhost and one with your hostname: 127.0.0.1 localhost 127.0.1. Then have a look at nano /etc/hosts There you should find two lines. '/var/run/docker.sock:/var/run/docker.sock' 2 Answers Sorted by: 4 Have a look at nano /etc/hostname There you should find one line with the name of your machine. Are there any special characters not printed out user279434 at 14:13 Add a comment 2 Answers Sorted by: 3 This may mean your DNS lookups are broken. ![]() '/srv/gitlab-runner/config:/etc/gitlab-runner' Manfred Van de Waarsenburg 181 1 1 5 Compare content of your /etc/hostname with the second line of /etc/hosts. I think the issue comes from the image alpine which can not resolve the host. In both containers, I can access to the hostname. Running on runner-12ba77f7-project-1-concurrent-6621a827.įatal: unable to access Could not resolve host: ![]() Using Docker executor with image alpine:latest. Then, when I start the job, I got this error message: Running with gitlab-runner 10.7.1 (b9bba623) I register successfully a runner with this command: docker exec -it gitlab_gitlab-runner_1 gitlab-runner register -non-interactive -url -registration-token _wgMgEx3nBocYQtoi83c -executor docker -docker-image alpine:latest I understand that there are different manual ways to fix this issue, but as in the first time it did work for me, and as I would assume that the stack creation process is automatic, I suspect that there is some config/cache/? issue I am not aware of.Im using 2 containers on my Ubuntu OS: Gitlab-ce and gitlab-runnerĬontainers names are: gitlab_gitlab_1 and gitlab_gitlab-runner_1 ![]() I have gone through the steps three times already, but it always comes down to this.īased on that, I inserted the private ip/dns into etc/hosts, but it did not help (though it talks about 'network restart'. I tried everything, like adding my localhost, as specified in /etc/hostname, to the /etc/hosts. but I think when I first installed the bash it worked. Since the second attempt, however, whenever I try to do anything there with sudo it reacts very slowly and I got the unable to resolve host ip-172-31-xx-xxx: Temporary failure in name resolution message. rootlocalhost: sudo true sudo: unable to resolve host localhost. This is how I create the stack aws cloudformation create-stack \Īnd this is how I access it: ssh -i influxdb_example_3.pem manage to create the stack/instance and access it. rootlocalhost: sudo true sudo: unable to resolve host localhost. GroupDescription: for the app nodes that allow ssh I had another issue with an instance, so I decided that I delete it and redo the steps to create a new one:Īpt-get install -y apt-transport-https ca-certificatesĪpt-key adv apt-key adv -keyserver hkp://:80 -recv-keys 58118E89F3A912897C070ADBF76221572C52609DĪpt-get update -qq apt-get purge lxc-docker || trueĪdd-apt-repository "deb bionic stable"Īpt-get -y install linux-image-extra-$(uname -r) linux-image-extra-virtualĭocker image pull quay.io/influxdb/influxdb:v2.0.2ĭocker container run -p 80:9999 quay.io/influxdb/influxdb:v2.0.2 ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |