All my builds are failing due to resource limitations in depot builder. I keep trying to reset App Builders or change settings to increase RAM (after also increasing Node.js memory in Dockerfile) but Fly.io errors. It doesn’t even try to make an API request so it seems it’s an error in dashboard code.
There’s two alternatives here, mentioned a fair bit in this forum. One is that you use the local build option in the deploy command, and the other is that you do the build locally, push the image to the Fly registry, then do the deploy specifying the image.
So this does not answer your question, but does offer some alternatives, which may be a bit more reliable.
Yes, I had seen some of these workarounds so I switched to the --local-only deploy flag to get around this issue for now. We’re using Fly’s FlyCtl GitHub Action (with custom config file) so I simply changed this line from:
run: flyctl deploy --config apps/web/fly-qa-main.toml --remote-only
to:
run: flyctl deploy --config apps/web/fly-qa-main.toml --local-only
Interestingly enough, on the very next day the app builder’s reset and settings interface in the dashboard started working again.
I also noticed comparable – and sometimes better – build times with “local” builds so I’m leaving it for now. It would be nice to have more visibility into the Depot app builders but maybe we should just continue running builds this way.
1 Like
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.