From f89cb852aeb38da51bd7683557fae0c44c3abed6 Mon Sep 17 00:00:00 2001 From: "W. Trevor King" Date: Fri, 11 Dec 2015 13:38:30 -0800 Subject: [PATCH] lifecycle: Don't require /run/opencontainer//containers We already require it for Linux/Unix-based systems [1], so we don't have to repeat it here. And other systems will use different paths, which we haven't specified yet. When I asked why we didn't specify a path for Windows [2], Vincent said we were waiting on help from PoC implementations [3]. So this commit punts the location to the "State" section, and lets the "Lifecycle" section just focus on when the write-to-filesystem happens. There's also discussion about removing the filesystem state registry completely [4], in which case we'd want to remove the whole line from the lifecycle. [1]: https://github.com/opencontainers/specs/commit/7713efc1be66dda08548ad12da6509fd93662308#diff-b84a8d65d8ed53f4794cd2db7e8ea731L7 [2]: https://github.com/opencontainers/specs/pull/211#discussion_r41066673 [3]: https://github.com/opencontainers/specs/pull/211#discussion_r41067134 [4]: https://groups.google.com/a/opencontainers.org/forum/#!topic/dev/q6TYqVZOcX8 Subject: removal of /run/opencontainer/containers Date: Wed, 25 Nov 2015 14:29:35 +0000 Message-ID: Signed-off-by: W. Trevor King --- runtime.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/runtime.md b/runtime.md index 0f12f317..e3f1b79f 100644 --- a/runtime.md +++ b/runtime.md @@ -40,7 +40,7 @@ The lifecycle describes the timeline of events that happen from when a container 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. -3. The container's state.json file is written to the filesystem under /run/opencontainer//containers//. +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. 5. The user specified process is executed in the container.