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

runcexecutor: allow disabling subreaper #583

Closed
wants to merge 1 commit into from

Conversation

tiborvass
Copy link
Collaborator

When other daemons such as dockerd set subreaper, there can be issues.
This allows those daemons to disable subreaping if they need to.

Hopefully this commit either gets reverted soon or will have a valid
concrete usecase, as the investigation continues on
moby/moby#37676

Signed-off-by: Tibor Vass tibor@docker.com

cc @AkihiroSuda @ijc

When other daemons such as dockerd set subreaper, there can be issues.
This allows those daemons to disable subreaping if they need to.

Hopefully this commit either gets reverted soon or will have a valid
concrete usecase, as the investigation continues on
moby/moby#37676

Signed-off-by: Tibor Vass <tibor@docker.com>
@ijc
Copy link
Collaborator

ijc commented Aug 21, 2018

Seems OK to me, and is easily enough to revert.

I don't think the comment about the interface stability is particularly necessary since that sub-package is not something which buildkit makes any guarantees about in the first place. The only versioning guarantees I know about are for e.g. the gRPC gateway interfaces and the LLB (such as #465) and some of the Dockerfile frontend functionality (see #528).

@tiborvass
Copy link
Collaborator Author

This is wrong and thus useless. Michael's PR #584 solves my problem better.

@tiborvass tiborvass closed this Aug 22, 2018
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