WSL2 Support for Windows Server 2019

[kamalmaheshwari]

What's the plan to support WSL2 on Windows Server 2019? We are eagerly waiting to run Linux containers on Windows Server 2019 platform

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 233355e5-2fe3-a827-a1bf-ef1ae3ee5f36
• Version Independent ID: 991e4422-12dc-68a6-21a6-9741710fd47a
• Content: WSL 2
• Content Source: WSL/wsl2-index.md
• Product: dev-environment
• Technology: windows-subsystem-for-linux
• GitHub Login: Craig Loewen (@craigloewen-msft)
• Microsoft Alias: crloewen

[TBBle]

Since WSL2 was introduced well after Windows Server 2019, I cannot see that it would be backported to an LTSC version. I haven't confirmed this, but the Windows Server, version 2004 SAC release should have WSL2 support. The Windows Server, version 2004 SAC release notes are focused on the container image release, even though ISO releases and cloud provider VMs have been appearing since May.

[chara1ampos]

Paul "TBBle" Hampson (@TBBle) the 2004 version has no desktop support. Only LTSC versions have desktop support. It is a sad situation that we have to wait until year 2022 or 2025 for a new Windows Server LTSC, just to be able to use WSL2, by which time it may well be obsolete. I will have to downgrade a 28 core workstation to regular Windows 10 just to use WSL2 and CUDA, but then I will lose the ability for multiple users to be logged in. Microsoft needs to do (a lot) better if they want Windows Server to keep up with Linux.

[TBBle]

Harry (@chara1ampos): Given that it's 2-3 years between LTSC releases, and Windows Server 2019 was based on Windows 10 1809, there is a strong expectation of an LTSC release in 2021.

You could jump forward to the vNext LTSC preview, perhaps? Given the timing, this suggests we might get a Windows Server LTSC release paired with Windows 10 21H1, as there's been no indication yet that 21H1 has forked from the "active development builds".

[therealdandecker]

I can confirm after testing tonight WIndows Server 2019 Preview that even in the preview release of 2004 LTSC with desktop experience (I typically use server core but wanted to see) that WSL2 is not functioning; I did an install with the same setup as on my windows 10 box where I have it running and could not get it to run either Docker or Ubuntu in Version 2.

I did read that the Linux kernel was not included in the preview releases, but I am unclear as to what that meant, i.e. is it not supported or simply its moved beyond preview releases.

[tonytwostep]

Also can confirm the above. I'm on the latest preview release of Server 2019 (based on 2004)

The commands
wsl --set-default-version 2 or wsl --set-version <distro> 2
just output the help message.

Docker EE doesn't use WSL2 and when attempting to force it or Docker Desktop to do so it errors out saying it cannot parse the output of the wsl command (which is just the help message). Even tried building the WSL kernel from source and that didn't work...

[TBBle]

Yeah, it sounds like the wsl binary is still from WSL1, if it doens't know the --set-default-version parameter, which suggests the whole subsystem is WSL 1 still.

Same problem has been reported at https://techcommunity.microsoft.com/t5/windows-server-insiders/wsl-2-not-working-after-installing-20262/m-p/1928823.

Apparently it used to work: https://techcommunity.microsoft.com/t5/windows-server-insiders/how-to-install-wsl-2-on-windows-server/m-p/858359

[awakecoding]

I would be interested as well, especially if the Linux MongoDB container works correctly with a docker volume under WSL2. I have a multi-container application using Windows containers on Windows, but there are critical issues that have been known for years that prevent MongoDB (and possibly other databases) from working correctly inside Windows containers. At this point I don't care if we have to use Windows containers or Linux containers, all I really want are containers on Windows Server 2019.

[therealdandecker]

WSL2 is the only way I think. The windows containers are useful but severely limited in terms of availability compared with Linux. The ability to run Linux containers “natively” in Windows Server to me is critical. The fact that it is not included in the next LTSC release is very surprising as that means (potentially) it will not be available mainstream until 2024 (assuming same release schedule.) Best, Dan Decker

…

________________________________ From: Marc-André Moreau <notifications@github.com> Sent: Wednesday, December 9, 2020 1:45:41 PM To: MicrosoftDocs/WSL <WSL@noreply.github.com> Cc: Dan Decker <daniel.decker1@gmail.com>; Comment <comment@noreply.github.com> Subject: Re: [MicrosoftDocs/WSL] WSL2 Support for Windows Server 2019 (#678) I would be interested as well, especially if the Linux MongoDB container was work correctly with a docker volume under WSL2. I have a multi-container application using Windows containers on Windows, but there are critical issues that have been known for years that prevent MongoDB (and possibly other databases) from working correctly inside Windows containers. At this point I don't care if we have to use Windows containers or Linux containers, all I really want are containers on Windows Server 2019. — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#678 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACSWFW47MOQYRLX2SUCJJB3ST7AVLANCNFSM4M7VM5SA>.

[awakecoding]

Dan Decker (@therealdandecker) I agree it would definitely be better to have an officially supported option to run Linux containers on the latest LTSC release of Windows Server with a GUI. If WSL2 is added only on the upstream semi-annual channel, it would be very difficult to get customers to use it, as a lot of people still just want Windows Server + GUI and RDP (even though it may seem like a bad thing, it's what a lot of people do).

But realizing that getting Linux containers to run properly (including databases that are very tied to specific filesystem i/o calls) on Windows Server, I would settle for simply using Windows containers on Windows, as this is the only native option. However, even Windows containers on Windows suffer from severe limitations and critical issues, so we are stuck with no good option in the end.

WSL2 + proper database support, or Windows containers on Windows with bug fixes for the issues preventing databases from working, but we've got to have at least one of the two and fast. Otherwise, this really means that if you can put up with the long list of limitations that come with Windows containers, you are still stuck without containerized database support, which is ridiculous.

docker-library/mongo#385
microsoft/Windows-Containers#37

[therealdandecker]

How does support for feature requests like this work? Is it possible to open a ticket while LTSC is still in preview mode? Has it been included in one of the semi-annual release channels and just not here? I have seen things online but not fully tested WSL2 in SAC. Best, Dan Decker

…

________________________________ From: Marc-André Moreau <notifications@github.com> Sent: Wednesday, December 9, 2020 2:34:11 PM To: MicrosoftDocs/WSL <WSL@noreply.github.com> Cc: Dan Decker <daniel.decker1@gmail.com>; Mention <mention@noreply.github.com> Subject: Re: [MicrosoftDocs/WSL] WSL2 Support for Windows Server 2019 (#678) @therealdandecker<https://github.com/therealdandecker> I agree it would definitely be better to have an officially supported option to run Linux containers on the latest LTSC release of Windows Server with a GUI. If WSL2 is added only on the upstream semi-annual channel, it would be very difficult to get customers to use it, as a lot of people still just want Windows Server + GUI and RDP (even though it may seem like a bad thing, it's what a lot of people do). But realizing that getting Linux containers to run properly (including databases that are very tied to specific filesystem i/o calls) on Windows Server, I would settle for simply using Windows containers on Windows, as this is the only native option. However, even Windows containers on Windows suffer from severe limitations and critical issues, so we are stuck with no good option in the end. WSL2 + proper database support, or Windows containers on Windows with bug fixes for the issues preventing databases from working, but we've got to have at least one of the two and fast. Otherwise, this really means that if you can put up with the long list of limitations that come with Windows containers, you are still stuck without containerized database support, which is ridiculous. docker-library/mongo#385<docker-library/mongo#385> microsoft/Windows-Containers#37<microsoft/Windows-Containers#37> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#678 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACSWFW7AUZS2KS7K4A2YZ7LST7GLHANCNFSM4M7VM5SA>.

[den-run-ai]

Scott Hanselman (@shanselman) I really wanted to use WSL2 that you advertised. But there is no VM with Windows Server + WSL2 that I can run with it in the cloud! I guess going back to Linux ¯\_(ツ)_/¯

[TBBle]

There is a ticket specifically for WSL2 on the now-announced Windows Server LTSC 2022 (late 2021) microsoft/WSL#6301. The current ticket, being a report against the docs, is probably not bringing much visibility to a feature request.

The documentation does currently correctly state that you need a newer build of windows for WSL2 than Windows Server 2019, and actually explicitly says "Windows 10" is the requirement; the Windows Server instructions don't mention WSL2 at all, but no released Windows Server LTSC version has a new enough kernel build for WSL2 anyway.

[awakecoding]

Paul "TBBle" Hampson (@TBBle) WSL2 + Linux containers on Windows Server appear to be dead in the water, unfortunately. I managed to get a clearer statement answer twitter: https://twitter.com/WSV_GUY/status/1358522964052832257?s=19

So the current thinking is that WSL2 is great as a developer tool on Windows 10, but supporting it officially on Windows Server would give people the wrong idea since they might start using it for production workloads.

The thing is that this is precisely what most people waiting for WSL2 on Windows Server want to do it with: run production workloads. I don't see a reason why it would not be possible to make it run unofficially, but it'll always be an unsupported option without Microsoft's stamp of approval.

Unless someone can convince Microsoft otherwise, I think WSL2 will remain a Windows 10 developer toy, unfortunately. It's just very frustrating because WSL2 correctly handles filesystem operations required by databases, so it's almost perfect as-is, if only it could be made official.

[therealdandecker]

That’s the end of that I guess. Surprised in a way that the folks there making these decisions do not see WSL2 as a viable path for production workloads when WSL2 is using the Hyper-V framework. I am more surprised I think that it’s framed as a “wholly bad idea” rather than something that Microsoft just does not want to support at this time from a strategic standpoint (production WSL2.) I would think its a matter of product support / maintenance but there must be other things under the covers they think make it less reliable for production workloads.

…

________________________________ From: Marc-André Moreau <notifications@github.com> Sent: Sunday, March 7, 2021 10:16:17 AM To: MicrosoftDocs/WSL <WSL@noreply.github.com> Cc: Dan Decker <daniel.decker1@gmail.com>; Mention <mention@noreply.github.com> Subject: Re: [MicrosoftDocs/WSL] WSL2 Support for Windows Server 2019 (#678) @TBBle<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FTBBle&data=04%7C01%7C%7C83af0822dc444995ceaf08d8e17bf5d5%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637507269816436905%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=yU3naHjYPuRainhtQX77EdJpImZPexPFMsYraShVRgU%3D&reserved=0> WSL2 + Linux containers on Windows Server appear to be dead in the water, unfortunately. I managed to get a clearer statement answer twitter: https://twitter.com/WSV_GUY/status/1358522964052832257?s=19<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftwitter.com%2FWSV_GUY%2Fstatus%2F1358522964052832257%3Fs%3D19&data=04%7C01%7C%7C83af0822dc444995ceaf08d8e17bf5d5%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637507269816446903%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=gGifLn8YR26%2FFAguKzzBS%2F6OWASkGuh0PwncntCHGHI%3D&reserved=0> So the current thinking is that WSL2 is great as a developer tool on Windows 10, but supporting it officially on Windows Server would give people the wrong idea since they might start using it for production workloads. The thing is that this is precisely what most people waiting for WSL2 on Windows Server want to do it with: run production workloads. I don't see a reason why it would not be possible to make it run unofficially, but it'll always be an unsupported option without Microsoft's stamp of approval. Unless someone can convince Microsoft otherwise, I think WSL2 will remain a Windows 10 developer toy, unfortunately. It's just very frustrating because WSL2 correctly handles filesystem operations required by databases, so it's almost perfect as-is, if only it could be made official. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FWSL%2Fissues%2F678%23issuecomment-792294928&data=04%7C01%7C%7C83af0822dc444995ceaf08d8e17bf5d5%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637507269816446903%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=YmUDOVbS7cns1okbTqOcVpaADCURiJ3ay3LqZ63zWCo%3D&reserved=0>, or unsubscribe<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACSWFWYA5HGJSQMUPBMHD7DTCOKEDANCNFSM4M7VM5SA&data=04%7C01%7C%7C83af0822dc444995ceaf08d8e17bf5d5%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637507269816456895%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=gQyeUFLDnqbu0YelE42M2ZMowib%2BZgSubusI2E4yMkw%3D&reserved=0>.