Fix #56.

After WSL 0.60.0 release, microsoft switched to bind mount the /tmp/.X11-unix rather than symlink it as they previously do. This breaks wslg in Distrod for latest WSL on MS Store.

Distrod should bind mount for WSL 0.60.0, and keep the symlink strategy for older versions of WSL.

I've tested the fix on WSL 0.60.0, WSL 0.58.3 and in-box WSL, all of them worked ok.

EDIT: Before this PR is merged, you may use opt tar packaged by me for a while 👉 opt_distrod.tar.gz

Is it safe to use a different shell with a user? As the default shell is set to /opt/distrod/alias/usr/bin/bash and I'd like to use fish as the shell for my default user.

Is it changing it to /usr/bin/fish okay, or will this break any distrod functionality?

I see weston crashing in "dmesg -Tw" after enabling wsl-distrod. I wrote an issue report to Microsoft's WSLg repository too a week ago.

https://github.com/microsoft/wslg/issues/564

There I used https://github.com/DamionGans/ubuntu-wsl2-systemd-script to enable systemd in WSL 2 Ubuntu-20.04 distro. Somehow the problem is related to Windows task scheduler because when manually starting WSL 2, there is no problem with weston.

Hi, when I boot up the first shell in Ubuntu Community Preview, I get: grep: /proc/sys/fs/binfmt_misc/WSLInterop: No such file or directory grep: /proc/sys/fs/binfmt_misc/WSLInterop: No such file or directory In the stable Ubuntu, however, I get: Failed to connect to bus: No such file or directory Failed to connect to bus: No such file or directory

However, nothing seems to be broken.

steps to reproduce: wsl --shutdown and then open up a new shell

Following the README, choosing Option 1 i checked that default for WSL is version 2, then downloaded the .zip linked in Step 1 and executed the .exe to run Distrod. The following is the (self-explaining) output:

        ██████╗ ██╗███████╗████████╗██████╗  ██████╗ ██████╗
        ██╔══██╗██║██╔════╝╚══██╔══╝██╔══██╗██╔═══██╗██╔══██╗
        ██║  ██║██║███████╗   ██║   ██████╔╝██║   ██║██║  ██║
        ██║  ██║██║╚════██║   ██║   ██╔══██╗██║   ██║██║  ██║
        ██████╔╝██║███████║   ██║   ██║  ██║╚██████╔╝██████╔╝
        ╚═════╝ ╚═╝╚══════╝   ╚═╝   ╚═╝  ╚═╝ ╚═════╝ ╚═════╝
=================================================================================
Thanks for trying Distrod! Choose your distribution to install.
You can install a local .tar.xz, or download an image from linuxcontainers.org.

* linuxcontainers.org is a vendor-neutral project that offers distro images for
  containers, which is not related to Distrod. LXC/LXD is one of its projects.
  BTW, you can run Systemd with distrod, so you can try LXC/LXD with distrod!
=================================================================================
[1] Use a local tar.xz file
[2] Download an image from linxcontainers.org
[Distrod] Choose the way to get a distro image from the list above.
[Distrod] Type the name or the index of your choice.
[Default: Download an image from linxcontainers.org]: 2
[Distrod] Fetching from linuxcontainers.org...
[1] almalinux
[2] alpine
[3] alt
[4] amazonlinux
[5] apertis
[6] archlinux
[7] busybox
[8] centos
[9] debian
[10] devuan
[11] fedora
[12] funtoo
[13] gentoo
[14] kali
[15] mint
[16] opensuse
[17] openwrt
[18] oracle
[19] plamo
[20] pld
[21] rockylinux
[22] sabayon
[23] springdalelinux
[24] ubuntu
[25] voidlinux
[Distrod] Choose a linuxcontainers.org image from the list above.
[Distrod] Type the name or the index of your choice.
[Default: ubuntu]: 11
[Distrod] Fetching from linuxcontainers.org...
[1] 33
[2] 34
[3] 35
[Distrod] Choose a version from the list above.
[Distrod] Type the name or the index of your choice.
[Default: 35]: 35
[Distrod] Fetching from linuxcontainers.org...
[Distrod] Downloading 'https://images.linuxcontainers.org/images/fedora/35/amd64/default/20211118_20:33/rootfs.tar.xz'...
  [00:00:13] [####################################################] 85.36MiB/85.36MiB (6.23MiB/s, 0s)
[Distrod] Download done.
[Distrod] Unpacking and merging the given rootfs to the distrod rootfs. This may take a while...
[Distrod] Now Windows is installing the new distribution. This may take a while...
[Distrod] Distrod is installed in %LocalAppData%\Distrod
[Distrod] Done!
[Distrod] Please input the new Linux user name. This doesn't have to be the same as your Windows user name.
[Input user name]: cldsrphl
Changing password for user cldsrphl.
New password:
Retype new password:
passwd: all authentication tokens updated successfully.
[Distrod] Querying the generated uid. This may take some time depending on your machine.
[Distrod] Initializing the new Distrod distribution. This may take a while...
[Distrod] Distrod has been enabled. Now your shell will start under systemd.
[Distrod] Setting the default user to uid: 1000
[Distrod] Installation of Distrod is now complete.
[Distrod][ERROR] Failed to run the given command in the Systemd container. Fall back to normal WSL2 command execution without using Systemd. Failed to launch the distro.

Caused by:
    0: Failed to make mountpoint shared.
    1: Failed to make the /tmp mountpoint shared.
    2: EINVAL: Invalid argument
[cldsrphl@D11MMWNX0SDPS66ENGUS distrod_wsl_launcher-x86_64]$

The following is (redacted/freed from personal data) info about my system - commands executed in CMD:

1. SystemInfo:

C:\Users\cldsrphl>systeminfo
Host Name:                 D11MMWNX0SDPS66
OS Name:                   Microsoft Windows 10 Pro
OS Version:                10.0.19044 N/A Build 19044
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free

Original Install Date:     9/16/2021, 3:20:20 AM

System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.
                           [01]: AMD64 Family 16 Model 2 Stepping 3 AuthenticAMD ~2300 Mhz

Windows Directory:         C:\Windows
System Directory:          C:\Windows\system32
Boot Device:               \Device\HarddiskVolume1
System Locale:             en-us;English (United States)
Input Locale:              en-us;English (United States)
Time Zone:                 (UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna
Total Physical Memory:     7,678 MB
Available Physical Memory: 1,221 MB
Virtual Memory: Max Size:  15,337 MB
Virtual Memory: Available: 2,595 MB
Virtual Memory: In Use:    12,742 MB
Page File Location(s):     C:\pagefile.sys
Domain:                    WORKGROUP
Logon Server:              \\D11MMWNX0SDPS66
Hotfix(s):                 5 Hotfix(s) Installed.
                           [01]: KB5006365
                           [02]: KB5003791
                           [03]: KB5007186
                           [04]: KB5006753
                           [05]: KB5005699
Network Card(s):           4 NIC(s) Installed.
                           [01]: Realtek 8185 Extensible 802.11b/g Wireless Device
                                 Connection Name: Wi-Fi
                                 Status:          Media disconnected
                           [02]: Broadcom NetXtreme 57xx Gigabit Controller
                                 Connection Name: Ethernet
                                 DHCP Enabled:    Yes
                                 DHCP Server:     192.168.2.1
                                 IP address(es)
                                 [01]: 192.168.2.136
                                 [02]: fe80::545:81ae:63c6:a9fc
                                 [03]: 2003:cd:70c:bd6f:c551:a499:d529:d25c
                                 [04]: 2003:cd:70c:bd6f:7cfb:63a1:995f:7c7
                                 [05]: 2003:cd:70c:bd6f:545:81ae:63c6:a9fc
                           [03]: VirtualBox Host-Only Ethernet Adapter
                                 Connection Name: VirtualBox Host-Only Network
                                 DHCP Enabled:    No
                                 IP address(es)
                                 [01]: 192.168.56.1
                                 [02]: fe80::34ba:1c8b:7b2:8608
                           [04]: Bluetooth Device (Personal Area Network)
                                 Connection Name: Bluetooth Network Connection 2
                                 Status:          Media disconnected
Hyper-V Requirements:      A hypervisor has been detected. Features required for Hyper-V will not be displayed.

2. WSL --status:

C:\Users\cldsrphl>wsl --status
Default Distribution: Ubuntu-20.04
Default Version: 2

Windows Subsystem for Linux was last updated on 11/3/2021
WSL automatic updates are on.

Kernel version: 5.10.60.1

3. WSL --list:

C:\Users\cldsrphl>wsl --list
Windows Subsystem for Linux Distributions:
Ubuntu-20.04 (Default)
Distrod
Ubuntu

4. WSL -d distrod:

C:\Users\cldsrphl>wsl -d distrod
[Distrod][ERROR] Failed to run the given command in the Systemd container. Fall back to normal WSL2 command execution without using Systemd. Failed to launch the distro.

Caused by:
    0: Failed to make mountpoint shared.
    1: Failed to make the /tmp mountpoint shared.
    2: EINVAL: Invalid argument
[cldsrphl@D11MMWNX0SDPS66ENGUS cldsrphl]$

5. SystemCtl status (executed inside distrod):

[cldsrphl@D11MMWNX0SDPS66ENGUS cldsrphl]$ systemctl status
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down

Please advise how to go on, what commands/procedures might help to investigate the issue.

Note: I was already running the default Ubuntu wsl-distro as installed originally via wsl --install (not the Ubuntu-20.04 - this one was added later). After the initial setup (specifying user/passwd) i ran sudo apt update and sudo apt full-upgrade - the latter was processing when i executed distrod - mentioning in case there is a need to not have a wsl-distro already running when doing the install via distrod.

I will now try Option 2, by applying it to the fresh setup and updated Ubuntu wsl-distro.

Describe the bug

Bug happens when I try to run systemctl with --user flag

normal systemctl enable service works fine but I would like to run as user, is this possible?

Steps to reproduce

systemctl --user enable service

Expected behavior

No response

Windows version

21H2 19044.1348

Linux kernel version

Linux win 5.10.60.1-microsoft-standard-WSL2 #1 SMP Wed Aug 25 23:20:18 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Distro

Ubuntu Focal

Logs

a

additional comment

No response

Describe the bug

After I installed Distrod, ubuntu focal, I tried installing some programs, but the internet speed is crazy slow.

I had normal WSL 2 installed previously, and the internet speed was fine, just wondering if this issue is well known or?

Kindly

Steps to reproduce

Install distrod, run a sudo apt-get install command

Expected behavior

No response

Windows version

21H2 19044.1348

Linux kernel version

Linux win 5.10.60.1-microsoft-standard-WSL2 #1 SMP Wed Aug 25 23:20:18 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Distro

Ubuntu 20.04

Logs

.

additional comment

No response

I have followed instructions and installed Debian with distrod, now i've tried to install docker-ce-cli

manually dockerdis running but service cannot be started, how can i debug or analyse more?

systemctl status docker.service
● docker.service - Docker Application Container Engine
     Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Thu 2021-11-25 19:24:50 CET; 32s ago
TriggeredBy: ● docker.socket
       Docs: https://docs.docker.com
    Process: 2930 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
   Main PID: 2930 (code=exited, status=1/FAILURE)

Nov 25 19:24:50 md3fhv6c systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Nov 25 19:24:50 md3fhv6c systemd[1]: Stopped Docker Application Container Engine.
Nov 25 19:24:50 md3fhv6c systemd[1]: docker.service: Start request repeated too quickly.
Nov 25 19:24:50 md3fhv6c systemd[1]: docker.service: Failed with result 'exit-code'.
Nov 25 19:24:50 md3fhv6c systemd[1]: Failed to start Docker Application Container Engine.
Nov 25 19:25:16 md3fhv6c systemd[1]: docker.service: Start request repeated too quickly.
Nov 25 19:25:16 md3fhv6c systemd[1]: docker.service: Failed with result 'exit-code'.
Nov 25 19:25:16 md3fhv6c systemd[1]: Failed to start Docker Application Container Engine.

I installed ArchLinux using Distrod. I have enabled it upon being given a prompt. I install xorg-server and xorg-xinit. I installed lightdm and lightdm-gtk-greeter and enabled it using systemctl enable lightdm. I also installed qtile using pacman -S qtile. After that, to start lightdm at startup, I did systemctl reboot. I got the following error:

Hangup [Distrod][ERROR] Failed to spawn the command. Caused by: status.code() is None unexpectedly.

I then tried to start x server manually by doing startx which gave the following error: Xorg.1.log

I had also install alacritty terminal emulator and when I ran alacritty, it worked fine and a terminal instance spawned.

I also tried starting qtile directly by running qtile start but got the error

2021-11-22 16:49:34,139 libqtile core.py:init():L106 not starting; existing window manager Weston WM Traceback (most recent call last): File "/usr/sbin/qtile", line 33, in sys.exit(load_entry_point('qtile==0.18.1', 'console_scripts', 'qtile')()) File "/usr/lib/python3.9/site-packages/libqtile/scripts/main.py", line 55, in main options.func(options) File "/usr/lib/python3.9/site-packages/libqtile/scripts/start.py", line 87, in start q = make_qtile(options) File "/usr/lib/python3.9/site-packages/libqtile/scripts/start.py", line 50, in make_qtile kore = libqtile.backend.get_core(options.backend) File "/usr/lib/python3.9/site-packages/libqtile/backend/init.py", line 15, in get_core return importlib.import_module(f"libqtile.backend.{backend}.core").Core(*args) File "/usr/lib/python3.9/site-packages/libqtile/backend/x11/core.py", line 107, in init raise ExistingWMException(existing_wmname) libqtile.backend.x11.core.ExistingWMException: Weston WM

meaning that Weston WM (which I guess wsl is built on) was already running

I am on windows build 22504.1010

System: Windows 10 Pro, WSL version 2. Here's the log:

[Distrod] Choose a linuxcontainers.org image from the list above.
[Distrod] Type the name or the index of your choice.
[Default: ubuntu]: 4
[Distrod] Fetching from linuxcontainers.org...
[1] 2.0.20210525.0
[2] current
[Distrod] Choose a version from the list above.
[Distrod] Type the name or the index of your choice.
[Default: current]:
[Distrod] Fetching from linuxcontainers.org...
[Distrod] Downloading 'https://images.linuxcontainers.org/images/amazonlinux/current/amd64/default/20211109_05:09/rootfs.tar.xz'...
  [00:00:02] [#########################################################################] 52.27MiB/52.27MiB (25.77MiB/s, 0s)
[Distrod] Download done.
[Distrod] Unpacking and merging the given rootfs to the distrod rootfs. This may take a while...
[Distrod] Now Windows is installing the new distribution. This may take a while...
Unspecified error
[Distrod][ERROR] Failed to register the distribution.
Caused by:
    Failed: cmd.exe /C wsl --import Distrod %LocalAppData%\Distrod "C:\\Users\\me\\AppData\\Local\\Temp\\.tmpdmQenr\\install.tar.gz"

I followed the steps in Option 2 of README.

Step 1, downloading and installing scripts succeeded.

In step 2, I got this error.

[Distrod][WARN] whoami.exe had an error:
[Distrod][ERROR] Failed to enable the autostart on Windows boot.

Caused by:
    wslpath -w '/tmp/.tmpTQ234D' exited with error. stderr: /bin/wslpath: /tmp/.tmpTQ234D: Invalid argument

I checked whoami.exe and wslpath, and I found these commands do not work with sudo.

> /mnt/c/Windows/System32/whoami.exe
desktop-xxxxxx\tomyk
~
> sudo /mnt/c/Windows/System32/whoami.exe
((no output with exit status code 255))

> wslpath -w /tmp/.tmpTQ234D
\\wsl.localhost\Ubuntu\tmp\.tmpTQ234D
~
> sudo wslpath -w /tmp/.tmpTQ234D
wslpath: /tmp/.tmpTQ234D: Invalid argument

This is fixed by running /opt/distrod/bin/distrod enable, wsl --termiante Ubuntu, and wsl zsh, then run /opt/distrod/bin/distrod enable --start-on-windows-boot again. Here these commands return the same results with and without sudo.

I suggest to put instructions to restart WSL2 for --start-on-windows-boot if it fails.

Describe the bug

I try to make my Nixos Distro Run Systemd with the second method.

Steps to reproduce

It'run on my Nixos on wsl.

I do what is written on the paragraph "Option 2: Make your Current Distro Run Systemd"

curl -L -O "https://raw.githubusercontent.com/nullpo-head/wsl-distrod/main/install.sh"
chmod +x install.sh

I've change install.sh mkdir become mkdir -p in order to fix the following problem: can't create the file sudo ./install.sh install It works

/opt/distrod/bin/distrod enable --start-on-windows-boot doesn't work. I need root permission.

sudo /opt/distrod/bin/distrod enable --start-on-windows-boot

[Distrod][WARN] Faled to disable systemd-resolved.service. Error: Failed to parse unit file '"/etc/systemd/system/systemd-resolved.service"'.

Caused by: description() is deprecated; use Display: No directives in the file [Distrod][ERROR] Failed to initialize the rootfs.

Caused by: 0: Failed to create per-user WSL envs load script. 1: Failed to create HostPath("/etc/profile.d/distrod-user-wsl-envs.sh") 2: No such file or directory (os error 2)

It doesn't work. I've already done that with Debian on WSL and it has worked fine. That is a problem specific to Nixos

Expected behavior

No response

Windows version

windows 11

Linux kernel version

Linux nixos 5.15.79.1-microsoft-standard-WSL2 #1 SMP Wed Nov 23 01:01:46 UTC 2022 x86_64 GNU/Linux

Distro

Nixos

How did you install that distro?

Installed by Distrod wizard

Logs

I've used the second option I haven't launch Distrod. I've tried the first option, but it has worked as I gived the tar.something file but that is another problem.

additional comment

No response

Describe the bug

I don't know if these failures are serious but after an upgrade to systemd 102 and distrod 0.1.7 with archlinux, my system is shown as degraded because of 4 services which have failed.

Steps to reproduce

1. updade wsl with wsl-update
2. updade archlinux
3. update distrod

Expected behavior

Before update, system was fine (no service failures).

Windows version

Windows 10 version 21H2 (19044.2251)

Linux kernel version

Linux HOSTNAME 5.10.102.1-microsoft-standard-WSL2 #1 SMP Wed Mar 2 00:30:59 UTC 2022 x86_64 GNU/Linux

Distro

Archlinux (rollling)

How did you install that distro?

Installed by Distrod wizard

Logs

$ systemctl status --failed
× systemd-sysctl.service - Apply Kernel Variables
     Loaded: loaded (/usr/lib/systemd/system/systemd-sysctl.service; static)
     Active: failed (Result: exit-code) since Tue 2022-12-13 09:26:19 CET; 33min ago
       Docs: man:systemd-sysctl.service(8)
             man:sysctl.d(5)
    Process: 123 ExecStart=/usr/lib/systemd/systemd-sysctl (code=exited, status=243/CREDENTIALS)
   Main PID: 123 (code=exited, status=243/CREDENTIALS)

× systemd-tmpfiles-clean.service - Cleanup of Temporary Directories
     Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-clean.service; static)
    Drop-In: /run/systemd/system/systemd-tmpfiles-clean.service.d
             └─exclude_wslg_sockets.conf
     Active: failed (Result: exit-code) since Tue 2022-12-13 09:41:48 CET; 17min ago
TriggeredBy: ● systemd-tmpfiles-clean.timer
       Docs: man:tmpfiles.d(5)
             man:systemd-tmpfiles(8)
    Process: 1226 ExecStart=systemd-tmpfiles --clean --exclude-prefix=/tmp/.X11-unix (code=exited, status=243/CREDENTIA>
   Main PID: 1226 (code=exited, status=243/CREDENTIALS)

× systemd-tmpfiles-setup-dev.service - Create Static Device Nodes in /dev
     Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup-dev.service; static)
     Active: failed (Result: exit-code) since Tue 2022-12-13 09:26:19 CET; 33min ago
       Docs: man:tmpfiles.d(5)
             man:systemd-tmpfiles(8)
    Process: 132 ExecStart=systemd-tmpfiles --prefix=/dev --create --boot (code=exited, status=243/CREDENTIALS)
   Main PID: 132 (code=exited, status=243/CREDENTIALS)

× systemd-tmpfiles-setup.service - Create Volatile Files and Directories
     Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static)
    Drop-In: /run/systemd/system/systemd-tmpfiles-setup.service.d
             └─exclude_wslg_sockets.conf
     Active: failed (Result: exit-code) since Tue 2022-12-13 09:26:19 CET; 33min ago
       Docs: man:tmpfiles.d(5)
             man:systemd-tmpfiles(8)
    Process: 147 ExecStart=systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev --exclude-prefix=/tmp/.X11-u>
   Main PID: 147 (code=exited, status=243/CREDENTIALS)

additional comment

No response

Microsoft will format a user's folder as "C:\Users\FirstName LastName" in some circumstances. The command line arguments must be quoted to ensure that the file path is treated as one argument.

I have some problems with running Apache and MariaDB in CentOS7 on Distrod. I have installed both in a fresh WSL 2 installation of CentOS7, they work until I restart WSL with wsl --shutdown or wsl --terminate Distrod.

It turned out that Apache fails to start after reboot because the /run/httpd directory gets deleted when restarting CentOS. I managed to get Apache running by recreating the missing directory: sudo mkdir /run/httpd sudo chown root:apache /run/httpd sudo chmod 0710 /run/httpd sudo systemctl start httpd.service sudo systemctl status -l httpd.service

However, I can't start MariaDB, must be something similar, but I don't know yet what is missing here.

My question is how to make the contents of the /run/ directory persistent to survive rebooting?

Describe the bug

after installing the first distro, if we open the setup file again it throws me in the same first distro and doesnot let me install another distro.

Steps to reproduce

try to install two distros

Expected behavior

setup doesnot run like the first run

Windows version

11

Linux kernel version

5.15.74.2

Distro

Arch Linux

How did you install that distro?

Installed by Distrod wizard

Logs

sorry, can't provide logs

additional comment

No response