docker network create options incorrectly documented

[aphofstede]

File: engine/reference/commandline/network_create.md

The options look slightly different for me on macOS. How to do --ip-masq now for example?

✗ docker network create --help

Usage:  docker network create [OPTIONS] NETWORK

Create a network

Options:
      --attachable           Enable manual container attachment
      --aux-address map      Auxiliary IPv4 or IPv6 addresses used by Network driver (default map[])
      --config-from string   The network from which to copy the configuration
      --config-only          Create a configuration only network
  -d, --driver string        Driver to manage the Network (default "bridge")
      --gateway strings      IPv4 or IPv6 Gateway for the master subnet
      --ingress              Create swarm routing-mesh network
      --internal             Restrict external access to the network
      --ip-range strings     Allocate container ip from a sub-range
      --ipam-driver string   IP Address Management Driver (default "default")
      --ipam-opt map         Set IPAM driver specific options (default map[])
      --ipv6                 Enable IPv6 networking
      --label list           Set metadata on a network
  -o, --opt map              Set driver specific options (default map[])
      --scope string         Control the network's scope
      --subnet strings       Subnet in CIDR format that represents a network segment

[thaJeztah]

Thanks for reporting; the --ip-masq option is a daemon configuration option (on dockerd, or set through the daemon.json configuration file; see the paragraph above that table; https://docs.docker.com/engine/reference/commandline/network_create/#bridge-driver-options

The following are those options and the equivalent docker daemon flags used for docker0 bridge:

I admit that it may be explained a bit more in-depth (and probably with links to (e.g.) https://docs.docker.com/engine/reference/commandline/dockerd/#miscellaneous-options

Contributions welcome!

[docker-robot]

There hasn't been any activity on this issue for a long time.
If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale comment.
If not, this issue will be closed in 14 days. This helps our maintainers focus on the active issues.

Prevent issues from auto-closing with a /lifecycle frozen comment.

/lifecycle stale

[docker-robot]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

/lifecycle locked

[thaJeztah]

Looks like this went stale, but was not yet addressed (or at least needs to be verified if it was addressed in other ways); let me re-open, and see if we can address this one.

/cc @dvdksn @robmry