can't resolve host name

maxcnunes / waitforit

Wait until an address become available.

MIT License

173 stars 26 forks source link

can't resolve host name #11

Open Tjomas opened 7 years ago

Tjomas commented 7 years ago

Hi, if i use waitforit within a docker-compose project, the waitforit app can't resolve the database hostname on the first run.

I use the following command: waitforit -full-connection=tcp://database:3306 -timeout=20 -debug

On the first run the output is "ping TCP: 0.0.0.0:3306" until the 20 secound timeout comes in. On the secound run the output is "ping TCP: database:3306".

Setup: mysql:8 + node:7-alpine Node depends on the mysql database in the docker-compose.yml.

Is it possible to resolve the hostname on every request and not at the first start?

maxcnunes commented 7 years ago

That is weird. Why is the first time resolving the hostname to 0.0.0.0 and the other times it isn't? Could you provide a simple docker-compose so I can reproduce that?

maxcnunes commented 6 years ago

Closing for no updates. Please reopen it if you have new details.

Marek00Malik commented 5 years ago

Could you please reopen this ? Either it is a problem with my setup or the tool is wrongly recognising the host.

Example in: https://github.com/Marek00Malik/sqs-wait-for-it-example

Just run: ./run_example.sh -r test

Keep geting:

2019/04/15 06:36:54 Down: localstack:4571
2019/04/15 06:36:54 dial tcp: lookup localstack on 127.0.0.11:53: no such host

While running it outside from docker-compose, running locally: ./wait-for-it.sh -address=http://localhost:4571 -timeout=20 -- echo "SQS is READY" is running OK.