github/kata-containers
1
0
Fork 1
mirror of https://github.com/kata-containers/kata-containers.git synced 2025-07-12 14:48:13 +00:00
Code Issues Projects Releases Wiki Activity

Merge pull request #2261 from ManaSugi/fix/oci-hooks-explanation

Browse Source 
config: Fix description for OCI hooks
This commit is contained in:
Fabiano Fidêncio 2021-07-19 10:38:16 +02:00 committed by GitHub
commit 462e445d2f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
src/runtime/cli/config/configuration-acrn.toml.in
View File

@ -105,10 +105,10 @@ block_device_driver = "@DEFBLOCKSTORAGEDRIVER_ACRN@"
# the OCI spec passed to the runtime. # the OCI spec passed to the runtime.
# #
# You can create a rootfs with hooks by customizing the osbuilder scripts: # You can create a rootfs with hooks by customizing the osbuilder scripts:
# https://github.com/kata-containers/osbuilder # https://github.com/kata-containers/kata-containers/tree/main/tools/osbuilder
# #
# Hooks must be stored in a subdirectory of guest_hook_path according to their # Hooks must be stored in a subdirectory of guest_hook_path according to their
# hook type, i.e. "guest_hook_path/{prestart,postart,poststop}". # hook type, i.e. "guest_hook_path/{prestart,poststart,poststop}".
# The agent will scan these directories for executable files and add them, in # The agent will scan these directories for executable files and add them, in
# lexicographical order, to the lifecycle of the guest container. # lexicographical order, to the lifecycle of the guest container.
# Hooks are executed in the runtime namespace of the guest. See the official documentation: # Hooks are executed in the runtime namespace of the guest. See the official documentation:

4
src/runtime/cli/config/configuration-clh.toml.in
View File

@ -120,10 +120,10 @@ block_device_driver = "virtio-blk"
# the OCI spec passed to the runtime. # the OCI spec passed to the runtime.
# #
# You can create a rootfs with hooks by customizing the osbuilder scripts: # You can create a rootfs with hooks by customizing the osbuilder scripts:
# https://github.com/kata-containers/osbuilder # https://github.com/kata-containers/kata-containers/tree/main/tools/osbuilder
# #
# Hooks must be stored in a subdirectory of guest_hook_path according to their # Hooks must be stored in a subdirectory of guest_hook_path according to their
# hook type, i.e. "guest_hook_path/{prestart,postart,poststop}". # hook type, i.e. "guest_hook_path/{prestart,poststart,poststop}".
# The agent will scan these directories for executable files and add them, in # The agent will scan these directories for executable files and add them, in
# lexicographical order, to the lifecycle of the guest container. # lexicographical order, to the lifecycle of the guest container.
# Hooks are executed in the runtime namespace of the guest. See the official documentation: # Hooks are executed in the runtime namespace of the guest. See the official documentation:

4
src/runtime/cli/config/configuration-fc.toml.in
View File

@ -204,10 +204,10 @@ valid_entropy_sources = @DEFVALIDENTROPYSOURCES@
# the OCI spec passed to the runtime. # the OCI spec passed to the runtime.
# #
# You can create a rootfs with hooks by customizing the osbuilder scripts: # You can create a rootfs with hooks by customizing the osbuilder scripts:
# https://github.com/kata-containers/osbuilder # https://github.com/kata-containers/kata-containers/tree/main/tools/osbuilder
# #
# Hooks must be stored in a subdirectory of guest_hook_path according to their # Hooks must be stored in a subdirectory of guest_hook_path according to their
# hook type, i.e. "guest_hook_path/{prestart,postart,poststop}". # hook type, i.e. "guest_hook_path/{prestart,poststart,poststop}".
# The agent will scan these directories for executable files and add them, in # The agent will scan these directories for executable files and add them, in
# lexicographical order, to the lifecycle of the guest container. # lexicographical order, to the lifecycle of the guest container.
# Hooks are executed in the runtime namespace of the guest. See the official documentation: # Hooks are executed in the runtime namespace of the guest. See the official documentation:

4
src/runtime/cli/config/configuration-qemu.toml.in
View File

@ -314,10 +314,10 @@ valid_entropy_sources = @DEFVALIDENTROPYSOURCES@
# the OCI spec passed to the runtime. # the OCI spec passed to the runtime.
# #
# You can create a rootfs with hooks by customizing the osbuilder scripts: # You can create a rootfs with hooks by customizing the osbuilder scripts:
# https://github.com/kata-containers/osbuilder # https://github.com/kata-containers/kata-containers/tree/main/tools/osbuilder
# #
# Hooks must be stored in a subdirectory of guest_hook_path according to their # Hooks must be stored in a subdirectory of guest_hook_path according to their
# hook type, i.e. "guest_hook_path/{prestart,postart,poststop}". # hook type, i.e. "guest_hook_path/{prestart,poststart,poststop}".
# The agent will scan these directories for executable files and add them, in # The agent will scan these directories for executable files and add them, in
# lexicographical order, to the lifecycle of the guest container. # lexicographical order, to the lifecycle of the guest container.
# Hooks are executed in the runtime namespace of the guest. See the official documentation: # Hooks are executed in the runtime namespace of the guest. See the official documentation: