actions / actions/actions-runner-controller
Ability to configure DIND bridge network
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.5k
- Forks
- 1.5k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 27
Description
Is your feature request related to a problem? Please describe.
The default Docker bridge network, 172.17.0.0/16, overlaps with our VPC network. This breaks network connectivity within the DIND container.
Describe the solution you'd like
Similar to the dockerMTU parameter, could there be a parameter that could be used to override the default Docker bridge network?
Describe alternatives you've considered
Alternatively, could the controller implement a way to specify a different DOCKER_HOST other than localhost? I'm able to get a separate DIND deployment running by manually setting the bridge network, but there doesn't seem a way to make ARC connect to it.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the controller handles the existing dockerMTU parameter and how the DIND deployment configures its Docker bridge network and DOCKER_HOST. Determine whether configuration should support a custom bridge network, a non-localhost DIND endpoint, or both. Done means ARC can connect to DIND without the default 172.17.0.0/16 overlap.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, go, kubernetes
- Domain
- devops, infrastructure, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100