Workaround for hang in dockerd when reading a tarfile over a socket
connection. Is this the only place where the race can occur in dockerd?
A workaround fix in dockerd, per

   https://groups.google.com/forum/#!msg/golang-nuts/PMm8nH0yaoA/sWDpPpjcdk8J

suggests that putting a read timeout in the http connection in
dockerd will mask the race condition.

I don't have time to hack on dockerd right now so I propose the following
temporary fix.
Merge pull request #122 from rakitzis/timeout

Workaround for hang in dockerd when reading a tarfile over http
Added support for automatic cleanup of objects that are run.
fix tests to pass with new container naming
Merge pull request #123 from iansmith/better_cleanup

LGTM
do more cleanup on ctrl+c
Merge pull request #124 from mcellis33/ctrlc

do more cleanup on ctrl+c
Big fat warning
Revert "do more cleanup on ctrl+c"

This reverts commit 027da2dec3dd36305321cd07cb68cd8f9aa20ed4.
Revert "fix tests to pass with new container naming"

This reverts commit 9bc46cd04b7261833f08355239c75adadac1e555.
Revert "Added support for automatic cleanup of objects that are run."

This reverts commit 6ac12ca5f588079b752cd0db3bcc359ed65c3f88.
Merge pull request #127 from jeffdh/revert_bad

Revert topo name, cleanup and ctrl-c work
Fake Stdin to make client library hijack work
Merge pull request #126 from jeffdh/fix_stdin_4real

Fake stdin to ensure the docker API libs don't exit early on hijack