7

's description is "Docker implementation for Windows, running on Hyper-V".

Why is limited to just Hyper-V? Even Docker Desktop on Windows by default displays the system requirements for the non Hyper-V version. Those who want the Hyper-V version actually need to click something extra in order to see the system requirements for the Hyper-V version.

Docker Desktop on Windows' System requirements

7
  • 2
    Just a guess... before WSL2 and associated backends were available Hyper-V was the preferred solution? The tag was last edited in 2017 which is quite a while ago. If you have a better tag description, following our tag wiki guidelines, then you are free to propose it at superuser.com/tags/docker-for-windows/info
    – Mokubai Mod
    Commented Oct 21, 2022 at 13:56
  • 1
    Done, thanks, hope it'll get approved.
    – LWC
    Commented Oct 21, 2022 at 14:02
  • 1
    Also, the WSL2 backend is built on top of WSL2 which is built on top of the Hyper-V engine, so its arguably not incorrect to say that the WSL2 backend runs on hyper-v as well. Commented Oct 24, 2022 at 14:59
  • but one impact of the tech stack to consider, is that you cannot use Docker for Windows on a system where you are already using VirtualBox, since you can't install HyperV and Virtualbox on the same system. Commented Oct 24, 2022 at 18:50
  • Isn't that what the WSL2 variant is for?
    – LWC
    Commented Oct 24, 2022 at 21:12
  • 1
    Wait a second: "WSL2 backend" would be a Hyper-V backend (WSL2 runs only on Hyper-V) that runs LINUX containers. While the "Hyper-V backend and Windows containers" runs WINDOWS containers... both choices relate to Hyper-V, one runs Linux via WSL2, the other runs Windows containers. Or am I missing something? So, to answer your questions, "docker-for-windows", according to your screenshot only runs on Hyper-V.
    – GACy20
    Commented Oct 26, 2022 at 13:19
  • Since this comment (and also the one about VirtualBox) was remade to an answer, I've commented there.
    – LWC
    Commented Oct 26, 2022 at 17:36

1 Answer 1

3

Because it's only for Hyper-V.

It doesn't work with VirtualBox or anything else. You can choose from Linux containers on WSL2 (which uses Hyper-V) or Windows containers directly on Hyper-V. Either way you have to have Hyper-V enabled.

6
  • 1
    @LWC You can use VirtualBox separately, but Docker for Windows requires Hyper-V. It doesn't use VirtualBox. Notice there's no option for VirtualBox in your screenshot.
    – OrangeDog
    Commented Oct 27, 2022 at 13:23
  • 1
    @LWC is it mentioned "in here" - "The newest version of WSL uses Hyper-V architecture to enable its virtualization"
    – OrangeDog
    Commented Oct 27, 2022 at 13:23
  • @LWC and according to this then only way that VirtualBox can be used alongside Hyper-V is by VirtualBox switching its backend to use Hyper-V.
    – OrangeDog
    Commented Oct 27, 2022 at 13:30
  • Is there a source for Linux containers having to run on WSL2 (Hyper-V indirectly) while Windows containers having to run on Hyper-V (directly)?
    – LWC
    Commented Oct 27, 2022 at 21:18
  • @LWC your screenshot? Older DfW versions used their own Hyper-V VM for Linux containers with the option for WSL2 instead, but that seems to be discontinued now.
    – OrangeDog
    Commented Oct 29, 2022 at 20:14

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .