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
Copy file name to clipboardExpand all lines: runtime.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -70,7 +70,7 @@ The lifecycle describes the timeline of events that happen from when a container
70
70
If any `startContainer` hook fails, the runtime MUST [generate an error](#errors), stop the container, and continue the lifecycle at step 12.
71
71
8. The runtime MUST run the user-specified program, as specified by [`process`](config.md#process).
72
72
9. The [`poststart` hooks](config.md#poststart) MUST be invoked by the runtime.
73
-
If any `poststart` hook fails, the runtime MUST [log a warning](#warnings), but the remaining hooks and lifecycle continue as if the hook had succeeded.
73
+
If any `poststart` hook fails, the runtime MUST [generate an error](#errors), stop the container, and continue the lifecycle at step 12.
74
74
10. The container process exits.
75
75
This MAY happen due to erroring out, exiting, crashing or the runtime's [`kill`](runtime.md#kill) operation being invoked.
76
76
11. Runtime's [`delete`](runtime.md#delete) command is invoked with the unique identifier of the container.
0 commit comments