From 2d8d50c2f830ee74a235fc0b4b7567604fd3c1f3 Mon Sep 17 00:00:00 2001 From: "W. Trevor King" Date: Mon, 27 Feb 2017 16:23:15 -0800 Subject: [PATCH] runtime: Remove status redefinitions from operations These states are already defined in the "State" section. There's no need to redefine them in the operation sections. Operation-level redefinitions are dicy anyway, because they imply something testable about the immediately-after-this-operation time, and it's not possible to run race-free tests of that time (e.g. the process could die for other reasons between the successful 'create' call and the 'state' call you made to look for a 'created' status). Signed-off-by: W. Trevor King --- runtime.md | 6 ------ 1 file changed, 6 deletions(-) diff --git a/runtime.md b/runtime.md index 4786848a..8827297f 100644 --- a/runtime.md +++ b/runtime.md @@ -104,8 +104,6 @@ Using the data in [`config.json`](config.md), this operation MUST create a new c This means that all of the resources associated with the container MUST be created, however, the user-specified program MUST NOT be run at this time. If the runtime cannot create the container as specified in [`config.json`](config.md), it MUST [generate an error](#errors) and a new container MUST NOT be created. -Upon successful completion of this operation the `status` property of this container MUST be `created`. - The runtime MAY validate `config.json` against this spec, either generically or with respect to the local system capabilities, before creating the container ([step 2](#lifecycle)). Runtime callers who are interested in pre-create validation can run [bundle-validation tools](implementations.md#testing--tools) before invoking the create operation. @@ -119,8 +117,6 @@ Attempting to start a container that does not exist MUST [generate an error](#er Attempting to start an already started container MUST have no effect on the container and MUST [generate an error](#errors). This operation MUST run the user-specified program as specified by [`process`](config.md#process). -Upon successful completion of this operation the `status` property of this container MUST be `running`. - ### Kill `kill ` @@ -128,8 +124,6 @@ This operation MUST [generate an error](#errors) if it is not provided the conta Attempting to send a signal to a container that is not running MUST have no effect on the container and MUST [generate an error](#errors). This operation MUST send the specified signal to the process in the container. -When the process in the container is stopped, irrespective of it being as a result of a `kill` operation or any other reason, the `status` property of this container MUST be `stopped`. - ### Delete `delete `