-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WSL2 crashes at launch after enabling distrod [Distrod][ERROR] Failed to spawn the command.
#9
Comments
[Distrod][ERROR] Failed to spawn the command.
Hmm.. It looks systemd crashed for some reason. Possibly due to some Genie's initialization script which wasn't completely removed, but I'm not sure, I'm not so familiar with genie. Or, it could be just a bug of Distrod. Could you enable the logging of both /opt/distrod/bin/distrod-exec /bin/bash bash It should crash in the same way as before, but with debug logging this time. sudo cat /dev/kmsg > kmsg_log.txt # this doesn't return. Press ctrl + c after a few seconds |
Thank you for the reply ! I have gathered the logs, looks like some mount problem (???) I don't really understand though.. Thank you very much for your help !
|
Hi, I cannot find anything wrong in your log. I will check if I can reproduce the problem by installing / uninstalling Genie later. |
Thank you checking, do you know where it failed so I can try to work around it ? |
There are two possibilities as far as I can guess.
In both cases, there is no workaround. What I can suggest as a workaround is to install a clean new distro by Distrod. |
To check whether Systemd crashes or not, could you share the result of |
I seem to be having the exact same problem running the Here's the output of
There doesn't seem to be any parameters passed to |
@oDn thanks for sharing the outputs! Could you also try What I can tell from your outputs.
|
@nullpo-head, I think you're spot on !
I was sure I'd set WSL's default version to 2 a while ago but that obviously wasn't the case.
Now that I've created a new VM using WSL 2, everything seems to be running fine !
Thanks ! |
By the way, as for the original issue reporter, @eizanprime , it's unlikely the cause is WSL1, since they used genie once, which doesn't run on WSL1. I'm still waiting for their comments. |
I am finally back, sorry for being late (was a bit busy these days, I'm actually work in tokyo too) here is the output of the ps command, the process doesn't look there..
I would recreate a new distro if I could but my current system is quite customized and I don't really want to restart from scratch (as everything is vmdk in wsl2 I suppose a good old dd on the disk would not work so well) |
In attempting to bring up a Fedora 36 or Rawhide container without first upgrading the 35 base from linuxcontainers.org (which BTW puts systemd into a degraded state), I'm seeing the same issue with images from: https://koji.fedoraproject.org/koji/packageinfo?packageID=26387 After extracting layer.tar from the tar.xz and performing the following steps:
I get symlink errors after enabling distrod:
Here are the errors from subsequent launch 1:
And subsequent launch 2:
This is from a clean Windows 11 Pro install, so wsl2 is implied and confirmed.
|
Any progress for this issue? I'm having similar problem. The distro I use is from this https://github.com/machsix/ubuntu-impi. You can download the rootfs here https://github.com/machsix/ubuntu-impi/actions/runs/2157438149 |
This error just started to appear on my laptop running windows 11. I haven't changed anything: it just doesn't launch anymore. |
Here is the error when launching wsl2
my distro sort of becomes borked after that.. the only way to get back in was to use wsl --exec to get back in and disable distrod
I am on archlinux and I was using systemd-genie (I uninstalled it to use this)
would somebody know how to fix this ?
Thank you very much
The text was updated successfully, but these errors were encountered: