You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AMD64 is AMD's 64-bit extension of Intel's x86 architecture, and is also
3
+
referred to as x86_64 (or x86-64).
4
+
arm64: |
5
+
ARM64 is the 64-bit extension of the ARM CPU architecture. arm64 architecture
6
+
is used in Apple silicon machines.
7
+
build: |
8
+
Build is the process of building Docker images using a Dockerfile.
9
+
The build uses a Dockerfile and a "context". The context is the set of files in the directory in which the image is built.
10
+
layer: |
11
+
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.
12
+
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.
13
+
libcontainer: |
14
+
libcontainer provides a native Go implementation for creating containers with
15
+
namespaces, cgroups, capabilities, and filesystem access controls. It allows
16
+
you to manage the lifecycle of the container performing additional operations
17
+
after the container is created.
18
+
libnetwork: |
19
+
libnetwork provides a native Go implementation for creating and managing container network namespaces and other network resources. It manages the networking lifecycle of the container performing additional operations after the container is created.
20
+
namespace: |
21
+
A [Linux namespace](https://man7.org/linux/man-pages/man7/namespaces.7.html)
22
+
is a Linux kernel feature that isolates and virtualizes system resources. Processes which are restricted to a namespace can only interact with resources or processes that are part of the same namespace. Namespaces
23
+
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/containers/run/) and [Isolate containers with a user namespace](/engine/security/userns-remap/).
24
+
Worker nodes execute tasks.
25
+
overlay network driver: |
26
+
Overlay network driver provides out of the box multi-host network connectivity
27
+
for Docker containers in a cluster.
28
+
overlay storage driver: |
29
+
OverlayFS is a [filesystem](#filesystem) service for Linux which implements a
30
+
[union mount](https://en.wikipedia.org/wiki/Union_mount) for other file systems.
31
+
It is supported by the Docker daemon as a storage driver.
32
+
base image: |
33
+
A base image is an image you designate in a `FROM` directive in a Dockerfile.
34
+
It defines the starting point for your build.
35
+
Dockerfile instructions create additional layers on top of the base image.
36
+
A Dockerfile with the `FROM scratch` directive uses an empty base image.
37
+
persistent storage: |
38
+
Persistent storage or volume storage provides a way for a user to add a
39
+
persistent layer to the running container's file system. This persistent layer
40
+
could live on the container host or an external device. The lifecycle of this
41
+
persistent layer is not connected to the lifecycle of the container, allowing
42
+
a user to retain state.
43
+
SSH: |
44
+
SSH (secure shell) is a secure protocol for accessing remote machines and applications.
45
+
It provides authentication and encrypts data communication over insecure networks such as the Internet. SSH uses public/private key pairs to authenticate logins.
46
+
Union file system: |
47
+
Union file systems implement a [union
48
+
mount](https://en.wikipedia.org/wiki/Union_mount) and operate by creating
49
+
layers. Docker uses union file systems in conjunction with
50
+
[copy-on-write](#copy-on-write) techniques to provide the building blocks for
51
+
containers, making them very lightweight and fast.
52
+
53
+
For more on Docker and union file systems, see [Docker and OverlayFS in
A virtual machine is a program that emulates a complete computer and imitates dedicated hardware.
61
+
It shares physical hardware resources with other users but isolates the operating system. The end user has the same experience on a Virtual Machine as they would have on dedicated hardware.
62
+
63
+
Compared to containers, a virtual machine is heavier to run, provides more isolation, gets its own set of resources and does minimal sharing.
64
+
65
+
*Also known as VM*
66
+
volume: |
67
+
A volume is a specially-designated directory within one or more containers
68
+
that bypasses the Union File System. Volumes are designed to persist data,
69
+
independent of the container's life cycle. Docker therefore never automatically deletes volumes when you remove a container, nor will it "garbage collect" volumes that are no longer referenced by a container.
70
+
*Also known as: data volume*
71
+
72
+
There are three types of volumes: *host, anonymous, and named*:
73
+
74
+
- A **host volume** lives on the Docker host's filesystem and can be accessed from within the container.
75
+
76
+
- A **named volume** is a volume which Docker manages where on disk the volume is created, but it is given a name.
77
+
78
+
- An **anonymous volume** is similar to a named volume, however, it can be difficult to refer to the same volume over time when it is an anonymous volume. Docker handles where the files are stored.
79
+
x86_64: |
80
+
x86_64 (or x86-64) refers to a 64-bit instruction set invented by AMD as an
81
+
extension of Intel's x86 architecture. AMD calls its x86_64 architecture,
82
+
AMD64, and Intel calls its implementation, Intel 64.
0 commit comments