Unable to deploy; Docker layers can't be pushed to registry.fly.io

Questions / Help
1

I’m currently unable to deploy any apps in the sea region. I’ve tried fly deploy with both --remote-only and --local-only, but in all cases the deploy hangs while trying to push Docker layers to registry.fly.io. The status of each layer remains at either “Waiting” or “Preparing”, with the “Preparing” layers occasionally retrying but continuing to be stuck.

For example:

==> Pushing image to fly
The push refers to repository [registry.fly.io/pie-gd-elasticsearch]
57346e92f405: Retrying in 1 second
4676f432612d: Retrying in 1 second
d7abfb850f92: Retrying in 8 seconds
ec38f0fbc826: Retrying in 5 seconds
c7b1b186be7c: Retrying in 1 second
196629012d43: Waiting
b8e43dae07e5: Waiting
8a989a27c6ad: Waiting
5f70bf18a086: Waiting
898c9863ca15: Waiting
f1aaa78493e8: Waiting
f5bb4f853c84: Waiting

If I wait long enough, the deploy will sometimes eventually fail with this error:

Error: failed to fetch an image or build from source: error rendering push status stream: received unexpected HTTP status: 500 Internal Server Error

There’s nothing unusual about the apps I’m trying to deploy; none are particularly large, and all have been successfully deployed in the past.

Is something wrong with registry.fly.io right now?

2

I have the same problem. I have this erro too:

Investigating 2023-11-21 00:41:34 UTC We are investigating elevated rates of error 500 when pushing images to our Docker registry.

1 Like
3

Looks like this is now acknowledged as an incident and is under investigation: Fly.io Status - Registry errors

1 Like
4

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