Are the the details in the comment above definitely true?
The details that are posted are true as far as I have been able to determine. The Jenkins docker-plugin fails automated tests when those tests are configured to run with Apache httpclient 5 API plugin 5.4-118.v199115451c4d. They pass when those tests are configured to run with Apache httpclient 5 library 5.3.1-110.v77252fb_d4da_5. Users have reported that the docker-plugin fails in production when attempting to use a Unix domain socket if the Apache httpclient 5 API plugin 5.4-118.v199115451c4d is used.
* Is this an Apache regression?
Yes, as far as I can tell, this is a regression in the Apache httpclient 5 API plugin 5.4-118.v199115451c4d, since that is the only component that changed from the working case to the non-working case.
* Is there a matching bug logged against the httpcomponents library?
Not for this case. I've not yet taken the time to extract enough details for a bug report to the httpclient issue tracker. Are you interested in doing that investigation and submitting the issue? I don't have an account on the Apache issue tracker.
* Is someone (Apache?) missing a regression test? Or is this an unsupported use of that library and docker-plugin should change?
I assume there is a missing test because this is the second release of Apache httpclient 5 that has broken the Jenkins docker-plugin use through the docker-java library. Are you offering to investigate further?
Apologies if this is the wrong place to ask this question.
Are the the details in the comment above definitely true?