Skip to content

Conversation

@wking
Copy link
Collaborator

@wking wking commented Mar 21, 2018

We already have two ways to specify a process to launch (for the container process and for hooks). This commit recycles the hook-process schema for launcing the hypervisor. I prefer using the more-fundamental container process schema, but @crosbymichael felt it had too many properties that wouldn't apply to the hypervisor-launching case.

@wking wking force-pushed the use-hook-structure-for-hypervisor branch from 85e26b0 to 218660d Compare March 21, 2018 16:22
So we'll be able to link to it without linking the rest of the 'hooks'
structure.

Signed-off-by: W. Trevor King <[email protected]>
We already have two ways to specify a process to launch (for the
container process and for hooks).  This commit recycles the
hook-process schema for launching the hypervisor.  I prefer using the
more-fundamental container process schema, but Michael felt it had too
many properties that wouldn't apply to the hypervisor-launching case
[1].

[1]: opencontainers#949 (comment)

Signed-off-by: W. Trevor King <[email protected]>
@wking wking force-pushed the use-hook-structure-for-hypervisor branch from 218660d to 9da1f6e Compare April 2, 2018 03:59
@wking
Copy link
Collaborator Author

wking commented Apr 2, 2018

With opencontainers#949 merged, I'm closing this PR and opening one against master with the same content: opencontainers#962.

@wking wking closed this Apr 2, 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.

1 participant