Workaround: downgrade from 2.1.3.0 to 2.1.2.0. Installers are available here.

Verified that the WSL 2 Tech Preview works when I uninstall 2.1.3.0 and installed 2.1.2.0 instead.

I encountered the identical problem and had to downgrade to fix. Selecting WSL 2 Tech Preview in 2.1.3.0 seems to be missing the WSL 2 Tech Preview features. It indicates Loading..., but never visibly does anything.

Here's 2.1.3.0:

Compared with 2.1.2.0:

Also experienced the same issue. Nothing to add that wasn't already stated before. Downgrading also allowed me to use WSL2 once again with Docker.

Windows Version: Build 18980.vb_release.190907-1301
Docker Desktop Version: 2.1.3.0 (38275)
Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM: No

Hi, I also experienced the same issue as described by sc0ttwad3 and his screenshots . I do have the same configuration as stated by JohnCrist1988 and AdamVig however my Windows OS Version is slightly different = 18980.1
Downgrading to 2.1.2.0 allowed me to use successfully WSL2 Tech preview again

Sorry for a question that I should know... but doesn't uninstalling destroy everything already in docker's world, all images, volumes, etc? I note that I can't downgrade easily... installing 2.1.2.0 after just exiting 2.1.3.0 results in the installer saying "Existing installation is up to date".

vb_release. Sorry for a question that I should know... but doesn't uninstalling destroy everything already in docker's world, all images, volumes, etc? I note that I can't downgrade easily... installing 2.1.2.0 after just exiting 2.1.3.0 results in the installer saying "Existing installation is up to date".

hi im fairly new to the github environment so if i've done anything wrong please understand.
Yes. As the daemon cannot be running there is no way to backup containers and images that i know of... or is there? thanks and im much appreciated of this project!!

*edit
windows build 18980.vb_release.190907-1301
ubuntu18.04 (latest from microsoft store)
WSL 2

Same issue here.
-Latest W10 insiders fast
-Ubuntu 18.04.3 LTS
-Docker Desktop Community 2.1.3.0

I'm also experiencing this issue.

I bit the bullet and

• Uninstalled 2.1.3.0
• Installed 2.1.2.0
  It made docker work with the tech preview.

Interestingly enough, I lost all the volumes and images on the windows side, but retained all the volumes and images on the WSL2 side. Not what I expected.

How do you install the older specific version? (2.1.2.0) The installer gives me 2.1.0.0, and offers me an update to 2.1.3.0 (which I verified doesn't work on my WSL 2 / build 18985 setup) but no option for 2.1.2.0 ...

How do you install the older specific version? (2.1.2.0) The installer gives me 2.1.0.0, and offers me an update to 2.1.3.0 (which I verified doesn't work on my WSL 2 / build 18985 setup) but no option for 2.1.2.0 ...

Have you tried this one? https://docs.docker.com/docker-for-windows/edge-release-notes/#docker-desktop-community-2120

How do you install the older specific version? (2.1.2.0) The installer gives me 2.1.0.0, and offers me an update to 2.1.3.0 (which I verified doesn't work on my WSL 2 / build 18985 setup) but no option for 2.1.2.0 ...

Hi, @wayne-optin Here is the 2.1.2.0 download link:　https://download.docker.com/win/edge/38030/Docker%20Desktop%20Installer.exe

I confirm that Docker Desktop 2.1.3.0 breaks WSL 2 Tech Preview, and Docker no longer works in WSL.
Reinstalling version 2.1.2.0 fixes it.
Skipping version 2.1.3.0...
Thank you!

Confirmed that moving back to version 2.1.2.0 fixed the problem for me with windows version 18990, do we know what broke on 2.1.3.0 and when we might get a fix.

Ongoing confirmation that Windows 10 Build 18990.vb_release.190921-1704 works well with 2.1.2.0 but does not work with 2.1.3.0 regarding the use of the WSL2 technical preview.

Also experiencing this, installed the latest version of Windows, and then WSL would not launch.

Also I cannot launch Visual Studio from WSL.
All in all I gotta say I'm dissappointed, I was holding out for the WSL setup to work, just work, and its not working.

Disapointed in how many devs feel the need to post "me too" comments

We are planning a new Edge release this week, which (we believe!) will fix this issue.

Disapointed in how many devs feel the need to post "me too" comments

I'm disappointed how someone thinks everyone posting on a bug report thread is a Docker dev. But that's none of my business.

Thanks for your work on this @stephen-turner .

I just installed 2.1.4 and it didn't seem to show me the WSL2 Tech Preview option, unless I am looking in the wrong place.

Any direction would be greatly appreciated. Seems like people are also talking about this issue over here (at least I parsed them as the same issue): #4361

What link did you use to download it? the one on the edge release pages just returns 404 for me? maybe a CDN propagation issue.

I didn't use a link. I had an earlier version installed and when docker started, it prompted me to update.

For me WSL2 works well in version 2.1.4.0 (39357): https://i.imgur.com/Eyz3jL4.png
I upgraded from 2.1.2.0 via chocolatey.

Version 2.1.4.0 works great, again, for me the past hour. (Prompted to upgrade from 2.1.2.0, simply clicked OK) Ubuntu-18.04 running hyper-fast...

@daegalus - since build number of 2.1.4.0 is 39357, the correct download link should probably be https://download.docker.com/win/edge/39357/Docker%20Desktop%20Installer.exe

That is so odd. I am also running Ubuntu-18.04 LTS from the windows store. I don't see the WSL 2 Tech Preview (as shown in my above screenshot)

I upgraded docker and then rebooted with no luck. Did you guys do anything else?

I'll start by uninstalling docker altogether and installing the latest version of edge.

Things are still not working for me.

1. I completely uninstalled Docker, I even went into the AppData folder and blew away all remnants of Docker that I could find.
2. I installed Docker 2.1.4.0
   At this point, I waited for Docker to run and then right clicked on the little icon and there was no sign of WSL 2 Tech Preview
3. I uninstalled Ubuntu 18.04
4. I installed Ubuntu 18.04 and I set it as my default wsl in powershell, then I opened and setup Ubuntu 18.04

Still, no sign of WSL 2 Tech Preview

Anybody have any other ideas?

I've rebooted

Just throwing some things at the wall:

• Have you tried using the troubleshooter to run diagnostics?
• Under Settings...Command Line...is Enable experimental features on?
• Did you verify/set the default version of WSL to use for the new distro installations (wsl --set-default-version or manually wsl --set-version )?
• Anything in the Docker logs that might indicate a problem?

@coltenkrauter If you go to Settings and click Docker Engine, does it look like this?

The upgrade works for me and I wonder it your settings has "experimental": true in it.

@coltenkrauter Maybe a silly question, but which build of Windows do you have?

Encountering the same issue. WSL2 is not showing up on 2.1.4.0 (39357)

@stephen-turner

Windows Version 10.0.18362 Build 18362

I appreciate your time!

Apparently you are not in the fast ring. Your windows build is old, you need at least 18917 to have WSL 2:
https://docs.microsoft.com/en-us/windows/wsl/wsl2-install

Oh my word... #SlapsOwnFace

Thanks for recognizing that. Can't believe that skated past me. Time to update Windows.

I would like to know if this is supposed to be shown with Archlinux WSL 2 (https://github.com/yuk7/ArchWSL)? I am in Windows Build 18970 and with Docker Desktop 2.1.4.0 installed but cannot see the menu entry also.

Still having challenges with Docker Desktop 2.1.4.0 and WSL2 in that the window arrives but remains blank, failing to load. The docker deamon doesn't report as started. Have reverted back to build 2.1.2.0 in the meantime. Running Windows Fast Ring build 18999-1 and have WSL defaulted to run WSL2 with Ubuntu 18.04 LTS as per the documented recommendations.

Maybe, if this is going to be in play for the next 6 months before going GA with H120 someone can point me (users?) to a post about where to get better debug logs to pass on with issues rather than just version numbers of random things? Thanks

remove old docker, and install new docker desktop (solved)

I have run into similar issues to robertiansweetman. I have the latest Insider Preview on the Fast ring and WSL2 enabled for the Ubuntu (Default) which is 18.04 under the hood. I started with 2.1.4.0 (Edge) from one of the direct links above and I could at least see the WSL2 Tech Preview option in the menu and get to the "secret" config page that utilizes WSL2. After installing it has suggested upgrading from 2.1.4.0 to 2.1.6.0, but I waited until I had at least tried starting once from the menu, which did work. After upgrading the menu item disappeared though I did find under the General settings there was a toggle for the WSL2 based engine, but it failed to detect my WSL2 enabled Ubuntu VM (Default, but basically 18.04 under the hood), so I went through and created the specific Ubuntu-18.04 version from the Store and converted it to WSL2 (probably should have enabled WSL2 as the default earlier but hadn't thought I'd be making this many VMs to test it out).

Even with the Ubuntu-18.04 WSL2 enabled system present, the new 2.1.6.0 build is unable to detect it, and oddly it prompts me to enable WSL via the Windows Features, and when I follow those directions (copy and pasting the command it gives), the returned message is "Feature already enabled, no reboot required".

OK, after uninstalling and going back to 2.1.4.0 and setting my default WSL back to Ubuntu I was able to get it working again, and it even continued working after upgrading to 2.1.6.0 again. I found the "secret" to getting it working in my WSL2 containers was to grant them access under "Resources > WSL Integration", though initially after doing this it showed I had two Docker engines running according to the status bar at the lower left. After a system reboot and another upgrade it only shows 1 Docker engine status again.

I figured out I can switch between the contexts of default and wsl in Powershell, but once I set wsl I can't interact with the containers from Powershell, but if I set it back to default, WSL machines can run docker ps but can't pull/start containers. It also seems like the DockerCli command to switch to a specific engine or switchdaemon don't appear to be properly taking effect, perhaps because of a different location for the CLI/engine with the changes in the Tech Preview/Edge builds?

Docker Desktop (tech preview) break wsl..
Dockerd service/process use port 53 and prevent wsl to start

/cc @simonferquel

OK, after uninstalling and going back to 2.1.4.0 and setting my default WSL back to Ubuntu I was able to get it working again, and it even continued working after upgrading to 2.1.6.0 again. I found the "secret" to getting it working in my WSL2 containers was to grant them access under "Resources > WSL Integration", though initially after doing this it showed I had two Docker engines running according to the status bar at the lower left. After a system reboot and another upgrade it only shows 1 Docker engine status again.

I figured out I can switch between the contexts of default and wsl in Powershell, but once I set wsl I can't interact with the containers from Powershell, but if I set it back to default, WSL machines can run docker ps but can't pull/start containers. It also seems like the DockerCli command to switch to a specific engine or switchdaemon don't appear to be properly taking effect, perhaps because of a different location for the CLI/engine with the changes in the Tech Preview/Edge builds?

@dragon788 - finally got to the bottom of my own particular issue here:
#5326

Obviously it's a challenge to not conflate things so YMMV

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked