Skip to content
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.

Sign up for GitHub

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

Jump to bottom

doc: Add interop troubleshooting tip #235

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

doc: Add interop troubleshooting tip #235

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6617b2d
doc: Add interop troubleshooting tip
jaredbrogan Aug 23, 2023
dfe2f51
Merge pull request #1 from jaredbrogan/jaredbrogan-patch-1
jaredbrogan Aug 23, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -128,6 +128,12 @@ On older WSL versions where `/mnt/wsl/resolv.conf` is not available, `wsl-vpnkit
#### wsl-gvproxy.exe is not executable due to WSL interop settings or Windows permissions

`wsl-vpnkit` requires that the WSL 2 distro be able to run Windows executables. This [`interop` setting](https://learn.microsoft.com/en-us/windows/wsl/wsl-config#interop-settings) is enabled by default in WSL 2 and in the `wsl-vpnkit` distro.
* To resolve `cannot execute binary file: Exec format error`, please check for the existence of this file: `/usr/lib/binfmt.d/WSLInterop.conf`
* If the file is not found, run this to generate it and restart the related service:
```
sudo sh -c 'echo :WSLInterop:M::MZ::/init:PF > /usr/lib/binfmt.d/WSLInterop.conf'
sudo systemctl restart systemd-binfmt
```

Security configurations on the Windows host may only permit running executables in certain directories. You can copy `wsl-gvproxy.exe` to an appropriate location and use the `GVPROXY_PATH` environment variable to specify the location.

Expand Down