moby--moby/libnetwork
Jana Radhakrishnan bcd996f4c3 Explicitly set namespace for all network operations
Make sure to always explicitly set namespace for all
kernel bound network operations irrespective of whether
the operation is performed in init namespace or a user
defined namespace. This already happens for user defined
netns. But doesn't happen for initial netns that libnetwork
runs in.

Signed-off-by: Jana Radhakrishnan <mrjana@docker.com>
2015-09-01 14:00:58 -07:00
..
Godeps Update vishvananda/netlink 2015-08-14 18:01:15 -07:00
api Explicitly set namespace for all network operations 2015-09-01 14:00:58 -07:00
bitseq idm and ipam to use bitseq atomic APIs 2015-08-16 09:38:17 -07:00
client Introduce Sandbox entity 2015-08-27 11:19:02 -07:00
cmd Introduce Sandbox entity 2015-08-27 11:19:02 -07:00
config Datastore handles creating objects atomically. 2015-06-25 10:53:48 -07:00
datastore Minor spelling fixes in documentation and code comments 2015-06-26 11:02:54 +01:00
docs Fixing Vagrant to use ubuntu 15.04 to get Experimental docker working again 2015-07-31 18:08:27 -07:00
driverapi Introduce Sandbox entity 2015-08-27 11:19:02 -07:00
drivers Explicitly set namespace for all network operations 2015-09-01 14:00:58 -07:00
etchosts Do not update /etc/hosts for empty endpoints 2015-06-24 12:09:44 -07:00
hostdiscovery Reworked endpoint store operation to address a few cases 2015-06-10 23:59:29 -07:00
idm idm and ipam to use bitseq atomic APIs 2015-08-16 09:38:17 -07:00
ipallocator Misc fixes to ipallocator & bridge driver about FixedCIDR 2015-07-27 18:12:33 -07:00
ipam Fix ip range allocation in ipam 2015-08-16 09:38:17 -07:00
iptables Seperates the driver-specific and network-specific iptable operations 2015-08-04 17:26:41 -04:00
netlabel Overlay driver 2015-06-18 15:06:24 -07:00
netutils Explicitly set namespace for all network operations 2015-09-01 14:00:58 -07:00
options Remove pkg directory 2015-05-16 16:12:13 -07:00
osl Explicitly set namespace for all network operations 2015-09-01 14:00:58 -07:00
portallocator Adding libnetwork support to publish on custom host port ranges. 2015-08-08 00:23:03 +00:00
portmapper Adding libnetwork support to publish on custom host port ranges. 2015-08-08 00:23:03 +00:00
resolvconf Add DNS 'options' support 2015-08-28 09:19:33 -07:00
test/integration
types Fix preferred ip allocation in ipam 2015-08-16 09:38:17 -07:00
.gitignore
LICENSE
MAINTAINERS Add Alessandro as a libnetwork maintainer 2015-05-29 18:46:33 +00:00
Makefile Use github golang tools mirror 2015-07-01 12:57:39 +08:00
README.md Introduce Sandbox entity 2015-08-27 11:19:02 -07:00
ROADMAP.md Update ROADMAP.md 2015-06-09 15:06:02 -07:00
circle.yml
controller.go Merge pull request #470 from WeiZhang555/master 2015-08-30 12:42:14 -07:00
drivers_freebsd.go Replacing isReservedNetwork with Driver capability 2015-06-10 23:59:38 -07:00
drivers_linux.go Overlay driver 2015-06-18 15:06:24 -07:00
drivers_windows.go Replacing isReservedNetwork with Driver capability 2015-06-10 23:59:38 -07:00
endpoint.go Introduce Sandbox entity 2015-08-27 11:19:02 -07:00
endpoint_info.go Introduce Sandbox entity 2015-08-27 11:19:02 -07:00
error.go Add LeaveAll support 2015-06-19 18:55:26 -07:00
errors_test.go Provide interface to categorize errors 2015-05-20 22:29:29 -07:00
libnetwork_internal_test.go Moved the TOML based Configuration to dnet 2015-06-12 12:46:12 -07:00
libnetwork_test.go Explicitly set namespace for all network operations 2015-09-01 14:00:58 -07:00
network.go Introduce Sandbox entity 2015-08-27 11:19:02 -07:00
sandbox.go Add DNS 'options' support 2015-08-28 09:19:33 -07:00
sandbox_test.go Explicitly set namespace for all network operations 2015-09-01 14:00:58 -07:00
store.go Introduce Sandbox entity 2015-08-27 11:19:02 -07:00

README.md

libnetwork - networking for containers

Circle CI Coverage Status GoDoc

Libnetwork provides a native Go implementation for connecting containers

The goal of libnetwork is to deliver a robust Container Network Model that provides a consistent programming interface and the required network abstractions for applications.

NOTE: libnetwork project is under heavy development and is not ready for general use.

Design

Please refer to the design for more information.

Using libnetwork

There are many networking solutions available to suit a broad range of use-cases. libnetwork uses a driver / plugin model to support all of these solutions while abstracting the complexity of the driver implementations by exposing a simple and consistent Network Model to users.

        // Create a new controller instance
        controller, err := libnetwork.New()
        if err != nil {
                return
        }

        // Select and configure the network driver
        networkType := "bridge"

        driverOptions := options.Generic{}
        genericOption := make(map[string]interface{})
        genericOption[netlabel.GenericData] = driverOptions
        err = controller.ConfigureNetworkDriver(networkType, genericOption)
        if err != nil {
                return
        }

        // Create a network for containers to join.
        // NewNetwork accepts Variadic optional arguments that libnetwork and Drivers can use.
        network, err := controller.NewNetwork(networkType, "network1")
        if err != nil {
                return
        }

        // For each new container: allocate IP and interfaces. The returned network
        // settings will be used for container infos (inspect and such), as well as
        // iptables rules for port publishing. This info is contained or accessible
        // from the returned endpoint.
        ep, err := network.CreateEndpoint("Endpoint1")
        if err != nil {
                return
        }

        // Create the sandbox for the containr.
        sbx, err := controller.NewSandbox("container1",
        libnetwork.OptionHostname("test"),
        libnetwork.OptionDomainname("docker.io"))
		
        // A sandbox can join the endpoint via the join api.
        // Join accepts Variadic arguments which libnetwork and Drivers can use.
        err = ep.Join(sbx)
        if err != nil {
                return
        }

		// libnetwork client can check the endpoint's operational data via the Info() API
		epInfo, err := ep.DriverInfo()
		mapData, ok := epInfo[netlabel.PortMap]
		if ok {
			portMapping, ok := mapData.([]types.PortBinding)
			if ok {
				fmt.Printf("Current port mapping for endpoint %s: %v", ep.Name(), portMapping)
			}
		}

Current Status

Please watch this space for updates on the progress.

Currently libnetwork is nothing more than an attempt to modularize the Docker platform's networking subsystem by moving it into libnetwork as a library.

Future

Please refer to roadmap for more information.

Contributing

Want to hack on libnetwork? Docker's contributions guidelines apply.

Code and documentation copyright 2015 Docker, inc. Code released under the Apache 2.0 license. Docs released under Creative commons.