IPv6 link-local scope only networks
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 2.2k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
Description
What I'd like to see is rather simple: the ability to create a network with the following characteristics:
- no IPv4
- no IPv6 address assignment
- just IPv6 link-local scope address
Before people ask, I need this for security reasons, for both ingress AND egress reasons. Obviously, at least one of the container attached to this network will have to attach to something else, but this is outside the scope of this request. It should also be on a different host so macvlan would probably be the choice, but that is also outside the scope of the request.
I did try with ipam-driver set to none or to null but that did not work ("none" not found and "null ipam driver does not handle IPv6 address pool pool requests").
It this possible?
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
No files, tests, or entry points are named. Start by reproducing the reported failures with ipam-driver set to none and null, then trace the Docker CLI network and IPAM handling for a network with no IPv4 assignment and only IPv6 link-local scope. Done means the requested network can be created with those properties and the behavior is covered by an appropriate test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- cli, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100