Allow Process Isolation Windows Containers without Hyper-V in Windows 10 #151
Tell us about your request
Number 2 has the compound effect of not letting you even start Docker unless you have VT Extensions enabled in the BIOS, or enabling Nested Virtualization in a VM. I don't believe these technologies are required in a pure Windows Container Process Isolation mode environment. I recently ran into a company doing fully remote work with VDI (virtual remote desktops), but didn't have the ability to use Nested Virt in those Windows 10 VMs, and therefore, can't use Docker Desktop for their Windows Container work.
I also have worked with orgs that aren't allowed to run any VM locally without a full security audit of the solution, and only "approved" VM's can be run. They were mostly a Windows shop, currently evaluating Windows Containers. Providing this option for VM-less containers could provide those types of orgs a path forward, without hacks, or long dealys around security approvals.
Which service(s) is this request for?
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Are you currently working around the issue?
The text was updated successfully, but these errors were encountered:
I am also highly interested in this feature. In our company we want to use devices with Windows 10 IOT Enterprise and cannot use Hyper-V. I tought I need to hande the microservices as Windows Services and IIS configuration.
This statement is false. I successfully use Docker Desktop inside VirtualBox that doesn't support Hyper-V nested virtualization. I cannot say that process of switching to Windows containers is easy though.
@slonopotamus "installed" Docker Desktop 4.0.0, but upon restart, it pops a dialog saying this:
Does that mean it actually installed Docker Desktop 3.6.0, or that it might be running in a mode as if it were 3.6.0? Did 3.6.0 not have the Hyper-V feature check yet?
Is there any news regarding this? I work using Unity3d and for some reason the licens activation doensn't work with Hyper-V active so I'm force to run without Hyper-V active. So far I have been able to do it by using Docker-CE from Moby but I'm not able to work by using the current version of Docker Desktop.