Hyper-V isolation with buildkit v0.13 for Window Containers

[donno]

Summary

How would I go about configuring buildkitd to use Hyper-V isolation?

Detailed version

In my set-up I'm using containerd and require Hyper-V isolation to be able to run containers.

When following the Windows example, it fails.

> buildctl build `
>> --frontend=dockerfile.v0 `
>> --local context=. \ `
>> --local dockerfile=. `
>> --output type=image,name=docker.io/<your_username>/hello-buildkit,push=false
....
=> ERROR [3/3] RUN echo "Goodbye!" >> hello.txt                                                                                                        0.4s
------
 > [3/3] RUN echo "Goodbye!" >> hello.txt:
------
Dockerfile:4
--------------------
   2 |     USER ContainerAdministrator
   3 |     COPY hello.txt C:/
   4 | >>> RUN echo "Goodbye!" >> hello.txt
   5 |     CMD ["cmd", "/C", "type C:\\hello.txt"]
   6 |
--------------------
error: failed to solve: process "cmd /S /C echo \"Goodbye!\" >> hello.txt" did not complete successfully: failed to create shim task: hcs::CreateComputeSystem ps6ikpwd1vj91ury65xrts52h: The container operating system does not match the host operating system.: unknown

Normally, I can address similar issue by using Hyper-V isolation however I can't quite figure out how to configure either buildctl or buildkd.

If its not possible, I think I can reconfigure containerd to default to use Hyper-V rather than trying process isolation.

Supplementary Information

> buildctl.exe debug workers
ID                              PLATFORMS
j6vc9awy41o7w1ngh28tihgjg       windows/amd64

Running containers with nerdctl.

> nerdctl.exe run --isolation hyperv mcr.microsoft.com/windows/nanoserver:ltsc2022-amd64 -- cmd /c echo hello
hello
> nerdctl.exe run mcr.microsoft.com/windows/nanoserver:ltsc2022-amd64 -- cmd /c echo hello
mcr.microsoft.com/windows/nanoserver:ltsc2022: resolving      |--------------------------------------|
elapsed: 0.1 s                                 total:   0.0 B (0.0 B/s)
time="2024-03-15T18:33:28+10:30" level=fatal msg="no match for platform in manifest: not found"

The no match for platform in manifest also happens if I drop the -amd64 on the end.