You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In PR #1008 3 new steps in the lifecycle were added and the referencing of the states to the corresponding lifecycle step was not adjusted. Corrected based on Tag v1.0.0-rc6.
Copy file name to clipboardexpand all lines: runtime.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -18,8 +18,8 @@ The state of a container includes the following properties:
18
18
19
19
*`creating`: the container is being created (step 2 in the [lifecycle](#lifecycle))
20
20
*`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
21
-
*`running`: the container process has executed the user-specified program but has not exited (after step 5 in the [lifecycle](#lifecycle))
22
-
*`stopped`: the container process has exited (step 7 in the [lifecycle](#lifecycle))
21
+
*`running`: the container process has executed the user-specified program but has not exited (after step 8 in the [lifecycle](#lifecycle))
22
+
*`stopped`: the container process has exited (step 10 in the [lifecycle](#lifecycle))
23
23
24
24
Additional values MAY be defined by the runtime, however, they MUST be used to represent new runtime states not defined above.
25
25
***`pid`** (int, REQUIRED when `status` is `created` or `running` on Linux, OPTIONAL on other platforms) is the ID of the container process.
0 commit comments