microsoft / microsoft/vscode-remote-release

Issue with self signed certificates when installing extensions

Open
#2,987 17 comments 9 reactions 1 assignee View on GitHub

@chrmarti is already working on this.

Since Jun 3, 2020.

containers feature-request
Dominant language
Dockerfile
Stars
4.2k
Forks
470
Avg merge
1d 1h
Merged PRs (30d)
1

Description

Version: 1.45.0
Commit: d69a79b73808559a91206d73d7717ff5f798f23c
Date: 2020-05-07T15:57:33.467Z (5 days ago)
Electron: 7.2.4
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 18.7.0

I am using a very simple environment using a dockerfile behind a corporate network. I am able to install extensions locally fine without any issues however this fails when attempting to install them within the docker container

.devcontainer.json file:

{
    "name": "My-Project",
    "dockerFile": "./Dockerfile",
    "settings": {
        "terminal.integrated.shell.linux": "/bin/bash",
        "http.proxyStrictSSL": false
    },
    "extensions" : [
        "docsmsft.docs-yaml",
        "GrapeCity.gc-excelviewer",
        "Gruntfuggly.todo-tree",
        "Ikuyadeu.r",
        "ionutvmi.path-autocomplete",
        "ivan-bocharov.stan-vscode",
        "ms-azuretools.vscode-docker",
        "ms-python.python",
        "ms-vscode-remote.remote-containers",
        "notZaki.pandocciter",
        "redhat.vscode-yaml",
        "REditorSupport.r-lsp",
        "ryuta46.multi-command",
        "thenikso.github-plus-theme",
        "VisualStudioExptTeam.vscodeintellicode",
        "vscode-icons-team.vscode-icons",
        "vscodevim.vim",
        "edonet.vscode-command-runner"
    ]
}

Dockerfile

FROM ubuntu:18.04

When the container is being built I then get the following messages

3568 ms] Start: Run in container: cd /root/.vscode-server/bin/d69a79b73808559a91206d73d7717ff5f798f23c; export VSCODE_AGENT_FOLDER=/root/.vscode-server; /root/.vscode-server/bin/d69a79b73808559a91206d73d7717ff5f798f23c/server.sh --install-extension docsmsft.docs-yaml --install-extension GrapeCity.gc-excelviewer --install-extension Gruntfuggly.todo-tree --install-extension Ikuyadeu.r --install-extension ionutvmi.path-autocomplete --install-extension ivan-bocharov.stan-vscode --install-extension ms-azuretools.vscode-docker --install-extension ms-python.python --install-extension ms-vscode-remote.remote-containers --install-extension notZaki.pandocciter --install-extension redhat.vscode-yaml --install-extension REditorSupport.r-lsp --install-extension ryuta46.multi-command --install-extension thenikso.github-plus-theme --install-extension VisualStudioExptTeam.vscodeintellicode --install-extension vscode-icons-team.vscode-icons --install-extension vscodevim.vim --install-extension edonet.vscode-command-runner --force
[27816 ms] Installing extensions...
[27816 ms] self signed certificate in certificate chain
self signed certificate in certificate chain
self signed certificate in certificate chain
self signed certificate in certificate chain
self signed certificate in certificate chain
self signed certificate in certificate chain
self signed certificate in certificate chain
self signed certificate in certificate chain
self signed certificate in certificate chain
self signed certificate in certificate chain
self signed certificate in certificate chain
self signed certificate in certificate chain
self signed certificate in certificate chain
self signed certificate in certificate chain
self signed certificate in certificate chain
self signed certificate in certificate chain
self signed certificate in certificate chain
getaddrinfo EAI_AGAIN edonet.gallery.vsassets.io
[27816 ms] Exit code 1

Note that the container still builds and runs fine, just that when I access it none of the extensions are installed. Though the extensions are all still listed (see screenshot below) and I can click through and manually install them all (with the exception of the python extension that still won't install)

image

Any advice on how to solve this would be appreciated

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.