"error reading server preface" builder not ready

[ShedPlant]

What happened?

Sometimes but not always, building Image fails in GitHub Action CI with error "error reading server preface: EOF".

Retrying may work.

Example

    docker-build:index:Image (my-image):
      error: listing workers for Build: failed to list workers: Unavailable: connection error: desc = "error reading server preface: EOF"
  
    pulumi:pulumi:Stack (my-project.staging):
      error: update failed
  
      error: dial unix /run/buildkit/buildkitd.sock: connect: no such file or directory
  
    docker-build:index:Image (my-image):
      #0 building with "thirsty_elbakyan" instance using docker-container driver
      
      #1 [internal] booting buildkit
      #1 pulling image moby/buildkit:buildx-stable-1
      #1 pulling image moby/buildkit:buildx-stable-1 0.3s done
      #1 creating container buildx_buildkit_thirsty_elbakyan0
      #1 creating container buildx_buildkit_thirsty_elbakyan0 8.0s done
      error: listing workers for Build: failed to list workers: Unavailable: connection error: desc = "transport: Error while dialing: use of closed network connection"

Output of pulumi about

This is on my dev machine:

CLI          
Version      3.119.0
Go Version   go1.22.4
Go Compiler  gc

Plugins
KIND      NAME          VERSION
resource  aws           5.43.0
resource  docker-build  0.0.2
language  python        unknown

Host     
OS       darwin
Version  14.5
Arch     arm64

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

[ShedPlant]

It happens quite often and wastes a lot of CI and my time 😢 .

[blampe]

It happens quite often and wastes a lot of CI and my time 😢 .

Yes, ours too :(

@ShedPlant please try updating to 0.0.3 and let me know if the issue persists. That release includes a small change to wait for builders to boot, although I suspect the issue might persist.

[ShedPlant]

Thanks, I've upgraded to 0.0.3 and will let you know if I see the problem again.