Docker Cookbook

90 | Chapter 3: Docker Networking

---

$ docker run -it --rm --name foobar --net=none ubuntu:14.04 bash
root@8fda6e33eb88:/#
In a different shell on your Docker host, use pipework to create a network interface
(you will need to install pipework) in your 
foobar
container:
$ sudo su
# ./pipework ovs-cookbook foobar 10.0.0.10/24@10.0.0.1
# ovs-vsctl list-ports ovs-cookbook
veth1pl31350
Your bridge will also have been assigned the IP address 10.0.0.1 by pipework:
$ ifconfig
ovs-cookbook Link encap:Ethernet HWaddr 36:b1:d3:e5:fc:44
inet addr:10.0.0.1 Bcast:0.0.0.0 Mask:255.255.255.0
...
Your container will now have a network interface:
root@8fda6e33eb88:/# ifconfig
eth1 Link encap:Ethernet HWaddr 52:fe:9f:78:b7:fc
inet addr:10.0.0.10 Bcast:0.0.0.0 Mask:255.255.255.04
....
You could also create the interface by hand by using 
ip netns
, as you did in the dis‐
cussion section of 
Recipe 3.7
.
See Also
• The Open vSwitch 
website
3.10 Building a GRE Tunnel Between Docker Hosts
Problem
You need to have network connectivity between containers on multiple hosts using
their own IP addresses.
Solution
Several recipes (see 
Recipe 3.11
 and 
Recipe 3.13
) show solutions that can be used in
production deployment. This recipe presents a step-by-step example of how to set up
multihost networking, to help you build a solid foundation for understanding Docker
networking.
To build a toy setup that provides network connectivity between containers on multi‐
ple hosts, build a Generic Routing Encapsulation (GRE) tunnel to encapsulate IPv4
traffic and provide a route between containers using their private addresses. To show‐