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

devcontainer.json: Extensions installed by VSIX are not installed automatically in devcontainer #7874

Open
MBAatEJOT opened this issue Jan 20, 2023 · 4 comments
Labels
containers Issue in vscode-remote containers feature-request Request for new features or functionality
Milestone

Comments

@MBAatEJOT
Copy link

  • VSCode Version: 1.74.3 (user setup)

  • Local OS Version: Windows_NT x64 10.0.19044

  • Remote OS Version: Ubuntu 20.04.5 LTS

  • Remote Extension/Connection Type: Containers

  • Logs:

2023-01-20 06:46:56.196 [error] Error: Failed Installing Extensions: my-unique-id.my-first-extension
    at g.installExtensions (/vscode/vscode-server/bin/linux-x64/97dec172d3256f8ca4bfb2143f3f76b503ca0534/out/vs/server/node/server.main.js:91:42)

Steps to Reproduce:

  1. Create a custom VSCode Extension
  2. Install the extension locally from VSIX
  3. Start a dev container
  4. Install your custom extension in the dev container by clicking the button image
  5. Click on the gear and then on image
  6. Rebuild your container
  7. Check the logs for the Remote Server

The logs say that it failed to install the extension.

I guess that this problem happens because the dev container only checks the marketplace if there is an extension with this id.

However, since you can install extensions in the container that were previously installed locally via a VSIX file, the process of installing extensions via a devcontainer.json entry should be the following:

Search the marketplace for the extension
If Extension is found then
  install from marketplace
else if Extension exists locally then
  install by using locally installed extension
else
  log installation failed

Alternatively it's of course als possible to check for locally installed extensions first and then check the marketplace.

Does this issue occur when you try this locally?: No
Does this issue occur when you try this locally and all extensions are disabled?: Not applicable

@github-actions github-actions bot added the containers Issue in vscode-remote containers label Jan 20, 2023
@bamurtaugh bamurtaugh added the feature-request Request for new features or functionality label Jan 24, 2023
@vscodenpa vscodenpa added this to the Backlog Candidates milestone Jan 24, 2023
@vscodenpa
Copy link

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 10 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

@vscodenpa
Copy link

🙂 This feature request received a sufficient number of community upvotes and we moved it to our backlog. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

@vscodenpa vscodenpa modified the milestones: Backlog Candidates, Backlog Feb 22, 2023
@daltonv
Copy link

daltonv commented Oct 16, 2023

According to this issue #8827 this is already supported, but you have to give the path to the VSIX file in the container AND vscode currently incorrectly warns you this is incorrect syntax.

@NCC1701M
Copy link

According to this issue #8827 this is already supported, but you have to give the path to the VSIX file in the container AND vscode currently incorrectly warns you this is incorrect syntax.

Doesn't work for me.

I tried but the extension is not installed in the remote container.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
containers Issue in vscode-remote containers feature-request Request for new features or functionality
Projects
None yet
Development

No branches or pull requests

5 participants