Fixed bug in utils.mkbuildcontext for BytesIO Dockerfiles
- resetting dockerfile seek position to 0 after dockerfile.getvalue() is called
- prevents traceback on line utils.py line 43
- 'IOError("end of file reached")' in tarfile.py
Should be done for StringIO objects as well
Add support for tailing logs (introduced in API : v1.13)
Updated default version to v1.13
Added support for 'cpuset'
Expand registry URL before login.
Make history() return json.
Clear the UNIX connection sockets properly
Test resource warnings when using the client
Add tests to sdist.
Add tests to sdist.
Change remove_image to check if image is a dictionary and use Id value if it is.
Remove trailing whitespace.
Catch invalid path in build method

The server responds with an unuseful message (server error EOF), which
happens because an empty tar file is sent over. So check in the client,
who knows why that's happening and tell the user.
Added pause/unpause methods.
Unit and integration tests for pause/unpause.
Add support for filtering images and containers

[`filters` is a json encoded value of the filters (a map[string][string]) to process on the images list. ][1]
The tricky thing is that we must convert boolean value to string and any filter value to list to make a `map[string][string]` json format

[1]: https://docs.docker.com/reference/api/docker_remote_api_v1.14/#list-images
Stop TLS sockets being closed when attaching

When calling attach_socket, the response is garbage collected,
which triggers a close method on the file object, closing the socket.
This stop the response from being garbage collected until we've
finished with the underlying socket.

Fixes #350

Signed-off-by: Ben Firshman <ben@firshman.co.uk>
Ship 0.5.2

Signed-off-by: Ben Firshman <ben@firshman.co.uk>
Merge pull request #352 from bfirsh/fix-tls-sockets-being-closed-when-attaching

Stop TLS sockets being closed when attaching
Merge pull request #353 from bfirsh/ship-0.5.2

Ship 0.5.2