Feature Request: Creation of anonymous networks (name should not be required)

[hossman]

Background on Current State of "Names" in Docker Usage
from a lay-users perspective

• "Names" (ie: tags) are not required when creating/using a docker image
  • docker build does not require the --tag option
  • docker build supports an --iidfile <string> option to record the (auto-generated) unique "Image ID" of the image created for later reference
  • All other docker commands that need to refer to an image can be given either a tag or an "Image ID"
• Names are not required when running/using a docker container
  • The --name <string> option is optional when using docker run - if it is not specified a random name is chosen for convenience
  • docker run supports a --cidfile <string> option to record the (auto-generated) unique "Container ID" of the container created for later reference
  • All other docker commands that need to refer to a container can be given either a name or a "Container ID"
• Names ARE required for creating docker networks but not when using to them
  • docker network create REQUIRES a (unique) name be specified in the command line
  • Even though every docker network has a unique (auto-generated) "Network ID", docker network create does NOT offer a --nidfile <string> command line option to capture this ID when the network is created
  • All other docker commands that need to refer to a network CAN be given either a name or a "Network ID" (ie: in the --network <string> option of other commands, or future docker network ... commands)

Feature Request: Allow Creation of "Anonymous" Networks

• It should be possible to create a network with out needing to specify a name
  • This would be particularly useful for automated scripts / tests that should not have any "names" hardcoded in them, and are specifically creating networks for the point of isolation
• docker network create should be changed to make the "NAME" argument optional
• docker network create should support a new --nidfile <string> option