NOTE: If you have Windows 11 there is now an official way to do this in WSL 2, use it if possible - see MS post here (WINDOWS 11 ONLY)
This guide will enable systemd
to run as normal under WSL 2. This will enable services like microk8s
, docker
and many more to just work
during a WSL session. Note: this was tested on Windows 10 Build 2004, running Ubuntu 20.04 LTS in WSL 2.
-
To enable
systemd
under WSL we require a tool calledsystemd-genie
-
Copy the contents of
install-sg.sh
to a new file/tmp/install-sg.sh
:cd /tmp wget --content-disposition \ "https://gist.githubusercontent.com/djfdyuruiry/6720faa3f9fc59bfdf6284ee1f41f950/raw/952347f805045ba0e6ef7868b18f4a9a8dd2e47a/install-sg.sh"
-
Make it executable:
chmod +x /tmp/install-sg.sh
-
Run the new script:
/tmp/install-sg.sh && rm /tmp/install-sg.sh
-
Exit the WSL terminal and shutdown the WSL env:
wsl --shutdown
-
To open a new WSL terminal with
systemd
enabled, run:wsl genie -s
-
Prove that it works:
sudo systemctl status time-sync.target
Works with minimal debugging, caution and patience. At the time of writing default script runs well on WSL2 Ubuntu 20.04 three units that had to be masked or dealt with can be found on the previously linked page : https://github.com/arkane-systems/genie/wiki/Systemd-units-known-to-be-problematic-under-WSL .
On the first run before debugging the message " Waiting for systemd....!!!" seems to take ages however give it at least a minute before you panic. It will load and show all service/units that are causing a delay at boot. when you deal with them it reduces startup significantly.
Thanks to the OP and other for their input.