This bug was fixed in the package wsl-setup - 0.2
---------------
wsl-setup (0.2) jammy; urgency=medium
* Systemd experimental support (LP: #1962556)
-- Didier Roche <didro...@ubuntu.com> Thu, 17 Mar 2022 16:08:44 +0100
** Changed in: wsl-setup (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wsl-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1962556
Title:
[FFe] WSL systemd experimental support
Status in wsl-setup package in Ubuntu:
Fix Released
Bug description:
WSL on Ubuntu 22.04 has a strecth goal to ship systemd experimental support.
This relies on 3 changes:
- a script started up on WSL VM boot, which is shipped as part of this
package to start systemd in its own namespace.
- a change in the ubuntu Windows launcher executable, which is then looking
for the boot= parameter in wsl.conf and if systemd experimental support is
enabled, starts any new commands into that systemd namespace
- an option in our OOBE installer, under advanced menu, disabled by default,
to change the boot= parameter in wsl.conf. The feature will be labeled as
experimental.
So, this experimental support won’t be enabled by default and paved the way
to have a discussion with Microsoft for potential limitations and how we can
get this to a wider audience in the long term.
This feature is long-awaited for WSL users.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wsl-setup/+bug/1962556/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
