-
Notifications
You must be signed in to change notification settings - Fork 822
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
socket(AF_VSOCK, SOCK_STREAM|SOCK_CLOEXEC, 0) = -1 ENOSYS (Function not implemented) #12268
Comments
Logs are required for review from WSL teamIf this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. How to collect WSL logsDownload and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
The script will output the path of the log file once done. If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here Once completed please upload the output files to this Github issue. Click here for more info on logging View similar issuesPlease view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it! Open similar issues:
Closed similar issues:
|
The similar issues mentioned above do not resolve my problem. I don't encounter this issue when starting the service with Python. |
Windows Version
Microsoft Windows [Version 10.0.22631.4460]
WSL Version
2.3.26.0
Are you using WSL 1 or WSL 2?
Kernel Version
Linux version 5.15.167.4-microsoft-standard-WSL2
Distro Version
Ubuntu 22.04
Other Software
Docker version 27.3.1, build ce12230
Repro Steps
Cross-compile Linux service on Windows, then run it on Docker.
In Windows
run server in Docker
Expected Behavior
no exception
Actual Behavior
root@b3b95375ee86:/app/51# ./run_server
<3>WSL (6598) ERROR: UtilBindVsockAnyPort:287: socket failed 38
strace logs
Diagnostic Logs
The text was updated successfully, but these errors were encountered: