Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Docker option for IPv6 #1094

Closed
william00179 opened this issue Feb 27, 2024 · 4 comments · May be fixed by #1095
Closed

Support Docker option for IPv6 #1094

william00179 opened this issue Feb 27, 2024 · 4 comments · May be fixed by #1095
Labels
stale Issue/PR is stale and closed automatically

Comments

@william00179
Copy link
Contributor

Describe the solution you'd like

I'm trying to use the runner in a IPv6 only environment. The runner itself works well and is able to connect to my Gitlab instance, but when the job starts within its own docker container it gets a connection timeout to Gitlab as its not able to make use of the IPv6 networking.

To allow this to work, enable_ipv6 needs to be set in the Docker configuration otherwise docker networks don't support it.

See https://docs.docker.com/config/daemon/ipv6/ and https://gitlab.com/gitlab-org/gitlab-runner/-/issues/36994

Suggest a solution

Add the enable_ipv6 flag to runner_worker_docker_options. Note the enable_ipv6 documentation is currently missing, see the issue above.

@kayman-mk
Copy link
Collaborator

Seems to be mandatory, if you want to IPv6 only.

@kayman-mk
Copy link
Collaborator

@william00179 Are you working in a IPv6 only setup? There is #1075 claiming that SSM access in not working for IPv6 only so the Runner will not be able to start.

@kayman-mk kayman-mk modified the milestone: Release v8 Mar 2, 2024
Copy link
Contributor

github-actions bot commented May 2, 2024

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 15 days.

@github-actions github-actions bot added the stale Issue/PR is stale and closed automatically label May 2, 2024
Copy link
Contributor

This issue was closed because it has been stalled for 15 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Issue/PR is stale and closed automatically
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants