Failed to start remote builder heartbeat and Docker error

Questions / Help
1

I’m getting this error when I try to deploy an app. It’s in a GitHub action that worked fine yesterday.

Trying locally with debug logging gets me this:

==> Building image
DEBUG trying remote docker daemon
DEBUG --> POST https://api.fly.io/graphql

{
  "query": "mutation($input: EnsureMachineRemoteBuilderInput!) { ensureMachineRemoteBuilder(input: $input) { machine { id state ips { nodes { family kind ip } } }, app { name organization { id slug } } } }",
  "variables": {
    "input": {
      "appName": "MY-APP-NAME",
      "organizationId": null
    }
  }
}

DEBUG {}
DEBUG <-- 500 https://api.fly.io/graphql (201.94ms)

{
  "errors": [
    {
      "message": "You hit a Fly API error with request ID: 01H2XHBTNJP2KYXNH470CDSMNR-lax",
      "extensions": {
        "code": "SERVER_ERROR",
        "fly_request_id": "01H2XHBTNJP2KYXNH470CDSMNR-lax"
      }
    }
  ],
  "data": {}
}
WARN Failed to start remote builder heartbeat: You hit a Fly API error with request ID: 01H2XHBTNJP2KYXNH470CDSMNR-lax

Then a little later this:

DEBUG Trying 'Dockerfile' strategy
DEBUG --> POST https://api.fly.io/graphql

{
  "query": "mutation($input: EnsureMachineRemoteBuilderInput!) { ensureMachineRemoteBuilder(input: $input) { machine { id state ips { nodes { family kind ip } } }, app { name organization { id slug } } } }",
  "variables": {
    "input": {
      "appName": "MY-APP-NAME",
      "organizationId": null
    }
  }
}

DEBUG {}
DEBUG <-- 500 https://api.fly.io/graphql (919.04ms)

{
  "errors": [
    {
      "message": "You hit a Fly API error with request ID: 01H2XHBTZTJGKFF8KA5HVRCDXN-lax",
      "extensions": {
        "code": "SERVER_ERROR",
        "fly_request_id": "01H2XHBTZTJGKFF8KA5HVRCDXN-lax"
      }
    }
  ],
  "data": {}
}
DEBUG result image:<nil> error:error connecting to docker: You hit a Fly API error with request ID: 01H2XHBTZTJGKFF8KA5HVRCDXN-lax

https://status.flyio.net/ shows everything is good. Any help would be greatly appreciated!

2

Same here!

3

Sorry about that, can you try again now? We just deployed a fix.

4

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