[Bug] Dev Containers extension incompatibility with Void

[jovazxc]

Version

VSCode Version: 1.99.30031 (system setup) Void Version: 1.3.7 Commit: 4b86bfa184b176c26649d77fbbe30026de0c3e81 Date: 2025-05-13T03:21:14.422Z Electron: 34.3.2 ElectronBuildId: undefined Chromium: 132.0.6834.210 Node.js: 20.18.3 V8: 13.2.152.41-electron.0 OS: Windows_NT x64 10.0.26100

Issue Is there a way to get working dev containers in WSL ?

I got the following message

[andrewpareles]

There is likely an open source devcontainers extension that we simply need to drop into the extensions/ folder (and add a link to reh, which I can help with).

[jovazxc]

any updates of this ? @andrewpareles

[avg-joe]

I'm keen to know any updates on this as well.

[DavidBalaban01]

Hi @andrewpareles, Are there any updates on this? It’s a bit of a blocker — without support for Dev Containers, I might have to consider switching to another editor. Would really appreciate any insight or plans regarding this.

Thanks!

[manupatet]

Please update, devcontainers are quite central to how I code for different stacks

[psirenny]

FWIW, Dev Containers do work in Cursor.

[johnkntran]

Yes works in original VS Code and Windsurf as well. This is the error I get for Void (I'm on Mac M1 and not WSL):

Void is more or less unusable for me without support for Dev Containers. While it's nice to bring-your-own-key (BYOK) for all the LLM providers (Windsurf only lets you BYOK for Anthropic), the lack of container support is a big issue - basically a non-starter to using this Editor.

[andrewpareles]

Thanks for sharing, I would have thought the built-in would work (after uninstalling any extra devcontainer extensions)... Apologies for this, working on it