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
cannot connect to host: fork/exec /app/wsl-gvproxy.exe: no such file or directory #217
Comments
I had a similar problem, but instead it was "exec format error". This fixed it. |
@kropptrevor, thanks a lot for the valid path! As a result, everything was solved by adding lines to wsl.conf |
Same here, but I used the approach described in the comment bellow the one you've used. |
Hi guys!
Something strange happened. The service stopped running all of a sudden.
wsl.exe -d wsl-vpnkit --cd /app wsl-vpnkit
starting vm and gvproxy...
ERRO[0000] cannot connect to host: fork/exec /app/wsl-gvproxy.exe: no such file or directory
started vm and gvproxy
ERRO[0001] cannot connect to host: fork/exec /app/wsl-gvproxy.exe: no such file or directory
ERRO[0002] cannot connect to host: fork/exec /app/wsl-gvproxy.exe: no such file or directory
ERRO[0003] cannot connect to host: fork/exec /app/wsl-gvproxy.exe: no such file or directory
ERRO[0004] cannot connect to host: fork/exec /app/wsl-gvproxy.exe: no such file or directory
ERRO[0005] cannot connect to host: fork/exec /app/wsl-gvproxy.exe: no such file or directory
ERRO[0006] cannot connect to host: fork/exec /app/wsl-gvproxy.exe: no such file or directory
Installation was done according to the manual. Yesterday and before everything works fine. No updates have been installed.
The change systemd=false in /etc/wsl.conf helps to start the kit in manual mode. But at the same time, it is not possible to start the service at the start of the WSL.
Ubuntu 22.04
WSL 1.2.5.0
Please, help!!!
The text was updated successfully, but these errors were encountered: