mccAug 5, 2023
Last year I had Docker briefly running on my Win10 machine, just long enough to verify it was working, then today I ran it and it said it can't run because of my BIOS settings. Is this surprising? Does this imply I changed my BIOS, possibly by accident, sometime in the last nine months? If I changed out my boot disk, might that have reset some BIOS settings?
Show threadSgeoAug 5, 2023

@mcc Is Core Isolation Memory Protection on? Can Hyper-V or WSL2 run?

I sometimes disable those to get VirtualBox and VMware to run more smoothly. Although recently discovered on Windows 11, memory integrity causes the OS to be virtualized, even if I tried to turn that off. Although that sounds like the opposite of your problem, where the VM stuff is disabled when you want it enabled.

Show threadmccAug 5, 2023
@sgeo I don't know, unless I can check that without going into BIOS. I use WSL1 because it has faster disk access so I don't know if WSL2 can run.
Show threadSgeoAug 5, 2023
@mcc I think, but am not sure, that if you don't have the hypervisor stuff running needed for Hyper-V and WSL2, you can't turn memory integrity on. Also there are multiple versions of Docker Desktop, one based on Hyper-V and one based on WSL2, I'm not sure what the difference is, I'd assume they both have the same requirement.
Show threadmcc
@sgeo I think I was using the WSL2 one last year.
Aug 5, 2023 at 10:06pmWeb