Cancellation on streaming requests can lead to connection leak

[mathpl]

When doing a streaming request we can end-up leaking connections to the docker daemon if there's no activity on the stream. A simple example of this is calling Client.ContainerLogs() with Follow:true and stopping. No new logs must be generated from that point on. While we do have access to http.Response.Body to close it, the connection will only close on the next write error.

This module would make cancellation fairly easy to integrate with the current code.

[calavera]

I agree with you, it's a good feature to have for those requests that handle streams. We manage cancellations in the server already, so we should incorporate them in the client too.

[calavera]

Please, take a look at #35.

[mathpl]

Looks great!