Skip to content

remove WSL_INTEROP check - #298

Merged
sakai135 merged 1 commit into
mainfrom
remove-interop-check
Sep 1, 2026
Merged

remove WSL_INTEROP check#298
sakai135 merged 1 commit into
mainfrom
remove-interop-check

Conversation

@sakai135

@sakai135 sakai135 commented Sep 1, 2026

Copy link
Copy Markdown
Owner

Remove the check for WSL_INTEROP. This was intended as a sanity check, but seems like it's not a safe bet in all cases. As long as gvproxy.exe is available, WSL_INTEROP is not needed.

Fixes #297

@sakai135
sakai135 merged commit d491ba0 into main Sep 1, 2026
2 checks passed
@sakai135
sakai135 deleted the remove-interop-check branch September 1, 2026 00:43
yvh added a commit to yvh/wsl-vpnkit that referenced this pull request Sep 2, 2026
Port sakai135#298: the WSL_INTEROP environment variable is not
a reliable signal for Windows interop. sakai135#297 reports a
false negative when the interop socket it points to is not readable, and
systemd units do not always inherit it. The gvproxy execution check that
follows already proves interop works, so drop the variable check, its
test case and the WSL_INTEROP=1 plumbing in the Docker harness.

Add .gitattributes forcing LF so Windows clones with autocrlf keep the
shell scripts runnable, as upstream does. All tracked files are already
LF, so no renormalisation results.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

WSL interop not available on startup

1 participant