@@ -37,6 +37,7 @@ Let's start with listing the images you have locally on our host. You can

 do this using the `docker images` command like so:

     $ docker images

+

     REPOSITORY          TAG                 IMAGE ID            CREATED             SIZE

     ubuntu              14.04               1d073211c498        3 days ago          187.9 MB

     busybox             latest              2c5ac3f849df        5 days ago          1.113 MB

@@ -87,6 +88,7 @@ can download it using the `docker pull` command. Suppose you'd like to

 download the `centos` image.

     $ docker pull centos

+

     Pulling repository centos

     b7de3133ff98: Pulling dependent layers

     5cc9e91966f7: Pulling fs layer

@@ -101,6 +103,7 @@ can run a container from this image and you won't have to wait to

 download the image.

     $ docker run -t -i centos /bin/bash

+

     bash-4.1#

 ## Finding images

@@ -158,6 +161,7 @@ You've identified a suitable image, `training/sinatra`, and now you can download

 The team can now use this image by running their own containers.

     $ docker run -t -i training/sinatra /bin/bash

+

     root@a8cb6ce02d85:/#

 ## Creating our own images

@@ -176,6 +180,7 @@ To update an image you first need to create a container from the image

 you'd like to update.

     $ docker run -t -i training/sinatra /bin/bash

+

     root@0b2616b0e5a8:/#

 > **Note:**

@@ -195,6 +200,7 @@ command.

     $ docker commit -m "Added json gem" -a "Kate Smith" \

     0b2616b0e5a8 ouruser/sinatra:v2

+

     4f177bd27a9ff0f6dc2a830403925b5360bfe0b93d476f7fc3231110e7f71b1c

 Here you've used the `docker commit` command. You've specified two flags: `-m`

@@ -217,6 +223,7 @@ You can then look at our new `ouruser/sinatra` image using the `docker images`

 command.

     $ docker images

+

     REPOSITORY          TAG     IMAGE ID       CREATED       SIZE

     training/sinatra    latest  5bc342fa0b91   10 hours ago  446.7 MB

     ouruser/sinatra     v2      3c59e02ddd1a   10 hours ago  446.7 MB

@@ -225,6 +232,7 @@ command.

 To use our new image to create a container you can then:

     $ docker run -t -i ouruser/sinatra:v2 /bin/bash

+

     root@78e82f680994:/#

 ### Building an image from a `Dockerfile`

@@ -240,7 +248,9 @@ tell Docker how to build our image.

 First, create a directory and a `Dockerfile`.

     $ mkdir sinatra

+

     $ cd sinatra

+

     $ touch Dockerfile

 If you are using Docker Machine on Windows, you may access your host

@@ -275,6 +285,7 @@ Sinatra gem.

 Now let's take our `Dockerfile` and use the `docker build` command to build an image.

     $ docker build -t ouruser/sinatra:v2 .

+

     Sending build context to Docker daemon 2.048 kB

     Sending build context to Docker daemon

     Step 1 : FROM ubuntu:14.04

@@ -469,6 +480,7 @@ containers will get removed to clean things up.

 You can then create a container from our new image.

     $ docker run -t -i ouruser/sinatra:v2 /bin/bash

+

     root@8196968dac35:/#

 > **Note:**

@@ -495,6 +507,7 @@ user name, the repository name and the new tag.

 Now, see your new tag using the `docker images` command.

     $ docker images ouruser/sinatra

+

     REPOSITORY          TAG     IMAGE ID      CREATED        SIZE

     ouruser/sinatra     latest  5db5f8471261  11 hours ago   446.7 MB

     ouruser/sinatra     devel   5db5f8471261  11 hours ago   446.7 MB

@@ -508,6 +521,7 @@ unchanged, the digest value is predictable. To list image digest values, use

 the `--digests` flag:

     $ docker images --digests | head

+

     REPOSITORY        TAG      DIGEST                                                                     IMAGE ID      CREATED       SIZE

     ouruser/sinatra   latest   sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf    5db5f8471261  11 hours ago  446.7 MB

@@ -527,6 +541,7 @@ allows you to share it with others, either publicly, or push it into [a

 private repository](https://hub.docker.com/account/billing-plans/).

     $ docker push ouruser/sinatra

+

     The push refers to a repository [ouruser/sinatra] (len: 1)

     Sending image list

     Pushing repository ouruser/sinatra (3 tags)

@@ -540,6 +555,7 @@ containers](usingdocker.md) using the `docker rmi` command.

 Delete the `training/sinatra` image as you don't need it anymore.

     $ docker rmi training/sinatra

+

     Untagged: training/sinatra:latest

     Deleted: 5bc342fa0b91cabf65246837015197eecfa24b2213ed6a51a8974ae250fedd8d

     Deleted: ed0fffdcdae5eb2c3a55549857a8be7fc8bc4241fb19ad714364cbfd7a56b22f

@@ -30,6 +30,7 @@ Running an application inside a container takes a single command: `docker run`.

 Let's run a hello world container.

     $ docker run ubuntu /bin/echo 'Hello world'

+

     Hello world

 You just launched your first container!

@@ -59,6 +60,7 @@ the container stops once the command is executed.

 Let's specify a new command to run in the container.

     $ docker run -t -i ubuntu /bin/bash

+

     root@af8bae53bdd3:/#

 In this example:

@@ -78,8 +80,11 @@ command prompt inside it:

 Let's try running some commands inside the container:

     root@af8bae53bdd3:/# pwd

+

     /

+

     root@af8bae53bdd3:/# ls

+

     bin boot dev etc home lib lib64 media mnt opt proc root run sbin srv sys tmp usr var

 In this example:

@@ -100,6 +105,7 @@ finished, the container stops.

 Let's create a container that runs as a daemon.

     $ docker run -d ubuntu /bin/sh -c "while true; do echo hello world; sleep 1; done"

+

     1e5535038e285177d5214659a068137486f96ee5c2e85a4ac52dc83f2ebe4147

 In this example:

@@ -132,6 +138,7 @@ The `docker ps` command queries the Docker daemon for information about all the

 about.

     $ docker ps

+

     CONTAINER ID  IMAGE         COMMAND               CREATED        STATUS       PORTS NAMES

     1e5535038e28  ubuntu  /bin/sh -c 'while tr  2 minutes ago  Up 1 minute        insane_babbage

@@ -154,6 +161,7 @@ command.

 Let's use the container name `insane_babbage`.

     $ docker logs insane_babbage

+

     hello world

     hello world

     hello world

@@ -169,6 +177,7 @@ Dockerized application!

 Next, run the `docker stop` command to stop our detached container.

     $ docker stop insane_babbage

+

     insane_babbage

 The `docker stop` command tells Docker to politely stop the running

@@ -177,6 +186,7 @@ container and returns the name of the container it stopped.

 Let's check it worked with the `docker ps` command.

     $ docker ps

+

     CONTAINER ID  IMAGE         COMMAND               CREATED        STATUS       PORTS NAMES

 Excellent. Our container is stopped.

@@ -57,6 +57,7 @@ interface or by using the command line interface. Searching can find images by i

 name, user name, or description:

     $ docker search centos

+

     NAME           DESCRIPTION                                     STARS     OFFICIAL   AUTOMATED

     centos         The official build of CentOS                    1223      [OK]

     tianon/centos  CentOS 5 and 6, created using rinse instea...   33

@@ -72,6 +73,7 @@ a user's repository from the image name.

 Once you've found the image you want, you can download it with `docker pull <imagename>`:

     $ docker pull centos

+

     Using default tag: latest

     latest: Pulling from library/centos

     f1b10cd84249: Pull complete

@@ -204,6 +204,7 @@ using the `docker volume create` command.

 ```bash

 $ docker volume create -d flocker --name my-named-volume -o size=20GB

+

 $ docker run -d -P \

   -v my-named-volume:/opt/webapp \

   --name web training/webapp python app.py

@@ -41,26 +41,28 @@ You name your container by using the `--name` flag, for example launch a new con

 Use the `docker ps` command to check the name:

     $ docker ps -l

+

     CONTAINER ID  IMAGE                  COMMAND        CREATED       STATUS       PORTS                    NAMES

     aed84ee21bde  training/webapp:latest python app.py  12 hours ago  Up 2 seconds 0.0.0.0:49154->5000/tcp  web

 You can also use `docker inspect` with the container's name.

     $ docker inspect web

+

     [

-    {

-        "Id": "3ce51710b34f5d6da95e0a340d32aa2e6cf64857fb8cdb2a6c38f7c56f448143",

-        "Created": "2015-10-25T22:44:17.854367116Z",

-        "Path": "python",

-        "Args": [

-            "app.py"

-        ],

-        "State": {

-            "Status": "running",

-            "Running": true,

-            "Paused": false,

-            "Restarting": false,

-            "OOMKilled": false,

+       {

+           "Id": "3ce51710b34f5d6da95e0a340d32aa2e6cf64857fb8cdb2a6c38f7c56f448143",

+           "Created": "2015-10-25T22:44:17.854367116Z",

+           "Path": "python",

+           "Args": [

+               "app.py"

+           ],

+           "State": {

+               "Status": "running",

+               "Running": true,

+               "Paused": false,

+               "Restarting": false,

+               "OOMKilled": false,

       ...

 Container names must be unique. That means you can only call one container

@@ -68,8 +70,11 @@ Container names must be unique. That means you can only call one container

 (with `docker rm`) before you can reuse the name with a new container. Go ahead and stop and remove your old `web` container.

     $ docker stop web

+

     web

+

     $ docker rm web

+

     web

@@ -83,6 +88,7 @@ that you can create your own drivers but that is an advanced task.

 Every installation of the Docker Engine automatically includes three default networks. You can list them:

     $ docker network ls

+

     NETWORK ID          NAME                DRIVER

     18a2866682b8        none                null                

     c288470c46f6        host                host                

@@ -91,12 +97,14 @@ Every installation of the Docker Engine automatically includes three default net

 The network named `bridge` is a special network. Unless you tell it otherwise, Docker always launches your containers in this network. Try this now:

     $ docker run -itd --name=networktest ubuntu

+

     74695c9cea6d9810718fddadc01a727a5dd3ce6a69d09752239736c030599741

 Inspecting the network is an easy way to find out the container's IP address.

 ```bash

 $ docker network inspect bridge

+

 [

     {

         "Name": "bridge",

@@ -153,6 +161,7 @@ Docker Engine natively supports both bridge networks and overlay networks. A bri

 The `-d` flag tells Docker to use the `bridge` driver for the new network. You could have left this flag off as `bridge` is the default value for this flag. Go ahead and list the networks on your machine:

     $ docker network ls

+

     NETWORK ID          NAME                DRIVER

     7b369448dccb        bridge              bridge              

     615d565d498c        my-bridge-network   bridge              

@@ -162,6 +171,7 @@ The `-d` flag tells Docker to use the `bridge` driver for the new network. You c

 If you inspect the network, you'll find that it has nothing in it.

     $ docker network inspect my-bridge-network

+

     [

         {

             "Name": "my-bridge-network",

@@ -196,6 +206,7 @@ If you inspect your `my-bridge-network` you'll see it has a container attached.

 You can also inspect your container to see where it is connected:

     $ docker inspect --format='{{json .NetworkSettings.Networks}}'  db

+

     {"my-bridge-network":{"NetworkID":"7d86d31b1478e7cca9ebed7e73aa0fdeec46c5ca29497431d3007d2d9e15ed99",

     "EndpointID":"508b170d56b2ac9e4ef86694b0a76a22dd3df1983404f7321da5649645bf7043","Gateway":"172.18.0.1","IPAddress":"172.18.0.2","IPPrefixLen":16,"IPv6Gateway":"","GlobalIPv6Address":"","GlobalIPv6PrefixLen":0,"MacAddress":"02:42:ac:11:00:02"}}

@@ -206,17 +217,20 @@ Now, go ahead and start your by now familiar web application. This time leave of

 Which network is your `web` application running under? Inspect the application and you'll find it is running in the default `bridge` network.

     $ docker inspect --format='{{json .NetworkSettings.Networks}}'  web

+

     {"bridge":{"NetworkID":"7ea29fc1412292a2d7bba362f9253545fecdfa8ce9a6e37dd10ba8bee7129812",

     "EndpointID":"508b170d56b2ac9e4ef86694b0a76a22dd3df1983404f7321da5649645bf7043","Gateway":"172.17.0.1","IPAddress":"172.17.0.2","IPPrefixLen":16,"IPv6Gateway":"","GlobalIPv6Address":"","GlobalIPv6PrefixLen":0,"MacAddress":"02:42:ac:11:00:02"}}

 Then, get the IP address of your `web`

     $ docker inspect --format='{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' web

+

     172.17.0.2

 Now, open a shell to your running `db` container:

     $ docker exec -it db bash

+

     root@a205f0dd33b2:/# ping 172.17.0.2

     ping 172.17.0.2

     PING 172.17.0.2 (172.17.0.2) 56(84) bytes of data.

@@ -233,6 +247,7 @@ Docker networking allows you to attach a container to as many networks as you li

 Open a shell into the `db` application again and try the ping command. This time just use the container name `web` rather than the IP Address.

     $ docker exec -it db bash

+

     root@a205f0dd33b2:/# ping web

     PING web (172.18.0.3) 56(84) bytes of data.

     64 bytes from web (172.18.0.3): icmp_seq=1 ttl=64 time=0.095 ms

@@ -115,6 +115,7 @@ Lastly, you've specified a command for our container to run: `python app.py`. Th

 Now you can see your running container using the `docker ps` command.

     $ docker ps -l

+

     CONTAINER ID  IMAGE                   COMMAND       CREATED        STATUS        PORTS                    NAMES

     bc533791f3f5  training/webapp:latest  python app.py 5 seconds ago  Up 2 seconds  0.0.0.0:49155->5000/tcp  nostalgic_morse

@@ -186,6 +187,7 @@ specify the ID or name of our container and then the port for which we need the

 corresponding public-facing port.

     $ docker port nostalgic_morse 5000

+

     0.0.0.0:49155

 In this case you've looked up what port is mapped externally to port 5000 inside

@@ -197,6 +199,7 @@ You can also find out a bit more about what's happening with our application and

 use another of the commands you've learned, `docker logs`.

     $ docker logs -f nostalgic_morse

+

     * Running on http://0.0.0.0:5000/

     10.0.2.2 - - [23/May/2014 20:16:31] "GET / HTTP/1.1" 200 -

     10.0.2.2 - - [23/May/2014 20:16:31] "GET /favicon.ico HTTP/1.1" 404 -

@@ -212,6 +215,7 @@ In addition to the container's logs we can also examine the processes

 running inside it using the `docker top` command.

     $ docker top nostalgic_morse

+

     PID                 USER                COMMAND

     854                 root                python app.py

@@ -245,6 +249,7 @@ We can also narrow down the information we want to return by requesting a

 specific element, for example to return the container's IP address we would:

     $ docker inspect -f '{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' nostalgic_morse

+

     172.17.0.5

 ## Stopping our web application container

@@ -253,6 +258,7 @@ Okay you've seen web application working. Now you can stop it using the

 `docker stop` command and the name of our container: `nostalgic_morse`.

     $ docker stop nostalgic_morse

+

     nostalgic_morse

 We can now use the `docker ps` command to check if the container has

@@ -268,6 +274,7 @@ can create a new container or restart the old one. Look at

 starting your previous container back up.

     $ docker start nostalgic_morse

+

     nostalgic_morse

 Now quickly run `docker ps -l` again to see the running container is

@@ -284,6 +291,7 @@ Your colleague has let you know that they've now finished with the container

 and won't need it again. Now, you can remove it using the `docker rm` command.

     $ docker rm nostalgic_morse

+

     Error: Impossible to remove a running container, please stop it first or use -f

     2014/05/24 08:12:56 Error: failed to remove one or more containers

@@ -292,8 +300,11 @@ you from accidentally removing a running container you might need. You can try

 this again by stopping the container first.

     $ docker stop nostalgic_morse

+

     nostalgic_morse

+

     $ docker rm nostalgic_morse

+

     nostalgic_morse

 And now our container is stopped and deleted.

@@ -29,8 +29,11 @@ It can be as simple as this to create an Ubuntu base image:

     $ sudo debootstrap raring raring > /dev/null

     $ sudo tar -C raring -c . | docker import - raring

+

     a29c15f1bf7a

+

     $ docker run raring cat /etc/lsb-release

+

     DISTRIB_ID=Ubuntu

     DISTRIB_RELEASE=13.04

     DISTRIB_CODENAME=raring

@@ -192,6 +192,7 @@ on how to query labels set on a container.

 These labels appear as part of the `docker info` output for the daemon:

     $ docker -D info

+

     Containers: 12

      Running: 5

      Paused: 2

@@ -23,6 +23,7 @@ when it starts:

 ```

 $ sudo iptables -t nat -L -n

+

 ...

 Chain POSTROUTING (policy ACCEPT)

 target     prot opt source               destination

@@ -56,6 +57,7 @@ network stack by examining your NAT tables.

 # is finished setting up a -P forward:

 $ iptables -t nat -L -n

+

 ...

 Chain DOCKER (2 references)

 target     prot opt source               destination

@@ -27,8 +27,11 @@ stopping the service and removing the interface:

 # Stopping Docker and removing docker0

 $ sudo service docker stop

+

 $ sudo ip link set dev docker0 down

+

 $ sudo brctl delbr docker0

+

 $ sudo iptables -t nat -F POSTROUTING

 ```

@@ -41,12 +44,15 @@ customize `docker0`, but it will be enough to illustrate the technique.

 # Create our own bridge

 $ sudo brctl addbr bridge0

+

 $ sudo ip addr add 192.168.5.1/24 dev bridge0

+

 $ sudo ip link set dev bridge0 up

 # Confirming that our bridge is up and running

 $ ip addr show bridge0

+

 4: bridge0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state UP group default

     link/ether 66:38:d0:0d:76:18 brd ff:ff:ff:ff:ff:ff

     inet 192.168.5.1/24 scope global bridge0

@@ -55,11 +61,13 @@ $ ip addr show bridge0

 # Tell Docker about it and restart (on Ubuntu)

 $ echo 'DOCKER_OPTS="-b=bridge0"' >> /etc/default/docker

+

 $ sudo service docker start

 # Confirming new outgoing NAT masquerade is set up

 $ sudo iptables -t nat -L -n

+

 ...

 Chain POSTROUTING (policy ACCEPT)

 target     prot opt source               destination

@@ -20,6 +20,7 @@ How can Docker supply each container with a hostname and DNS configuration, with

 ```

 $$ mount

+

 ...

 /dev/disk/by-uuid/1fec...ebdf on /etc/hostname type ext4 ...

 /dev/disk/by-uuid/1fec...ebdf on /etc/hosts type ext4 ...

@@ -31,9 +31,13 @@ set `--ip-forward=false` and your system's kernel has it enabled, the

 or to turn it on manually:

 ```

   $ sysctl net.ipv4.conf.all.forwarding

+

   net.ipv4.conf.all.forwarding = 0

+

   $ sysctl net.ipv4.conf.all.forwarding=1

+

   $ sysctl net.ipv4.conf.all.forwarding

+

   net.ipv4.conf.all.forwarding = 1

 ```

@@ -98,6 +102,7 @@ You can run the `iptables` command on your Docker host to see whether the `FORWA

 # When --icc=false, you should see a DROP rule:

 $ sudo iptables -L -n

+

 ...

 Chain FORWARD (policy ACCEPT)

 target     prot opt source               destination

@@ -110,6 +115,7 @@ DROP       all  --  0.0.0.0/0            0.0.0.0/0

 # the subsequent DROP policy for all other packets:

 $ sudo iptables -L -n

+

 ...

 Chain FORWARD (policy ACCEPT)

 target     prot opt source               destination

@@ -30,6 +30,7 @@ Once you have one or more containers up and running, you can confirm that Docker

 # Display bridge info

 $ sudo brctl show

+

 bridge name     bridge id               STP enabled     interfaces

 docker0         8000.3a1d7362b4ee       no              veth65f9

                                                         vethdda6

@@ -45,6 +46,7 @@ Finally, the `docker0` Ethernet bridge settings are used every time you create a

 $ docker run -i -t --rm base /bin/bash

 $$ ip addr show eth0

+

 24: eth0: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000

     link/ether 32:6f:e0:35:57:91 brd ff:ff:ff:ff:ff:ff

     inet 172.17.0.3/16 scope global eth0

@@ -53,6 +55,7 @@ $$ ip addr show eth0

        valid_lft forever preferred_lft forever

 $$ ip route

+

 default via 172.17.42.1 dev eth0

 172.17.0.0/16 dev eth0  proto kernel  scope link  src 172.17.0.3

@@ -43,6 +43,7 @@ range* on your Docker host. Next, when `docker ps` was run, you saw that port

 5000 in the container was bound to port 49155 on the host.

     $ docker ps nostalgic_morse

+

     CONTAINER ID  IMAGE                   COMMAND       CREATED        STATUS        PORTS                    NAMES

     bc533791f3f5  training/webapp:latest  python app.py 5 seconds ago  Up 2 seconds  0.0.0.0:49155->5000/tcp  nostalgic_morse

@@ -88,6 +89,7 @@ configurations. For example, if you've bound the container port to the

 `localhost` on the host machine, then the `docker port` output will reflect that.

     $ docker port nostalgic_morse 5000

+

     127.0.0.1:49155

 > **Note:**

@@ -132,6 +134,7 @@ name the container `web`. You can see the container's name using the

 `docker ps` command.

     $ docker ps -l

+

     CONTAINER ID  IMAGE                  COMMAND        CREATED       STATUS       PORTS                    NAMES

     aed84ee21bde  training/webapp:latest python app.py  12 hours ago  Up 2 seconds 0.0.0.0:49154->5000/tcp  web

@@ -187,6 +190,7 @@ example as:

 Next, inspect your linked containers with `docker inspect`:

     $ docker inspect -f "{{ .HostConfig.Links }}" web

+

     [/db:/web/db]

 You can see that the `web` container is now linked to the `db` container

@@ -273,6 +277,7 @@ command to list the specified container's environment variables.

 ```

     $ docker run --rm --name web2 --link db:db training/webapp env

+

     . . .

     DB_NAME=/web2/db

     DB_PORT=tcp://172.17.0.5:5432

@@ -310,7 +315,9 @@ source container to the `/etc/hosts` file. Here's an entry for the `web`

 container:

     $ docker run -t -i --rm --link db:webdb training/webapp /bin/bash

+

     root@aed84ee21bde:/opt/webapp# cat /etc/hosts

+

     172.17.0.7  aed84ee21bde

     . . .

     172.17.0.5  webdb 6e5cdeb2d300 db

@@ -324,7 +331,9 @@ also be added in `/etc/hosts` for the linked container's IP address. You can pin

 that host now via any of these entries:

     root@aed84ee21bde:/opt/webapp# apt-get install -yqq inetutils-ping

+

     root@aed84ee21bde:/opt/webapp# ping webdb

+

     PING webdb (172.17.0.5): 48 data bytes

     56 bytes from 172.17.0.5: icmp_seq=0 ttl=64 time=0.267 ms

     56 bytes from 172.17.0.5: icmp_seq=1 ttl=64 time=0.250 ms

@@ -348,9 +357,13 @@ will be automatically updated with the source container's new IP address,

 allowing linked communication to continue.

     $ docker restart db

+

     db

+

     $ docker run -t -i --rm --link db:db training/webapp /bin/bash

+

     root@aed84ee21bde:/opt/webapp# cat /etc/hosts

+

     172.17.0.7  aed84ee21bde

     . . .

     172.17.0.9  db

@@ -48,7 +48,9 @@ starting dockerd with `--ip-forward=false`):

 ```

 $ ip -6 route add 2001:db8:1::/64 dev docker0

+

 $ sysctl net.ipv6.conf.default.forwarding=1

+

 $ sysctl net.ipv6.conf.all.forwarding=1

 ```

@@ -113,6 +115,7 @@ configure the IPv6 addresses `2001:db8::c000` to `2001:db8::c00f`:

 ```

 $ ip -6 addr show

+

 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536

     inet6 ::1/128 scope host

        valid_lft forever preferred_lft forever

@@ -165,6 +168,7 @@ device to the container network:

 ```

 $ ip -6 route show

+

 2001:db8::c008/125 dev docker0  metric 1

 2001:db8::/64 dev eth0  proto kernel  metric 256

 ```

@@ -29,6 +29,7 @@ these networks using the `docker network ls` command:

 ```

 $ docker network ls

+

 NETWORK ID          NAME                DRIVER

 7fca4eb8c647        bridge              bridge

 9f904ee27bf5        none                null

@@ -47,6 +48,7 @@ the `ifconfig` command on the host.

 ```

 $ ifconfig

+

 docker0   Link encap:Ethernet  HWaddr 02:42:47:bc:3a:eb  

           inet addr:172.17.0.1  Bcast:0.0.0.0  Mask:255.255.0.0

           inet6 addr: fe80::42:47ff:febc:3aeb/64 Scope:Link

@@ -100,6 +102,7 @@ command returns information about a network:

 ```

 $ docker network inspect bridge

+

 [

    {

        "Name": "bridge",

@@ -132,9 +135,11 @@ The `docker run` command automatically adds new containers to this network.

 ```

 $ docker run -itd --name=container1 busybox

+

 3386a527aa08b37ea9232cbcace2d2458d49f44bb05a6b775fba7ddd40d8f92c

 $ docker run -itd --name=container2 busybox

+

 94447ca479852d29aeddca75c28f7104df3c3196d7b6d83061879e339946805c

 ```

@@ -142,6 +147,7 @@ Inspecting the `bridge` network again after starting two containers shows both n

 ```

 $ docker network inspect bridge

+

 {[

     {

         "Name": "bridge",

@@ -215,6 +221,7 @@ Then use `ping` for about 3 seconds to test the connectivity of the containers o

 ```

 root@0cb243cd1293:/# ping -w3 172.17.0.3

+

 PING 172.17.0.3 (172.17.0.3): 56 data bytes

 64 bytes from 172.17.0.3: seq=0 ttl=64 time=0.096 ms

 64 bytes from 172.17.0.3: seq=1 ttl=64 time=0.080 ms

@@ -229,6 +236,7 @@ Finally, use the `cat` command to check the `container1` network configuration:

 ```

 root@0cb243cd1293:/# cat /etc/hosts

+

 172.17.0.2	3386a527aa08

 127.0.0.1	localhost

 ::1	localhost ip6-localhost ip6-loopback

@@ -243,6 +251,7 @@ To detach from a `container1` and leave it running use `CTRL-p CTRL-q`.Then, att

 $ docker attach container2

 root@0cb243cd1293:/# ifconfig

+

 eth0      Link encap:Ethernet  HWaddr 02:42:AC:11:00:03  

           inet addr:172.17.0.3  Bcast:0.0.0.0  Mask:255.255.0.0

           inet6 addr: fe80::42:acff:fe11:3/64 Scope:Link

@@ -262,6 +271,7 @@ lo        Link encap:Local Loopback

           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

 root@0cb243cd1293:/# ping -w3 172.17.0.2

+

 PING 172.17.0.2 (172.17.0.2): 56 data bytes

 64 bytes from 172.17.0.2: seq=0 ttl=64 time=0.067 ms

 64 bytes from 172.17.0.2: seq=1 ttl=64 time=0.075 ms

@@ -311,6 +321,7 @@ $ docker network create --driver bridge isolated_nw

 1196a4c5af43a21ae38ef34515b6af19236a3fc48122cf585e3f3054d509679b

 $ docker network inspect isolated_nw

+

 [

     {

         "Name": "isolated_nw",

@@ -332,6 +343,7 @@ $ docker network inspect isolated_nw

 ]

 $ docker network ls

+

 NETWORK ID          NAME                DRIVER

 9f904ee27bf5        none                null

 cf03ee007fb4        host                host

@@ -344,6 +356,7 @@ After you create the network, you can launch containers on it using  the `docker

 ```

 $ docker run --net=isolated_nw -itd --name=container3 busybox

+

 8c1a0a5be480921d669a073393ade66a3fc49933f08bcc5515b37b8144f6d47c

 $ docker network inspect isolated_nw

@@ -73,6 +73,7 @@ key-value stores. This example uses Consul.

 5. Run the `docker ps` command to see the `consul` container.

 		$ docker ps

+

 		CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS                                                                            NAMES

 		4d51392253b3        progrium/consul     "/bin/start -server -"   25 minutes ago      Up 25 minutes       53/tcp, 53/udp, 8300-8302/tcp, 0.0.0.0:8500->8500/tcp, 8400/tcp, 8301-8302/udp   admiring_panini

@@ -111,6 +112,7 @@ that machine options that are needed by the `overlay` network driver.

 3. List your machines to confirm they are all up and running.

 		$ docker-machine ls

+

 		NAME         ACTIVE   DRIVER       STATE     URL                         SWARM

 		default      -        virtualbox   Running   tcp://192.168.99.100:2376

 		mh-keystore  *        virtualbox   Running   tcp://192.168.99.103:2376

@@ -134,6 +136,7 @@ To create an overlay network

 2. Use the `docker info` command to view the Swarm.

 		$ docker info

+

 		Containers: 3

 		Images: 2

 		Role: primary

@@ -171,6 +174,7 @@ To create an overlay network

 4. Check that the network is running:

 		$ docker network ls

+

 		NETWORK ID          NAME                DRIVER

 		412c2496d0eb        mhs-demo1/host      host

 		dd51763e6dd2        mhs-demo0/bridge    bridge

@@ -187,14 +191,19 @@ To create an overlay network

 5. Switch to each Swarm agent in turn and list the networks.

 		$ eval $(docker-machine env mhs-demo0)

+

 		$ docker network ls

+

 		NETWORK ID          NAME                DRIVER

 		6b07d0be843f        my-net              overlay

 		dd51763e6dd2        bridge              bridge

 		b4234109bd9b        none                null

 		1aeead6dd890        host                host

+

 		$ eval $(docker-machine env mhs-demo1)

+

 		$ docker network ls

+

 		NETWORK ID          NAME                DRIVER

 		d0bb78cbe7bd        bridge              bridge

 		1c0eb8f69ebb        none                null

@@ -219,6 +228,7 @@ Once your network is created, you can start a container on any of the hosts and

 4. Run a BusyBox instance on the `mhs-demo1` instance and get the contents of the Nginx server's home page.

 		$ docker run -it --rm --net=my-net --env="constraint:node==mhs-demo1" busybox wget -O- http://web

+

 		Unable to find image 'busybox:latest' locally

 		latest: Pulling from library/busybox

 		ab2b8a86ca6c: Pull complete

@@ -268,6 +278,7 @@ to have external connectivity outside of their cluster.

 2. View the `docker_gwbridge` network, by listing the networks.

 		$ docker network ls

+

 		NETWORK ID          NAME                DRIVER

 		6b07d0be843f        my-net              overlay

 		dd51763e6dd2        bridge              bridge

@@ -278,7 +289,9 @@ to have external connectivity outside of their cluster.

 3. Repeat steps 1 and 2 on the Swarm master.

 		$ eval $(docker-machine env mhs-demo0)

+

 		$ docker network ls

+

 		NETWORK ID          NAME                DRIVER

 		6b07d0be843f        my-net              overlay

 		d0bb78cbe7bd        bridge              bridge

@@ -289,6 +302,7 @@ to have external connectivity outside of their cluster.

 2. Check the Nginx container's network interfaces.

 		$ docker exec web ip addr

+

 		1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default

 		link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

 		inet 127.0.0.1/8 scope host lo

@@ -42,7 +42,9 @@ bridge network for you.

 ```bash

 $ docker network create simple-network

+

 69568e6336d8c96bbf57869030919f7c69524f71183b44d80948bd3927c87f6a

+

 $ docker network inspect simple-network

 [

     {

@@ -134,8 +136,11 @@ For example, now let's use `-o` or `--opt` options to specify an IP address bind

 ```bash

 $ docker network create -o "com.docker.network.bridge.host_binding_ipv4"="172.23.0.1" my-network

+

 b1a086897963e6a2e7fc6868962e55e746bee8ad0c97b54a5831054b5f62672a

+

 $ docker network inspect my-network

+

 [

     {

         "Name": "my-network",

@@ -158,9 +163,13 @@ $ docker network inspect my-network

         }

     }

 ]

+

 $ docker run -d -P --name redis --net my-network redis

+

 bafb0c808c53104b2c90346f284bda33a69beadcab4fc83ab8f2c5a4410cd129

+

 $ docker ps

+

 CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS                        NAMES

 bafb0c808c53        redis               "/entrypoint.sh redis"   4 seconds ago       Up 3 seconds        172.23.0.1:32770->6379/tcp   redis

 ```

@@ -179,9 +188,11 @@ Create two containers for this example:

 ```bash

 $ docker run -itd --name=container1 busybox

+