Implement VS Code remote extensions

[nhooyr]

• Container
• SSH
• Tunnels

Related #1032

[lukasmasuch]

In case this issue is about fixing the remote extensions to work with code-server, this related issue can be closed: #892. I would really like to see the SSH extension to work within code-server and would be happy to test it once there is any fix.

[sr229]

@nhyoor if this interests you, there's a remote subfolder in the main vscode folder, wanna abuse reuse that?

[frank-dspeed]

The remote extension does some checks as far as i know i decompiled it some times.

There is a validation shema i think we should first automate the decompile process and check that.

[nhooyr]

We cannot and will not decompile the extension, that is not valid per the license terms.

[Just-Insane]

Is there any further plan to implement these extensions?

[kirscheGIT]

Is there any further plan to implement these extensions?

Would also like to know, if you have still have plans to implement this. Thanks!

[code-asher]

Nothing concrete at the moment.

[gyzerok]

I currently have a need for Remote - SSH extension and unfortunately the official one doesn't work for me (which is unlikely to be solved upstream in the near future). So I am considering implementing it myself.

At least initially I would like to have it as simple as possible. Without any fancy terminal forwarding or something like that. Just make it so that the work with the filesystem and all the language servers are running on the vm and UI is running in the vscode. Similar two what we now have with code-server in the browser, but without browser version problems (such as cmd+w for example).

Would you have some pointers as to where to start investigating from inside vscode source?

[code-asher]

At the moment I don't have a good idea of the full scope of what'll be required to make this work but it'll probably have to do with using and/or implementing the remote authority stuff.

There's a workspace.registerRemoteAuthorityResolver in the proposed API which might be a good starting point.

[JayDoubleu]

building from vscode-1.48.0 branch + adding 9fb33dc , as well as adding ms-vscode-remote.remote-containers to extensionAllowedProposedApi.

This gets the remote extensions installed however it is still complaining with the error:

[ms-vscode-remote.remote-containers]: View container 'remote' requires 'enableProposedApi' turned on to be added to 'Remote'.

Tried executing via below.

code-server --enable-proposed-api ms-vscode-remote.remote-containers
code-server --enable-proposed-api=ms-vscode-remote.remote-containers

Is there any more direct way to add arguments to the vscode to execute ?
I'm not sure if the enable-proposed-api switch simply does nothing or there is something else to be enabled.