Skip to content
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.

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

Update runtime.md #157

Merged
merged 1 commit into from
Sep 10, 2015
Merged

Update runtime.md #157

merged 1 commit into from
Sep 10, 2015

Conversation

liangchenye
Copy link
Member

Add an explicit explanation of the hooks order.

Signed-off-by: Liang Chenye [email protected]

@liangchenye
Copy link
Member Author

Clean the original PR #156..

@vbatts
Copy link
Member

vbatts commented Sep 8, 2015

LGTM

@@ -60,6 +61,7 @@ If a hook returns a non-zero exit code, then an error including the exit code an

### Post-stop
The post-stop hooks are called after the container process is stopped. Cleanup or debugging could be performed in such a hook.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably no need to add this empty line.

@philips
Copy link
Contributor

philips commented Sep 9, 2015

lgtm

@vbatts
Copy link
Member

vbatts commented Sep 10, 2015

@liangchenye rebase needed for merging

Add an explicit explanation of the hooks order.
 
Signed-off-by: Liang Chenye <[email protected]>
@liangchenye liangchenye reopened this Sep 10, 2015
@liangchenye
Copy link
Member Author

@vbatts done.

vbatts added a commit that referenced this pull request Sep 10, 2015
@vbatts vbatts merged commit 51c9265 into opencontainers:master Sep 10, 2015
wking added a commit to wking/opencontainer-runtime-spec that referenced this pull request Dec 11, 2015
Extend [1,2,3] to avoid:

  hook 1: spawn ---------------> reaped
  hook 2:       spawn ----------------> reaped
  hook 3:             spawn -----> reaped

and explicitly require:

  hook 1: spawn --> reaped
  hook 2:                  spawn --> reaped
  hook 3:                                   spawn --> reaped

Folks who do want parallel execution are free to use a parallelizing
wrapper:

  hook 1: spawn ---------------------------> reaped
                child 1 -----> reaped
                  child 2 ---------> reaped
                    child 3 ---> reaped

Although that cuts both ways (with parallel hooks, folks could always
use a single hook with a serializing wrapper).  Still, I'd guess most
current implementations are already taking the serialized approach, so
it makes bundle-author life easier if we are explicit about that.

[1]: opencontainers#20 (comment)
[2]: opencontainers#156
[3]: opencontainers#157

Signed-off-by: W. Trevor King <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants