_stream_helper returns invalid JSON or cannot decode

[danpalmer]

docker-py
1.8.0

python
3.5.0

docker
Version 1.11.1-beta10 (build: 6662)

OS
Mac OS X 10.11 Beta 15A279b

---

While using https://github.com/6si/shipwright, I found that invalid JSON was being returned by docker-py. According to the docs, the output of client.build should be an iterable of valid JSON objects encoded as strings (or the JSON objects decoded if decode=True is passed). e.g.

'{"stream":"Step 1 : FROM ubuntu:xenial\\n"}'

However, I have found while using the setup listed above, that it is returning strings like:

'{"stream":"Step 1 : FROM ubuntu:xenial\\n"}\r\n{"stream":"Step 2 : COPY foo\\n"}\r\n'

(Note the trailing CRLFs as well, differs from the documentation)

I suspect this issue is being triggered by the Docker side of things, it looks like the chunks in the chunked response used to align exactly with JSON objects, but now no longer do, although I'm not familiar enough with the Docker API to know if this is correct.

I also suspect I reached this issue because of the pre-release Docker installation, however I see that docker-py doesn't list compatible Docker versions, which makes it difficult to know if this is a bug or unimplemented functionality.

[shin-]

I think there's an issue with requests concatenating the entire response when the connection closes before we start reading it. Do you think that could be what you're seeing?

If the objects are separated by CRLFs, we can easily parse that somewhere.

[danpalmer]

@shin- I don't think this is an issue with requests, it looks like docker-py assumes chunks will be at the JSON object boundary, and that something at the Docker API level has broken that previously-true assumption. Obviously there is no such guarantee from Requests, Docker (according to the docs), or HTTP. It looks like Docker is using "almost" line-delimited JSON, but with the difference that it sends CRLFs instead of just LFs.

I think the best solution to this would be to continually receive chunks into a buffer, and then attempt to consume CRLF delimited JSON objects out of that buffer. docker-py should be able to handle receiving a chunk that contains multiple JSON objects, or a chunk that doesn't contain any valid JSON and must be concatenated with past or future blocks for the JSON to be valid.

[danpalmer]

Quick note, I don't think this is an enhancement (as I understand them), this is a bug fix for me.

[danpalmer]

After some investigation about ways to solve this, it looks like _stream_raw_result and _stream_raw_result_old would be the correct way of doing this. I don't have the context for why these aren't being used here, but it looks like they solve this problem exactly. Much better to delegate the chunking to Requests I think.

[stromnet]

Hi,

seems like this issue describes a problem I'm seeing with docker-compose.

When doing docker restart <container>, where the container is started by docker-compose which is tailing the log, the docker-compose CLI sometimes emits the following:

CONTAINER exited with code 143
Exception in thread Thread-5:
Traceback (most recent call last):
  File "threading.py", line 810, in __bootstrap_inner
  File "threading.py", line 763, in run
  File "compose/cli/log_printer.py", line 190, in watch_events
  File "compose/project.py", line 343, in events
  File "site-packages/docker/client.py", line 253, in _stream_helper
  File "json/__init__.py", line 338, in loads
  File "json/decoder.py", line 369, in decode
ValueError: Extra data: line 2 column 1 - line 3 column 1 (char 689 - 1382)

Then it fails to output any more log data that container (which is now running, and also outputs proper logs if checked with docker logs).
From the trace of it, I guess this is not an actual docker-compose issue but just wanted to report it.

Env:

Mac OS 10.11.3

Docker For Mac Version 1.12.0-a (build: 11213, ad6ab836187e4111082447b7c0a6a74d01929a5c)

docker-compose version 1.8.0, build f3628c7
Docker version 1.12.0, build 8eab29e

[robbiet480]

This is still an issue for me as well (I'm having this in Ansible's docker_image module and got here through ansible/ansible-modules-core#4116 and then #4116).

The fix proposed in #1081 works perfectly for me. I suggest that gets merged.

[pmarques]

I also would like to see this released, I'm having some trouble right now to work this around.... 👍

[pmarques]

Thanks @shin- there is any expected date to be released?