Skip to content
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

Closed
renan-abm opened this issue Feb 1, 2024 · 15 comments
Closed

VSCode 1.86 doesn't work with stable Dev Containers extension #203964

renan-abm opened this issue Feb 1, 2024 · 15 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug containers

Comments

@renan-abm
Copy link

renan-abm commented Feb 1, 2024

Does this issue occur when all extensions are disabled?: No

  • VS Code Version: 1.86.0
  • OS Version: MacOS 14.2.1

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.

@vscodenpa
Copy link

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!

@jkbzkl
Copy link

jkbzkl commented Feb 1, 2024

Same versions (vscode, mac). Upgrading Dev Containers to v0.338.0 (pre-release) worked for me.

@FerdyGuar97
Copy link

Thank you! Worked for me!

@chrmarti
Copy link
Contributor

chrmarti commented Feb 1, 2024

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!

@lourivalcs
Copy link

Still doesn't work, switching to pre-release version gives another error

[25965 ms] Start: Run in container: '/home/glue_user/.vscode-server/bin/05047486b6df5eb8d44b2ecd70ea3bdf775fd937/bin/helpers/check-requirements.sh' [34476 ms] Warning: Missing GLIBCXX >= 3.4.25! from /usr/lib64/libstdc++.so.6.0.24 Warning: Missing GLIBC >= 2.28! from /usr/lib64/libc-2.26.so Error: Missing required dependencies. Please refer to our FAQ https://aka.ms/vscode-remote/faq/old-linux for additional information. [34476 ms] [34476 ms] Exit code 99 [34483 ms] Command in container failed: '/home/glue_user/.vscode-server/bin/05047486b6df5eb8d44b2ecd70ea3bdf775fd937/bin/helpers/check-requirements.sh' [34483 ms] Warning: Missing GLIBCXX >= 3.4.25! from /usr/lib64/libstdc++.so.6.0.24 Warning: Missing GLIBC >= 2.28! from /usr/lib64/libc-2.26.so Error: Missing required dependencies. Please refer to our FAQ https://aka.ms/vscode-remote/faq/old-linux for additional information. [34484 ms] Exit code 99

docker image: amazon/aws-glue-libs:glue_libs_4.0.0_image_01
e2ce367
I found this recent change, before that access worked without problems

FAQ https://aka.ms/vscode-remote/faq/old-linux only returns error 503
image

@nikaro
Copy link

nikaro commented Feb 1, 2024

I can confirm that's it is working for me now with v0.338.1 stable.

@chrmarti
Copy link
Contributor

chrmarti commented Feb 1, 2024

@lourivalcs Please see #203967 for the error during server startup. The website appears to be back.

@rpolverini
Copy link

Same problem on Ubuntu 22.04.3 LTS
Downgrade to previous resolves the issue
This is the error
[581 ms] Command failed: /usr/share/code/code --ms-enable-electron-run-as-node /home/../.vscode/extensions/ms-vscode-remote.remote-containers-0.275.1/dist/spec-node/devContainersSpecCLI.js up --user-data-folder /home/..../.config/Code/User/globalStorage/ms-vscode-remote.remote-containers/data --container-session-data-folder /tmp/devcontainers-99b2e47c-100c-4d3a-8244-08dec4ad85ec1706822769176 --workspace-folder /home/.../../.../../e --workspace-mount-consistency cached --id-label devcontainer.local_folder=/home/../../../../.. --id-label devcontainer.config_file=/home/../../../../../.devcontainer/devcontainer.json --log-level trace --log-format json --config /home/../../../clients/web/.devcontainer/devcontainer.json --default-user-env-probe loginInteractiveShell --mount type=volume,source=vscode,target=/vscode,external=true --skip-post-create --update-remote-user-uid-default on --mount-workspace-git-root true

@chrmarti
Copy link
Contributor

chrmarti commented Feb 1, 2024

@rpolverini Please see above: #203964 (comment)

@chrmarti chrmarti added bug Issue identified by VS Code Team member as probable bug containers labels Feb 1, 2024
@rpolverini
Copy link

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
Thanks for hyper quick response and actions on that!!

@chrmarti chrmarti closed this as completed Feb 2, 2024
@chrmarti
Copy link
Contributor

chrmarti commented Feb 2, 2024

Closing as fixed. Thanks.

@stanislavstoyanov99
Copy link

With reinstalling VS Code to 1.86.0 and DevContainers extension to v0.339.0 still there is an issue on MacOS.
Screenshot 2024-02-06 at 10 32 08

@stanislavstoyanov99
Copy link

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.

@chrmarti
Copy link
Contributor

chrmarti commented Feb 6, 2024

@stanislavstoyanov99 We are working on a workaround for this for the upcoming 1.86.1 (#204344).

@gushh
Copy link

gushh commented Feb 27, 2024

Downgrade to 1.85.2 works for me!

warning: downgrading code from 1.86.2-1707854558 to 1.85.2-1705561292

@microsoft microsoft locked and limited conversation to collaborators Jun 10, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug containers
Projects
None yet
Development

No branches or pull requests

10 participants