vscode-remote-release icon indicating copy to clipboard operation
vscode-remote-release copied to clipboard

Failed to fetch control manifest: connect ETIMEDOUT

Open taoqf opened this issue 1 year ago • 7 comments

  • VSCode Version:1.89.1
  • Local OS Version:Debian 12
  • Remote OS Version:Debian 12
  • Remote Extension/Connection Type: Containers
  • Logs:
....
Loading 140 extra certificates from /etc/ssl/certs/ca-certificates.crt.
[131719 ms] Failed to fetch control manifest: connect ETIMEDOUT 185.199.111.153:443

Steps to Reproduce:

  1. open in container
  2. waiting for timeout.
  3. remote opened.

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

taoqf avatar Jun 05 '24 06:06 taoqf

It is an issue about network. We chineses could not access github smoothly. Is there a way to avoid this?

taoqf avatar Jun 05 '24 06:06 taoqf

Part of this is security related (we can put harmful Dev Container Features on a disallow list). It would be best to allow the connection. If you can't do that a workaround would be to immediately reject the connection at your network's firewall instead of letting it time out which takes a lot of time.

chrmarti avatar Jun 06 '24 07:06 chrmarti

Cancer? then Is there an configuration to set timeout?

taoqf avatar Jun 06 '24 08:06 taoqf

Not only github, there are to many connection we are been blocking.

taoqf avatar Jun 06 '24 08:06 taoqf

I'm not a networking expert, but the error message you posted above ETIMEDOUT suggests that some firewall is silently dropping your connection attempts. It would be much faster if that firewall actively rejected the connection attempt, so it immediately fails and doesn't wait until the timeout occurs.

We can look into lowering the timeout on our side, but that would still have to be a value long enough to let slow connections succeed.

chrmarti avatar Jun 06 '24 14:06 chrmarti

That would be nice then.

taoqf avatar Jun 07 '24 00:06 taoqf

Reopening to track lowering the timeout here. Thanks.

chrmarti avatar Jun 07 '24 06:06 chrmarti

Looking forward to customizable timeout too. Have same error:

[7515 ms] userEnvProbe is taking longer than 2 seconds. Process not found.
[7978 ms] Stop (3516 ms): Run: docker buildx version
[7980 ms] github.com/docker/buildx 0.12.1 0.12.1-0ubuntu2.1
[7980 ms] 
[7981 ms] Start: Run: docker -v
[8016 ms] Stop (35 ms): Run: docker -v
[8017 ms] Start: Resolving Remote
[8027 ms] Start: Run: git rev-parse --show-cdup
[8035 ms] Stop (8 ms): Run: git rev-parse --show-cdup
[144217 ms] Failed to fetch control manifest: 
[144223 ms] Start: Run: docker ps -q -a --filter label=devcontainer.local_folder=/home/titov_g/monorepo --filter label=devcontainer.config_file=/home/titov_g/monorepo/.devcontainer/devcontainer.json

But as you can see i haven't got an error type.

I'm not sure does this problem cause hang, but I don't see other slow tasks.

liftchampion avatar Sep 18 '24 17:09 liftchampion

#8808 Adding 127.0.0.1 containers.dev to /etc/hosts? Worked for me. See this.

richex-cn avatar Sep 20 '24 06:09 richex-cn

@richex-cn Thanks

taoqf avatar Dec 19 '24 09:12 taoqf