0.3 Project Page

Tracking

• libnetwork 0.3 Milestone

Features

The following features will be shipped in the Docker 1.7 release

• Network will become a first class object and users can create multiple networks
• Replace docker networking codebase with libnetwork

Experimental Features

The following are experimental features that are NOT part of the 1.7 release. But are developed in the same time-frame in the master branch.

• Provide support for networking plugins from ecosystem partners
• The overlay driver may be used to span networks across more than one Engine

Requirements

Functional

• A Docker Engine MAY have more than one Network
• Each Network MAY be backed by a different driver
• Containers MAY be attached to multiple networks
• A network MAY be identified by an auto-generated or user-specified name
• Each network MUST be given a UUID when it is created. This can be used interchangeably with the name.
• Containers CANNOT have more than one endpoint on a single network. Attempting to do this will result in an error.
• Users SHOULD be able to attach/detach containers to/from networks after the container has been created
• The network MUST be available before the container entry point is run
• Drivers MUST be able to offer defaults for the default gateway, search domain, name server etc...

Non-Functional

• Changes to the Docker CLI will be clearly documented including any constraints
• User experience will be preserved for existing functionality (e.g daemon flags) only on the "bridge" network
• New features do not need to be backwards compatible