-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Unable to launh on WSL2 with WSLg #282
Comments
The error seems similar to #280 at first glance. |
work for me. But fail to install bigsur |
Keep hitting the Big Sur Installer, it needs to reboot about 3 times during the installation |
I got segmentation fault and docker stop
Le mer. 21 juil. 2021 à 16:50, sickcodes ***@***.***> a
écrit :
… work for me.
But fail to install bigsur
Keep hitting the Big Sur Installer, it needs to reboot about 3 times
during the installation
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#282 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAWNIBTBX2AXDYDSXY6IMDLTY3NFBANCNFSM45J2FOWA>
.
|
Fixed with #318 |
I am also getting this exact output/error. Did you ever get it resolved? I am using Docker Desktop which my Distro is using. I am able to launch gedit through WSLg and I am also able to launch xclock through x11. |
OS related issued, please help us identify the issue by posting the output of this
Hello, I was trying to get this run, but I got some issue since I'm not familiar with kvm/qemu.
I was following this guide to enable nested-kvm on wsl.
Since the latest insider include WSLg, I didn't install additional xserver like vcXsrv or X410. Not sure whether this caused it or not, but I did manage to run
gedit
successfully.I also installed
x11-apps
.However, I got the following error when trying to run the container:
Can you help me?
The text was updated successfully, but these errors were encountered: