logspout
logspout copied to clipboard
Container can't start on connection refused
During logspuot start if the connection to the log server fails (papertrail, BTW) the container fails to start
$ docker run -p 8000:8000 -v=/var/run/docker.sock:/tmp/docker.sock gliderlabs/logspout:latest tcp+tcl://yyyyyy.papertrailapp.com:xxPORTxx
# logspout v3.2.2 by gliderlabs
# adapters: raw syslog tcp udp tls
# options : persist:/mnt/routes
!! dial tcp zzzzzz:xxPORTxx: getsockopt: connection refused
The same happens with gliderlabs/logspout:v3 but it works on gliderlabs/logspout:v2
docker run -p 8000:8000 -v=/var/run/docker.sock:/tmp/docker.sock gliderlabs/logspout:v2 tcp+tcl://yyyyyy.papertrailapp.com:xxPORTxx
2017/09/01 17:52:38 routing all to tcp+tcl://yyyyyy.papertrailapp.com:xxPORTxx
2017/09/01 17:52:38 loading and persisting routes in /mnt/routes
2017/09/01 17:52:38 logspout v2 serving http on :8000
I believe this is now by design in v3
@michaelshobbs I guess so, but couldn't find it at v3 changelog :-(
Fair point
EDIT: I think it was a side effect of the retry logic TBH.