Deploying on CI fails with --remote-only, only --local-only works currently

Questions / Help Build debugging
1

I have been having this issue since yesterday using fly after some months now.

only aftter setting the --local-only flag seems to deploy to the machines using docker btw

I got this error in CI - GithubActions

 
#12 [builder 2/5] WORKDIR /app
#12 CACHED

#13 [internal] load build context
#13 transferring context: 27B 3.3s
#13 transferring context: 249.10kB 8.5s
#13 transferring context: 1.80MB 13.8s
#13 transferring context: 3.31MB 19.1s
#13 transferring context: 4.55MB 24.5s
#13 transferring context: 5.03MB 29.7s
#13 transferring context: 5.57MB 35.2s
#13 transferring context: 5.63MB 38.6s done
#13 ERROR: rpc error: code = Canceled desc = grpc: the client connection is closing
------
 > [internal] load build context:
------
Error: failed to fetch an image or build from source: error building: failed to solve: rpc error: code = Canceled desc = grpc: the client connection is closing

Not sure how to proceed. Just pushed locally again to prod. This situation is not ideal!

2

Hi @pollux, I wonder if your remote builder app is unhealthy. You can try deleting it, which causes a fresh builder to spawn.

You’d do that by running fly apps list to find the app name starting with fly-builder, and then destroying that with fly destroy <builder-app-name> . The next deployment should use a new builder app.

Hope that helps!