compose: docker-compose slow, timing out

The system was working properly on the toolbox but now after the upgrade and removal of toolbox I’m getting timeouts or very slow builds… 5-10mins +

My docker-compose build is hanging at

[ home/docker ] - $ docker-compose --verbose build app
compose.config.config.find: Using configuration files: ./docker-compose.yml
docker.auth.auth.load_config: File doesn't exist
compose.cli.command.get_client: docker-compose version 1.8.0, build f3628c7
docker-py version: 1.9.0
CPython version: 2.7.9
OpenSSL version: OpenSSL 1.0.2h  3 May 2016
compose.cli.command.get_client: Docker base_url: http+docker://localunixsocket
compose.cli.command.get_client: Docker version: KernelVersion=4.4.15-moby, Os=linux, BuildTime=2016-07-28T21:15:28.963402499+00:00, ApiVersion=1.24, Version=1.12.0, GitCommit=8eab29e, Arch=amd64, GoVersion=go1.6.3
compose.service.build: Building app
compose.cli.verbose_proxy.proxy_callable: docker build <- (pull=False, stream=True, nocache=False, tag=u'docker_app', buildargs=None, rm=True, forcerm=False, path='/Users/bartdabek/Sites/docker', dockerfile='Dockerfile-app')
docker.api.build._set_auth_headers: Looking for auth config
docker.api.build._set_auth_headers: No auth config in memory - loading from filesystem
docker.auth.auth.load_config: File doesn't exist
docker.api.build._set_auth_headers: No auth config found

docker-compose up is failing

[ home/docker ] - $ docker-compose --verbose up app
compose.config.config.find: Using configuration files: ./docker-compose.yml
docker.auth.auth.load_config: File doesn't exist
compose.cli.command.get_client: docker-compose version 1.8.0, build f3628c7
docker-py version: 1.9.0
CPython version: 2.7.9
OpenSSL version: OpenSSL 1.0.2h  3 May 2016
compose.cli.command.get_client: Docker base_url: http+docker://localunixsocket
compose.cli.command.get_client: Docker version: KernelVersion=4.4.15-moby, Os=linux, BuildTime=2016-07-28T21:15:28.963402499+00:00, ApiVersion=1.24, Version=1.12.0, GitCommit=8eab29e, Arch=amd64, GoVersion=go1.6.3
compose.cli.verbose_proxy.proxy_callable: docker info <- ()
compose.cli.verbose_proxy.proxy_callable: docker info -> {u'Architecture': u'x86_64',
 u'BridgeNfIp6tables': True,
 u'BridgeNfIptables': True,
 u'CPUSet': True,
 u'CPUShares': True,
 u'CgroupDriver': u'cgroupfs',
 u'ClusterAdvertise': u'',
 u'ClusterStore': u'',
 u'Containers': 0,
 u'ContainersPaused': 0,
...
compose.cli.verbose_proxy.proxy_callable: docker inspect_network <- (u'docker_default')
compose.network.ensure: Creating network "docker_default" with the default driver
compose.cli.verbose_proxy.proxy_callable: docker create_network <- (ipam=None, driver=None, options=None, name=u'docker_default')
Traceback (most recent call last):
  File "<string>", line 3, in <module>
  File "compose/cli/main.py", line 61, in main
  File "compose/cli/main.py", line 113, in perform_command
  File "contextlib.py", line 35, in __exit__
  File "compose/cli/errors.py", line 56, in handle_connection_errors
TypeError: log_timeout_error() takes exactly 1 argument (0 given)
docker-compose returned -1

I’ve tried all the tricks people have been mentioning of using google dns, turning off wifi, adding hosts entries to include

127.0.0.1 localunixsocket 127.0.0.1 localunixsocket.local 127.0.0.1 localunixsocket.home

nothing is helping…

The amount of time I’ve spent over the past 6 months fighting docker is soo frustrating…

About this issue

Original URL
State: closed
Created 8 years ago
Reactions: 4
Comments: 17

Most upvoted comments

I was having this issue, and as @xeger points out, switching networks did the trick. In our case, we have found that the issue is resolved by changing the DNS server (we used Google’s 8.8.8.8). Don’t ask me why everything else works perfectly fine except docker-compose, but you may want to look into it.

sha1sum on Jan 13, 2017

updated 😃

raptor235 on Sep 13, 2016

Seeing the same problems listed here and have tried running a docker-compose --verbose up There’s a seemingly fixed 5s delay between these lines, as others have pointed out it’s probably a hard timeout:

docker.api.build._set_auth_headers: Sending auth config (u'https://index.docker.io/v1/')
compose.cli.verbose_proxy.proxy_callable: docker build -> <generator object _stream_helper at 0x0000000003EA39D8>

Even trying something like docker-compose ps is incredibly slow. You can see the slowness is in the same sort of areas:

compose.config.config.find: Using configuration files: .\docker-compose.yml
docker.auth.find_config_file: Trying paths: [foo]
docker.auth.find_config_file: Found file at path: foo\config.json
docker.auth.load_config: Found 'auths' section
docker.auth.parse_auth: Auth data for {0} is absent. Client might be using a credentials store instead.
docker.auth.load_config: Found 'credsStore' section
**compose.cli.command.get_client: docker-compose version 1.11.2, build f963d76f**
docker-py version: 2.1.0
CPython version: 2.7.13
OpenSSL version: OpenSSL 1.0.2j  26 Sep 2016
compose.cli.command.get_client: Docker base_url: http+docker://localnpipe
compose.cli.command.get_client: Docker version: KernelVersion=4.9.13-moby, Arch=amd64, BuildTime=2017-03-15T20:28:18.193664702+00:00, ApiVersion=1.27, Version=
17.03.1-ce-rc1, MinAPIVersion=1.12, GitCommit=3476dbf, Os=linux, Experimental=True, GoVersion=go1.7.5
**compose.cli.verbose_proxy.proxy_callable: docker containers <- (all=True, filters={u'label': [u'com.docker.compose.project=foo', u'com.docker.compose.oneoff=
False']})**
compose.cli.verbose_proxy.proxy_callable: docker containers -> (list with 0 items)
compose.cli.verbose_proxy.proxy_callable: docker containers <- (all=False, filters={u'label': [u'com.docker.compose.project=foo', u'com.docker.compose.oneoff
=True']})
**compose.cli.verbose_proxy.proxy_callable: docker containers -> (list with 0 items)**
Name   Command   State   Ports
------------------------------

I’ve highlighted the 3 problem lines, and they all come from compose.cli. Running a docker ps completes immediately. What else can I do to highlight the issue? This is absolutely crushing the experience.

herecydev on Apr 10, 2017

I’m having the same issue as @raptor235, also having tried all the tricks mentioned in various other issues to no avail. I also wish he would edit his post to use fenced code blocks so we could read the multi-line output.

maackle on Sep 12, 2016

I don’t have a solution to your issue, but it would probably be useful to used fenced code blocks so that others can read your multi-line content. For example, using the console highlighter:

$ docker --version
Docker version 1.12.0, build 8eab29e

christianbundy on Aug 16, 2016