-
Notifications
You must be signed in to change notification settings - Fork 299
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
Extension are not installed when configured in devcontainer.json #5620
Comments
I found the problem. The script server.sh use node to download the extensions and by default node doesn't use the ssl configured certificates.
I found two ways to solve it:
This assumes that you already configured your ssl certificate with something like:
After either one of the above the extensions are installed correctly:
|
Related: #986 |
I have the same problem with VS Code 1.60.2 (Remote - Containers v0.194.3), Windows 10.
It happens for me and some of my students using Windows 10 when connected to eduroam Wifi. In my Wifi at home after rebuilding the container it works as expected: all the extensions defined in devcontainer.sjon are installed. Any ideas what we could do? edit: the problem only appears for some Windows 10 Laptops, not every Windows 10 Laptop is affected. We didn't notice those problems with Ubuntu Laptops. |
I'll open a new issue, because maybee my issue has nothing to do with self signed certificates |
I encountered the same issue. Extensions are not installed during the build process but I can install them without problems via the GUI afterwards. Running the |
During the built phase:
So apparently no error occurs, but no extension is installed. I checked Inside the container
But from the logs I see that a different dir is checked
/home/vscode/.vscode-server/extensionsCache
or/vscode/vscode-server/extensionsCache
. Neither of them existsSteps to Reproduce:
Does this issue occur when you try this locally?: No
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: