Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docker pull returns Client.Timeout exceeded while awaiting headers) #5697

Closed
2 of 3 tasks
dgaffuri opened this issue May 17, 2021 · 4 comments
Closed
2 of 3 tasks

Docker pull returns Client.Timeout exceeded while awaiting headers) #5697

dgaffuri opened this issue May 17, 2021 · 4 comments

Comments

@dgaffuri
Copy link

  • I have tried with the latest version of Docker Desktop
  • I have tried disabling enabled experimental features
  • I have uploaded Diagnostics
  • Diagnostics ID:

Expected behavior

docker pull downloads requested container

Actual behavior

docker pull returns an error
Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

Information

  • Is it reproducible? yes
  • Is the problem new? yes
  • Did the problem appear with an update? yes
  • macOS Version: 11.3
  • Intel chip or Apple chip: Intel
  • Docker Desktop Version: 3.3.3
  • New virtualization framework enabled
  • It worked on 3.3.1, and after downgrading to 3.3.1
  • It works after disabling new virtualization framework

Steps to reproduce the behavior

  1. docker pull redis (or any other container)

~/Library/Containers/com.docker.docker/Data/log/vm/http-proxy.log contents when working

2021-05-17T10:21:17Z http-proxy time="2021-05-17T10:21:17Z" level=info msg="listening on /run/guest-services/http-proxy-control.sock for control messages"
2021-05-17T10:21:17Z http-proxy time="2021-05-17T10:21:17Z" level=info msg="rewritten http_proxy="
2021-05-17T10:21:17Z http-proxy time="2021-05-17T10:21:17Z" level=info msg="rewritten https_proxy="
2021-05-17T10:21:17Z http-proxy time="2021-05-17T10:21:17Z" level=info msg="http_proxy="
2021-05-17T10:21:17Z http-proxy time="2021-05-17T10:21:17Z" level=info msg="https_proxy="
2021-05-17T10:21:17Z http-proxy time="2021-05-17T10:21:17Z" level=info msg="no_proxy="
2021-05-17T10:21:17Z http-proxy time="2021-05-17T10:21:17Z" level=info msg="transparent HTTP ports: []"
2021-05-17T10:21:17Z http-proxy time="2021-05-17T10:21:17Z" level=info msg="transparent HTTPS ports: []"
2021-05-17T10:21:17Z http-proxy time="2021-05-17T10:21:17Z" level=info msg="listening on http.docker.internal:3128 for HTTP proxy requests"
2021-05-17T10:21:17Z http-proxy time="2021-05-17T10:21:17Z" level=info msg="starting HTTP proxy on 192.168.65.5:3128"
2021-05-17T10:21:17Z http-proxy time="2021-05-17T10:21:17Z" level=info msg="listening on 192.168.65.5:3129 for transparent HTTPS proxy requests"
2021-05-17T10:21:17Z http-proxy time="2021-05-17T10:21:17Z" level=info msg="starting transparent HTTPS proxy on 192.168.65.5:3129"
2021-05-17T10:21:18Z http-proxy time="2021-05-17T10:21:18Z" level=info msg="/vm/httpproxy <-"
2021-05-17T10:21:18Z http-proxy time="2021-05-17T10:21:18Z" level=info msg="HTTP proxy shutting down"
2021-05-17T10:21:18Z http-proxy time="2021-05-17T10:21:18Z" level=info msg="transparent HTTPs proxy shutting down"
2021-05-17T10:21:18Z http-proxy time="2021-05-17T10:21:18Z" level=info msg="rewritten http_proxy="
2021-05-17T10:21:18Z http-proxy time="2021-05-17T10:21:18Z" level=info msg="rewritten https_proxy="
2021-05-17T10:21:18Z http-proxy time="2021-05-17T10:21:18Z" level=info msg="http_proxy="
2021-05-17T10:21:18Z http-proxy time="2021-05-17T10:21:18Z" level=info msg="https_proxy="
2021-05-17T10:21:18Z http-proxy time="2021-05-17T10:21:18Z" level=info msg="no_proxy=*.local, 169.254/16, localhost.sideupreply.eu, api.sideupreply.eu"
2021-05-17T10:21:18Z http-proxy time="2021-05-17T10:21:18Z" level=info msg="transparent HTTP ports: [80]"
2021-05-17T10:21:18Z http-proxy time="2021-05-17T10:21:18Z" level=info msg="transparent HTTPS ports: [443]"
2021-05-17T10:21:18Z http-proxy time="2021-05-17T10:21:18Z" level=info msg="listening on http.docker.internal:3128 for HTTP proxy requests"
2021-05-17T10:21:18Z http-proxy time="2021-05-17T10:21:18Z" level=info msg="starting HTTP proxy on 192.168.65.5:3128"
2021-05-17T10:21:18Z http-proxy time="2021-05-17T10:21:18Z" level=info msg="listening on 192.168.65.5:3129 for transparent HTTPS proxy requests"
2021-05-17T10:21:18Z http-proxy time="2021-05-17T10:21:18Z" level=info msg="starting transparent HTTPS proxy on 192.168.65.5:3129"
2021-05-17T10:21:18Z http-proxy time="2021-05-17T10:21:18Z" level=info msg="/vm/httpproxy -> OK"
2021-05-17T10:26:26Z http-proxy 2021/05/17 10:26:26 [001] INFO: Running 1 CONNECT handlers
2021-05-17T10:26:26Z http-proxy time="2021-05-17T10:26:26Z" level=info msg="CONNECT to registry-1.docker.io:443"
2021-05-17T10:26:26Z http-proxy 2021/05/17 10:26:26 [001] INFO: on 0th handler: &{0 <nil> 0x55c8e4cc3fe0} registry-1.docker.io:443
2021-05-17T10:26:26Z http-proxy 2021/05/17 10:26:26 [001] INFO: Accepting CONNECT to registry-1.docker.io:443
2021-05-17T10:26:27Z http-proxy 2021/05/17 10:26:27 [002] INFO: Running 1 CONNECT handlers
2021-05-17T10:26:27Z http-proxy time="2021-05-17T10:26:27Z" level=info msg="CONNECT to auth.docker.io:443"
2021-05-17T10:26:27Z http-proxy 2021/05/17 10:26:27 [002] INFO: on 0th handler: &{0 <nil> 0x55c8e4cc3fe0} auth.docker.io:443
2021-05-17T10:26:27Z http-proxy 2021/05/17 10:26:27 [002] INFO: Accepting CONNECT to auth.docker.io:443

~/Library/Containers/com.docker.docker/Data/log/vm/http-proxy.log contents when NOT working

2021-05-17T10:37:09Z http-proxy time="2021-05-17T10:37:09Z" level=info msg="listening on /run/guest-services/http-proxy-control.sock for control messages"
2021-05-17T10:37:09Z http-proxy time="2021-05-17T10:37:09Z" level=info msg="rewritten http_proxy="
2021-05-17T10:37:09Z http-proxy time="2021-05-17T10:37:09Z" level=info msg="rewritten https_proxy="
2021-05-17T10:37:09Z http-proxy time="2021-05-17T10:37:09Z" level=info msg="http_proxy="
2021-05-17T10:37:09Z http-proxy time="2021-05-17T10:37:09Z" level=info msg="https_proxy="
2021-05-17T10:37:09Z http-proxy time="2021-05-17T10:37:09Z" level=info msg="no_proxy="
2021-05-17T10:37:09Z http-proxy time="2021-05-17T10:37:09Z" level=info msg="transparent HTTP ports: []"
2021-05-17T10:37:09Z http-proxy time="2021-05-17T10:37:09Z" level=info msg="transparent HTTPS ports: []"
2021-05-17T10:37:10Z http-proxy time="2021-05-17T10:37:10Z" level=info msg="rewritten http_proxy="
....
2021-05-17T10:37:19Z http-proxy time="2021-05-17T10:37:19Z" level=info msg="transparent HTTPS ports: []"
2021-05-17T10:37:19Z http-proxy time="2021-05-17T10:37:19Z" level=info msg="still retrying initial proxy setup after 10.034681834s, last error was listening on http.docker.internal:3128: listen tcp 192.168.65.1:3128: bind: cannot assign requested address"
@sharfaz
Copy link

sharfaz commented May 17, 2021

I am having similar issue on M1 mac with latest Mac OS update and updated docker desktop

❯ docker-compose up -d --build Docker Compose is now in the Docker CLI, try docker compose up`

Docker desktop Mac 3.3.3
Mac OS 11.3.1
Apple M1 Chip

Building app
[+] Building 30.8s (3/3) FINISHED
=> [internal] load build definition from Dockerfile 0.4s
=> => transferring dockerfile: 37B 0.0s
=> [internal] load .dockerignore 0.6s
=> => transferring context: 2B 0.0s
=> ERROR [internal] load metadata for docker.io/library/php:7.2-apache 30.0s

[internal] load metadata for docker.io/library/php:7.2-apache:


failed to solve with frontend dockerfile.v0: failed to create LLB definition: failed to do request: Head https://registry-1.docker.io/v2/library/php/manifests/7.2-apache: proxyconnect tcp: dial tcp 192.168.65.1:3128: i/o timeout
`

@stephen-turner
Copy link
Contributor

The new virtualization framework doesn't work with VPNs. This is as documented, and is out of our control.

@dgaffuri
Copy link
Author

dgaffuri commented May 18, 2021

I’m not using any VPN, but I realize only now that this is a duplicate of #5680. Sorry for the noise.

@docker-robott
Copy link
Collaborator

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked

@docker docker locked and limited conversation to collaborators Jun 17, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants