Jana Radhakrishnan 128ad3ca2d Fix bridge driver panic in CreateNetwork
Bridge driver panics in `CreateNetwork` if called without
a prior `Config` call. This causes issues in dnet which
tries to create network using default driver configuration.
It should be valid to call `CreateNetwork` without a prior
`Config` call in which case we need to assume default driver
config.

Fixed this by properly initializing the driver config pointer.
Also introduced a `configured` bool to make sure that still
`Config` is called exactly once for the instance of the bridge
driver.

Signed-off-by: Jana Radhakrishnan <mrjana@docker.com>
2015-09-04 11:19:52 -07:00
2015-09-03 13:36:08 +09:00
2015-08-27 11:19:02 -07:00
2015-08-27 11:19:02 -07:00
2015-08-27 11:19:02 -07:00
2015-08-14 18:01:15 -07:00
2015-08-16 09:38:17 -07:00
2015-06-18 15:06:24 -07:00
2015-08-26 11:30:17 +08:00
2015-09-02 08:48:45 -07:00
2015-08-16 09:38:17 -07:00
2015-09-01 21:48:14 -07:00
2015-06-18 15:06:24 -07:00
2015-08-27 11:19:02 -07:00
2015-08-27 11:19:02 -07:00
2015-06-19 18:55:26 -07:00
2015-09-01 21:48:14 -07:00
2015-02-19 17:20:15 -08:00
2015-09-01 21:48:09 -07:00
2015-08-27 11:19:02 -07:00
2015-08-27 11:19:02 -07:00
2015-06-09 15:06:02 -07:00
2015-09-01 21:48:14 -07:00
2015-08-27 11:19:02 -07:00
2015-09-01 21:48:09 -07:00

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.

S
Description
No description provided
Readme Apache-2.0 6.9 MiB
Languages
Go 96.3%
Shell 3.3%
Makefile 0.4%