Vscode-remote-release: Remote-Containers: Downloading VS Code Server Stuck When Attach to Running Container

Created on 16 Apr 2020  Â·  14Comments  Â·  Source: microsoft/vscode-remote-release

Version of VS Code

$ code --version
1.44.1
a9f8623ec050e5f0b44cc8ce8204a1455884749f
x64

What type of remote connection you were using
Containers

Your operating system

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.4 LTS
Release:    18.04
Codename:   bionic

The remote operating system you are connecting to

# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.1 LTS
Release:    18.04
Codename:   bionic

List of extensions that you have installed

$ code --list-extensions
ms-azuretools.vscode-docker
ms-vscode-remote.remote-containers
ms-vscode.cmake-tools
ms-vscode.cpptools
twxs.cmake
wesbos.theme-cobalt2
zxh404.vscode-proto3

Reproducible steps that cause the issue

  1. CLick _Open a remote window_ button on the left bottom
  2. Select "Remote-Containers: Attach to Running Container..."
  3. Select the running container

What you expected to see, versus what you actually saw
I expect the container is open, but what I saw is never end "Starting with Dev Container: Installing server" on the right bottom, and "Opening Remote..." with spin icon on the left bottom of the window.

Images, animations, or a link to a video showing the issue occurring
https://drive.google.com/file/d/1TxlA75w5p-Sa1cQffbm6ywKSlHmAAaUe/view?usp=sharing

Errors from the Dev Tools Console

[0 ms] Start: Resolving remote
[1 ms] Setting up container /ubuntu-18.04

[2 ms] Start: Run: docker inspect --type container /ubuntu-18.04
[43 ms] Start: Check Docker is running
[43 ms] Start: Run: docker info
[160 ms] Start: Inspecting container
[161 ms] Start: Run: docker inspect --type container cfba4ec0de861b5d84423fabc2cbd85164bc04c1e7a2d9721f71c494bc6aa427
[194 ms] Start: Run: docker exec -i -u root -e VSCODE_REMOTE_CONTAINERS_SESSION=6aea491b-a492-4801-a7d3-abf2cbe555801587026458139 cfba4ec0de861b5d84423fabc2cbd85164bc04c1e7a2d9721f71c494bc6aa427 /bin/sh
[196 ms] Start: Run in container: uname -m
[389 ms] x86_64
[389 ms] 
[389 ms] Start: Run in container: (cat /etc/os-release || cat /usr/lib/os-release) 2>/dev/null
[390 ms] NAME="Ubuntu"
VERSION="18.04.3 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.3 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
[390 ms] 
[390 ms] Start: Run in container: cat /etc/passwd
[391 ms] Start: Run in container: test -d /root/.vscode-server
[392 ms] 
[392 ms] 
[392 ms] Start: Run in container: set -o noclobber ; mkdir -p '/root/.vscode-server/data/Machine' && { > '/root/.vscode-server/data/Machine/.writeMachineSettingsMarker' ; } 2> /dev/null
[393 ms] 
[393 ms] 
[393 ms] Exit code 2
[393 ms] Start: Run in container: test -d /root/.vscode-server/bin/a9f8623ec050e5f0b44cc8ce8204a1455884749f
[393 ms] 
[393 ms] 
[393 ms] Exit code 1
[394 ms] Installing VS Code Server for commit a9f8623ec050e5f0b44cc8ce8204a1455884749f
[394 ms] Start: Run in container: mkdir -p /root/.vscode-server/bin/a9f8623ec050e5f0b44cc8ce8204a1455884749f_1587026459005
[395 ms] 
[396 ms] 
[396 ms] Start: Downloading VS Code Server

I leave it overnight and it still stuck.

bug containers needs-more-info

Most helpful comment

Still facing the same issue in Singapore, resolved by using a VPN to Seoul.

I added 51.144.164.215 update.code.visualstudio.com to my hosts file as a temporary hack (the result of nslookup update.code.visualstudio.com on the VPN) and it now works without the VPN.

Normally, update.code.visualstudio.com would resolve to 104.42.78.153 — probably an issue with this particular CDN at the moment.

All 14 comments

I change my internet from cable LAN to Wi-fi. Now after several minutes (around 1-5), this error appear

[0 ms] Start: Resolving remote
[1 ms] Setting up container /ubuntu-18.04

[2 ms] Start: Run: docker inspect --type container /ubuntu-18.04
[38 ms] Start: Check Docker is running
[38 ms] Start: Run: docker info
[124 ms] Start: Inspecting container
[124 ms] Start: Run: docker inspect --type container 5ec235b690f54d97a2e509b5a20a711d6093b3c8e432b2d95dc08aa7aaad58f1
[156 ms] Start: Run: docker exec -i -u root -e VSCODE_REMOTE_CONTAINERS_SESSION=d4e55bd4-a1d4-4eba-bb82-ca4b16c5e6c71587111755882 5ec235b690f54d97a2e509b5a20a711d6093b3c8e432b2d95dc08aa7aaad58f1 /bin/sh
[159 ms] Start: Run in container: uname -m
[325 ms] x86_64
[325 ms] 
[325 ms] Start: Run in container: (cat /etc/os-release || cat /usr/lib/os-release) 2>/dev/null
[326 ms] NAME="Ubuntu"
VERSION="18.04.4 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.4 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
[326 ms] 
[327 ms] Start: Run in container: cat /etc/passwd
[328 ms] Start: Run in container: test -d /root/.vscode-server
[328 ms] 
[328 ms] 
[328 ms] Exit code 1
[328 ms] Start: Run in container: test -d /root/.vscode-remote
[329 ms] 
[329 ms] 
[329 ms] Exit code 1
[329 ms] Start: Run in container: set -o noclobber ; mkdir -p '/root/.vscode-server/data/Machine' && { > '/root/.vscode-server/data/Machine/.writeMachineSettingsMarker' ; } 2> /dev/null
[331 ms] 
[331 ms] 
[331 ms] Start: Run in container: test -d /root/.vscode-server/bin/a9f8623ec050e5f0b44cc8ce8204a1455884749f
[332 ms] 
[332 ms] 
[332 ms] Exit code 1
[332 ms] Installing VS Code Server for commit a9f8623ec050e5f0b44cc8ce8204a1455884749f
[332 ms] Start: Run in container: mkdir -p /root/.vscode-server/bin/a9f8623ec050e5f0b44cc8ce8204a1455884749f_1587111756635
[334 ms] 
[334 ms] 
[334 ms] Start: Downloading VS Code Server
[265643 ms] Error: read ECONNRESET
        at TLSWrap.onStreamRead (internal/stream_base_commons.js:183:27)

I have the same problem.

I have resolved this problem by connecting to a VPN in Canada (I'm in Indonesia).
I encountered this kind of problem and the same solution when installing Visual Studio Enterprise 2019.
I don't know what causes this problem though.
I hope this helps.

@topazsorowako Thank you. I am also in Indonesia. I am resolved this problem by always retry to connect when the error occur, but only using Wi-Fi. If I use cable, the downloading VS Code Server will stuck.

Still facing the same issue in Singapore, resolved by using a VPN to Seoul.

I added 51.144.164.215 update.code.visualstudio.com to my hosts file as a temporary hack (the result of nslookup update.code.visualstudio.com on the VPN) and it now works without the VPN.

Normally, update.code.visualstudio.com would resolve to 104.42.78.153 — probably an issue with this particular CDN at the moment.

Why this server can't download with Remote Development, it's too slow to download.

I'm facing same issue.

Same problem here. Not able to build a development container while connected to my VPN service (if I disconnect from the VPN then everything works fine).

I get this issue sometimes, what I do is change to some different internet connection, and it works..

When this happens, could you check if downloading using curl works:

curl -v -L https://update.code.visualstudio.com/commit:89c002ab02f87102d91efc83c191ef1174756c6a/server-linux-x64/insider -o file.tgz

hi I experienced same issues 3 days ago and it still stuck at some points. Every time I open the folder into docker, after finishing building the image, it will be stuck on vs code server installation process

When this happens, could you check if downloading using curl works:

curl -v -L https://update.code.visualstudio.com/commit:89c002ab02f87102d91efc83c191ef1174756c6a/server-linux-x64/insider -o file.tgz

I've already tried to download using curl but it still doesn't work

<
  0 30.8M    0     0    0     0      0      0 --:--:--  0:00:02 --:--:--     0{ [5 bytes data]
  1 30.8M    1  511k    0     0   2454      0  3:39:48  0:03:33  3:36:15     0* OpenSSL SSL_read: Connection reset by peer, errno 54
  1 30.8M    1  511k    0     0   2451      0  3:40:04  0:03:33  3:36:31     0
* Closing connection 1
} [5 bytes data]
curl: (56) OpenSSL SSL_read: Connection reset by peer, errno 54

Are you on a VPN and/or behind a proxy?

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

mxdmedia picture mxdmedia  Â·  3Comments

robertlugg picture robertlugg  Â·  3Comments

abdullahiabdirahman picture abdullahiabdirahman  Â·  3Comments

grzegorz-silarski picture grzegorz-silarski  Â·  3Comments

sulume picture sulume  Â·  3Comments