[
https://issues.apache.org/jira/browse/LIBCLOUD-864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15591815#comment-15591815
]
Pavlos Tzianos commented on LIBCLOUD-864:
-----------------------------------------
Sample of response that is returned now:
......
{"status":"Pull complete","progressDetail":{},"id":"44710c456ffc"}
{"status":"Extracting","progressDetail":{"current":162,"total":162},"progress":"[==================================================\u003e]
162 B/162 B","id":"56e70ac3b314"}
{"status":"Extracting","progressDetail":{"current":162,"total":162},"progress":"[==================================================\u003e]
162 B/162 B","id":"56e70ac3b314"}
{"status":"Pull complete","progressDetail":{},"id":"56e70ac3b314"}
{"status":"Digest:
sha256:992069aee4016783df6345315302fa59681aae51a8eeb2f889dea59290f21787"}
{"status":"Status: Downloaded newer image for ubuntu:12.04"}
Same behavior on both linux and mac with docker v1.12.2 and api version 1.24
> Docker Driver install_image fails when parsing response
> -------------------------------------------------------
>
> Key: LIBCLOUD-864
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-864
> Project: Libcloud
> Issue Type: Bug
> Reporter: Pavlos Tzianos
> Priority: Minor
> Labels: easyfix, newbie
>
> In previous version of the docker api when the install_image() method was
> called, the response would be one json doc with a success or fail and the id
> of the pulled image of the id. Now, in docker api 1.24 the entire sequence of
> logs produced while pulling the image is returned in a chunked response. When
> the DockerResponse.parse_body() is called it fails to parse this response and
> an exception is thrown. Also, previously the id was returned in a field
> called, now the image id is returned in a field marked sha256.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
