From 9f2322274c7b10f75b0dd6a297624a2c64ba63f0 Mon Sep 17 00:00:00 2001 From: Pavel Safronov Date: Tue, 17 Feb 2026 13:04:05 +0000 Subject: [PATCH] Don't ignore poststop hook failures Signed-off-by: Pavel Safronov --- runtime.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/runtime.md b/runtime.md index 3e111c63b..97709d355 100644 --- a/runtime.md +++ b/runtime.md @@ -76,7 +76,7 @@ The lifecycle describes the timeline of events that happen from when a container 11. Runtime's [`delete`](runtime.md#delete) command is invoked with the unique identifier of the container. 12. The container MUST be destroyed by undoing the steps performed during create phase (step 2). 13. The [`poststop` hooks](config.md#poststop) MUST be invoked by the runtime. - If any `poststop` hook fails, the runtime MUST [log a warning](#warnings), but the remaining hooks and lifecycle continue as if the hook had succeeded. + If any `poststop` hook fails, the runtime MUST [generate an error](#errors), and the remaining hooks MUST NOT be executed. ## Errors