docker network create does not accept `--no-dad` option for IPv6
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.2k
- Forks
- 875
- PR merge metrics
- No merged PRs in 30d
Description
I wanted to create IPv6 networks using docker bridge plugin. However, when I create the network with a v6 CIDR the address on the linux bridge (gateway) are marked as tenative due to DAD. How can I pass the --no-dad option to docker during network creation?
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
Start by tracing the docker network create entry point for bridge networks and the IPv6 gateway setup on Linux. Determine where network-creation options are parsed and how the gateway address is configured. Done means users can request --no-dad during IPv6 network creation and the resulting bridge gateway honors it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, linux
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100