'ERROR: Get https://registry-1.docker.io/v2/: net/http: TLS handshake timeout in Docker

I went through this link: Docker push - net/http: TLS handshake timeout, but it did not solved my issue. I am simply running the https://github.com/sqshq/PiggyMetrics using the docker-compose up command.

Status: Downloaded newer image for sqshq/piggymetrics-mongodb:latest
Pulling rabbitmq (rabbitmq:3-management)...
ERROR: Get https://registry-1.docker.io/v2/: net/http: TLS handshake timeout
[root@ech-10-1XXX PiggyMetrics]#
[root@ech-10-1XXX PiggyMetrics]# docker-compose up
Pulling rabbitmq (rabbitmq:3-management)...
ERROR: Get https://registry-1.docker.io/v2/library/rabbitmq/manifests/3-management: Get https://auth.docker.io/token?scope=repository%3Alibrary%2Frabbitmq%3Apull&service=registry.docker.io: net/http: TLS handshake timeout

Deployed and run the code on

uname -a

Linux ech-10-XXXX 4.1.12-61.1.18.el7uek.x86_64 #2 SMP Fri Nov 4 15:48:30 PDT 2016 x86_64 x86_64 x86_64 GNU/Linux



Solution 1:[1]

This most of the times happens when my internet connection is slow. Please check your internet connection and retry.

Solution 2:[2]

The reason is the network policy in my area.You can change your mirror address and try, in my cases, I changed the mirror address and works.I am using macOS Catalina:

"registry-mirrors" : [
    "https://dockerhub.azk8s.cn"
  ]

Hope this help you.

enter image description here

Solution 3:[3]

Try switching your internet connection. If you are connected via WiFi try connecting with LAN.

Solution 4:[4]

I was having same issue. It was fixed by resetting demon settings on Docker Desktop macOS Catalina. I hope It will work for you .

Possible Solutions

  1. Check internet speed and connect to Faster Internet

  2. Restart Docker

  3. Reset Demon Settings

enter image description here

Solution 5:[5]

Put debug: true under the docker-engine tab and restart the docker. This worked for me on MAC M1.enter image description here

Solution 6:[6]

If your region is restricted by the Docker server's use proxy.

Solution 7:[7]

On windows, try restarting the docker daemon.

Then log in with your docker Id docker login in your terminal...

Worked for me.

Solution 8:[8]

I suspect the issue is that the @ sign needs to be URL Encoded when you pass it into the Twilio SDK.

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution Source
Solution 1 Manuh.__
Solution 2 Dolphin
Solution 3 Girish Sharma
Solution 4
Solution 5 impyadav
Solution 6 behrad
Solution 7 Davidhero
Solution 8 tripleee