Support Windows Agents

[gburkecw]

Description

Attempting to use this action on 'windows-latest' agents results in the following error during "Booting builder":

C:\Windows\system32\docker.exe buildx inspect --bootstrap --builder builder-6b9f230d-ee8f-43d3-a89f-71c9c655a311
#1 [internal] booting buildkit
#1 pulling image moby/buildkit:buildx-stable-1
#1 pulling image moby/buildkit:buildx-stable-1 2.4s done
#1 creating container buildx_buildkit_builder-6b9f230d-ee8f-43d3-a89f-71c9c655a3110 done
#1 ERROR: Error response from daemon: Windows does not support privileged mode

[internal] booting buildkit:

---

ERROR: Error response from daemon: Windows does not support privileged mode
Error: The process 'C:\Windows\system32\docker.exe' failed with exit code 1

[gburkecw]

I'm not sure if this action is intended to work on Windows agents or not... but it throws an error after attempting to setup. I am attempting to use the build-and-push action for the GHA caching features, which require buildx. Any advice or workarounds would be appreciated, thanks!

[crazy-max]

ERROR: Error response from daemon: Windows does not support privileged mode

Same as #228 (comment)

Why are you using Windows runners? Are you building a Windows container image? If that's the case, BuildKit does not support Windows containers yet. This is tracked in moby/buildkit#616. If not and you're building a Linux container image, then just use the Ubuntu runner.

[Togtja]

There is now experimental support for Windows, and I was wondering if setup buildx action would attempt to support the windows buildx?

[cwoodhayes]

+1

[crazy-max]

There is now experimental support for Windows, and I was wondering if setup buildx action would attempt to support the windows buildx?

cc @colinhemmings