日本語のみで絞り込む
2023/11/18 -If using multiple DNS servers, they must both resolve the same IP's, and also have all the DNS entries required. Any missing entry on either of ...
We discovered that the `dns` setting in the section `[runners.docker]` does not apply to the service as well. Logging in to `docker:dind` revealed `/etc/resolv.
GitLab Runner uses the Docker executor to run jobs on Docker images. As a workaround, manually provide the custom DNS settings to the dind service. can use 127 ...
For example, a shared GitLab Runner environment that uses the docker-machine executor would have a {selector} similar to node=shared-runner-123 . Was this ...
2018/5/14 -For anyone trying to deploy a runner using a docker executor in a private network with its own dns setup (i.e. having their own dns server) ...
2019/6/4 -Hello, I install gitlab runner into google cloud network. The gitlab instance is installed into private network, so there are a public ip ...
2025/11/24 -This series documents my journey of learning and deploying GitLab Runner on Kubernetes, Debug DNS resolution issues in containerized ...
2021/8/21 -Running a docker build with gitlab-ci. Works well locally, but we are moving runners to AWS on ubuntu 20 and it appears that DNS is not working ...
2018/8/30 -The GitLab Runner cannot resolve an ip for the the GitLab instance because it is using Google's DNS for domain name resolution, and Google's ...
2020/8/11 -Hello, I have installed gitlab on my CentOS VM I have also installed gitlab runner on the same VM Docker is installed on the VM.