...

Text file src/github.com/opencontainers/runtime-spec/glossary.md

Documentation: github.com/opencontainers/runtime-spec

     1# <a name="glossary" />Glossary
     2
     3## <a name="glossaryBundle" />Bundle
     4
     5A [directory structure](bundle.md) that is written ahead of time, distributed, and used to seed the runtime for creating a [container](#container) and launching a process within it.
     6
     7## <a name="glossaryConfiguration" />Configuration
     8
     9The [`config.json`](config.md) file in a [bundle](#bundle) which defines the intended [container](#container) and container process.
    10
    11## <a name="glossaryContainer" />Container
    12
    13An environment for executing processes with configurable isolation and resource limitations.
    14For example, namespaces, resource limits, and mounts are all part of the container environment.
    15
    16## <a name="glossaryContainerNamespace" />Container namespace
    17
    18On Linux,the [namespaces][namespaces.7] in which the [configured process](config.md#process) executes.
    19
    20## <a name="glossaryFeaturesDocument" />Features Structure
    21
    22A [JSON][] structure that represents [the implemented features](#features.md) of the [runtime](#runtime).
    23Irrelevant to the actual availability of the features in the host operating system.
    24
    25## <a name="glossaryJson" />JSON
    26
    27All configuration [JSON][] MUST be encoded in [UTF-8][].
    28JSON objects MUST NOT include duplicate names.
    29The order of entries in JSON objects is not significant.
    30
    31## <a name="glossaryRuntime" />Runtime
    32
    33An implementation of this specification.
    34It reads the [configuration files](#configuration) from a [bundle](#bundle), uses that information to create a [container](#container), launches a process inside the container, and performs other [lifecycle actions](runtime.md).
    35
    36## <a name="glossaryRuntimeCaller" />Runtime caller
    37An external program to execute a [runtime](#runtime), directly or indirectly.
    38
    39Examples of direct callers include containerd, CRI-O, and Podman.
    40Examples of indirect callers include Docker/Moby and Kubernetes.
    41
    42Runtime callers often execute a runtime via [runc][]-compatible command line interface, however, its interaction interface is currently out of the scope of the Open Container Initiative Runtime Specification.
    43
    44## <a name="glossaryRuntimeNamespace" />Runtime namespace
    45
    46On Linux, the namespaces from which new [container namespaces](#container-namespace) are [created](config-linux.md#namespaces) and from which some configured resources are accessed.
    47
    48[JSON]: https://tools.ietf.org/html/rfc8259
    49[UTF-8]: http://www.unicode.org/versions/Unicode8.0.0/ch03.pdf
    50[runc]: https://github.com/opencontainers/runc
    51
    52[namespaces.7]: http://man7.org/linux/man-pages/man7/namespaces.7.html

View as plain text