Skip to content

Commit

Permalink
config-linux: RFC 2119 MUST for absolute linux.namespaces[].path
Browse files Browse the repository at this point in the history
The old language is from 72cbff6 (config-linux.md: clearly require
absolute path for namespace, 2017-03-10, opencontainers#720), but without RFC 2119
language in the absolute path wording, it's not a compliance
requirement (per spec.md's "compliant" definition).  This commit
adjusts the language to bring it in line with our current wording for
maskedPaths and readonlyPaths, which we've had since 25f44dd (
config-linux: fix format and definitely require value of masked and
readonly paths, 2016-09-30, opencontainers#587).

Signed-off-by: W. Trevor King <wking@tremily.us>
  • Loading branch information
wking committed Sep 28, 2017
1 parent a812559 commit f231492
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion config-linux.md
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,8 @@ The following parameters can be specified to set up namespaces:
* **`user`** the container will be able to remap user and group IDs from the host to local users and groups within the container.
* **`cgroup`** the container will have an isolated view of the cgroup hierarchy.

* **`path`** *(string, OPTIONAL)* - an absolute path to namespace file in the [runtime mount namespace](glossary.md#runtime-namespace).
* **`path`** *(string, OPTIONAL)* - namespace file.
This value MUST be an absolute path in the [runtime mount namespace](glossary.md#runtime-namespace).
The runtime MUST place the container process in the namespace associated with that `path`.
The runtime MUST [generate an error](runtime.md#errors) if `path` is not associated with a namespace of type `type`.

Expand Down

0 comments on commit f231492

Please sign in to comment.