Signed-off-by: John Howard <jhoward@microsoft.com>
| ... | ... |
@@ -240,8 +240,8 @@ You now have a running container! From here you can manage your container, inter |
| 240 | 240 |
your application and then, when finished, stop and remove your container. |
| 241 | 241 |
|
| 242 | 242 |
## The underlying technology |
| 243 |
-Docker is written in Go and makes use of several Linux kernel features to |
|
| 244 |
-deliver the functionality we've seen. |
|
| 243 |
+Docker is written in Go and makes use of several kernel features to |
|
| 244 |
+deliver the functionality we've seen. |
|
| 245 | 245 |
|
| 246 | 246 |
### Namespaces |
| 247 | 247 |
Docker takes advantage of a technology called `namespaces` to provide the |
| ... | ... |
@@ -251,7 +251,7 @@ creates a set of *namespaces* for that container. |
| 251 | 251 |
This provides a layer of isolation: each aspect of a container runs in its own |
| 252 | 252 |
namespace and does not have access outside it. |
| 253 | 253 |
|
| 254 |
-Some of the namespaces that Docker uses are: |
|
| 254 |
+Some of the namespaces that Docker uses on Linux are: |
|
| 255 | 255 |
|
| 256 | 256 |
- **The `pid` namespace:** Used for process isolation (PID: Process ID). |
| 257 | 257 |
- **The `net` namespace:** Used for managing network interfaces (NET: |
| ... | ... |
@@ -263,7 +263,7 @@ Some of the namespaces that Docker uses are: |
| 263 | 263 |
Timesharing System). |
| 264 | 264 |
|
| 265 | 265 |
### Control groups |
| 266 |
-Docker also makes use of another technology called `cgroups` or control groups. |
|
| 266 |
+Docker on Linux also makes use of another technology called `cgroups` or control groups. |
|
| 267 | 267 |
A key to running applications in isolation is to have them only use the |
| 268 | 268 |
resources you want. This ensures containers are good multi-tenant citizens on a |
| 269 | 269 |
host. Control groups allow Docker to share available hardware resources to |