Frozen setup_remote_docker step


#1

Hiya,

Our builds were reporting pipe2: too many open files errors earlier, so I SSH’d into a build to investigate. I reproduced the error, but after a few commands all docker commands locked up. Now whenever the docker engine VM with id prealloc-ffzgc5rd-c13e1d09-7027-4699-8a26-7c4351052341 gets allocated to our build, it never finishes starting up. If that engine is not used, it starts up fine. I do not see a way to force a new docker engine VM to start, nor does “build without cache” appear to circumvent the problem. Any ideas? This is blocking many of our builds, including staging and production.

Also, on builds that aren’t freezing, they still fail with this message:

Sending build context to Docker daemon  132.1kB

Error response from daemon: Untar error on re-exec cmd: pipe2: too many open files
Exited with code 1

Any help is greatly appreciated.

Cheers,

-Ian


#2

This topic was automatically closed 41 days after the last reply. New replies are no longer allowed.