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

Mac 版 终端:WSL extension is supported only in Microsoft versions of VS Code #108

Open
xiaoguaihou opened this issue Feb 17, 2025 · 11 comments
Assignees

Comments

@xiaoguaihou
Copy link

基础信息
Version: 1.0.2
VS Code Version: 1.96.4
Commit: 787c1a33d566d74c783a51d8c4b8e583b095fa0c
Date: 2025-02-16 23:44:21.862
Electron: 32.2.6
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Darwin arm64 24.3.0
Build Version: 1.0.6692
Machine Id: 11b47af397cd3756b7113c1acf8296d1c8b1f903196b8aafe1e4290eb120603e

Bug描述
Mac 版每次启动,打开终端都会显示这个:WSL extension is supported only in Microsoft versions of VS Code

截图 / 录屏

Image

@davelet
Copy link

davelet commented Feb 17, 2025

你是不是复制的windows的vscode,导致每次都尝试启动wsl?

@xiaoguaihou
Copy link
Author

你是不是复制的windows的vscode,导致每次都尝试启动wsl?

没有特别操作过。我本地的 vscode,cursor等,都没有这个问题。 Trae 是最后装的

@gagmeng
Copy link

gagmeng commented Feb 17, 2025

我windows下也报这个错误

@michabbb
Copy link

i guess this issue is about WSL not working.... so here´s my info to that:

[Trace  - 15:19:00.32] Server install command stdout:
Error downloading server from https://github.com/VSCodium/vscodium/releases/download/1.96.4./vscodium-reh-linux-x64-1.96.4..tar.gz
b436d02e0a082b8d85a3186b: start
exitCode==1==
listeningOn====
connectionToken====
logFile==/home/micha/.trae-server/.787c1a33d566d74c783a51d8c4b8e583b095fa0c.log==
osReleaseId==ubuntu==
arch==x86_64==
platform==Linux==
tmpDir==/run/user/1000/==
b436d02e0a082b8d85a3186b: end

[Error  - 15:19:00.32] Error resolving authority
Error: Couldn't install vscode server on remote server, install script returned non-zero exit status
	at t.installCodeServer (c:\Users\micha\.trae\extensions\jeanp413.open-remote-wsl-0.0.4-universal\out\extension.js:1:26792)
	at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
	at async c:\Users\micha\.trae\extensions\jeanp413.open-remote-wsl-0.0.4-universal\out\extension.js:1:1739
Version: 1.0.2
VS Code Version: 1.96.4 (user setup)
Commit: 787c1a33d566d74c783a51d8c4b8e583b095fa0c
Date: 2025-02-16 16:07:29.946
Electron: 32.2.6
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.22631
Build Version: 1.0.6690

@SirLouen
Copy link

It seems that WSL is not supported yet

@michabbb
Copy link

funny: releasing a windows version and ignoring WSL - respect....🙈

@SirLouen
Copy link

funny: releasing a windows version and ignoring WSL - respect....🙈

Its not the first. Most VSCode new wrappers doesnt have this support. Barely a handful have it. I hope they comment here and support it anytime soon.

@saeedblanchette
Copy link

up we need support

@Sampwood
Copy link

是不是安装了 Remote - SSH 插件。我卸载这个插件后,没有这个报错了

@michabbb
Copy link

what has ssh to do with WSL ? answer: absolutely nothing

@SirLouen
Copy link

SirLouen commented Feb 21, 2025

what has ssh to do with WSL ? answer: absolutely nothing

Yes and no

Thanks to @Sampwood idea, I've found a workaround that for now, works pretty well

First install an SSH server in your WSL machine.

Then install such extension that he comments:

Image

ATM It has a minor bug, so I recommend checking this issue:
jeanp413/open-remote-ssh#195 (comment)

And then connect to the WSL2 SSH server using your WSL2 IP and credentials.

I've not gone much deeper, but I think that the extension can be configured adding some credentials, so the integration could be seamless as if we were using the VSCode WSL original extension.

Still I hope they add some WSL2 support by default.

EDIT:
I've have discovered now, that using this other extension:

Image

You can connect using the command palette to WSL straight without having to configure any SSH credentials
(Still the bug I comment above must be solved for this to work using my settings.json workaround)

Image

The only difference is that instead of adding remote.SSH.serverDownloadUrlTemplate when using the WSL extension we must add remote.WSL.serverDownloadUrlTemplate


For now its pretty sweet for me to start playing with Trae and WSL2 (because I hate to work on the Windows machine)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants