Concourse CI Pipeline giving error :- Get https://registry-1.docker.io/v2: net/http: request canceled while waiting for connection

I installed Concourse CI using BOSH deployment on AWS.After successful installation i am able to see Concourse CI on browser.I have created hello-world pipeline using Concourse CI official page :- http://concourse.ci/getting-started.html
But when i am trying to run build for hello-world pipeline i am getting error :- Get https://registry-1.docker.io/v2: net/http: request canceled while waiting for connection Please let me know how i can fix this issue.Thanks in advance.
My CI Pipeline code :-

jobs:
– name: hello-world
plan:
– task: say-hello
config:
platform: linux
image: “docker:///ubuntu”
run:
path: echo
args: [“Hello, world!”]

  • How to send node.js logs to Cloudwatch Logs from Elastic Beanstalk Docker application?
  • How do you get a VPC Endpoint to work in a Docker container?
  • Multilayer Docker Deployment on AWS
  • how is cluster IP in kubernetes-aws configured?
  • Elastic Beanstalk Single-Container Docker current container name
  • AWS ECS container with tomcat + jdk
  • How to configure dns for concourse build container?
  • Separate CI workflows for multiple applications within same Git repo
  • Sharing directories in a Docker container both with a Dockerfile and after the container is running
  • Amazon Container Registry Only with ECS?
  • How to setup Continuous Integration (with Ansible)? [closed]
  • Framework auto-scale container docker on AWS
  • 3 Solutions collect form web for “Concourse CI Pipeline giving error :- Get https://registry-1.docker.io/v2: net/http: request canceled while waiting for connection”

    I met this problem too, but a little different.I use docker to install concourse ci. It fails with ping https://registry-1.docker.io/v2 always timeout. Finally, I found that the DNS address cause this problem. I bind specify the dns server address, then it works! So you should check your dns configuration. Hope this can help you!

    You can still refer this link [https://github.com/concourse/concourse/issues/347]

    enter image description here

    Image for details

    You can use the following command to restart your docker-machine, then the network will reconnect:

    $ docker-machine restart default
    

    Result:
    enter image description here

    More info: https://forums.docker.com/t/error-response-from-daemon-get-https-registry-1-docker-io-v2/23741/10

    Close your agent like following:

    enter image description here

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.