Remote-containers: Error while attaching to a running container

[InsaneZulol]

• VSCode Version: 1.64
• Local OS Version:
• Remote OS Version: Red Hat Enterprise Linux Server release 7.7 (Maipo)
• Remote Extension/Connection Type: SSH + Docker
• Logs:

[101 ms] Remote-Containers 0.217.1 in VS Code 1.64.0 (5554b12acf27056905806867f251c859323ff7e9).
[101 ms] Start: Resolving Remote
[103 ms] Host: ssh://179.emea.net
[144 ms] Start: Run in host: id -un
[95224 ms] akaluza
[95225 ms] 
[95225 ms] Start: Run in host: cat /etc/passwd
[95342 ms] Start: Run in host: echo ~
[95444 ms] /home/akaluza
[95444 ms] 
[95445 ms] Start: Run in host: test -x '/home/akaluza/.vscode-remote-containers/bin/5554b12acf27056905806867f251c859323ff7e9/node'
[95559 ms] 
[95560 ms] 
[95560 ms] Exit code 1
[95560 ms] Start: Run in host: test -x '/home/akaluza/.vscode-server/bin/5554b12acf27056905806867f251c859323ff7e9/node'
[95663 ms] 
[95664 ms] 
[95664 ms] Start: Run in host: test -f '/home/akaluza/.vscode-server/bin/5554b12acf27056905806867f251c859323ff7e9/node_modules/node-pty/package.json'
[95774 ms] 
[95775 ms] 
[95775 ms] Start: Run in host: test -f '/home/akaluza/.vscode-remote-containers/dist/vscode-remote-containers-server-0.217.1.js'
[95900 ms] 
[95901 ms] 
[95984 ms] userEnvProbe: loginInteractiveShell (default)
[95984 ms] userEnvProbe shell: /bin/sh

Container: None
[98354 ms] Start: Run in Host: docker inspect --type container /_bash_run_447c0c24b07f
[99696 ms] Start: Check Docker is running
[99697 ms] Start: Run in Host: docker version --format {{.Server.APIVersion}}
[100032 ms] Server API version: 1.41
[100033 ms] Start: Inspecting container
[100033 ms] Start: Run in Host: docker inspect --type container b9c4f1a0ccf3d7cd6f85ac4d363a99074cb4c6169a6a3d68c9abc8da2615445f
[100922 ms] Start: Run in Host: docker exec -i -u root -e VSCODE_REMOTE_CONTAINERS_SESSION=a0bd62a9-aa59-4d7c-b877-282d073261181644260322876 b9c4f1a0ccf3d7cd6f85ac4d363a99074cb4c6169a6a3d68c9abc8da2615445f /bin/sh
[101020 ms] Start: Run in container: uname -m
[101429 ms] x86_64
[101429 ms] 
[101536 ms] 
[101537 ms] Start: Run in container: cat /etc/passwd
[101640 ms] Start: Run in container: test -d /root/.vscode-server
[101734 ms] 
[101734 ms] 
[101735 ms] Start: Run in container: test ! -f '/root/.vscode-server/data/Machine/.writeMachineSettingsMarker' && set -o noclobber && mkdir -p '/root/.vscode-server/data/Machine' && { > '/root/.vscode-server/data/Machine/.writeMachineSettingsMarker' ; } 2> /dev/null
[101844 ms] 
[101844 ms] 
[101844 ms] Exit code 1
[101844 ms] Start: Run in container: cat /root/.vscode-server/data/Machine/settings.json
[101947 ms] 
[101947 ms] cat: /root/.vscode-server/data/Machine/settings.json: No such file or directory
[101947 ms] Exit code 1
[101948 ms] Start: Run in container: test -d /root/.vscode-server/bin/5554b12acf27056905806867f251c859323ff7e9
[102036 ms] 
[102036 ms] 
[102036 ms] Exit code 1
[102036 ms] Installing VS Code Server for commit 5554b12acf27056905806867f251c859323ff7e9
[102038 ms] Start: Downloading VS Code Server
[102039 ms] 5554b12acf27056905806867f251c859323ff7e9 linux-x64 stable
[124244 ms] Error: connect ETIMEDOUT 117.18.232.200:443
        at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16)
[124244 ms] Exit code ETIMEDOUT

Steps to Reproduce:

I'm connected with a remote machine through SSH.
On this machine I have a docker container running and I want to access it's workspace with VSCode.

1. F1->
2. Attach to a running container
3. I select my container
4. Wait...

[vytautas-petrikas]

It looks like behavior of the extension has changed... It no longer downloads VS Code Server locally and instead tries to download it on the remote machine.

This is related to:
#6280
Please vote on:
#6274

[chrmarti]

@InsaneZulol Are you behind a network proxy?

[InsaneZulol]

@chrmarti Yes. It's corporate network.

For now I have downgraded VS Code to 1.63.2 and it works, so this is some regression thing.

[chrmarti]

This must be microsoft/vscode#142201 then. Tracking it there. Thanks.