fly deploy stucked on pushing

[Sirio7]

Hi everyone,
running fly deploy my app gets stuck on 926b35a05f1d: Pushing.

I’ve already tried to change the region but nothing changed.

[Yaeger]

Machines won't start!

Hi guys, the ams builder problem has drifted into a network problem with the S3 bucket used as registry backend. The difference with pushing layers from other regions is that the bucket has S3 Transfer Acceleration enabled, so Amsterdam will go into AWS from a different entrypoint than others. In the meantime we ~have destroyed~ are destroying all ams builders and instructed our system to recreate them in iad on your next application deploy. cheers.

Possibly related. Try destroying your builder and running the deploy again

[Sirio7]

It worked!
Thanks

[talhajunaid]

I am facing the same issue, I have tried destroying the builder and redeploy it but it’s not working.

My app region is SIN

[jfschwarz]

Same here: fly deploy gets stuck when pushing the image to the registry.

I’ve destroyed the builder and tried multiple times–without success.

[jfent]

@jfschwarz, you can force the builder to a non-ams region:

Machines won't start!

For people having problems with deploys that hang pushing docker image layers to the registry the way to unblock it is to destroy the builder app and start a new deploy forcing the builder region to iad # be sure you are running flyctl v0.2.51 or greater ❯ flyctl version flyctl v0.2.51 linux/arm64 Commit: 3cb555f3be736f5e50be72c20f8dfd268f8cf238 BuildDate: 2024-05-08T20:14:10Z # find the builder app name and destroy it ❯ fly apps list |grep builder fly-builder-winter-tree-7706 personal …