Skip to content

Process isolation containers on Windows Client#27730

Closed
kika123 wants to merge 1 commit intomoby:masterfrom
kika123:patch-1
Closed

Process isolation containers on Windows Client#27730
kika123 wants to merge 1 commit intomoby:masterfrom
kika123:patch-1

Conversation

@kika123
Copy link
Copy Markdown

@kika123 kika123 commented Oct 25, 2016

- What I did

- How I did it

- How to verify it

- Description for the changelog

- A picture of a cute animal (not mandatory but encouraged)

Process isolation containers work fine on Windows client these days. This PR enables them to be set as default.

@GordonTheTurtle GordonTheTurtle added status/0-triage dco/no Automatically set by a bot when one of the commits lacks proper signature labels Oct 25, 2016
Process isolation containers work fine on Windows client these days. This PR enables them to be set as default.

Signed-off-by:  <[email protected]>
Signed-off-by: M. Mediouni <[email protected]>
@GordonTheTurtle GordonTheTurtle removed the dco/no Automatically set by a bot when one of the commits lacks proper signature label Oct 25, 2016
@lowenna
Copy link
Copy Markdown
Member

lowenna commented Oct 25, 2016

No. This is explicit licensing policy. Does NOT LGTM.

@kika123
Copy link
Copy Markdown
Author

kika123 commented Oct 25, 2016

So why does it work officially on Hyper-V containers and via PowerShell containers then? (Windows 10 Enterprise N)
Centennial BaseOS images are licensed for client as far as I know.

@lowenna
Copy link
Copy Markdown
Member

lowenna commented Oct 25, 2016

As per above this is not a technical debate - this is licensing. Closing.

@lowenna lowenna closed this Oct 25, 2016
@thaJeztah
Copy link
Copy Markdown
Member

This has now been done in #38000

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants