Busybox's timeout requires different arguments about wait-for-it HOT 10 CLOSED

If you are interested in adding support for busybox, please feel free to fork this repository and adjust it to your needs. If your modifications provide simultaneous compatibility with bash, I would welcome a pull request.

from wait-for-it.

See mirror/busybox@c9720a7

LOL, Busybox has fixed that. Newer busybox will not wok with workaround made for old one (!)

from wait-for-it.

While I like the idea of simultaneously supporting busybox, the problem is that busybox doesn't seem to support the /dev/tcp extension that is built into bash, which is an intrinsic requirement of wait-for-it. If you have different information, please let me know.

from wait-for-it.

Perhaps netcat could substitute?

nc -z $HOST $PORT seems like it's behaving similarly to /dev/tcp. nc appears to be part of busy box too. Though I don't really know the implications of switching or falling back. I guess "pure bash" may still prevent it's use.

from wait-for-it.

Also of note in this case, echoerr "$cmdname: timeout occurred after waiting $TIMEOUT seconds for $HOST:$PORT" is executed immediately after timeout fails with a status code of 127.

I'm wondering if it might be preferable that the script just waits the maximum time?

from wait-for-it.

@vishnubob have you looked into #6 yet?

from wait-for-it.

+1

bash-4.3# wait-for-it google.com:80
timeout: can't execute '15': No such file or directory
wait-for-it: timeout occurred after waiting 15 seconds for google.com:80

from wait-for-it.

#31 fixes the call to timeout on busybox while not breaking the the call to timeout on debian.

from wait-for-it.

Busybox support added with this pull request. Note that this does require bash to be installed on busybox.

from wait-for-it.

@iturgeon Thanks for posting this!! Helped me figure out why timeout was not working when switching from a fat ubuntu docker image to alpine.

from wait-for-it.