UnixDomainSocketInitializer uses configured docker host in connect()

[aantoniadisatypon]

As described in this comment UnixDomainSocketInitializer is using a default value for the socketPath instead of the one configured.

[bsideup]

@aantoniadisatypon merged, thanks!
FYI next release will use OkHttp transport by default, but your change is still helpful for the ones who want to switch back to Netty :)

[aantoniadisatypon]

@bsideup thank you! are there any plans regarding the release date?

[bsideup]

@aantoniadisatypon yes :) There will be RC1 later this week

[rnorth]

We have this out in a Release Candidate build (1.9.0-rc1) for anyone who is keen to try it!

Release notes

[aantoniadisatypon]

@bsideup It turns out that now we need to change ResourceReaper class as well to get the dockerHostPath from the dockerConfig, since it uses a hardcoded value for the socket and it fails to start if we use a different value for docker host. See PR #862