-
Notifications
You must be signed in to change notification settings - Fork 170
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
Only start if needed: wsl-vpnkit status not working #160
Comments
Update: Seems the docs refer to a feature implemented after the release. Probably should only be there after it was released ;-). |
I've added that to the documentation after changing the init scripts (#147), however this will only become effective when there is a new release published. Alternatively you can build it from source. Or use the following:
I use flock because I use windows terminal with multiple splited panes, so this prevents concurrency starting those external services |
@STiAT @josesa-xx thanks, |
v0.3.8 should resolve this issue. |
First of all thank you, this made it possible to reliably use WSL2 via VPN.
To the issue:
In your documentation, you say we could only start the service if required (or not already running).
The issue is, that wsl-vpnkit in the 0.3.4 release seems to be missing the status option:
Therefore the command fails and it always tries to start the service anyway.
The text was updated successfully, but these errors were encountered: