`fly deploy` stuck on "Waiting for remote builder"

1

It’s impossible for me to deploy for the last few hours. It gets stuck on “Waiting for remote builder”.

image
image1654×300 55.3 KB

After a while it errors with:

Error failed to fetch an image or build from source: error connecting to docker: remote builder app unavailable

I ran fly destroy a few times on the builder but it doesn’t change anything.

2 Likes
2

hey, thank you for letting us know. It looks like this builder got into a weird state – this one should be good to go now, and we’re working on a general fix for this as well. Please let us know if you run into this error moving forward !

1 Like
3

Thank you!

4

@eli - found this thread, so, quickly replying you here. Hope this is fine. Actually I am also facing same issue today. Please find screenshot attached. Could you help me with it please?
Flyio-error

5

@eli I face the same issue right now. Destroyed the app, destroyed the builder, still hangs forever. Thanks in advance

6

@eli Hi! I found this thread. I have a same problem :disappointed_relieved:

スクリーンショット 2022-09-29 184804
スクリーンショット 2022-09-29 184804742×100 16.3 KB

7

I had the same issue as well so I destroyed the builder with
fly apps destroy fly-builder-name

Now when I try to deploy I get:

Error failed to fetch an image or build from source: error connecting to docker│
: You hit a Fly API error with request ID: REDACTED

Are we sure there’s not an outage of some sort @eli?

8

Seems to be happening again:

❯ fly deploy --remote-only
==> Verifying app config
--> Verified app config
==> Building image
Error failed to fetch an image or build from source: error connecting to docker: You hit a Fly API error with request ID: 01GE54E86KC51C0AKW36RTDF17-hkg
9

Same…

image
image1285×350 13.2 KB

This is getting frustrating :frowning:

10

Same :frowning:

11

Would love an acknowledgment at least that y’all have seen this and are on it if possible? Desperately trying anything I can on my end to deploy my app lol :sweat_smile:

2 Likes
12

Error failed to fetch an image or build from source: error connecting to docker: upstream service is unavailable

13

Tried running with LOG_LEVEL=debug:

{
  "data": {
    "ensureMachineRemoteBuilder": null
  },
  "errors": [
    {
      "message": "upstream service is unavailable",
      "locations": [
        {
          "line": 1,
          "column": 54
        }
      ],
      "path": [
        "ensureMachineRemoteBuilder"
      ],
      "extensions": {
        "code": "SERVICE_UNAVAILABLE"
      }
    }
  ]
}
2 Likes
14

Seems like it’s being looked at! The status page just updated:

2 Likes
15

Not sure if this could be related, but I first tried to resolve by destroying my free builder. A new one was automatically created, but the storage on it is growing out of control
image

16

image
image1656×168 15.7 KB

17

That’s kind of fun! I’m not sure that’s accurate (honestly have no idea), but the builders work off the machines API and there’s an open issue right now (https://status.flyio.net) so hang tight!

1 Like
18

Hey folks! This incident should be resolved now, and we just released v0.0.399 of the flyctl which should help with some of the inconsistencies waiting for your builder.

19

Still hanging for me, and fly version update does nothing (it says 0.0.399 is available, but then brew tries to install 0.0.398)

20

Ah brew versions take a little bit of time to update.

You could use this other install method if you prefer which receives new versions a little quicker GitHub - superfly/flyctl: Command line tools for fly.io services