microsoft / microsoft/vscode-remote-release

Container Feature installation broken due to self signed certificates (since 0.251.0)

Open
#7,150 17 comments 35 reactions 1 assignee View on GitHub

@chrmarti is already working on this.

Since Sep 6, 2022.

bug containers plan-review proxy
Dominant language
Dockerfile
Stars
4.2k
Forks
470
Avg merge
1d 1h
Merged PRs (30d)
1

Description

  • VSCode Version: 1.71.0
  • Local OS Version: WSL2 Ubuntu 22.04 LTS on Windows 10 Pro(Build 19044.1889)
  • Remote OS Version: debian bullseye
  • Remote Extension/Connection Type: Containers
  • Logs:
[41 ms] Remote-Containers 0.251.0 in VS Code 1.71.0 (784b0177c56c607789f9638da7b6bf3230d47a8c).
[40 ms] Start: Run: wsl -d Ubuntu-20.04 -e wslpath -u \\wsl$\Ubuntu-20.04\home\userXYZ\projects\projectXYZ
[423 ms] Start: Resolving Remote
[450 ms] Start: Run: wsl -d Ubuntu-20.04 -e wslpath -u \\wsl$\Ubuntu-20.04\home\userXYZ\projects\projectXYZ
[683 ms] Start: Run: wsl -d Ubuntu-20.04 -e /bin/sh -c cd '/home/userXYZ/projects/projectXYZ' && /bin/sh
[697 ms] Start: Run in host: id -un
[797 ms] userXYZ
[798 ms] 
[798 ms] Start: Run in host: cat /etc/passwd
[801 ms] Start: Run in host: echo ~
[802 ms] /home/userXYZ
[802 ms] 
[803 ms] Start: Run in host: test -x '/home/userXYZ/.vscode-remote-containers/bin/784b0177c56c607789f9638da7b6bf3230d47a8c/node'
[805 ms] 
[805 ms] 
[806 ms] Start: Run in host: test -f '/home/userXYZ/.vscode-remote-containers/dist/vscode-remote-containers-server-0.251.0.js'
[807 ms] 
[808 ms] 
[809 ms] userEnvProbe: loginInteractiveShell (default)
[810 ms] userEnvProbe shell: /bin/bash
[1355 ms] userEnvProbe PATHs:
Probe:     '/home/userXYZ/.local/bin:/home/userXYZ/bin:/home/userXYZ/.nvm/versions/node/v16.13.1/bin:/home/userXYZ/.cargo/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/lib/wsl/lib:/mnt/c/Program Files/Amazon Corretto/jdk1.8.0_332/bin:/mnt/c/Program Files/Amazon Corretto/jdk11.0.15_9/bin:/mnt/c/WINDOWS/system32:/mnt/c/WINDOWS:/mnt/c/WINDOWS/System32/Wbem:/mnt/c/WINDOWS/System32/WindowsPowerShell/v1.0/:/mnt/c/Program Files/Amazon Corretto/jdk1.8.0_332/bin:/mnt/c/Program Files/SafeNet/Authentication/SAC/x64:/mnt/c/Program Files/SafeNet/Authentication/SAC/x32:/mnt/c/Program Files/nodejs/":/mnt/c/Program Files/Amazon Corretto/jdk1.8.0_192/bin:/mnt/c/Program Files/Microsoft VS Code/bin":/mnt/c/Program Files/Amazon Corretto/jdk1.8.0_192:/mnt/c/WINDOWS/System32/OpenSSH/:/mnt/c/Program Files/Java/jdk1.8.0_192/bin:/mnt/c/apache-maven-3.6.3/bin:/mnt/c/Program Files/Git/cmd:/mnt/c/Users/userXYZ/AppData/Local/Microsoft/WindowsApps:/mnt/c/Users/userXYZ/cygwin/bin:/mnt/c/php7.2:/mnt/c/Program Files/JetBrains/IntelliJ IDEA 2020.3.2/bin:/mnt/c/Users/userXYZ/AppData/Local/Programs/Microsoft VS Code/bin:/snap/bin:/home/userXYZ/.dotnet/tools'
Container: None
[1358 ms] Setting up container for folder or workspace: /home/userXYZ/projects/projectXYZ
[1360 ms] Start: Check Docker is running
[1360 ms] Start: Run in Host: docker version --format {{.Server.APIVersion}}
[2096 ms] Server API version: 4.1.0
[2096 ms] Start: Run in Host: docker volume ls -q
[2538 ms] Start: Run in Host: docker ps -q -a --filter label=vsch.local.folder=\\wsl$\Ubuntu-20.04\home\userXYZ\projects\projectXYZ --filter label=vsch.quality=stable
[2955 ms] Start: Run in Host: docker ps -q -a --filter label=devcontainer.local_folder=\\wsl$\Ubuntu-20.04\home\userXYZ\projects\projectXYZ
[3407 ms] Start: Run in Host: /home/userXYZ/.vscode-remote-containers/bin/784b0177c56c607789f9638da7b6bf3230d47a8c/node /home/userXYZ/.vscode-remote-containers/dist/dev-containers-cli-0.251.0/dist/spec-node/devContainersSpecCLI.js up --workspace-folder /home/userXYZ/projects/projectXYZ --workspace-mount-consistency cached --id-label devcontainer.local_folder=\\wsl$\Ubuntu-20.04\home\userXYZ\projects\projectXYZ --log-level debug --log-format json --config /home/userXYZ/projects/projectXYZ/.devcontainer/devcontainer.json --default-user-env-probe loginInteractiveShell --mount type=volume,source=vscode,target=/vscode,external=true --skip-post-create --update-remote-user-uid-default on --mount-workspace-git-root true
[3793 ms] remote-containers 0.251.0.
[3793 ms] Start: Run: docker buildx version
[3840 ms] Start: Resolving Remote
[3845 ms] Start: Run: git rev-parse --show-cdup
[3853 ms] Start: Run: docker ps -q -a --filter label=devcontainer.local_folder=\\wsl$\Ubuntu-20.04\home\userXYZ\projects\projectXYZ
[4270 ms] local container features stored at: /home/userXYZ/.vscode-remote-containers/dist/dev-containers-cli-0.251.0/dist/node_modules/vscode-dev-containers/container-features
[4272 ms] Start: Run: tar --no-same-owner -x -f -
[4340 ms] * Processing feature: git
[4480 ms] Failed to get registry auth token with error: Error: self signed certificate in certificate chain
[4575 ms] (!) WARNING: Falling back to deprecated GitHub Release syntax. See https://github.com/devcontainers/spec/blob/main/proposals/devcontainer-features.md#referencing-a-feature for updated specification.
[4575 ms] Github feature.
[4575 ms] Invalid parse for GitHub Release feature: Follow format '<publisher>/<feature-set>/<feature>, or republish feature to OCI registry.'
[4446 ms] Error: Failed to process feature ghcr.io/devcontainers/features/git:1
[4446 ms]     at QR (/home/userXYZ/.vscode-remote-containers/dist/dev-containers-cli-0.251.0/dist/spec-node/devContainersSpecCLI.js:188:2956)
[4447 ms]     at processTicksAndRejections (node:internal/process/task_queues:96:5)
[4447 ms]     at async uc (/home/userXYZ/.vscode-remote-containers/dist/dev-containers-cli-0.251.0/dist/spec-node/devContainersSpecCLI.js:188:2279)
[4447 ms]     at async Zs (/home/userXYZ/.vscode-remote-containers/dist/dev-containers-cli-0.251.0/dist/spec-node/devContainersSpecCLI.js:188:12771)
[4447 ms]     at async OF (/home/userXYZ/.vscode-remote-containers/dist/dev-containers-cli-0.251.0/dist/spec-node/devContainersSpecCLI.js:257:3261)
[4447 ms]     at async Wf (/home/userXYZ/.vscode-remote-containers/dist/dev-containers-cli-0.251.0/dist/spec-node/devContainersSpecCLI.js:257:2801)
[4447 ms]     at async pb (/home/userXYZ/.vscode-remote-containers/dist/dev-containers-cli-0.251.0/dist/spec-node/devContainersSpecCLI.js:257:1779)
[4447 ms]     at async DF (/home/userXYZ/.vscode-remote-containers/dist/dev-containers-cli-0.251.0/dist/spec-node/devContainersSpecCLI.js:263:2006)
[4448 ms]     at async to (/home/userXYZ/.vscode-remote-containers/dist/dev-containers-cli-0.251.0/dist/spec-node/devContainersSpecCLI.js:263:3110)
[4448 ms]     at async Ak (/home/userXYZ/.vscode-remote-containers/dist/dev-containers-cli-0.251.0/dist/spec-node/devContainersSpecCLI.js:383:8108)
[4458 ms] Exit code 1
[4460 ms] Command failed: /home/userXYZ/.vscode-remote-containers/bin/784b0177c56c607789f9638da7b6bf3230d47a8c/node /home/userXYZ/.vscode-remote-containers/dist/dev-containers-cli-0.251.0/dist/spec-node/devContainersSpecCLI.js up --workspace-folder /home/userXYZ/projects/projectXYZ --workspace-mount-consistency cached --id-label devcontainer.local_folder=\\wsl$\Ubuntu-20.04\home\userXYZ\projects\projectXYZ --log-level debug --log-format json --config /home/userXYZ/projects/projectXYZ/.devcontainer/devcontainer.json --default-user-env-probe loginInteractiveShell --mount type=volume,source=vscode,target=/vscode,external=true --skip-post-create --update-remote-user-uid-default on --mount-workspace-git-root true
[4460 ms] Exit code 1

Steps to Reproduce:

  1. Add devcontainer.json and Dockerfile
  2. Rebuild container (without cache)
  3. Error as seen in logs appears
  • I also tested the pre-release version which produced the same issue
  • the 0.245.2 version works just fine
  • We normally download the company certificates within the Dockerfile and then execute update-ca-certificates. Now since the new version it "seems" to me that all the feature installations like git happen before the dockerfile is executed?

Does this issue occur when you try this locally?: Yes
Does this issue occur when you try this locally and all extensions are disabled?: Yes

Thanks for you help

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.