-
Notifications
You must be signed in to change notification settings - Fork 61
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
Running over WSL #111
Comments
I already tried fixing that but i'm not using WSL that much, so i've given up for the moment. Sorry. |
Hi, I'm a big fan of your plugin. It makes a huge difference to workflow! But +1 for fixing this issue -- I am trying to consolidate all my windows terms into WSL and so close right now :) |
+1 for this. Lack of NFS synced folder in WSL is my main gripe with the Win10 dev environment so this could be the missing link and mean vm-based development workflow would be the same between OSX and Win10. :-) |
+1 from me too. This would be wonderful. |
@marcharding When do you anticipate this issue being resolved? I would help with the code if I could, but I unfortunately don't have enough knowledge with Windows internals/networking. What else can I do to help you expedite this? |
For what it's worth, I'd +1 this issue too... |
+1 |
Isn't NFS support now included int he WSL kernels (like Ubuntu 20.04)? |
Hey,
Vagrant supports running on top of WSL: https://www.vagrantup.com/docs/other/wsl.html.
This plugin is incompatible with such scheme atm. While I was able to pass netsh to it:
It still does not work after setting up firewall rule.
The text was updated successfully, but these errors were encountered: