Skip to content

Poststop hooks receives correct pid#565

Closed
zachgersh wants to merge 1 commit intoopencontainers:masterfrom
zachgersh:poststop-pid
Closed

Poststop hooks receives correct pid#565
zachgersh wants to merge 1 commit intoopencontainers:masterfrom
zachgersh:poststop-pid

Conversation

@zachgersh
Copy link

While developing a poststop hook, we discovered that the container state provided on stdin always had pid set to 0.

This patch sets the pid field correctly.

cc: @rosenhouse @evanfarrar

Signed-off-by: Gabe Rosenhouse <grosenhouse@pivotal.io>
@crosbymichael
Copy link
Member

Since this is the post stop hook the pid was set to 0 because it is no longer alive. What is the usecase for providing this?

@rosenhouse
Copy link

You're right -- we were confused about the lifecycle here. We will close this.

@zachgersh zachgersh closed this Feb 17, 2016
@crosbymichael
Copy link
Member

No problem, thanks!

stefanberger pushed a commit to stefanberger/runc that referenced this pull request Sep 8, 2017
stefanberger pushed a commit to stefanberger/runc that referenced this pull request Sep 8, 2017
We dropped these in 4774080 (specs-go/config: Drop "this field is
platform dependent", 2016-09-14, opencontainers#568) but f9e48e0 (Windows: User
struct changes, 2016-09-14, opencontainers#565) was developed in parallel and
brought in a new one.

Signed-off-by: W. Trevor King <wking@tremily.us>
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.

3 participants