-
Notifications
You must be signed in to change notification settings - Fork 670
[proxy] use a container-local unix socket to get the address, instead of logs #1474
Conversation
return 1 | ||
fi | ||
fractional_sleep 3.1 | ||
done |
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
shift 4 | ||
output=$(docker exec $container curl -s -S -X $http_verb --unix-socket $socket "$@" http:$url) | ||
[[ -n "$output" ]] || return 1 | ||
echo $output |
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
3e34a23
to
5dc6771
Compare
The CircleCI tests are timing out. Please review my refactor commit. The only behavioural change is the retry reduction. I think that is correct; the 3s connect timeout in the normal status case doesn't usually kick in; if there is nothing listening then curl instantly fails. |
The retry reduction means we're doing 10 docker execs/second until the proxy starts. that seems a bit excessive to me. |
It's not excessive and exactly what happens with the router. We don't a delay of several seconds in |
With the router we're just doing an http request, not a docker exec, though. |
meh |
571a8d3
to
47c97e8
Compare
I had accidentally used |
Fixes #1453 and, #1472