Skip to content

use the lifecycle states to define the hooks #250

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
laijs wants to merge 1 commit into from
Closed

use the lifecycle states to define the hooks #250

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions runtime-config.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,9 +5,9 @@
Lifecycle hooks allow custom events for different points in a container's runtime.
Presently there are `Prestart`, `Poststart` and `Poststop`.

* [`Prestart`](#prestart) is a list of hooks to be run before the container process is executed
* [`Poststart`](#poststart) is a list of hooks to be run immediately after the container process is started
* [`Poststop`](#poststop) is a list of hooks to be run after the container process exits
* [`Prestart`](#prestart) is a list of hooks to be run just after the container is created but before the container is started
* [`Poststart`](#poststart) is a list of hooks to be run immediately after the container is started
* [`Poststop`](#poststop) is a list of hooks to be run after the container is stopped

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