The Future of Docker Desktop for Windows

So, I think the main sticking point here is the lock-in of Hyper-V. By making a new popular feature completely dependent on a technology that explicitly disables the use of competitive hypervisors, they&#x27;re giving with one hand and taking with the other.<p>If I was on VM-Ware&#x27;s executive team, I&#x27;d be seriously thinking about filing an anti-trust complaint and the open source community should be thinking about whether submarining virtualbox is worth what Microsoft is doing here.

I&#x27;m forced to use Windows at work and am so looking forward to wsl2.<p>Starting a new terminal with wsl1 takes so long and I&#x27;m less than happy with all terminal emulators.<p>ConEmu has broken copy paste, alacrity doesn&#x27;t have proper tiling... Heck, I&#x27;ve started using hyper of all things.<p>I realize that I probably never be <i>happy</i> on Windows when I can actually use i3wm at home, but if it could just <i>suck less</i> I&#x27;d be so ecstatic.

We work with a lot of independent contractors, many of whom get by fine with Window Home, so this is great news:<p>&gt; ...because WSL 2 works on Windows 10 Home edition, so will Docker Desktop<p>Glad to see this too:<p>&gt; bind mounts from WSL will support inotify events and have nearly identical I&#x2F;O performance as on a native Linux machine

Boy I&#x27;m happy Microsoft is making Windows 10 into a great development platform for the web!<p>One of the rare things to feel upbeat about is that we have great choice when it comes to OSes.

I’ve been following this longstanding Docker issue: <a href="https:&#x2F;&#x2F;github.com&#x2F;docker&#x2F;docker.github.io&#x2F;issues&#x2F;6910" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;docker&#x2F;docker.github.io&#x2F;issues&#x2F;6910</a><p>The comments make it pretty clear how the Github crew feels about it, but I’m curious the response over here.

This is great news. No more CIFS bind mounts required for volume sharing with Windows drives. This is a particular issue with on corporate &#x2F; Enterprise windows boxes.

From what I understand, this will only affect Linux containers running on Windows. Is that correct? What about Windows containers? I know they&#x27;re not nearly as popular, but we did evaluate them at one time for running a legacy Windows application. I doubt we&#x27;re alone in that use case.

So... will WSL2 need to be installed as per WSL? because WSL will not install on my work machine as the machine is locked down by the firm.. So will I lose local Docker?

I&#x27;m very skeptical of this new technology. I used VirtualBox for years and I will continue to do so. I just don&#x27;t see any reason to switch to that new technology. Mounts? VirtualBox can do that. Fast boot? Well, VirtualBox boots in seconds, that&#x27;s more than enough for me. Dynamic memory allocation? VirtualBox has memory balooning, if I ever would run into memory limits, I can always do that. And zero problems with all those Hyper-V conflicts, like Android emulators, snapshot support, VM import&#x2F;export, actually any OS rather than just Linux, etc.

It&#x27;s sad that all this needs Windows 10 Pro, which makes all learner developers unable to use Docker to learn properly unless they upgrade.

Amazes me how far people go to avoid simply running Linux, why isnt that the preferred option here ?

So WSL2 would use a lightweight VM running a Linux kernel to avoid the slow windows I&#x2F;O.

Will I have full access to the GPU?

This is a big step toward the full merger of Windows and Linux on the desktop, which is the most logical way forward for both platforms. Kudos to Docker for taking a primary role and following Microsoft in this direction.