"db" is the parent image, and "web" links to it as the child image. There was a typo in the document which reversed the relation.
| ... | ... |
@@ -162,8 +162,8 @@ containers also shows `web/db` in the `NAMES` column. This tells us that the |
| 162 | 162 |
`web` container is linked to the `db` container in a parent/child relationship. |
| 163 | 163 |
|
| 164 | 164 |
So what does linking the containers do? Well we've discovered the link creates |
| 165 |
-a parent-child relationship between the two containers. The parent container, |
|
| 166 |
-here `web`, can access information on the child container `db`. To do this |
|
| 165 |
+a parent-child relationship between the two containers. The child container, |
|
| 166 |
+here `web`, can access information on the parent container `db`. To do this |
|
| 167 | 167 |
Docker creates a secure tunnel between the containers without the need to |
| 168 | 168 |
expose any ports externally on the container. You'll note when we started the |
| 169 | 169 |
`db` container we did not use either of the `-P` or `-p` flags. As we're |