Error in deployment: no capacity available in gru

Hello,

I am trying to redeploy one application, but it is failing with a “no capacity available” error:

➜  ✗ flyctl deploy --verbose
==> Verifying app config
Validating /home/renne/projects/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 gru

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

Error: failed to fetch an image or build from source: failed to create volume: no capacity available in gru (Request ID: 01J0M67DSC0CV7YYJWD7RHWD5N-gru) (Trace ID: 4c3d3fa93804c76076cfed693a3fff5f)

Is there anything that I can do to be able to update my application?

1 Like

I have the same issue

2 Likes

Same issue

I thought it could be something with my application, but today I tried to redeploy another application that I have and had the same error. So right now I have two different applications that I can’t upgrade because of a platform error.

Thanks y’all for raising this issue, we started an incident and we are investigating:

The build is stuck for me and also having issues trying to attach a postgresql to the app.

app region: ewr

fly deploy
==> Verifying app config
Validating /Users/.../fly.toml
✓ Configuration is valid
--> Verified app config
==> Building image

Here’s an workaround in the meantime:

  1. Destroy your current builder if it exists: fly apps destroy BUILDER_APP_NAME

To find your builder name you can use fly apps list or go to your dashboard and look at the “App Builders” tab on the left.

  1. Choose a different builder region such as Rio de Janeiro (gig): FLY_REMOTE_BUILDER_REGION=gig fly deploy

This will make sure when you deploy your builder will be on gig if its not created yet.

1 Like

EDIT: It seems to be working for me.

After deleting the builder, FLY_REMOTE_BUILDER_REGION=gig fly deploy got me a new builder but it is still get stuck showing ====> Building image

That sounds familiar, I’ve heard some customers having issues when they’re under VPNs.

Can you try fly wg websockets enable to see if it helps then maybe fly wg websockets disable too in case that fails?

1 Like

worked for me, thank you!! :smile:

1 Like

The workaround didn’t work with me.

I don’t have any app builder to delete. I wrongly deleted my app, and now I am not able to relaunch it in a different region as it is not possible to link the app to an existing database machine.

I will not try this in other app that I have (that have a data storage linked) because probably I will face the same problem.

Waiting for a solution in gru region.

1 Like

We shipped a potential fix a couple minutes ago, confirmed on my end I can create volumes on gru. Can you give it a try?

I redeployed one app that wasn’t working and everything looks fine now :slight_smile:

Thanks!!!

1 Like

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