To point out, the issue is not just with Docker but with WSL2. Docker uses WSL2 to execute, and w/o it working properly, it quits. And I’ve tried everything to sort out WSL, but it fails when executed (wsl --install -d Ubuntu) with the following error:
This leads me to think there’s something off about my laptop rather than a general issue. It would be nice if others with Gen12 Framework using WSL2 could confirm or deny my assumption.
I have been using WSL2 with Ubuntu 22.04 on a 12th gen framework with Windows 11 Pro without any problems, although I am not using Docker or the Windows Hypervisor Platform. My settings are otherwise the same as yours.
Yes, that was a dumb mistake on my part.
But since WSL2 is now working, I’m assuming virtualization is OK and it’s Docker for Windows that is acting up. Will try removing it and installing again, removing all the files it leaves in %appdata%/Docker after first.
Interesting enough, the latest version of Docker shouldn’t require Hyper-V if it uses WSL2. Which, I’d think, would mean WSL2 shouldn’t require Hyper-V either.
I’ve confirmed in two ways that there’s an issue with the laptop/BIOS and not a docker problem.
Hypervisor reported as not present
When using Coreinfo by SysInternals. Specifically, it shows wherever a hypervisor is detected or not. When I ran it on my system, the report detected no hypervisor.
Did you check the Hyper-V services? (Hyper-V Virtual Machine Management)
Is Data Execution Prevention (DEP) enabled in the BIOS? (Disclaimer: I still don’t have my Framework laptop, so possibly this setting doesn’t exist)
Run „bcdedit“ and check if the „hypervisorlaunchtype“ is set to auto, if not run „bcdedit /set hypervisortlaunchtype auto“ and reboot.
No, I meant Windows services: Win+R => services.msc
There are a lot of services starting with Hyper-V and a service called “HV Host Service”.
The startype of them should be set to “Manual (Trigger Start)”
The “HV Host Service” should be running.
The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled
And also this one that talks about HvHost, which might be related to Hyper-V:
The CmService service depends on the HvHost service which failed to start because of the following error:
A device attached to the system is not functioning.
The most interesting was about Secure Mode Extensions enabled in BIOS because I’ve reset the BIOS to the defaults, as instructed by the Framework support. I’ll have to reach out to them with this new information.
Thank you, @mahe, for this suggestion. It enforces my suspicion that it wasn’t Windows 11 at fault and that something else is at play.
As stated in the first error of your last post, check if Secure Mode Extensions (can be named SMX) are disabled in the BIOS.
Also check if all the virtualization features are enabled in the BIOS.
The error with VSM (2nd error you posted) is strange, afaik it can only occur on domain joined devices and usually has something to do with Credential Guard.
Which Windows Edition (Home, Pro, Enterprise, …) and version (feature version, like 21H2) are you running?
