p4u1/docker-cli
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Windows: Minor doc clarification

Browse Source 
Signed-off-by: John Howard <jhoward@microsoft.com>
Upstream-commit: 759ed647fbdb026ec91ba8ef84e0fac67b1c73bb
Component: engine
This commit is contained in:
John Howard
2015-08-25 09:36:51 -07:00
parent b498641d47
commit 77030d2282
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
components/engine/docs/introduction/understanding-docker.md
View File

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