microsoft / microsoft/vscode-remote-release
[Remote-SSH Bug]: Proxy not configured when Adding container definition
Open
@chrmarti is already working on this.
Since Sep 19, 2024.
bug
containers
proxy
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 469
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
- VSCode Version: 1.93.1
- Local OS Version: Windows 11 Enterprise
- Remote OS Version: Debian Bookworm
- Remote Extension/Connection Type: Remote - SSH
Logs:
Logs
[383 ms] Dev Containers 0.384.0 over Remote - SSH 0.114.3 in VS Code 1.93.1 (38c31bc77e0dd6ae88a4e9cc93428cc27a56ba40). [382 ms] Start: Loading environment from ExecServer [449 ms] Host OS: linux 6.1.0-25-amd64 [449 ms] Host CWD: /home/user/project [449 ms] Start: Run: /bin/sh [561 ms] Start: Run in host: echo ~ [709 ms] /home/user [710 ms] [710 ms] Start: Run in host: id -un [840 ms] user [841 ms] [841 ms] Start: Run in host: (command -v getent >/dev/null 2>&1 && getent passwd 'user' || grep -E '^user|^[^:]*:[^:]*:user:' /etc/passwd || true) [920 ms] userEnvProbe: loginInteractiveShell (default) [920 ms] userEnvProbe: not found in cache [920 ms] userEnvProbe shell: /usr/bin/zsh [1134 ms] userEnvProbe PATHs: Probe: '/home/user/bin:/usr/local/bin:/usr/bin:/bin:/usr/games' Container: None [1527 ms] Initializing configuration support... [1527 ms] Internal initialization of dev container support package... [3127 ms] Entering createDevContainerConfig_v2 [9624 ms] Preparing to apply Template 'ghcr.io/devcontainers/templates/dotnet' [9626 ms] Running Dev Containers CLI: templates apply --workspace-folder C:\Users\user\AppData\Local\Temp\tmp-output-dir-1726774943736 --template-id ghcr.io/devcontainers/templates/dotnet --template-args {"imageVariant":"8.0-bookworm"} --features [] --tmp-dir C:\Users\user\AppData\Local\Temp\tmp-dir-1726774943736 --log-level debug --omit-paths [".github/dependabot.yml"] [9634 ms] ProxyResolver#loadSystemCertificates count [9637 ms] ProxyResolver#loadSystemCertificates count filtered [9639 ms] Start: Run: C:\Users\user\AppData\Local\Programs\Microsoft VS Code\Code.exe c:\Users\user\.vscode\extensions\ms-vscode-remote.remote-containers-0.384.0\dist\spec-node\devContainersSpecCLI.js templates apply --workspace-folder C:\Users\user\AppData\Local\Temp\tmp-output-dir-1726774943736 --template-id ghcr.io/devcontainers/templates/dotnet --template-args {"imageVariant":"8.0-bookworm"} --features [] --tmp-dir C:\Users\user\AppData\Local\Temp\tmp-dir-1726774943736 --log-level debug --omit-paths [".github/dependabot.yml"] [9880 ms] [2024-09-19T19:42:23.988Z] @devcontainers/cli 0.69.0. Node.js v20.15.1. win32 10.0.22631 x64. [9884 ms] [2024-09-19T19:42:23.994Z] Loading 45 extra certificates from C:\Users\user\AppData\Local\Temp\vsch\certificates-cf4d0cfca8eda6ada23ef127d757c6cf21e9d9ab6174beb248396493164e5894.pem. [31021 ms] Error: connect ETIMEDOUT 140.82.113.34:443 [31021 ms] at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1606:16) { [31021 ms] errno: -4039, [31021 ms] code: 'ETIMEDOUT', [31021 ms] syscall: 'connect', [31021 ms] address: '140.82.113.34', [31021 ms] port: 443 [31021 ms] }Steps to Reproduce:
- Connect to remote server with Remote - SSH
- Run command: Dev Container: Add Dev Container Configuration Files ...
- Select any configuration and let process
I'm behind a corporate proxy and the remote machine is correctly configured with proxy environment variables (both docker and shell environment).
Error appears to be occurring when fetching the manifest on the local machine.
I believe the proxy is correctly configured on my local machine as VSCode is able to download and install the remote server as well as update and download extensions.
I think the problem is occurring due to @devcontainers/cli not correctly setting / inheriting the proxy config.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.