Ubuntu desktop team teases 'proof of concept' systemd on Windows Subsystem for Linux

Stop the rock, can't stop the rock, we can't stop the rock


Canonical may be working on introducing systemd to Ubuntu on Windows Subsystem for Linux (WSL), according to a post by Ubuntu Desktop Team Technical Leader Didier Roche.

Roche's remarks were posted on the Ubuntu Desktop Team Updates two days ago. "PoC of systemd on WSL at startup of an instance," he said, raising hopes (or fears) that the component will be introduced in a future WSL 2 update. The remark was first spotted by Phoronix.

Systemd manages services and other system software on Linux, and is widely used by the most popular distributions, such as Debian, Ubuntu, SUSE, and the Red Hat family. The original WSL did not support systemd for technical reasons, starting with the fact it had its own init process.

When WSL 2 was introduced, with a new container-based model for running Linux on Windows, supporting systemd seemed feasible (Linux distros running on Micrsoft's Hyper-V hypervisor have no problem with it) but Microsoft continued with its own init presumably for reasons related to the integration between WSL and the rest of Windows.

WSL 2 users though have frequently requested systemd support. The reasons are many and varied, but the lack of systemd does introduce friction for users familiar with other distros that include it. Canonical's Snap packaging system depends on systemd, and since Canonical regards Snap as the future of application deployment one can understand why the company is keen to have it supported in WSL, particularly now that GUI Linux applications are supported in Windows 11.

Another problem is that users do not always realise that commands they use like systemctl for managing services are actually part of systemd. As far as some are concerned, this is a bug in WSL 2, in this case because an attempt to start the SSH daemon gave the error, "System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down."

There are a number of workarounds to enable systemd on WSL 2 but an official solution would still be welcome.

It is important that systemd does not only run, but runs as PID 1, the first process in the operating system. A developer has come up with a project called genie to ensure this happens.

Then there's Distrod, which is described as "a systemd-based meta-distro for WSL2 that allows you to install Ubuntu, Arch Linux, Gentoo and many other distros with systemd in a minute, or make your current distro run systemd." We note such solutions are unofficial.

Distrod, one of several unofficial solutions for systemd on Windows Subsystem for Linux 2

Here's Distrod, one of several unofficial solutions for systemd on Windows Subsystem for Linux 2

Both projects work by introducing another container. Distrod, for example, "is a binary that creates a simple container that runs systemd as an init process, and starts your WSL sessions within that container." According to its author, even WSLg, for GUI desktop application support, works with Distrod. Genie, so called because it creates a systemd "bottle," also works with WSLg but the docs state that "Linux GUI apps started from the Windows Start Menu items created by WSLg will run outside the bottle."

Canonical is not Microsoft, of course, but has worked closely with the WSL team. There is little doubt that systemd in WSL 2 is a desirable feature for various users, at least as an option, so we will be watching progress with interest. ®


Other stories you might like

  • Ex-Qualcomm Snapdragon chief turns CEO at AI chip startup MemryX

    Meet the new boss

    A former executive leading Qualcomm's Snapdragon computing platforms has departed the company to become CEO at an AI chip startup.

    Keith Kressin will lead product commercialization for MemryX, which was founded in 2019 and makes memory-intensive AI chiplets.

    The company is now out of stealth mode and will soon commercially ship its AI chips to non-tech customers. The company was testing early generations of its chips with industries including auto and robotics.

    Continue reading
  • Aircraft can't land safely due to interference with upcoming 5G C-band broadband service

    Expect flight delays and diversions, US Federal Aviation Administation warns

    The new 5G C-band wireless broadband service expected to rollout on 5 January 2022 in the US will disrupt local radio signals and make it difficult for airplanes to land safely in harsh weather conditions, according to the Federal Aviation Administration.

    Pilots rely on radio altimeter readings to figure out when and where an aircraft should carry out a series of operations to prepare for touchdown. But the upcoming 5G C-band service beaming from cell towers threatens to interfere with these signals, the FAA warned in two reports.

    Flights may have to be delayed or restricted at certain airports as the new broadband service comes into effect next year. The change could affect some 6,834 airplanes and 1,828 helicopters. The cost to operators is expected to be $580,890.

    Continue reading
  • Canadian charged with running ransomware attack on US state of Alaska

    Cross-border op nabbed our man, boast cops and prosecutors

    A Canadian man is accused of masterminding ransomware attacks that caused "damage" to systems belonging to the US state of Alaska.

    A federal indictment against Matthew Philbert, 31, of Ottawa, was unsealed yesterday, and he was also concurrently charged by the Canadian authorities with a number of other criminal offences at the same time. US prosecutors [PDF] claimed he carried out "cyber related offences" – including a specific 2018 attack on a computer in Alaska.

    The Canadian Broadcasting Corporation reported that Philbert was charged after a 23 month investigation "that also involved the [Royal Canadian Mounted Police, federal enforcers], the FBI and Europol."

    Continue reading

Biting the hand that feeds IT © 1998–2021