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