Skip to content

Commit 37b8a20

Browse files
committed
runtime-config.md: use the lifecycle states to define the hooks
Signed-off-by: Lai Jiangshan <jiangshanlai@gmail.com>
1 parent 5c47a6c commit 37b8a20

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

runtime-config.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,9 +5,9 @@
55
Lifecycle hooks allow custom events for different points in a container's runtime.
66
Presently there are `Prestart`, `Poststart` and `Poststop`.
77

8-
* [`Prestart`](#prestart) is a list of hooks to be run before the container process is executed
9-
* [`Poststart`](#poststart) is a list of hooks to be run immediately after the container process is started
10-
* [`Poststop`](#poststop) is a list of hooks to be run after the container process exits
8+
* [`Prestart`](#prestart) is a list of hooks to be run just after the container is [created](runtime.md#create) but before the container is [started](runtime.md#start)
9+
* [`Poststart`](#poststart) is a list of hooks to be run immediately after the container is [started](runtime.md#start)
10+
* [`Poststop`](#poststop) is a list of hooks to be run after the container is [stopped](runtime.md#stop)
1111

1212
Hooks allow one to run code before/after various lifecycle events of the container.
1313
Hooks MUST be called in the listed order.

0 commit comments

Comments
 (0)