mirror of https://github.com/docker/docs.git
adding glossary items "layer" and "namespace" (#2976)
This commit is contained in:
parent
3476bae9c5
commit
881d56e841
|
|
@ -150,6 +150,12 @@ Kitematic: |
|
||||||
A legacy GUI, bundled with [Docker Toolbox](#toolbox), for managing Docker
|
A legacy GUI, bundled with [Docker Toolbox](#toolbox), for managing Docker
|
||||||
containers. We recommend upgrading to [Docker for Mac](#docker-for-mac) or
|
containers. We recommend upgrading to [Docker for Mac](#docker-for-mac) or
|
||||||
[Docker for Windows](#docker-for-windows/), which have superseded Kitematic.
|
[Docker for Windows](#docker-for-windows/), which have superseded Kitematic.
|
||||||
|
layer: |
|
||||||
|
In an image, a layer is modification to the image, represented by an instruction in the
|
||||||
|
Dockerfile. Layers are applied in sequence to the base image to create the final image.
|
||||||
|
When an image is updated or rebuilt, only layers that change need to be updated, and
|
||||||
|
unchanged layers are cached locally. This is part of why Docker images are so fast
|
||||||
|
and lightweight. The sizes of each layer add up to equal the size of the final image.
|
||||||
libcontainer: |
|
libcontainer: |
|
||||||
libcontainer provides a native Go implementation for creating containers with
|
libcontainer provides a native Go implementation for creating containers with
|
||||||
namespaces, cgroups, capabilities, and filesystem access controls. It allows
|
namespaces, cgroups, capabilities, and filesystem access controls. It allows
|
||||||
|
|
@ -170,6 +176,15 @@ Machine: |
|
||||||
installs Docker on them, then configures the Docker client to talk to them.
|
installs Docker on them, then configures the Docker client to talk to them.
|
||||||
|
|
||||||
*Also known as : docker-machine*
|
*Also known as : docker-machine*
|
||||||
|
namespace: |
|
||||||
|
A [Linux namespace](http://man7.org/linux/man-pages/man7/namespaces.7.html){: target="_blank" class="_"}
|
||||||
|
is a Linux kernel feature that isolates and vitualizes system resources. Processes which restricted to
|
||||||
|
a namespace can only interact with resources or processes that are part of the same namespace. Namespaces
|
||||||
|
are an important part of Docker's isolation model. Namespaces exist for each type of
|
||||||
|
resource, including `net` (networking), `mnt` (storage), `pid` (processes), `uts` (hostname control),
|
||||||
|
and `user` (UID mapping). For more information about namespaces, see [Docker run reference](/engine/reference/run.md)
|
||||||
|
and [Introduction to user namespaces](https://success.docker.com/KBase/Introduction_to_User_Namespaces_in_Docker_Engine){ :target="_blank" class="_" }.
|
||||||
|
|
||||||
node: |
|
node: |
|
||||||
A [node](/engine/swarm/how-swarm-mode-works/nodes/) is a physical or virtual
|
A [node](/engine/swarm/how-swarm-mode-works/nodes/) is a physical or virtual
|
||||||
machine running an instance of the Docker Engine in swarm mode.
|
machine running an instance of the Docker Engine in swarm mode.
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue