-
Notifications
You must be signed in to change notification settings - Fork 64
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
Bedrock will not install properly on WSL #107
Comments
While you have the fuse package installed, I don't think WSL supports the requisite kernel features for it to work. Copying The hijack process takes place in two steps. The first happens when you run the hijack script, which takes over the init subsystem. My guess is by copying Given the lack of FUSE support and the lack of proper init support I don't think we'll be able to get Bedrock working under WSL as it stands now. It might theoretically be possible to work around these issues (and likely other issues), but given our limited manpower I don't think we'll pursue this for the foreseeable future. I'll look into adding another sanity check to the installer to check for WSL and provide an error message indicating it doesn't work with WSL. Please leave this issue open for now as a reminder for me to do so. I'll close it once I've pushed a release whose installer includes this check. |
0.7.2 should report an error about not working on WSL if someone attempts to hijack a WSL instance. |
Closing the issue assuming 0.7.2 does in fact generate an error message when attempting to hijack WSL. If someone finds it does not, please re-open the issue and let me know. |
As far as I know there were two known blockers:
So quite possibly! I don't have a system to test this on, but I know others have been interested in getting Bedrock to play nicely with WSL; I can prod them to take a look. If you have a NULL-safe editor, do feel free to remove the check from the script and give it a try yourself and report back. |
Sadly, it doesn't run out of the box and bricks the install
Maybe someone else with more insight on Bedrock can make this work, though :) |
Alas, I don't have any ideas from that error message, but I did reach out to someone who might. If he finds something notable I'll update this issue accordingly. Even if efforts to get the current Bedrock Linux 0.7.x to work on WSL dead end, I do have some ideas to make the future Bedrock Linux 0.8.x more flexible such that it might be easier to get working. This is something we'll probably get working eventually, in some fashion or another. |
I think something broke with Path although I'm not sure because it failed to exec bash but it didn't give any useful error message.. |
I decided to try installing Bedrock on the Windows Subsystem for Linux, as that's more convenient for me than rebooting into a Linux distro when I want to run the occasional Linux program. However, upon attempting to install Bedrock over Ubuntu, I was greeted with this:
As you can see in the image, I do have Fuse, as WSL comes with it. I have not tried uninstalling & reinstalling it, as when I asked some full-time linux users about that I heard removing Fuse horribly breaks WSL.
After creating the
/bin/fuse
directory manually on my backup distro (Debian, since you can only have 1 install of each distro), the installer did run and finish. However, after rebooting I found thatbrl
simply left me with a command not found and neofetch still said I was running plain debian. The/bedrock
folder does exist though, with (what I assume is, anyway) all its folders intact. Even when going into/bedrock/bin
and typingbrl
orstrat
, I was simply greeted with another command not found. I tried going back into/bedrock
and typingsudo nano compete-hijack-install
to see if anything had been stored there, but it seemed to be completely empty.The text was updated successfully, but these errors were encountered: