-
-
Notifications
You must be signed in to change notification settings - Fork 127
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
Activating native systemd support breaks shell #486
Comments
It looks like systemd hasn't started properly. That should obviously not crash the shell though, I'll fix that |
As for the underlying problem: Can you send me the output of |
Is this the same error?
|
There is a workaround: first fire up WSL with a recovery shell |
@polybluez no, that is a diffferent error. I suspect that the one @aikooo7 experienced was a race condition, because the shell wrapper tried to connect to journald before that was started. That one should be fixed now, because it does not result in a crash anymore. Your error looks like the wrapper tries to start your shell, but the shell's binary just does not exist for some reason. The same probably would have happened without the wrapper |
This occurs for me as well, I basically have to revert to Data point: My NixOS-WSL is built using a flake, using a user created by the flake (and not the After the flake build, I cannot start up the distribution due to this error. |
@leonbreedt The latest tarball ships with native systemd enabled, so if that is working for you it being enabled isn't the actual problem. I suspect there's something in your config that interferes with it. Please open a new issue if you still have that problem. @aikooo7 Because the race-condition should be fixed and I didn't hear from you after that, I'm going to close this for now. Feel free to re-open if the issue is still present |
@nzbr: after i updated to latest nixpkgs, the issue no longer happens. thanks for the ping! |
Bug description
When enabling native systemd support and rebuild, switch and restart system you will be unable to log in to your system unless you use the recovery shell or use the shell binary directly instead of the wrapper.
Note: While trying to find what was the cause of the issue I rebuilt my home-manager and got
Failed to connect to bus: No such file or directory
so maybe #375 is related.To Reproduce
Steps to reproduce the behavior:
Add
wsl.nativeSystemd = true;
Run
sudo nixos-rebuild switch
Run
wsl --shutdown
in cmd.Run
wsl -d NixOS
in cmd. NixOS should be your nixos distro's name in wsl.Logs
WSL version
2.0.9.0
The text was updated successfully, but these errors were encountered: