-
Notifications
You must be signed in to change notification settings - Fork 2.2k
runc's poststart behaviour doesn't match the runtime-spec #4347
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
Labels
Milestone
Comments
Previous discussion in runtime-spec: opencontainers/runtime-spec#1259 |
Merged
Moved the milestone to 1.2.0. |
Moved the milestone to 1.3.0. Dealing with this is going to take a while, and we should just get 1.2.0 out (this is a pre-existing issue anyway). |
This completely dropped off my radar. We can try to consider this a bugfix for 1.3.0, or fix it in 1.4.0-rc.1 and see if it's worth backporting the fix. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
poststart run into runc create stage. doesn't match the runtime-spec
the spec say "poststart after the user-specified process is executed but before the start operation returns"
https://github.com/opencontainers/runtime-spec/blob/v1.2.0/config.md#poststart
Steps to reproduce the issue
config.json
I set
that means poststart run in create stage.
Describe the results you received and expected
match runtime-spec
What version of runc are you using?
1.1.12
Host OS information
linux
Host kernel information
any
The text was updated successfully, but these errors were encountered: