Docker Community Forums

Share and learn in the Docker community.

Version beta13 not working with compose


(Lenerd42) #1

Hi, since the update from beta 12 to 13 docker stopped working.
How can I go back to beta 12 for now?

Expected behavior

my containers start like before the update

Actual behavior

repeats this output with changed thread number

Exception in thread Thread-X:
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 149, in tail_container_logs
File “compose/cli/log_printer.py”, line 179, in wait_on_exit
File “compose/container.py”, line 239, in wait
File “site-packages/docker/utils/decorators.py”, line 21, in wrapped
File “site-packages/docker/api/container.py”, line 439, in wait
File “site-packages/docker/client.py”, line 154, in _raise_for_status
APIError: 500 Server Error: Internal Server Error (“dial unix /Users//Library/Containers/com.docker.docker/Data/*00000003.00000948: connect: connection refused”)

Information

  • the output of:
    • pinata diagnose -u on OSX

OS X: version 10.11.5 (build: 15F34)
Docker.app: version v1.11.1-beta13
Running diagnostic tests:
[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/20160526-102954.tar.gz
Most specific failure is: No error was detected
Your unique id is: DAA83CE2-D3EB-4183-B0F4-AD92FF2D8A13

  • host distribution and version ( OSX 10.10.x, OSX 10.11.x, Windows, etc )

OSX 10.11.5

I reinstalled and reset the docker client. The error won’t go away.

Steps to reproduce the behavior

I am not sure, a normal hello world works, even with compose.
However our 2 compose files inheriting from each other with about 250 lines of services don’t work.

I can not post them here, but they are compose v2 and use everything from images, over build and volumes to networks.
I know this might be not so easy to reproduce, but unfortunately I don’t have time right now, to narrow it down, to see were it breaks. It defiantly came up with beta13 though.

How can I go back to beta12