-
-
Notifications
You must be signed in to change notification settings - Fork 329
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
Comments
Seems to be mandatory, if you want to IPv6 only. |
@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. |
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. |
This issue was closed because it has been stalled for 15 days with no activity. |
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.The text was updated successfully, but these errors were encountered: