microsoft / microsoft/vscode-remote-release

Cannot open in container from WSL filesystem through tunnels

Open
#9,644 8 comments 7 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

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

Description

Type: Bug

Windows Server 2022 with WSL2 as Tunnel host (setup using VSCode UI and configured to run on logon)

VSCode on Windows 10 as client.

After connecting to the tunnel, connect to WSL (which connects to WSL to the remote host of course).
Navigate to a folder with .devcontainer configuration.
Run any of the devcontainer commands, such as "Rebuild and open folder in container" and get the following error message:

Command 'Dev Container: Build and Reopen in Container' resulted in an error
Shell server terminated (code: 4294967295, signal: null)
T

Extension version: 1.5.1
VS Code version: Code 1.87.1 (1e790d77f81672c49be070e04474901747115651, 2024-03-06T00:21:36.258Z)
OS version: Windows_NT x64 10.0.22631
Modes:
Remote OS version: Linux x64 5.15.133.1-microsoft-standard-WSL2
Remote OS version: Linux x64 5.15.133.1-microsoft-standard-WSL2

System Info
Item Value
CPUs 12th Gen Intel(R) Core(TM) i9-12950HX (24 x 2496)
GPU Status 2d_canvas: enabled
canvas_oop_rasterization: enabled_on
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
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
Load (avg) undefined
Memory (System) 127.67GB (85.37GB free)
Process Argv --folder-uri vscode-remote://attached-container%2B7b22636f6e7461696e65724e616d65223a222f6c6f76696e675f726f656e7467656e227d@tunnel%2Bilabs-gpuwin004/workspaces/batman --crash-reporter-id 7a683ffe-ed86-4a3e-874f-e3e57dfd3491
Screen Reader no
VM 0%
Item Value
Remote Container vsc-batman-ee560097f57f556b8fe32b81b40df9341d265ffde0cb12fc73d456ead0b481cd-features (loving_roentgen) @ ilabs-gpuwin004
OS Linux x64 5.15.133.1-microsoft-standard-WSL2
CPUs Intel(R) Xeon(R) Gold 6246 CPU @ 3.30GHz (48 x 3292)
Memory (System) 754.87GB (745.31GB free)
VM 0%
Item Value
Remote WSL: Ubuntu (ilabs-gpuwin004)
OS Linux x64 5.15.133.1-microsoft-standard-WSL2
CPUs Intel(R) Xeon(R) Gold 6246 CPU @ 3.30GHz (48 x 3292)
Memory (System) 754.87GB (745.31GB free)
VM 0%
A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscoreces:30445986
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:30899288
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
pythongtdpath:30769146
welcomedialogc:30910334
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
h48ei257:30968133
pythontbext0:30879054
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
pydisww2:30981708
cppperfnew:30979542
d34g3935:30971562
fegfb526:30981948
bg6jg535:30979843
78248357:30976999
dsvsc020:30976470
666c4381:30973075

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.