All devcontainers fail to open

[ianblitz]

Starting this morning, VS Code is no longer able to open any dev container. The only error I get is: "An error occurred setting up the container" immediately after triggering the window to reopen in container.

There are no other error logs anywhere I can find. It doesn't matter what the dev container definition is, this is the result. I have tried restarting my machine, uninstalling and reinstalling the devcontainer extension, and uninstalling and reinstalling VS Code entirely without any change in this behavior. Additionally, I do not get that popup if I try to "Reopen in Container" or "Rebuild and Reopen in Container" again after the failure. It just silently does nothing. Reload the window and trying one of those options results in the same popup error.

I tried installing the devcontainer CLI and using that, hoping to at least get a useful error message, but the only message I can seem to get is "Segmentation Fault".

Please let me know if there are logs somewhere I can grab that might be more helpful, but there are no terminal logs that I can see. I would appreciate any help anyone can provide.

Version: 1.78.2 (user setup)
Commit: b3e4e68a0bc097f0ae7907b217c1119af9e03435
Date: 2023-05-10T14:39:26.248Z
Electron: 22.5.2
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: 10.8.168.25-electron.0
OS: Windows_NT x64 10.0.22621
Sandboxed: No

[samruddhikhandale]

Hi 👋

Thanks for reporting this issue, and apologies for your inconvenience.

Starting this morning, VS Code is no longer able to open any dev container. The only error I get is: "An error occurred setting up the container" immediately after triggering the window to reopen in container.

@ianblitz Opening an issue in https://github.com/microsoft/vscode-remote-release/issues should help with the errors related to the "Dev Containers" extension.

I tried installing the devcontainer CLI and using that, hoping to at least get a useful error message, but the only message I can seem to get is "Segmentation Fault".

This is something we can help with, @alexander-smolyakov can you help investigate the issue here?
Wondering, if both the issues could have the same root cause.