Windows networking defaults and options are not documented
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 2.2k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
@PatrickLang commented on Tue May 23 2017
File: engine/reference/commandline/network_create.md, CC @mstanleyjones
There are some differences in naming between the Windows & Linux network types. We need some brief mention of this and the list of options needed to create networks on Windows. For example, someone may want to create a transparent network that uses a specific NIC, or set the IP address ranges used by the default nat network.
I'll file a work in progress PR for @Kallie-b and @jmesser81 to collaborate on.
@PatrickLang commented on Wed May 24 2017
Discussion is happening on the PR ^^
@joaofnfernandes commented on Tue Aug 22 2017
These PRs^^ never made it, so maybe someone can use them as a starting point to document address this issue moby/moby#33659
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 with engine/reference/commandline/network_create.md and use the referenced moby/moby#33659 as background for the Windows networking details. Document the Windows and Linux network-type naming differences, transparent-network NIC selection, and address-range options for the default nat network; the work is done when these defaults and options are clearly covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- cli, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100