This repository has been archived by the owner on May 12, 2021. It is now read-only.
Add support for OCI hooks inside the guest #348
Comments
eguzman3
added a commit
to eguzman3/agent
that referenced
this issue
Aug 30, 2018
In order to allow OCI hooks to be executed during the lifecycle of the container inside the guest the path "/usr/share/oci/hooks/" has been designated to allow for 'drop-in' hooks. Fixes kata-containers#348 Signed-off-by: Edward Guzman <eguzman@nvidia.com>
eguzman3
added a commit
to eguzman3/agent
that referenced
this issue
Sep 12, 2018
Adds support for running OCI hooks within the guest. A 'drop-in' path (guest_hook_path) is specified in the cli configuration file and if set, the agent will look for OCI hooks in this directory and inject them into the container life cycle. Fixes kata-containers#348 Signed-off-by: Edward Guzman <eguzman@nvidia.com>
eguzman3
added a commit
to eguzman3/agent
that referenced
this issue
Sep 13, 2018
Adds support for running OCI hooks within the guest. A 'drop-in' path (guest_hook_path) is specified in the cli configuration file and if set, the agent will look for OCI hooks in this directory and inject them into the container life cycle. Fixes kata-containers#348 Signed-off-by: Edward Guzman <eguzman@nvidia.com>
eguzman3
added a commit
to eguzman3/agent
that referenced
this issue
Sep 13, 2018
Adds support for running OCI hooks within the guest. A 'drop-in' path (guest_hook_path) is specified in the cli configuration file and if set, the agent will look for OCI hooks in this directory and inject them into the container life cycle. Fixes kata-containers#348 Signed-off-by: Edward Guzman <eguzman@nvidia.com>
flx42
added a commit
to flx42/agent
that referenced
this issue
Oct 2, 2018
Adds support for running OCI hooks within the guest. A 'drop-in' path (guest_hook_path) is specified in the cli configuration file and if set, the agent will look for OCI hooks in this directory and inject them into the container life cycle. Fixes: kata-containers#348 Replaces: kata-containers#365 Co-authored-by: Edward Guzman <eguzman@nvidia.com> Co-authored-by: Felix Abecassis <fabecassis@nvidia.com> Signed-off-by: Edward Guzman <eguzman@nvidia.com> Signed-off-by: Felix Abecassis <fabecassis@nvidia.com>
flx42
added a commit
to flx42/agent
that referenced
this issue
Oct 3, 2018
Adds support for running OCI hooks within the guest. A 'drop-in' path (guest_hook_path) is specified in the cli configuration file and if set, the agent will look for OCI hooks in this directory and inject them into the container life cycle. Fixes: kata-containers#348 Replaces: kata-containers#365 Co-authored-by: Edward Guzman <eguzman@nvidia.com> Co-authored-by: Felix Abecassis <fabecassis@nvidia.com> Signed-off-by: Edward Guzman <eguzman@nvidia.com> Signed-off-by: Felix Abecassis <fabecassis@nvidia.com>
jshachm
pushed a commit
to jshachm/agent
that referenced
this issue
Nov 22, 2018
Adds support for running OCI hooks within the guest. A 'drop-in' path (guest_hook_path) is specified in the cli configuration file and if set, the agent will look for OCI hooks in this directory and inject them into the container life cycle. Fixes: kata-containers#348 Replaces: kata-containers#365 Co-authored-by: Edward Guzman <eguzman@nvidia.com> Co-authored-by: Felix Abecassis <fabecassis@nvidia.com> Signed-off-by: Edward Guzman <eguzman@nvidia.com> Signed-off-by: Felix Abecassis <fabecassis@nvidia.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In order to leverage existing OCI hooks, there should be a way of designating hooks to execute within the life cycle of containers inside the guest.
The text was updated successfully, but these errors were encountered: