I’m attempting to build my app with fly deploy --build-target=prod --build-only And my build appears to be hanging ❯ fly deploy --build-target=prod --build-only ==> Verifying app config --> Verified app config ==> Building image Remote builder fly-builder-broken-wood-6619 ready ==> Creating buil…

For anyone else that encounters the same problem, I realised that instead I could pass the --local-only flag as I don’t strictly need a build server (I have the docker daemon running locally) fly deploy --local-only

This is most likely because the “docker context” is very large. Does it say how much data it’s trying to send? --local-only is a good workaround since it doesn’t have to push it over a network.

I had this error as well. The context size was only 63.7kb which left me puzzled (my network is slow but not that slow :slightly_smiling_face:) Also just switched to --local-only after i couldn’t resolve the issue.

This happens every time with my Fly projects. It makes no difference what size of container, anything except for a --local-only deploy will hang indefinitely.

[image] Remote builder connection timeout It looks like the builder ran out of space, which means the Docker daemon cannot start on it. [image] Remote builder connection timeout A quick fix for the space issue is to fly apps destroy your-builder-app. This worked in my case.

I had the same issue, tested with the image from the example Serve Small With Fly.io and GoStatic . # Dockerfile FROM pierrezemb/gostatic COPY ./public/ /srv/http/ [image] It happens quite randomly, sometimes fly apps destroy your-builder-app helps, sometimes not. I can suppose that it may happe…

Bumping into this constantly as well. Rarely, destroying the builder helps. Not sure how this is an issue when my context is pretty small (118 directories, 456 files). It’s a Laravel app that doesn’t have a lot of files, and dockerignore has been configured to be opt-in by directory. Running local-o…

I’ve also been having this issue for the past couple of days. I did a wireguard reset which worked for a while but now I’ve had to go back to --local-only

Fly build hangs sending context to docker daemon ([internal] load remote build context timeout)

Questions / Help Build debugging

salimb January 12, 2023, 5:08am 7

This worked in my case.

can't update my app(