From 0a55d5ca5a8114ed96e7e36faee070b262bcb6ba Mon Sep 17 00:00:00 2001 From: "W. Trevor King" Date: Fri, 11 Dec 2015 13:32:45 -0800 Subject: [PATCH] lifecycle: Mention runtime.json As discussed earlier [1,2]. I'm in favor of rolling it back into config.json [3], but we aren't there yet [4]. [1]: https://github.com/opencontainers/specs/pull/231#discussion_r43262848 [2]: https://github.com/opencontainers/specs/pull/231/files#r46735828 [3]: https://groups.google.com/a/opencontainers.org/forum/#!topic/dev/0QbyJDM9fWY Subject: Single, unified config file (i.e. rolling back specs#88) Date: Wed, 4 Nov 2015 09:53:20 -0800 Message-ID: <20151104175320.GC24652@odin.tremily.us> [4]: https://github.com/opencontainers/specs/blob/4a63e81a807edec3d67ed2b6bd99a6c2b288676f/bundle.md#container-format Signed-off-by: W. Trevor King --- runtime.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/runtime.md b/runtime.md index e3f1b79f7..090f9ea1e 100644 --- a/runtime.md +++ b/runtime.md @@ -38,8 +38,8 @@ This is provided so that consumers can find the container's configuration and ro The lifecycle describes the timeline of events that happen from when a container is created to when it ceases to exist. 1. OCI compliant runtime is invoked by passing the bundle path as argument. -2. The container's runtime environment is created according to the configuration in config.json. - Any updates to config.json after container is running do not affect the container. +2. The container's runtime environment is created according to the configuration in `config.json` and `runtime.json`. + Any updates to `config.json` or `runtime.json` after container is running do not affect the container. 3. The container's state.json file is written to the filesystem. 4. The prestart hooks are invoked by the runtime. If any prestart hook fails, then the container is stopped and the lifecycle continues at step 8.