Expected behavior
Containers currently being managed via Docker Compose are stopped.
Actual behavior
The containers are stopped. But, an exception occurs along the way.
^CGracefully stopping… (press Ctrl+C again to force)
Stopping dockerconveris_converis_1 …
Stopping dockerconveris_converis-dis_1 …
Stopping dockerconveris_converis-search_1 …
Stopping dockerconveris_converis-chemistry_1 …
Stopping dockerconveris_converis-database_1 …
Exception in thread Thread-11:
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
Stopping dockerconveris_converis_1 … done
Stopping dockerconveris_converis-dis_1 … done
Stopping dockerconveris_converis-search_1 … done
Stopping dockerconveris_converis-chemistry_1 … done
Stopping dockerconveris_converis-database_1 … done
Information
king-mbp:docker-converis king$ pinata diagnose -u
OS X: version 10.11.4 (build: 15E65)
Docker.app: version v1.11.0-beta8.2
Running diagnostic tests:
[OK] docker-cli
[OK] Moby booted
[OK] driver.amd64-linux
[OK] vmnetd
[OK] osxfs
[OK] db
[OK] slirp
[OK] menubar
[OK] environment
[OK] Docker
[OK] VT-x
Docker logs are being collected into /tmp/20160427-161103.tar.gz
Most specific failure is: No error was detected
Your unique id is: 89DDA91E-6706-49D7-A40B-BE09ED265728
Please quote this in all correspondence.
Steps to reproduce the behavior
Unfortunately, I can’t provide my containers.
- docker-compose up
- wait for containers to start up
- Control-C