-
Notifications
You must be signed in to change notification settings - Fork 29.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VSCode 1.86 doesn't work with stable Dev Containers extension #203964
Comments
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.86.0. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding! |
Same versions (vscode, mac). Upgrading Dev Containers to v0.338.0 (pre-release) worked for me. |
Thank you! Worked for me! |
Make sure you are running Dev Containers v0.338.1 stable or later (recent pre-releases also work). This was caused by the stable version being released with some delay to VS Code 1.86, sorry for the inconvenience! |
Still doesn't work, switching to pre-release version gives another error
docker image: amazon/aws-glue-libs:glue_libs_4.0.0_image_01 FAQ https://aka.ms/vscode-remote/faq/old-linux only returns error 503 |
I can confirm that's it is working for me now with v0.338.1 stable. |
@lourivalcs Please see #203967 for the error during server startup. The website appears to be back. |
Same problem on Ubuntu 22.04.3 LTS |
@rpolverini Please see above: #203964 (comment) |
Thanks @chrmarti I can confirm that reinstall the new package again (1.86.0) and install the devcontainer extension v0.339.0 (pre-release) make work all again |
Closing as fixed. Thanks. |
The fix that worked for me is to downgrade VS Code to 1.85.2 and then use latest version of Dev Containers extension, which is v0.327.0. |
@stanislavstoyanov99 We are working on a workaround for this for the upcoming 1.86.1 (#204344). |
Downgrade to 1.85.2 works for me!
|
Does this issue occur when all extensions are disabled?: No
Steps to Reproduce:
The recent VSCode 1.86 stable release broke our devcontainer. Reloading the window gives the error
bad option: --ms-enable-electron-run-as-node
. This is likely the same as #202096.The workaround was to use a pre-release version of the Dev Containers extension, but it would be nice if the stable VSCode and stable Dev Containers extension would work fine.
I'm opening this issue here but feel free to move it to https://github.com/microsoft/vscode-remote-release/issues if appropriate.
The text was updated successfully, but these errors were encountered: