Qarik-Group / concourse-tutorial

Learn to use https://concourse-ci.org with this linear sequence of tutorials. Learn each concept that builds on the previous concept.
870 stars 555 forks source link

Set CONCOURSE_WORKER_GARDEN_DNS_PROXY_ENABLE #250

Closed bvosk closed 3 years ago

bvosk commented 3 years ago

I was following the Hello World section of the concourse tutorial and ran into the following issue:

> fly -t tutorial execute -c task_hello_world.yml

executing build 1 at http://127.0.0.1:8080/builds/1
initializing
selected worker: ceb0899b4515
failed to ping registry: 2 error(s) occurred:

* ping https: Get "https://registry-1.docker.io/v2/": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
* ping http: Get "http://registry-1.docker.io/v2/": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
image check failed
errored

After some troubleshooting, I ran into this post on StackOverflow: https://stackoverflow.com/questions/48199558/concourse-cannot-reach-docker-registry. The instructions there fixed the issue, but I found that adding only the CONCOURSE_WORKER_GARDEN_DNS_PROXY_ENABLE environment variable was sufficient.

I don't know enough about the problem to say if this is appropriate in all scenarios, but I'm submitting this PR to start the discussion. This took me a couple of hours to fix. If this will save others some time, let's throw it in!

norman-abramovitz commented 3 years ago

The configuring of the container runtime is in flux as they move from Guardian to Containerd. It is not clear that the different failure modes belong in a tutorial. In 7.4.0 they backed off making contained the default at this time since migration is pretty rough.

https://concourse-ci.org/concourse-worker.html#configuring-runtimes

What is different about your environment that requires DNS proxy settings? Maybe we can describe that.

bvosk commented 3 years ago

I'm on macOS Big Sur Version 11.5.2. Not sure what about my environment would require that DNS proxy setting, so I thought others might encounter this too. I'll close this out so it doesn't gum up the works!