-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Disable the subreaper on exec #993
Disable the subreaper on exec #993
Conversation
This keeps the flag but makes it hidden so that existing clients do not encounter an error if we were to have removed the flag. Signed-off-by: Michael Crosby <crosbymichael@gmail.com>
@@ -115,7 +116,7 @@ func execProcess(context *cli.Context) (int, error) { | |||
return -1, err | |||
} | |||
r := &runner{ | |||
enableSubreaper: !context.Bool("no-subreaper"), | |||
enableSubreaper: false, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
remove this line as it because false
is already the default value ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ya, just thought i would make it explicit. it was not omitted but set that way for a reason
@cyphar ya, that is why I didn't put Fixes ;) |
@crosbymichael This doesn't fix the exec reparent problem, still child process of the exec process,PPID becomes 0 , after exec process exits. |
@sandyskies Yup, we know. Which is why #976 exists (as we discussed above). |
This keeps the flag but makes it hidden so that existing clients do not
encounter an error if we were to have removed the flag.
Linked to #971
Signed-off-by: Michael Crosby crosbymichael@gmail.com