From 98a6ef6aa582209b004b6501628c71dc0ecb0f2f Mon Sep 17 00:00:00 2001 From: "W. Trevor King" Date: Wed, 8 Feb 2017 16:35:12 -0800 Subject: [PATCH] runtime: "application" -> "container" Michael doesn't like "application" [1], and the runtime spec has standardized around "container process". [1]: https://github.com/opencontainers/runtime-spec/pull/107#issuecomment-145615479 Signed-off-by: W. Trevor King --- runtime.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/runtime.md b/runtime.md index 1000249..e4ca399 100644 --- a/runtime.md +++ b/runtime.md @@ -41,11 +41,11 @@ Start a container from a [bundle directory][bundle]. * *``* Set the container ID to create. * *Options* * *`--bundle `* Override the path to the [bundle directory][bundle] (defaults to the current working directory). -* *Standard streams:* The runtime MUST attach its standard streams directly to the application process without inspection. +* *Standard streams:* The runtime MUST attach its standard streams directly to the container process without inspection. * *Environment variables* * *`LISTEN_FDS`:* The number of file descriptors passed. - For example, `LISTEN_FDS=2` would mean that the runtime MUST pass file descriptors 3 and 4 to the application process (in addition to the [standard streams][standard-streams]) to support [socket activation][systemd-listen-fds]. -* *Exit code:* The runtime MUST exit with the application process's exit code. + For example, `LISTEN_FDS=2` would mean that the runtime MUST pass file descriptors 3 and 4 to the container process (in addition to the [standard streams][standard-streams]) to support [socket activation][systemd-listen-fds]. +* *Exit code:* The runtime MUST exit with the container process's exit code. #### Example