concourse / concourse-pipeline-resource

!!! use the `set_pipeline` step instead !!!
https://concourse-ci.org/jobs.html#schema.step.set-pipeline-step.set_pipeline
MIT License
76 stars 42 forks source link

Can't use docker network DNS resolution for target #50

Open benabineri opened 5 years ago

benabineri commented 5 years ago

We're using the docker images (on ECS) and the worker container is linked to the web container on the address concourse-web. ECS/Docker modifies /etc/hosts but presumably that isn't propagated through to the garden resource check containers. Is it possible to verify whether this resource would actually look at /etc/hosts?

Thanks.