Expected behavior
clean stop containers with no error message
Actual behavior
weird stacktrace output
Information
- the output of:
ctrl + c
on OSX with a foreground runningdocker-compose up
is
Traceback (most recent call last):
File “/Users/claudio/.pyenv/versions/2.7.10/lib/python2.7/threading.py”, line 810, in __bootstrap_inner
self.run()
File “/Users/claudio/.pyenv/versions/2.7.10/lib/python2.7/threading.py”, line 763, in run
self.__target(*self.__args, **self.__kwargs)
File “/Users/claudio/.virtualenvs/SOMEVENV/lib/python2.7/site-packages/compose/cli/log_printer.py”, line 190, in watch_events
for event in event_stream:
File “/Users/claudio/.virtualenvs/SOMEVENV/lib/python2.7/site-packages/compose/project.py”, line 343, in events
decode=True
File “/Users/claudio/.virtualenvs/SOMEVENV/lib/python2.7/site-packages/docker/client.py”, line 233, in _stream_helper
data = json.loads(data)
File “/Users/claudio/.pyenv/versions/2.7.10/lib/python2.7/json/init.py”, line 338, in loads
```
- host distribution and version ( OSX 10.10.5, Version 1.11.1-beta13.1 (build: 8193))
Steps to reproduce the behavior
ctrl + c
a running docker-compose