Skip to content

Commit 579548a

Browse files
authored
Merge pull request #465 from wking/stop-to-exit
runtime: Replace "process is stopped" with "process exits"
2 parents a059756 + 9eb32c0 commit 579548a

File tree

1 file changed

+6
-5
lines changed

1 file changed

+6
-5
lines changed

runtime.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -15,9 +15,10 @@ This MUST be unique across all containers on this host.
1515
There is no requirement that it be unique across hosts.
1616
* **`status`**: (string) is the runtime state of the container.
1717
The value MAY be one of:
18-
* `created`: the container has been created but the user-specified program has not yet been executed
19-
* `running`: the container has been created and the user-specified program is running
20-
* `stopped`: the container has been created and the user-specified program has been executed but is no longer running
18+
19+
* `created`: the container process has neither exited nor executed the user-specified program
20+
* `running`: the container process has executed the user-specified program but has not exited
21+
* `stopped`: the container process has exited
2122

2223
Additional values MAY be defined by the runtime, however, they MUST be used to represent new runtime states not defined above.
2324
* **`pid`**: (int) is the ID of the container process, as seen by the host.
@@ -55,8 +56,8 @@ The lifecycle describes the timeline of events that happen from when a container
5556
However, some actions might only be available based on the current state of the container (e.g. only available while it is started).
5657
4. Runtime's [`start`](runtime.md#start) command is invoked with the unique identifier of the container.
5758
The runtime MUST run the user-specified program, as specified by [`process`](config.md#process).
58-
5. The container's process is stopped.
59-
This MAY happen due to them erroring out, exiting, crashing or the runtime's [`kill`](runtime.md#kill) operation being invoked.
59+
5. The container process exits.
60+
This MAY happen due to erroring out, exiting, crashing or the runtime's [`kill`](runtime.md#kill) operation being invoked.
6061
6. Runtime's [`delete`](runtime.md#delete) command is invoked with the unique identifier of the container.
6162
The container MUST be destroyed by undoing the steps performed during create phase (step 2).
6263

0 commit comments

Comments
 (0)