I solved it with the same technique listed in Hanging on Waiting for depot builder... , but why don’t the Fly team fix the depot builders?
Glad to hear you found that, and good question-- we do, we monitor depot builds closely! But since we had already had fly-native builders wired up, when we launched depot builds, we also kept support for native builders via the --depot=false flag. Taking a look at your depot builder setup in particular, you should be good to go now. If you still have problems, check out our diagnostic guide for deploys and let us know what you’re seeing!
The OP does raise a good point. I think I’ve only had a minor experience of the Depot issue, but it seems to have been raised in the forum quite a bit over the last 12+ months. Is it a problem at Depot that Fly has no control over?
@halfer Depot builders run on fly, so there’s a great deal that our infra and platform teams do to ensure builds are running smoothly whenever issues crop up, in addition to working with the depot team. Broadly speaking, depot builds have made fly deploys much more reliable. Since builder choice is upstream of any other way a deploy could fail, it’s also true that switching builder methods is likely at least a little over-represented as a solution/troubleshooting step when problems do happen.
Here’s my log of fly deploy. It has been like this (hang at “waiting for depot builder”) since the first time I used fly.
The app’s source code is here: https://git.sr.ht/~iacore/mpi-translations/tree/main/item/terms-search
Hi @iacore1, I’ve moved your deployer machines to a different region to see if that helps. Let me know if that provisions a Depot builder for you.