-
Notifications
You must be signed in to change notification settings - Fork 313
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
WSL can't connect to VS Code after it updated #8684
Comments
after following microsoft/WSL#6220 when trying to run code . |
The folder |
I think I have the same issue. Here's what happens:
For now I can ignore the "install new version" notification, but I don't know what's going on. If there are some logs that I can capture please let me know |
@AhmadMayo Did you install using the Window Store? /cc @joaomoreno |
I tried to open code from wsl again today and it updated and worked without a problem. |
[03:00:03.821] Log Level: 2
[03:00:03.893] VS Code version: 1.79.2
[03:00:03.893] Remote-SSH version: remote-ssh@0.102.0
[03:00:03.894] win32 x64
Steps to Reproduce:
vs code updated, refused to connect
after restarting my pc and typing "code ." in wsl terminal it responds with:
`Updating VS Code Server to version 660393deaaa6d1996740ff4880f1bad43768c814
Removing previous installation...
rm: cannot remove '/home/nuked/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/node_modules/debug': Read-only file system
rm: cannot remove '/home/nuked/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/node_modules/es6-promise/package.json': Read-only file system
rm: cannot remove '/home/nuked/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/node_modules/es6-promise/auto.js': Read-only file system
...
rm: cannot remove '/home/nuked/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/bootstrap-amd.js': Read-only file system`
Does this issue occur when you try this locally?: Yes
Does this issue occur when you try this locally and all extensions are disabled?: Yes
The text was updated successfully, but these errors were encountered: