WARN Failed to start remote builder heartbeat: failed to create volume: no capacity available in arn

,
1

Hi. Unsure where to submit this.
It seems like an incident.

What can I do in the meantime? Change my primary_region in the fly.toml?

Thanks

2

Hi… It looks like there might be an environment variable that can be tweaked, :wrench:, as a temporary workaround:

https://community.fly.io/t/error-in-deployment-no-capacity-available-in-gru/20392/7

(This might also require --depot=false, these days.)

Hope this helps a little!

1 Like
3

Added builders, volumes

4

I have tried using the --depot=false parameter. (The output I got is the title of this topic)

Here is the output in it’s entirety. It is quite frustrating and I do not understand why it keeps saying “no capacity available in arn” because I have now destroyed the app several times and changed the primary_region every time to see if that helps. It did not.

<username>@fedora:~/<app>i$ fly deploy --depot=false
==> Verifying app config
Validating /home/<username>/<app>/fly.toml
âś“ Configuration is valid
--> Verified app config
==> Building image
WARN Failed to start remote builder heartbeat: failed to create volume: no capacity available in arn

==> Building image
WARN Failed to start remote builder heartbeat: failed to create volume: no capacity available in arn

Error: failed to fetch an image or build from source: failed to create volume: no capacity available in arn (Request ID: <request-id>-arn) (Trace ID: <request-id>)
5

I noticed that both my builders (one was default the other I created using fly deploy --depot-scope app) both are located in ARN.

How can I change this? Perhaps that will help me.

6

I kept trying to use fly deploy --depot-scope app and eventually it worked.

I suppose whatever caused the capacity issue has been resolved?

7

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.