Deploy failed: "unhealthy allocations"

[dentarg]

What does this mean?

--> You can detach the terminal anytime without stopping the deployment
==> Monitoring deployment

v0 is being deployed
ccbe7a0c: fra pending
ccbe7a0c: fra running healthy
ccbe7a0c: fra pending
ccbe7a0c: fra running healthy
--> v0 failed - Failed due to unhealthy allocations - no stable job version to auto revert to and deploying as v1 

--> Troubleshooting guide at https://fly.io/docs/getting-started/troubleshooting/
Error abort

Troubleshooting your Deployment · Fly Docs mentions “unhealthy allocations” but the “fix” over there does not make sense in my case

Also, why isn’t PRIMARY_REGION respected? I’ve set it to ams. Sure, fly regions list --app <app> only lists fra, so I guess I need to add ams there too?

[dentarg]

@dentarg

Troubleshooting your Deployment · Fly Docs mentions “unhealthy allocations” but the “fix” over there does not make sense in my case

I’ll take that back, fly logs showed that the app doesn’t start

[Yaeger]

Probably we are having the same issue:

"Failed due to unhealthy allocations"

Our deploys have stopped working with error “Failed due to unhealthy allocations”. I think we haven’t changed anything that could contribute to this, because the commit that successfully deployed 2 hours ago, now doesn’t work anymore :l App is called staxcloud-staging