'Error response from daemon: 400 Bad Request: malformed Host header'

[ambition-consulting]

I get the above mentioned error when pushing a docker image during mavenCanaryRelease on a single-node cluster (via docker private tagging).

I believe this has to do with this known issue, since the maven-builder image is build with docker 1.9.x . Interestingly, a simple upgrade to the newest version won't do either, since then I get an API conflict, presumably from the fabric8-docker-registry running on API 23, whilst the current docker install (after yum update docker), runs on API 24.

So, what worked for me was specifically updating docker on this builder to docker 1.10. I can create a pull request for that minor change, but would like to know if there is anything I understood wrong about the problem. Frankly I wonder why nobody else seems to encounter this problem, and if maybe I did something wrong during my gofabric8 standard deployment on GKE.

[jaseemabid]

@ambition-consulting Is this still an issue? We're probably running several builds everyday and haven't seen this one in a while.

[ambition-consulting]

I have switched to multi node because of this issue - not sure if it still affects single node clusters.