-
Notifications
You must be signed in to change notification settings - Fork 18.7k
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
Add isolation to info - enables Hyper-V containers CI bring-up #26255
Add isolation to info - enables Hyper-V containers CI bring-up #26255
Conversation
bdc2e2b
to
9fb7cee
Compare
LGTM, but needs a rebase |
9fb7cee
to
2865ea5
Compare
Rebased. Really weird though as there were no conflicts... github is having some issues I think! |
2865ea5
to
8480a98
Compare
Rebased again. Was real that time... |
ping @justincormack @vdemeester PTAL |
LGTM |
Put this in docs review, not sure if this needs anything. |
It needs to be added to the API documentation, and API changelog. Not sure if we want to add an example to the docker info reference (https://github.com/docker/docker/blob/master/docs/reference/commandline/info.md#display-docker-system-information), that may be a bit too much, but open to suggestions there |
Signed-off-by: John Howard <[email protected]>
8480a98
to
c4e1697
Compare
@thaJeztah Doc updates made. Added Windows sample output in |
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.
LGTM
ping @vdemeester for review/merge
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.
LGTM 🐸
…cture Add isolation to info - enables Hyper-V containers CI bring-up
Signed-off-by: John Howard [email protected]
This enables integration tests to know the isolation mode of the daemon under test so that they can take different actions between (on Windows) Window Server containers and Hyper-V containers. This change is essential to start getting coverage of Hyper-V containers - currently there is no coverage.