[5/5] libcloud git commit: changes for #918

[an...@apache.org]

changes for #918


Project: http://git-wip-us.apache.org/repos/asf/libcloud/repo
Commit: http://git-wip-us.apache.org/repos/asf/libcloud/commit/d6ec8912
Tree: http://git-wip-us.apache.org/repos/asf/libcloud/tree/d6ec8912
Diff: http://git-wip-us.apache.org/repos/asf/libcloud/diff/d6ec8912

Branch: refs/heads/trunk
Commit: d6ec8912350a71f0d22c633e1c0b64a8bb752262
Parents: d59e52c
Author: Anthony Shaw <an...@apache.org>
Authored: Mon Oct 24 13:29:36 2016 +0100
Committer: Anthony Shaw <an...@apache.org>
Committed: Mon Oct 24 13:29:36 2016 +0100

----------------------------------------------------------------------
 CHANGES.rst | 11 +++++++++++
 1 file changed, 11 insertions(+)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/libcloud/blob/d6ec8912/CHANGES.rst
----------------------------------------------------------------------
diff --git a/CHANGES.rst b/CHANGES.rst
index 4e5ae43..bfb38a1 100644
--- a/CHANGES.rst
+++ b/CHANGES.rst
@@ -37,6 +37,17 @@ Compute
   (GITHUB-856
   [Tom Melendez]
 
+Container
+~~~~~~~~~
+
+- [docker] As reported in the corresponding bug, the docker daemon will respond in an install_image call with all the messages
+  produced during the procedure parsed as json docs. In that case the response headers also contain the value 'transfer-encoding':'chunked'.
+  That kind of response can now be parsed properly by the DockerResponse parse_body method. Also, another small change is that previously
+  the id of the new image was marked in the json document as id, but now it's marked as sha256, so the regex used to discover the id
+  has been updated.
+  (GITHUB-918)
+  [Pavlos Tzianos]
+
 Storage
 ~~~~~~~