From 65d9d6b8851427416b63dd7ff6d9a663df70e673 Mon Sep 17 00:00:00 2001 From: "W. Trevor King" Date: Thu, 23 Jun 2016 14:25:00 -0700 Subject: [PATCH] runtime: Add 'creating' to state status To distinguish between "we're still setting this container up" and "we're finished setting up; you can call 'start' if you like". Also reference the lifecycle steps, because you can't be too explicit Signed-off-by: W. Trevor King --- runtime.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/runtime.md b/runtime.md index 3702a27d3..04a196ded 100644 --- a/runtime.md +++ b/runtime.md @@ -16,9 +16,10 @@ There is no requirement that it be unique across hosts. * **`status`**: (string) is the runtime state of the container. The value MAY be one of: - * `created`: the container process has neither exited nor executed the user-specified program - * `running`: the container process has executed the user-specified program but has not exited - * `stopped`: the container process has exited + * `creating`: the container is being created (step 2 in the [lifecycle](#lifecycle)) + * `created`: the runtime has finished the [create operation](#create) (after step 2 in the [lifecycle](#lifecycle)), and the container process has neither exited nor executed the user-specified program + * `running`: the container process has executed the user-specified program but has not exited (after step 4 in the [lifecycle](#lifecycle)) + * `stopped`: the container process has exited (step 5 in the [lifecycle](#lifecycle)) 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.