The bridge driver doesn't allow a v6 only option for containers
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.2k
- Forks
- 875
- PR merge metrics
- No merged PRs in 30d
Description
When I launch containers with a v6 bridge network, there is no way for me to specify disabling IPv4 address allocation for the containers. There should be a way for docker to explicitly allow users to turn off IPv4 address allocation in user networks.
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files or tests. Start by tracing bridge network creation and address-allocation configuration in the Go code, then identify how a user network could disable IPv4 allocation while retaining IPv6. Done means a v6-only bridge network can be created and its containers receive no IPv4 addresses, with coverage for that behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100