microsoft / microsoft/vscode-remote-release

Startup fails when not connected to the Internet

Open
#11,385 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Dockerfile
Stars
4.2k
Forks
469
Avg merge
1d 1h
Merged PRs (30d)
1

Description

Type: Bug

When I start VSCode without an Internet connection the WSL Remote sometimes does not start because it is trying to update itself. I think it could be smarter and forego the update process in this case. Here is a log:

[2025-12-18 10:21:07.553] Setting up server environment: Looking for /home/michiel/.vscode-server-insiders/server-env-setup. Not found.
[2025-12-18 10:21:07.553] WSL version: 6.6.87.1-microsoft-standard-WSL2 Ubuntu-24.04
[2025-12-18 10:21:07.553] Network mode: nat
[2025-12-18 10:21:07.553] Updating VS Code Server to version cff2c318f87b2ff763290e4d5020c250f78d61f8
[2025-12-18 10:21:07.553] Removing previous installation...
[2025-12-18 10:21:07.553] Installing VS Code Server for Linux x64 (cff2c318f87b2ff763290e4d5020c250f78d61f8)
[2025-12-18 10:21:07.553] Downloading:
[2025-12-18 10:21:27.526] 100%
[2025-12-18 10:21:27.526] Failed
[2025-12-18 10:21:27.528] --2025-12-18 11:21:27-- https://update.code.visualstudio.com/commit:cff2c318f87b2ff763290e4d5020c250f78d61f8/server-linux-x64/insider
[2025-12-18 10:21:27.838] Resolving update.code.visualstudio.com (update.code.visualstudio.com)...
[2025-12-18 10:21:47.583] failed: Temporary failure in name resolution.
[2025-12-18 10:21:47.583] wget: unable to resolve host address ‘update.code.visualstudio.com’
[2025-12-18 10:21:47.584] ERROR: Failed to download https://update.code.visualstudio.com/commit:cff2c318f87b2ff763290e4d5020c250f78d61f8/server-linux-x64/insider to /home/michiel/.vscode-server-insiders/bin/cff2c318f87b2ff763290e4d5020c250f78d61f8-1766053267.tar.gz
[2025-12-18 10:21:47.584] For help with startup problems, go to https://code.visualstudio.com/docs/remote/troubleshooting#_wsl-tips

Extension version: 0.104.3
VS Code version: Code - Insiders 1.108.0-insider (cff2c318f87b2ff763290e4d5020c250f78d61f8, 2025-12-17T14:28:55.820Z)
OS version: Windows_NT x64 10.0.26200
Modes:
Remote OS version: Linux x64 6.6.87.1-microsoft-standard-WSL2

System Info
Item Value
CPUs AMD Ryzen AI 9 HX 370 w/ Radeon 890M (24 x 1996)
GPU Status 2d_canvas: enabled
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
trees_in_viz: disabled_off
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off
Load (avg) undefined
Memory (System) 31.12GB (12.82GB free)
Process Argv --crash-reporter-id 6e7fe86c-a519-442f-8fb1-e4b3a7cabce1
Screen Reader no
VM 0%
Item Value
Remote WSL: Ubuntu-24.04
OS Linux x64 6.6.87.1-microsoft-standard-WSL2
CPUs AMD Ryzen AI 9 HX 370 w/ Radeon 890M (24 x 0)
Memory (System) 15.18GB (11.20GB free)
VM 0%
A/B Experiments
vsliv368:30146709
pythonvspyt551:31249597
nativeloc1:31118317
dwcopilot:31158714
dwoutputs:31242946
copilot_t_ci:31333650
g012b348:31231168
pythonrdcb7:31268811
pythonpcpt1:31399616
6518g693:31302842
4f60g487:31327383
6abeh943:31336334
envsactivate1:31349248
editstats-enabled:31346256
cloudbuttont:31366566
aihoversummaries_t:31413033
todos-1:31405333
3efgi100_wstrepl:31403338
trigger-command-fix:31379601
use-responses-api:31390341
je187915:31401257
afag3459:31419922
terminalsuggestenabled:31421703
none:31433635
cp_cls_c_966_ss:31435507
chatvisible:31417128
inlinechat_v2_hd992725:31426642
4je02754:31426859
find_all_ref_in_bg_t:31420845
478ah919:31426749
ge8j1254_inline_auto_hint_haiku:31426887
a5gib710:31434435
5j92g670_sonnet:31434465
nes-joint-0:31433609
7a04d226_do_not_restore_last_panel_session:31429685
anthropic_thinking_t:31427198
406hc587_ask_agent:31428392
cp_cls_t_1081:31433292
copilot-nes-oct-trt:31432609
ia-no-proxy-models-svc:31436618

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is named in the issue. Start by tracing the WSL Remote server startup path around the logged update and download step, then inspect how an existing server installation is reused. Done means startup succeeds without Internet access when the required server is already available, with tests covering the offline case.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, ubuntu, vscode
Domain
devtools, networking, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.