vminitd: Implement minimal init process to reap zombies#537
Open
dcantah wants to merge 1 commit intoapple:mainfrom
Open
vminitd: Implement minimal init process to reap zombies#537dcantah wants to merge 1 commit intoapple:mainfrom
dcantah wants to merge 1 commit intoapple:mainfrom
Conversation
There are some workloads that benefit from having a "true" init process that reaps zombies. This change implements a minimal init as part of vminitd and exposes an API to be able to use this init process in our containers. signals will be forwarded, any child procs will be reaped and the exit code of the actual workload will be propagated.
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There are some workloads that benefit from having a "true" init process that reaps zombies. This change implements a minimal init as part of vminitd and exposes an API to be able to use this init process in our containers. signals will be forwarded, any child procs will be reaped and the exit code of the actual workload will be propagated. The LinuxContainer/LinuxPod API is a very simple bool to ask to use this as our init process, and the init simply spawns whatever command you want as a child underneath this.