arkane-systems
Cannot start genie propperly, "Failed to read server status".
Windows version (build number): 21H2 (build 22000.832)
Linux distribution: Fedora from this tutorial: https://dev.to/bowmanjd/install-fedora-on-windows-subsystem-for-linux-wsl-4b26
Kernel version: 5.10.102.1-microsoft-standard-WSL2
Genie version: genie 2.4
Describe the bug Cannot start genie propperly, the kernel modules load but dont get "active".
Confirm that you are running inside the bottle: "inside"
To Reproduce 1- Install the provided rpm normally. 2- Start genie with "genie -i" 3- Watch as the entire world falls appart before your eyes.
Expected behavior Genie to start normally and give me access to systemd.
Screenshots
I confirm that I have read the ENTIRE supplied readme file and checked for relevant information on the repository wiki before raising this issue, and that if the solution to this issue is found in either location, it will be closed without further comment:
- [X] Yes.
-PS: I'm really sorry if this is irrelevent, i'm new to this and have been struggling for a while. Here, i need genie to get the ability to use systemd with docker as it is needed for my project. If you have a sugestion that would solve this and make me not have to use genie, i'm all ears!
What happens if you exit all instances and then perform wsl --shutdown in windows terminal/powershell. Then re-enter WSL and perform genie -s
The info about masking systemd-modules-load.service came directly from the wiki
Same exact thing...
I also tried restarting my entire laptop, nothing changes... I also tried re-installing the rpm... same thing.
I'm not going to lie, mine isn't working either, but I've gotten it to work with other dist (ubuntu 20.04) not fedora, so there's something here to investigate. However, if you're trying to do something for school or work in linux, you should definitely be using a full installation llike a dual boot. WSL2 cannot substitute a full linux desktop.
That "Failed to dump process list" issue is a general systemd issue under WSL these days, but doesn't stop it from working, only from displaying the status easily.
To debug further, we'll need the output of a systemctl --failed -- or just run systemctl and look for the failed unit (in red) to know what the problem is. There are a lot of possibilities, so.
