Skip to content

runtime: Add 'exit' to state for collecting the container exit code#677

Closed
wking wants to merge 1 commit intoopencontainers:masterfrom
wking:state-exit-code
Closed

runtime: Add 'exit' to state for collecting the container exit code#677
wking wants to merge 1 commit intoopencontainers:masterfrom
wking:state-exit-code

Conversation

@wking
Copy link
Copy Markdown
Contributor

@wking wking commented Feb 3, 2017

This gives us a more portable way to discover the container exit code (vs. requiring callers to use subreapers or other platform-specific approaches which require knowledge of the runtime implementation).

There would still be no portable way to discover when the container had exited (short of polling state), but we can handle that separately.

This gives us a more portable way to discover the container exit code
(vs. requiring callers to use subreapers [1] or other
platform-specific approaches which require knowledge of the runtime
implementation).

[1]: opencontainers/runc#827 (comment)

Signed-off-by: W. Trevor King <wking@tremily.us>
@crosbymichael
Copy link
Copy Markdown
Member

You cannot have this as required because that forces the runtime to always be running to update the state files.

This change just forces long running runtimes and will impact performance and usage down the road when you run at scale.

If you leave the runtime running it returns the container's exit status as its exit status anyway if you make that tradeoff. This does not belong in the spec.

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.

2 participants