Wsl: Please add the fact that WSL2 does not run systemd (or anything that systemd usually starts, like dbus-daemon)

[MedAnd]

As per feedback from @therealkenc on issue "WSL2: Service Fabric for Linux Installation Errors" - https://github.com/microsoft/WSL/issues/4178

---

Document Details

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

• ID: 57e78ef3-d2eb-1708-d319-be5c4d72274b
• Version Independent ID: 3f3f241f-6e72-859d-3d93-e115e2de0bfb
• Content: WSL 2 Frequently Asked Questions
• Content Source: WSL/wsl2-faq.md
• Product: windows-subsystem-for-linux
• GitHub Login: @mscraigloewen
• Microsoft Alias: mscraigloewen

[MedAnd]

Re: systemd, I should clarify that I'm not opinionated about how software runs on WSL2 as long as it installs, runs and is supported one day.

So far two important MS packages I tested do not even install... Service Fabric for Linux and the Azure Monitor for Linux (aka OMS for Linux agent). I assume SQL Server 2019 Preview for Linux does not work either.... if the issue is the same in all cases why not unblock this scenario, why not get existing MS software running on WSL2?

As I'm not sure how else to engage with the team hence this feedback, but my point is if WSL2 is going to be useful & production grade one day, there must be guidance on getting packages such as Service Fabric, OMS Agent, SQL Server etc working and supported?

For example create WSL2 compliance guidelines, how to port existing solutions (explaining how not to use systemd and instead use approach x), would love to see a blog post from @mscraigloewen @benhillis talking about this vision and road-map 😊

PS. The potential of WSL2 is evident... I just want my favorite MS Linux software to run on it!

[gsilvestri]

Why in the hell You are using MS Windows sofware ported to Linux in a virtual environment inside a Windows 10 installation in the first place??

Do You know that the more you port the more problems can arise??

_Use Windows software on Windows and Linux software on Linux_: the WSL 2 technology stack is meant to give You the best opportunities of both frameworks not to mix them to make the impossible.

This is my humble opinion, however judging by the problems You arise I think I'm on the right thesis here...

_Have a productive week_

[cerebrate]

Although if that's going to be added, it's probably also worth mentioning that while it may not run systemd by default, it's Not Hard to make it run systemd. 😊

[MedAnd]

Best for the WSL2 team to comment but if it’s simple, wondering why not support this through wsl config? 😊

[khuongduybui]

You may check out https://github.com/arkane-systems/genie

[jovton]

The following post is about enabling snap, but since is needs systemd, it is quite informative. It is also very short: https://forum.snapcraft.io/t/running-snaps-on-wsl2-insiders-only-for-now/13033. Works really well.