Vscode-remote-release: Support Installing VSIX from CLI

[adambattenburg]

When working inside a remote docker container and trying to install a VSIX file through the CLI, I get the error Ignoring option install-extension: not supported for code-insiders.

However, when running the command (code-insiders --install-extension /path/to/extension.vsix) not inside a remote container, it functions as expected.

[egamma]

@adambattenburg as a workaround you can install the VSIX in the remote case from the Extension Viewlet > ... > Install from VSIX

[adambattenburg]

Thanks for the suggestion @egamma! That's what I'm doing currently, but it would be nice to have the full environment setup when building the container.

I thought about issuing the VSCode command to install VSIX from a script, but not sure that's possible. I'll look into it and update this issue if it's a good workaround.

[egamma]

@adambattenburg we have some documentation for how you can do this using vscode-containers, pls see https://code.visualstudio.com/docs/remote/containers-advanced#_developing-inside-a-container-on-a-remote-docker-host.

[not-much-io]

@egamma I was unable to find information on how to install an extension from the commandline while in remote mode at the link you supplied.

I think currently it isn't supporter?

Example usecase: A developer working on making a VSCode plugin might have a neat workflow where they modify their code and run a single command to build, package and install their plugin for instant testing.

Currently without being able to install on the command line a manual step is needed for the install step.

[HotelCalifornia]

Same issue occurs when running VSCode from inside WSL

[DavidSouther]

I just started using Github Codespaces and figured this was the perfect use for the install script in my user dotfiles.

[vscode-triage-bot]

This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that are not going to be addressed in the foreseeable future: We look at the number of votes the issue has received and the number of duplicate issues filed. More details here. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!

[aramgre]

As a workaround, you can copy the vsix file to the extensions directory manually, for example in the postCreateCommand:

mkdir -p ~/.vscode-server/extensions && cd ~/.vscode-server/extensions && unzip /path/to/extension-name-1.0.0.vsix && mv extension extension-name-1.0.0

I don't know if this is supported behavior though