compose: docker-compose build hangs

Had the issue, and as for @dmoliveira it was because of a too heavy repo.

Adding big files to .dockerignore solved it!

Maybe a warning message when the loading context step takes more than x seconds would be helpful?

Cheers

I have the same on Ubuntu 16.04

root@npw-01:/home/username/dev/public-express# docker-compose --verbose build --force-rm
compose.config.config.find: Using configuration files: ./docker-compose.yml
docker.auth.find_config_file: Trying paths: ['/root/.docker/config.json', '/root/.dockercfg']
docker.auth.find_config_file: No config file found
compose.cli.command.get_client: docker-compose version 1.13.0, build 1719ceb
docker-py version: 2.2.1
CPython version: 2.7.12
OpenSSL version: OpenSSL 1.0.2g  1 Mar 2016
compose.cli.command.get_client: Docker base_url: http+docker://localunixsocket
compose.cli.command.get_client: Docker version: KernelVersion=4.4.0-75-generic, Arch=amd64, BuildTime=2017-05-04T22:10:54.638119411+00:00, ApiVersion=1.29, Version=17.05.0-ce, MinAPIVersion=1.12, GitCommit=89658be, Os=linux, GoVersion=go1.7.5
compose.project.build: redis uses an image, skipping
compose.service.build: Building express-www-prod
compose.cli.verbose_proxy.proxy_callable: docker build <- (pull=False, stream=True, nocache=False, cache_from=None, tag=u'publicexpress_express-www-prod', buildargs={}, forcerm=True, rm=True, path='/home/username/dev/public-express', dockerfile=None)

In docker log only one string DEBU[0363] Calling GET /v1.22/version

At same time, docker build -t latest . works fine

Docker version 17.05.0-ce, build 89658be

UPD: I have added .dockerignore file with

.git
node_modules

And my build was successfull. Seem like issue in context size, or file count.

One piece of info. For me is because of heavy files inside of the building image. Even if you use docker-compose build --no-cache it didn’t work. The solution was to put the heavy files in the .dockerignore only to not pass to the building at *.Dockerfile (e.g., my Solr cores with 100GB). After that, I could build very fast the image and access the files shared at volumes section on docker-compose.yml. I hope that help others. 😃

@dukedave wow I was suffering from the same problem. Great job working that out.

Here’s a quick command for everyone:

# In your project directory
find . -type p -delete &&\                                                                                                                                                                                                     
docker-compose build

Mystery solved - User error

I didn’t realize that the whole directory gets sent as “context” to the docker daemon. I had very large sql export files in the path (that are not copied to the container.) Moved them out of the build dir and all is well.

=================

Having the same problem, for the last week or so. docker-compose build hangs for about 20 minutes before completing. I added a .dockerignore file with .git entry. I don’t have any fifo. I tried the “chrome issue” fix, I’ve tried clearing the docker config auth. Nothing works. Considering going to virtualbox/toolkit. What else can I do?

My info:

$ docker version Client: Version: 17.03.1-ce API version: 1.27 Go version: go1.7.5 Git commit: c6d412e Built: Tue Mar 28 00:40:02 2017 OS/Arch: darwin/amd64

Server: Version: 17.03.1-ce API version: 1.27 (minimum version 1.12) Go version: go1.7.5 Git commit: c6d412e Built: Fri Mar 24 00:00:50 2017 OS/Arch: linux/amd64 Experimental: true

$ docker-compose version docker-compose version 1.11.2, build dfed245 docker-py version: 2.1.0 CPython version: 2.7.12 OpenSSL version: OpenSSL 1.0.2j 26 Sep 2016

Sweet mother of god.

There’s a SO post which mentions docker-compose build hangs when chrome is open (link)

My colleague was using Safari and his was working. I told him to open chrome and try again. It failed

Armed with this knowledge, I was able to fix by:

1. Update Chrome
2. Quit Chrome
3. rm -rf <my repository>
4. clone and setup repository
5. docker-compose build 👍
6. Open chrome
7. docker-compose build 👍

What. On. Earth.

Update This did not last. When I rebooted docker, it started to hang again.

Hey 😃

Just in case, I had the same problem but very different reason. In my docker-compose folder there’s a data folder that should have been ignored and is HUGE. The hanging was because of “sending context to the docker daemon” (more than 20G of context…), and this message was not displayed by docker-compose --verbose.

Docker Black Magic™

I just realized that my context (actual folder) was too big. So I moved my dockerfile to another folder and change my docker-compose.yml:

#...
services:
   app:
     build:
       context: ./another-folder-here
       dockerfile: YourDockerfileNameThatIsInsideAnotherFolderHereOrRemoveThisPropertyIfTheNameIsDockerfile

# ....

Argh, after much lamenting, it seems I was suffering from #4623 all along! I deleted my fifo pipes and it works perfectly.

---

The rest of this comment is somewhat redundant since I found the actual cause (⬆️) But I’ll leave it here for archival purposes (and so I don’t feel bad about how much time I spent writing it up 😊 ).

---

I’m seeing this also.

I was able to work around it by manually building the images with docker and tagging them with a name which matches the one docker-compose generates, e.g:

docker build -t myapp_web . 

Then I was able to docker-compose up web and have it start without hanging.

---

I re-read the comments and here’s some relevant bits from my set up:

• Ubuntu 16.04.2 LTS (4.4.0-79-generic)
• Docker version 17.03.1-ce, build c6d412e, installed from the repo, per here.
• docker-compose version 1.13.0, build 1719ceb, installed via the curl approach here.
• This is what I see when trying to build. I’ve left it there for several hours and nothing.
• This is what start up looks like via journalctl. Nothing else is written when I try the build.
• This is what running in debug. When I run build I see the three GET calls at the bottom, then nothing.

---

I’ve tried:

• Clean ~/.docker/config.json
• Logged in / out of Docker Hub.
• Deleting containers / images.
• Various .dockerignore files.

---

I rolled back to try compose 1.12.0 and 1.11.2 (via curl)and they all have the same issue. Will try downgrading my Docker version next. FYI this issue started occurring for me after I updated both Docker and docker-compose, unfortunately I did both at the same time, and both were (IIRC) rather big jumps.

---

I also just tried Docker engine 1.11.2 and 1.12.3 (installed via a .deb) and those seem to hang too.

In my case, docker-compose was hanging on a massive node_modules tree. Ignoring node_modules with a .dockerignore file solved the issue.

I had this problem, for me the fix was updating the version at the top of the docker-compose files to “2.1”

I just realized that my context (actual folder) was too big. So I moved my dockerfile to another folder and change my docker-compose.yml:

#...
services:
   app:
     build:
       context: ./another-folder-here
       dockerfile: YourDockerfileNameThatIsInsideAnotherFolderHereOrRemoveThisPropertyIfTheNameIsDockerfile

# ....

This just fixed my build too. It seems maybe building is searching through directories for some reason and hanging, even when told which files to read? As soon as I moved my dockerfiles into a subfolder and modified the context rather than sitting in the root, my builds stopped hanging and ran perfectly.

For me, docker hangs (actually just goes incredibly slowly) whenever I’m connected to the ‘eduroam’ WiFi (http://eduroam.org) - pointing at some weird reliance on network conditions.

I was seeing the same issue - EOF on step x/y while running docker-compose up --build.

Thanks to all you guys I looked in my repo for the largest files - found a test.log that was nearly 10GB… .gitignored, but not .dockerignored. Once I added it to the .dockerignore my build sped up abt 3x as fast and finished no problem.

Beefing up my .dockerignore now…

In my case, it was fixed adding my fifo to .dockerignore, as I use vim-plumber.

I’ve just checked if this has anything to do with my local login information. I logged out of all services

$ cat ~/.docker/config.json
{
        "auths": {}
}

docker-compose build still hangs. Then I logged in to Docker Hub (only). Still didn’t work.

Having the same issue… Mac OS Sierra

$ docker version
Client:
 Version:      17.03.0-ce
 API version:  1.26
 Go version:   go1.7.5
 Git commit:   60ccb22
 Built:        Thu Feb 23 10:40:59 2017
 OS/Arch:      darwin/amd64

Server:
 Version:      17.03.0-ce
 API version:  1.26 (minimum version 1.12)
 Go version:   go1.7.5
 Git commit:   3a232c8
 Built:        Tue Feb 28 07:52:04 2017
 OS/Arch:      linux/amd64
 Experimental: true

$ docker-compose version
docker-compose version 1.11.2, build dfed245
docker-py version: 2.1.0
CPython version: 2.7.12
OpenSSL version: OpenSSL 1.0.2j  26 Sep 2016

UPDATE: I left docker-compose sitting there for about 10 minutes with this as the last verbose message:

compose.cli.verbose_proxy.proxy_callable: docker build <- (pull=False, stream=True, nocache=False, tag=u'goliath_tmp_php', buildargs=None, rm=True, forcerm=False, path='/Users/jdrummond/Google Drive/www/goliath', dockerfile='./docker/phpfpm.dockerfile')

After that, it also stuck here for a couple minutes:

docker.api.build._set_auth_headers: Looking for auth config
docker.api.build._set_auth_headers: Sending auth config (u'https://index.docker.io/v1/')

And finally managed to proceed with the build.

The full output: https://gist.github.com/jlcd/f26c3a8283e54f2279d6844154277a8a

For anyone having the same issue with WSL, the correct Docker for Windows issue @patricknazar mentioned is the following: https://github.com/docker/for-win/issues/7808

As it seems, a recent Windows (Insider) release broke clip.exe, consequentially breaking docker-credential-desktop.exe. This bug is being discussed at https://github.com/microsoft/WSL/issues/5648

Also, this note present at the Docker for Windows issue worked for me:

Observation: Removing ~/.docker/config.json seems to solve the issue, but this file is re-created after restarting Docker or rebooting Windows.

Adding .dockerignore works, thanks https://github.com/docker/compose/issues/4396#issuecomment-301476026

I was facing same issue, docker-compose build hang, and reason at my end was I didn’t have enough space. After creating some space its start working.

In my case, .git folder had an issue, when I added it to .dockerignore, it started to work

Could I ask what y’all have in your .dockerignore files (if anything)? We have this delightful mess at the moment, and I think this might have something to do with the hang we’re experiencing:

**/*.cache
**/*/*.cache
**/*/*/*.cache
**/*/*/*/*.cache
**/*/*/*/*/*.cache
*.pyc
**/*.pyc
**/*/*.pyc
**/*/*/*.pyc
**/*/*/*/*.pyc
**/*/*/*/*/*.pyc
__pycache__
**/__pycache__
**/*/__pycache__
**/*/*/__pycache__
**/*/*/*/__pycache__
**/*/*/*/*/__pycache__