From 8efcfad4b16b547501e2d647c0b9aa527f84104d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E6=A2=81=E8=BE=B0=E6=99=94=20=28Liang=20Chenye=29?= Date: Thu, 10 Sep 2015 14:24:28 +0800 Subject: [PATCH] Update runtime.md Add an explicit explanation of the hooks order. Signed-off-by: Liang Chenye --- runtime.md | 1 + 1 file changed, 1 insertion(+) diff --git a/runtime.md b/runtime.md index 37f0a3c4..be2045b5 100644 --- a/runtime.md +++ b/runtime.md @@ -50,6 +50,7 @@ This event needs to be captured by runc to run onstop event handlers. ## Hooks Hooks allow one to run code before/after various lifecycle events of the container. +Hooks MUST be called in the listed order. The state of the container is passed to the hooks over stdin, so the hooks could get the information they need to do their work. Hook paths are absolute and are executed from the host's filesystem.