[18.09 backport] Windows:Allow process isolation #81
Conversation
Signed-off-by: John Howard <jhoward@microsoft.com> (cherry picked from commit c907c24) Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
|
ping @andrewhsu PTAL |
|
@thaJeztah will this make it into 18.09? |
|
@chlowell unfortunately, it did not make it for the 18.09.0 release (QA was already too far into verifying the release), but there probably will be a 18.09.1 patch release and, if approved, it may find its way into that release. |
|
@t0p4 what error message do you get? You need to run a container with a 1809 base image, I think some should be available now. |
|
cool solution, it's work |
|
Does it mean that on windows 1809 it will be possible to run any container based on previous windows server images (2016, 1709, etc) in process isolation mode? |
|
No, process isolation requires the base image to match the host version of Windows (this is due to Windows not having a stable kernel API) |
|
@thaJeztah ok and this means i could have windows 10 1709 and run a container windows servercore 1709 rght? |
|
Does this work in Windows 10 Home? I'm kind of curious. |
|
@nelsonjchen Windows 10 Home is not supported for Docker Desktop (requires "pro"), nor Docker EE, so not sure if it will run ok (i.e., it's untested). |
|
@lesanchez I think that works yes (but disclaimer: I'm not on Windows myself, so take it with a grain of salt 😅) |
|
@nelsonjchen we don't know, also kind of curious, it may still require other pieces that are not shipped in Home but I don't know anyone who has tried it yet. |
|
@thaJeztah Thanks! |
|
🔨 ⚰️ Windows 10 Home 1809 doesn't have the containers feature that can be installed like Pro. That was expected. I guess that's that. |
backport of moby#38000 for 18.09
fixes moby#27524
fixes moby#37873
fixes docker/for-win#1822
closes moby#37065
closes moby#27730
cherry-pick was clean, no conflicts