Skip to content

Commit 9f72004

Browse files
authored
Update gitlab_ci_demo.md
1 parent 593dfcf commit 9f72004

File tree

1 file changed

+0
-10
lines changed

1 file changed

+0
-10
lines changed

05_testing_and_ci/gitlab_ci_demo.md

-10
Original file line numberDiff line numberDiff line change
@@ -91,19 +91,9 @@ A few workarounds are needed to make the GitLab runner work in this IPv6-only en
9191
First, we need to tell Docker to use the host network and DNS. We also need to replace the helper image with [the one from Docker Hub](https://hub.docker.com/r/gitlab/gitlab-runner-helper/tags?name=x86_64-v17.10.1) (depends on the GitLab version. You can start without this setting, and see which image GitLab is trying to pull). Edit the `[runners.docker]` section in `/srv/gitlab-runner/config/config.toml`:
9292

9393
```toml
94-
volumes = ["/etc/resolv.conf:/etc/resolv.conf:ro", "/srv/gitlab-runner/custom-hosts:/etc/hosts:ro", "/cache"]
9594
helper_image = "gitlab/gitlab-runner-helper:x86_64-v17.10.1"
9695
network_mode = "host"
9796
```
9897

9998
While we already pass `--network host` to `docker run`, setting this system-wide makes it easier to also start the job containers with the same settings.
10099

101-
Whenever changing this configuration file, we need to restart the runner (e.g., by restarting the respective container).
102-
103-
We also need to hard-code the IPv6 address that corresponds to the GitLab instance domain. Add the following line in the `/srv/gitlab-runner/custom-hosts` (create the file):
104-
105-
```
106-
2001:7c0:2015:216::19 gitlab-sim.informatik.uni-stuttgart.de
107-
```
108-
109-
You can get this address by running `dig aaaa gitlab-sim.informatik.uni-stuttgart.de`.

0 commit comments

Comments
 (0)