-
Notifications
You must be signed in to change notification settings - Fork 814
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
Interop not working from WSL2 #6799
Comments
@joedborg can you please attach logs when you're reproing this problem? We aren't able to repro this issue and would need more info to diagnose it: Instructions here: |
Hi there, thanks for the reply. I've done some digging and can see that the issue is that the env var
If I set this variable to the last created socket file, it works again, but this is being set per shell, so I have to keep doing so with every shell launch. |
Awesome, thanks so much! Could you still collect logs using the link above? The info in the logs will help us diagnose why $WSL_INTEROP isn't behaving as expected. |
Thanks @craigloewen-msft, added the link in the original post. |
Thanks @therealkenc, It could also be that I'm using systemd instead of initd. Is there anywhere (or could you explain) that can show the chain of how WSL_INTEROP gets set, please? That way I can at least try and check to see where is overwriting it / isn't setting it correctly. Cheers! |
Hi! We've identified this issue as a duplicate of another one that already exists in this repository. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report! |
Windows Build Number
Microsoft Windows [Version 10.0.19042.906]
WSL Version
WSL 2
Distro Version
Ubuntu 20.04
Other Software
VS Code 1.55.1
Repro Steps
Run any .exe from WSL
Expected Behavior
.exe runs
Actual Behavior
<3>init: (747) ERROR: UtilConnectToInteropServer:300: connect failed 2
Diagnostic Logs
https://aka.ms/AAbxvmk
The text was updated successfully, but these errors were encountered: