Add support for oci-hooks to libkpod
Add new directory /etc/crio/hooks.d, where packagers can drop a json config file to specify a hook. The json must specify a valid executable to run. The json must also specify which stage(s) to run the hook: prestart, poststart, poststop The json must specify under which criteria the hook should be launched If the container HasBindMounts If the container cmd matches a list of regular expressions If the containers annotations matches a list of regular expressions. If any of these match the the hook will be launched. Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
This commit is contained in:
parent
8538c4067a
commit
139d0841e8
13 changed files with 365 additions and 1 deletions
|
@ -67,6 +67,9 @@ It is currently in active development in the Kubernetes community through the [d
|
|||
| ---------------------------------------------------- | ---------------------------------------------------------------------------------------------------- |
|
||||
| [crio.conf(5)](/docs/crio.conf.5.md) | CRI-O Configuation file |
|
||||
|
||||
## OCI Hooks Support
|
||||
|
||||
[CRI-O configures OCI Hooks to run when launching a container](./hooks.md)
|
||||
|
||||
## cri-o Usage Transfer
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue