ubuntu-wsl2-systemd-script icon indicating copy to clipboard operation
ubuntu-wsl2-systemd-script copied to clipboard

[Does not work anymore!] Script to enable systemd support on current Ubuntu WSL2 images

Results 51 ubuntu-wsl2-systemd-script issues
Sort by recently updated
recently updated
newest added

Hi, I had the same problem like described in https://github.com/microsoft/wslg/issues/238 ` xclock Error: Can't open display: :0` and the only solution for me was https://github.com/microsoft/wslg/issues/238#issuecomment-847804992 `export DISPLAY=:0 sudo rm -rf...

When first attempting `snap` after using install script, the system gave me an error: ```diff - error: too early for operation, device not yet seeded or device model not acknowledged...

Script run OK. Restarted. Call systemctl: blk-availability.service loaded active exited Availability of block devices dbus.service loaded active running D-Bus System Message Bus keyboard-setup.service loaded active exited Set the console keyboard...

The multi-user target on systemd runs a lot of needed services as cron and fix the snap mounting after reboot, which is also a "all snap packages broken" issue.

I followed the instructions and running `systemctl` lists units, but `sudo systemctl` returns `"Failed to connect to bus: No data available"`

* VSCode WSL-remote fails: fixes #33 * `/bin/login` does not support environment variable setting via the command line when used with the `-f` flag that allows login to operate without...

The wsl cannot be started due to this error after running the script nsenter: cannot open /proc/30/ns/time: No such file or directory