From 2a82607067e11a0aea234f6efd52c4f7cb0a48d7 Mon Sep 17 00:00:00 2001 From: Vishnu kannan Date: Fri, 22 Apr 2016 13:42:08 -0700 Subject: [PATCH] Run post-stop hooks before the container sandbox is deleted. Signed-off-by: Vishnu kannan --- runtime.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/runtime.md b/runtime.md index 370df3512..2966458b3 100644 --- a/runtime.md +++ b/runtime.md @@ -46,8 +46,9 @@ The lifecycle describes the timeline of events that happen from when a container If any poststart hook fails, then the container MUST be stopped and the lifecycle continues at step 8. 6. Additional actions such as pausing the container, resuming the container or signaling the container MAY be performed using the runtime interface. The container MAY also error out, exit or crash. -7. The container MUST be destroyed by undoing the steps performed during create phase (step 2). -8. The poststop hooks MUST be invoked by the runtime and errors, if any, MAY be logged. +7. The poststop hooks MUST be invoked by the runtime and errors, if any, MAY be logged. +8. The container MUST be destroyed by undoing the steps performed during create phase (step 2). + Note: The lifecycle is a WIP and it will evolve as we have more use cases and more information on the viability of a separate create phase.