Local dev containers are effectively unusable for me on Linux

[s-h-a-d-o-w]

• VSCode Version: 1.129.0 (also 1.130.0-insider)
• Local OS Version: Linux Mint 22.3
• Remote Extension/Connection Type: Dev Containers 0.466.0 (also 0.467.0 prerelease)

Steps to Reproduce:

1. Reopen any project in a dev container.

The following may happen:

1. Freezing during container building, window eventually terminating unexpectedly (code 135).

2. Infinite reconnect spinner right after successful building. (No files can be opened, no terminal spawned.)

3. Rebuild container and open container log => permanently disconnected and frozen log window.

Behavior cannot be reproduced consistently. It also doesn't seem to depend on dev container complexity. What happens is random and on rare occasions, things actually work.

I don't believe that user error is a factor here because I have been using dev containers in Cursor for a few weeks now. Not a single issue there.

Does this issue occur when you try this locally?: Yes
Does this issue occur when you try this locally and all extensions are disabled?: I mean... the dev containers extension is required?

[minorOffense]

Same problem on Rocky 9 Workstation.

Version: 1.129.0
Commit: 125df4672b8a6a34975303c6b0baa124e560a4f7
Date: 2026-07-15T00:08:44Z
Electron: 42.6.0
ElectronBuildId: 14623276
Chromium: 148.0.7778.280
Node.js: 24.18.0
V8: 14.8.178.38-electron.0
OS: Linux x64 5.14.0-611.55.1.el9_7.x86_64

End up having to reopen "dont restore editors" and then compose down all the containers. And then rebuild the dev containers without cache to get them to load at all. But even then once they're up if you try to use the remote explorer it just hangs.

[dib42]

Rolling back to 1.128.0 (fc3def6774c76082adf699d366f31a557ce5573f) to be able to work

[sandyperez]

I can reproduce this issue consistently.

Environment:

VS Code: 1.129.0
Dev Containers: 0.465.0, 0.466.0, and 0.467.0 (Pre-release) (same overall behavior)
Docker Engine: 29.5.2
OS: Ubuntu 24.04.4 LTS (Noble Numbat)
Kernel: 6.17.0-40-generic

Dev Containers stopped working immediately after upgrading to VS Code 1.129.0. Before the update, the same projects and devcontainer.json configurations worked without any issues.

What I tried

• Reinstalled the Dev Containers extension.
• Removed existing dev containers and rebuilt without cache.
• Cleared the VS Code caches (CachedData, CachedExtensionVSIXs, and workspaceStorage).
• Tested Dev Containers 0.465.0, 0.466.0, and 0.467.0 (Pre-release).

None of these steps resolved the issue.

Additional diagnostics

After inspecting the VS Code logs, it appears the container itself is not failing.

The Dev Container starts successfully, the Dev Containers CLI runs, and initialization begins. However, the local Extension Host crashes during Dev Containers initialization.

The logs consistently contain:

PendingMigrationError: navigator is now a global in nodejs

For both Dev Containers 0.465.0 and 0.467.0, the stack trace points into the Dev Containers extension itself (dist/extension/extension.js), after which the Extension Host terminates unexpectedly.

The shutdown monitor then reports:

Error confirming to extension:
connect ECONNREFUSED ...

After that, the container is stopped cleanly (SIGTERM, exit code 0). Docker itself reports no errors, and the container logs only contain:

Container started

This makes it look like the failure happens in the local Extension Host rather than in Docker, the container, or my devcontainer.json.