84abbcefa8
The first issue is an ordering problem where sandbox attached version of endpoint object should be pushed to the watch database first so that any other create endpoint which is in progress can make use of it immediately to update the container hosts file. And only after that the current container should try to retrieve the service records from the service data base and upate it's hosts file. With the previous order there is a small time window, when another endpoint create will find this endpoint but it doesn't have the sandbox context while the svc record population from svc db has already happened so that container will totally miss to populate the service record of the newly created endpoint. The second issue is trying to rebuild the /etc/hosts file from scratch during endpoint join and this may sometimes happen after the service record add for another endpoint has happened on the container file. Obviously this rebuilding will wipe out that service record which was just added. Removed the rebuilding of /etc/hosts file during endpoint join. The initial population of /etc/hosts file should only happen during sandbox creation time. In the endpoint join just added the backward-compatible self ip -> hostname entry as just another record. Signed-off-by: Jana Radhakrishnan <mrjana@docker.com> |
||
---|---|---|
.. | ||
Godeps | ||
api | ||
bitseq | ||
client | ||
cmd | ||
config | ||
datastore | ||
docs | ||
driverapi | ||
drivers | ||
etchosts | ||
hostdiscovery | ||
idm | ||
ipam | ||
ipamapi | ||
ipams | ||
ipamutils | ||
iptables | ||
netlabel | ||
netutils | ||
ns | ||
options | ||
osl | ||
portallocator | ||
portmapper | ||
resolvconf | ||
test/integration | ||
testutils | ||
types | ||
.dockerignore | ||
.gitignore | ||
Dockerfile.build | ||
LICENSE | ||
MAINTAINERS | ||
Makefile | ||
README.md | ||
ROADMAP.md | ||
Vagrantfile | ||
circle.yml | ||
controller.go | ||
default_gateway.go | ||
default_gateway_freebsd.go | ||
default_gateway_linux.go | ||
default_gateway_windows.go | ||
drivers.go | ||
drivers_freebsd.go | ||
drivers_linux.go | ||
drivers_windows.go | ||
endpoint.go | ||
endpoint_cnt.go | ||
endpoint_info.go | ||
error.go | ||
errors_test.go | ||
libnetwork_internal_test.go | ||
libnetwork_test.go | ||
network.go | ||
sandbox.go | ||
sandbox_externalkey.go | ||
sandbox_store.go | ||
sandbox_test.go | ||
store.go | ||
store_test.go | ||
wrapmake.sh |
README.md
libnetwork - networking for containers
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.
// Select and configure the network driver
networkType := "bridge"
// Create a new controller instance
driverOptions := options.Generic{}
genericOption := make(map[string]interface{})
genericOption[netlabel.GenericData] = driverOptions
controller, err := libnetwork.New(config.OptionDriverConfig(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 container.
// NewSandbox accepts Variadic optional arguments which libnetwork can use.
sbx, err := controller.NewSandbox("container1",
libnetwork.OptionHostname("test"),
libnetwork.OptionDomainname("docker.io"))
// A sandbox can join the endpoint via the join api.
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.
Copyright and license
Code and documentation copyright 2015 Docker, inc. Code released under the Apache 2.0 license. Docs released under Creative commons.