jasder
/
runc
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Update runtime.md 

Add an explicit explanation of the hooks order.
 
Signed-off-by: Liang Chenye <liangchenye@huawei.com>
This commit is contained in:
梁辰晔 (Liang Chenye) 2015-09-10 14:24:28 +08:00
parent 2d9842b0f5
commit 8efcfad4b1
1 changed files with 1 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
runtime.md
View File

@ -50,6 +50,7 @@ This event needs to be captured by runc to run onstop event handlers.
## Hooks ## Hooks
Hooks allow one to run code before/after various lifecycle events of the container. 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. 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. Hook paths are absolute and are executed from the host's filesystem.