jasder
/
runc
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Replace " : " with ": " 

There's an outside change that these are intentional, since I pointed
one of these out earlier [1] and it wasn't fixed.  But I haven't seen
" : " used intentionally outside of this project, and don't think we
want to break ground in that direction ;).

[1]: https://github.com/opencontainers/runtime-spec/pull/510#discussion_r77291554

Signed-off-by: W. Trevor King <wking@tremily.us>
This commit is contained in:
W. Trevor King 2016-09-06 22:21:33 -07:00
parent b2f69c69e8
commit a2d07dcfda
3 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
bundle.md
View File

@ -10,7 +10,7 @@ The definition of a bundle is only concerned with how a container, and its confi
A Standard Container bundle contains all the information needed to load and run a container. A Standard Container bundle contains all the information needed to load and run a container.
This MUST include the following artifacts: This MUST include the following artifacts:
1. `config.json` : contains configuration data. 1. `config.json`: contains configuration data.
This REQUIRED file MUST reside in the root of the bundle directory and MUST be named `config.json`. This REQUIRED file MUST reside in the root of the bundle directory and MUST be named `config.json`.
See [`config.json`](config.md) for more details. See [`config.json`](config.md) for more details.

4
config.md
View File

@ -289,7 +289,7 @@ If a hook returns a non-zero exit code, then an error is logged and the remainin
### Example ### Example
```json ```json
"hooks" : { "hooks": {
"prestart": [ "prestart": [
{ {
"path": "/usr/bin/fix-mounts", "path": "/usr/bin/fix-mounts",
@ -334,7 +334,7 @@ Implementations that are reading/processing this configuration file MUST NOT gen
```json ```json
"annotations": { "annotations": {
"com.example.gpu-cores" : "2" "com.example.gpu-cores": "2"
} }
``` ```

6
runtime.md
View File

@ -15,9 +15,9 @@ This MUST be unique across all containers on this host.
There is no requirement that it be unique across hosts. There is no requirement that it be unique across hosts.
* **`status`**: (string) is the runtime state of the container. * **`status`**: (string) is the runtime state of the container.
The value MAY be one of: The value MAY be one of:
* `created` : the container has been created but the user-specified code has not yet been executed * `created`: the container has been created but the user-specified code has not yet been executed
* `running` : the container has been created and the user-specified code is running * `running`: the container has been created and the user-specified code is running
* `stopped` : the container has been created and the user-specified code has been executed but is no longer running * `stopped`: the container has been created and the user-specified code has been executed but is no longer running
Additional values MAY be defined by the runtime, however, they MUST be used to represent new runtime states not defined above. Additional values MAY be defined by the runtime, however, they MUST be used to represent new runtime states not defined above.
* **`pid`**: (int) is the ID of the container process, as seen by the host. * **`pid`**: (int) is the ID of the container process, as seen by the host.