Remote builds with Depot fail at waiting for builder

1

Is there an outage on depot or in the communication between fly and depot? 90% of pipelines fail and those that succeed take a really long time. Only able to deploy with --local-only or --depot=false

==> Building image
Waiting for depot builder...

==> Building image
Waiting for depot builder...

Error: failed to fetch an image or build from source: error building: context deadline exceeded
Error: Process completed with exit code 126.

UPDATE: could be because of the capacity issues at FRA region, will revisit to close if it’s the case.

1 Like
2

I’ve seen a few Depot issues reported here in the last month or so. I wonder if folks should be switching it off in their pipelines? Does it build at an acceptable speed if you choose that option?

3

--depot=false is quite slow, i wouldn’t go there
--local-only depends on the machine, depot is still better but if it’s unreliable, this will be our new default

2 Likes
4

I’m experiencing this too. They work most of the time, but take really long (e.g. 6 min instead of 1.5 min).

Just a few week ago I had experimented with going back to building directly on GitHub Actions as I tried improving performance by using cache mounts (to cache the PNPM store and Next.js build). Back then the slower GitHub Actions Docker build would eliminate any improvements gained by the caching. But with the current build times it seems it would be the better option.