Skip to content

Commit

Permalink
runtime-config: Require hooks to execute in the host environment
Browse files Browse the repository at this point in the history
On IRC on 2015-09-28:

  11:28 < jojy_mesos> i guess i was expecting an additional attribute
    for hooks that specifies whether the hooks runs in the host
    namespace or in the container's namespace
  11:28 < lk4d4> they all run in host namespaces

Signed-off-by: W. Trevor King <wking@tremily.us>
  • Loading branch information
wking committed Sep 30, 2015
1 parent 023c751 commit bfe1aba
Showing 1 changed file with 1 addition and 0 deletions.
1 change: 1 addition & 0 deletions runtime-config.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,7 @@ Presently there are `Prestart`, `Poststart` and `Poststop`.
Hooks allow one to run code before/after various lifecycle events of the container.
Hooks MUST be called in the listed order.
The state of the container is passed to the hooks over stdin, so the hooks could get the information they need to do their work.
All hooks execute in the host environment (e.g. the same namespace, cgroups, etc. that apply to the host process).

Hook paths are absolute and are executed from the host's filesystem.

Expand Down

0 comments on commit bfe1aba

Please sign in to comment.