-
Notifications
You must be signed in to change notification settings - Fork 163
Hijack is incompatible with use of CloseNotifier #303
Comments
This is likely from connection re-use, which is automatic from the http package. In the client transport we'll either need to set |
This should work. Currently, I have to create a new Docker client for the |
This could probably be considered a golang bug. We should not have to manually manage this when the http package knows we've hijacked the connection. |
I belive fix for this was on go1.6 |
It would seem so. |
I get this bug with all versions of go, including tip. I think it's the docker engine that needs to be rebuilt with the new version of go. |
@cpuguy83 @LK4D4 saw that someone reported this issue on 1.12-rc3 (which uses go 1.6); moby/moby#12845 (comment) |
This is caused by moby/moby#12845
How can I fix this with
engine-api
?The text was updated successfully, but these errors were encountered: