|
...
|
...
|
@@ -32,6 +32,28 @@ An image that has no parent is a **base image**.
|
|
32
|
32
|
[boot2docker](http://boot2docker.io/) is a lightweight Linux distribution made
|
|
33
|
33
|
specifically to run Docker containers. The boot2docker management tool for Mac and Windows was deprecated and replaced by [`docker-machine`](#machine) which you can install with the Docker Toolbox.
|
|
34
|
34
|
|
|
|
35
|
+## bridge
|
|
|
36
|
+
|
|
|
37
|
+In terms of generic networking, a bridge is a Link Layer device which forwards
|
|
|
38
|
+traffic between network segments. A bridge can be a hardware device or a
|
|
|
39
|
+software device running within a host machine's kernel.
|
|
|
40
|
+
|
|
|
41
|
+In terms of Docker, a bridge network uses a software bridge which allows
|
|
|
42
|
+containers connected to the same bridge network to communicate, while providing
|
|
|
43
|
+isolation from containers which are not connected to that bridge network.
|
|
|
44
|
+The Docker bridge driver automatically installs rules in the host machine so
|
|
|
45
|
+that containers on different bridge networks cannot communicate directly with
|
|
|
46
|
+each other.
|
|
|
47
|
+
|
|
|
48
|
+The default bridge network, which is also named `bridge`, behaves differently
|
|
|
49
|
+from user-defined bridge networks. Containers connected to the default `bridge`
|
|
|
50
|
+network can communicate with each other across the bridge by IP address but
|
|
|
51
|
+cannot resolve each other's container name to an IP address unless they are
|
|
|
52
|
+explicitly linked using the `--link` flag to `docker run`.
|
|
|
53
|
+
|
|
|
54
|
+For more information about Docker networking, see
|
|
|
55
|
+[Understand container communication](https://docs.docker.com/engine/userguide/networking/default_network/container-communication/).
|
|
|
56
|
+
|
|
35
|
57
|
## btrfs
|
|
36
|
58
|
|
|
37
|
59
|
btrfs (B-tree file system) is a Linux [filesystem](#filesystem) that Docker
|