microsoft / microsoft/vscode-remote-release

Angular port forwarding hangs

Open
#11,521 6 comments 4 reactions 1 assignee View on GitHub

@chrmarti is already working on this.

Since Mar 6, 2026.

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

Description

Type: Bug

Run angular app from inside container. Ports tab shows that port 4200 is forwarded automatically. However the browser hangs waiting for, "http://localhost:4200 " to display a webpage.

I've also tried to forward the port explicilty from devcontainer.json which doesn't resolve the problem. When I run the Angular app locally it loads immediately in the browser.

Image

Extension version: 0.448.0
VS Code version: Code - Insiders 1.110.0-insider (67c59a1440590a328f6fd0f15c37383c7576a236, 2026-02-24T17:04:41.375Z)
OS version: Linux x64 6.18.13-200.fc43.x86_64
Modes:
Remote OS version: Linux x64 6.18.13-200.fc43.x86_64

System Info
Item Value
CPUs AMD Ryzen 9 5900X 12-Core Processor (24 x 4200)
GPU Status 2d_canvas: enabled
GPU0: VENDOR= 0x10de [Google Inc. (NVIDIA Corporation)], DEVICE=0x2216 [ANGLE (NVIDIA Corporation, NVIDIA GeForce RTX 3080/PCIe/SSE2, OpenGL ES 3.2 NVIDIA 580.126.18)], DRIVER_VENDOR=NVIDIA, DRIVER_VERSION=580.126.18 ACTIVE
Machine model name:
Machine model version:
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: disabled_software
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off
webnn: disabled_off
Load (avg) 0, 1, 1
Memory (System) 62.68GB (52.67GB free)
Process Argv . --crash-reporter-id d4a2a8ef-b606-408d-8d73-eb5af88691b6
Screen Reader no
VM 0%
DESKTOP_SESSION plasma
XDG_CURRENT_DESKTOP KDE
XDG_SESSION_DESKTOP KDE
XDG_SESSION_TYPE wayland
Item Value
Remote Dev Container: Debian
OS Linux x64 6.18.13-200.fc43.x86_64
CPUs AMD Ryzen 9 5900X 12-Core Processor (24 x 4200)
Memory (System) 62.68GB (52.67GB free)
VM 0%
A/B Experiments
vsliv368cf:30146710
pythonvspyt551:31249597
nativeloc1:31118317
dwcopilot:31158714
dwoutputs:31242946
copilot_t_ci:31333650
g012b348:31231168
pythonrdcb7:31268811
pythonpcpt1cf:31399617
6518g693:31302842
6abeh943:31336334
envsactivate1:31349248
editstats-enabled:31346256
cloudbuttont:31366566
42190218_ostrepl:31403339
use-responses-api:31390341
je187915:31454425
cp_cls_t_966_ss:31454198
4je02754:31455664
a5gib710:31434435
38bie571_auto:31426784
7a04d226_do_not_restore_last_panel_session:31429685
cp_cls_t_1081:31454832
ia-use-proxy-models-svc:31446143
a43f0574a:31442822
e9c30283:31453065
test_treatment2:31471001
idci7584:31454084
edit_mode_hidden:31453871
e3e4d672:31454087
showingstats:31457201
ei9d7968:31462942
b1f5h706:31455228
7ef87755:31455235
regwelcome:31461167
quick_suggest_off_75197330:31462668
67jbj424:31469978
7e884298:31462391
bg_compact_c:31466297
t-some:31466503
7e187181:31470441
cpptoolson-v2:31471363
commenticon:31472181

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.