Extensions not installed in remote container bootstrap

[neiltwist]

• VSCode Version: 1.38.0-insider (user setup)
• Commit: 20dd80d91a76cbe80fb1d1979c3a9f02d94ba161
• Date: 2019-08-29T14:06:00.070Z
• Electron: 4.2.9
• Chrome: 69.0.3497.128
• Node.js: 10.11.0
• V8: 6.9.427.31-electron.0
• OS Version: Windows_NT x64 10.0.16299

Steps to Reproduce:

1. Use a MITM coporate proxy.
2. Start a remote session in a container where an extension should be installed by default.
3. The extension is not installed.
4. Install extension into container manually (using extensions tab), which is successful.

Log:

Run: docker exec -w /root/.vscode-server-insiders/bin/20dd80d91a76cbe80fb1d1979c3a9f02d94ba161 -e VSCODE_AGENT_FOLDER=/root/.vscode-server-insiders b6674e548d4ea744733b659108a83630e937496c5cff44874c50fa57fad7ea3f /root/.vscode-server-insiders/bin/20dd80d91a76cbe80fb1d1979c3a9f02d94ba161/server.sh --install-extension ms-python.python --force
Installing extensions...
self signed certificate in certificate chain

Does this issue occur when all extensions are disabled?: N/A

[sandy081]

@neiltwist Do you have internet or proxy issues in the remote container?

[neiltwist]

@sandy081 No, and I can install manually, it's just not done automatically during the bootstrap stage, presumably due to not trusting the certificate authority that is presented.

[neiltwist]

It's worth noting that the certificate is installed in the OS (windows 10) and the "System Certificates" setting is on: "http.systemCertificates": true.

[chrmarti]

/duplicate #986

[vscodebot]

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for existing issues here. See also our issue reporting guidelines.

Happy Coding!