VS Code Server for WSL closed unexpectedly.

Nobody has claimed this yet.

Issue Type: Bug

Simply trying to launch VS Code. No changes I know of since I successfuly launched VS Code Server last night to this morning. WSL in Ubuntu terminal is running fine.

[2021-03-06 15:55:30.050] Resolving wsl+Ubuntu-20.04, resolveAttempt: 1
[2021-03-06 15:55:30.136] Starting VS Code Server inside WSL (Ubuntu-20.04)
[2021-03-06 15:55:30.136] Extension version: 0.54.0, Windows build: 18363. Multi distro support: available. WSL path support: enabled
[2021-03-06 15:55:30.136] No shell environment set or found for current distro.
[2021-03-06 15:55:30.355] Probing if server is already installed: C:\windows\System32\wsl.exe -d Ubuntu-20.04 -e sh -c "[ -d ~/.vscode-server/bin/f30a9b73e8ffc278e71575118b6bf568f04587c8 ] && printf found || ([ -f /etc/alpine-release ] && printf alpine-; uname -m)"
[2021-03-06 15:55:30.627] Probing result: found
[2021-03-06 15:55:30.627] Server install found in WSL
[2021-03-06 15:55:30.629] Launching C:\windows\System32\wsl.exe -d Ubuntu-20.04 sh -c '"$VSCODE_WSL_EXT_LOCATION/scripts/wslServer.sh" f30a9b73e8ffc278e71575118b6bf568f04587c8 stable .vscode-server 5000 '}
[2021-03-06 15:55:30.816] Setting up server environment: Looking for /home/bradley/.vscode-server/server-env-setup. Not found.
[2021-03-06 15:55:30.816] WSL version: 5.4.72-microsoft-standard-WSL2 Ubuntu-20.04
[2021-03-06 15:55:30.816] WSL2-shell-PID: 236
[2021-03-06 15:55:30.816] Starting server: /home/bradley/.vscode-server/bin/f30a9b73e8ffc278e71575118b6bf568f04587c8/server.sh --port=0 --use-host-proxy --without-browser-env-var --print-ip-address --enable-remote-auto-shutdown --fileWatcherPolling=5000:/mnt/**
[2021-03-06 15:55:30.817] VS Code Server for WSL closed unexpectedly.
[2021-03-06 15:55:30.817] For help with startup problems, go to
[2021-03-06 15:55:30.817] https://code.visualstudio.com/docs/remote/troubleshooting#_wsl-tips
[2021-03-06 15:55:30.820] C:\windows\System32\wsl.exe -d Ubuntu-20.04 -e kill 236
[2021-03-06 15:55:31.112] WSL Daemon exited with code 0

VS Code version: Code 1.54.1 (f30a9b73e8ffc278e71575118b6bf568f04587c8, 2021-03-04T22:38:31.419Z)
OS version: Windows_NT x64 10.0.18363
Fetching remote diagnostics for 'WSL: Ubuntu-20.04' failed: VS Code Server for WSL closed unexpectedly.
Check WSL terminal for more details.

System Info

Item	Value
CPUs	AMD Ryzen 5 4500U with Radeon Graphics (6 x 2371)
GPU Status	2d_canvas: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: enabled opengl: enabled_on protected_video_decode: unavailable_off rasterization: enabled skia_renderer: enabled_on video_decode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled
Load (avg)	undefined
Memory (System)	31.37GB (25.13GB free)
Process Argv	--crash-reporter-id c3c72f5a-b8ef-476b-986f-c832b8b737e5
Screen Reader	no
VM	0%

Fetching remote diagnostics for 'WSL: Ubuntu-20.04' failed: VS Code Server for WSL closed unexpectedly.
Check WSL terminal for more details.

Extensions: none

A/B Experiments

vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspyt653:30253241
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
vstry244:30256636
pythonvsdeb440:30248342
pythonvsded773:30248341
pythonvspyt875:30259475
dockersubset:30265998
pythontbcf:30265426
vspre833:30267464

Start with the reported WSL startup log, especially the launch of .vscode-server/bin/.../server.sh through scripts/wslServer.sh. Reproduce the failure with Ubuntu-20.04 and the listed VS Code and Windows versions, then use the WSL terminal details to identify why the server exits; done means the server launches successfully and remote diagnostics work.

Written by the indexing model from the issue text.

Description

Contributor guide

First steps

Research direction

Assessment