Build stuck on Validating connection to Docker daemon

Pipeline Workflows
1

What is currently happening?

Build is on the Initializing Process step and is stuck Validating connection to Docker daemon...

What are the expected results?

I expect the initialization process to complete in a few seconds and proceed to the Clone step

Details

Upon commiting a change to our repository a codefresh CI build kicks off and usually finishes without failure. However, several builds have failed now and restarting them does not resolve the issue.

How to reproduce

  1. Make a code change
  2. Commit code change
  3. Push to github repo
  4. CI build is triggered
  5. Initializing Process gets stuck

Impact

We currently can’t deploy our app because the build doesn’t succeed?

2

Codefresh Support were able to help. The solution was a combination of increasing resource size and setting Minimum disk space required for build filesystem which fixed the issue.

1 Like
3

The Codefresh runner failing before the Docker daemon can completely init is the cause of this issue, not Docker itself. It just hangs at “validating connection” with no helpful error when disk or resources are limited.

Your solution makes sense. Builds are kept from landing on a half-dead node by increasing the resource size and imposing a minimum disk space requirement. In most cases, runner pressure or residual Docker layers—rather than the pipeline itself—are the cause of sporadic issues.