My app is not being deployed due the following error.
WARN Failed to start remote builder heartbeat: You hit a Fly API error with request ID: 01GQWK6885ZG097C9GQ6W32F2G-maa
Error failed to fetch an image or build from source: error connecting to docker: You hit a Fly API error with request ID: 01GQWK69NP3GK0BY1ZY8F98X99-maa
I am running into this error since the past 3 hours and have tried
1)Deleting the app and rebuilding it
2)Deleting the docker file,exposing ports in dockerfile,deleting fly.toml and running
fly launch
fly deploy
Have also changed the locations but so far no luck
I still am unable to resolve the issue…The status of all services being displayed @ https://status.flyio.net/ indicate no issues…
Can someone hep me out?
WARN Remote builder did not start in time. Check remote builder logs with `flyctl logs -a fly-builder-dark-silence-168`
WARN Failed to start remote builder heartbeat: remote builder app unavailable
WARN Remote builder did not start in time. Check remote builder logs with `flyctl logs -a fly-builder-dark-silence-168`
Error failed to fetch an image or build from source: error connecting to docker: remote builder app unavailable
Not sure why that would be, but maybe there is a random fault with that particular builder?
You could try deleting it. Run fly destroy fly-builder-dark-silence-168.
Then when you next run fly deploy, Fly will see you have no remote builder. And make you another one. Which may solve the issue. Of course if that new remote builder also fails, well there is something else going on! But that’s worth a try first.
Hi Greg,
I have tried your suggestions but I find myself with the same errors…
WARN Failed to start remote builder heartbeat: You hit a Fly API error with request ID: 01GQXN1GHMD43W08QQAJFR847P-maa
WARN Remote builder did not start in time. Check remote builder logs with `flyctl logs -a fly-builder-summer-violet-1286`
Error failed to fetch an image or build from source: error connecting to docker: remote builder app unavailable
Also I’m having my builder logs which indicate its stuck on pulling the container image.same as @pyk
My app used to work fine during launch/deployment in the past week,but these started showing up since yesterday…
I’m afraid I don’t know what to suggest. My hack/fix is to delete the remote builder and hope its replacement works … but you’ve tried that and it hasn’t helped here. Hmm. I don’t know Fly’s innards. If the issue only started yesterday I wonder if there is some temporary issue with Fly in that region? Hopefully someone will be able to look up that API request ID to debug.
I have successfully deploy my app using fly deploy --local-only, this will use local docker to build the image instead of remote builder. If you want to try it, make sure you have docker running in your machine.
Hey thanks for the suggestion!
But the issue has been resolved and I’m able to deploy using the fly CLI…
Will surely try your solution next time if issues with remote-builder persist!
Thanks @greg. I had the same issue in AMS today. I destroyed the builder with fly destroy BUILDER_APP_NAME and ran fly deploy --remote-only and that worked for me
Having issues with fly machines… I’ve tried @PeterUllrich’s solution. Doesn’t seem to work for machines…
"errors": [
{
"message": "You hit a Fly API error with request ID: 01GRDXG0NEXE08M8XC0G3ZCZV7-ams",
"extensions": {
"code": "SERVER_ERROR",
"fly_request_id": "01GRDXG0NEXE08M8XC0G3ZCZV7-ams"
}
}
],
"data": {}
}
DEBUG result image:<nil> error:error connecting to docker: You hit a Fly API error with request ID: 01GRDXG0NEXE08M8XC0G3ZCZV7-ams
DEBUG --> POST https://api.fly.io/graphql```
```Testing authentication token... PASSED
Testing flyctl agent... PASSED
Testing local Docker instance... PASSED
Pinging WireGuard gateway (give us a sec)... PASSED
App specific checks for <app>:
Checking that app has ip addresses allocated... PASSED
Checking A record for <app>... PASSED
Oops, something went wrong! Could you try that again?```
$ /root/.fly/bin/flyctl deploy
==> Verifying app config
--> Verified app config
==> Building image
WARN Failed to start remote builder heartbeat: You hit a Fly API error with request ID: 01GRDYGMW93AXWZ81HDNBDA0B2-iad
Error failed to fetch an image or build from source: error connecting to docker: You hit a Fly API error with request ID: 01GRDYGQSSXJS0772T6CCDZR4P-iad
To be honest this is unacceptable. Fly is doing around for a few years already, but stability issues like this still popping up out of nowhere. I’ve used to recommend fly in my community but I can not anymore. While I’m capable of figuring out and troubleshooting issues like this, a lot of folks isn’t.
I know that in a large scale those errors are rare, but I’ve never had issues with Heroku, for example. Issues like this make experience very bad and made me think to move out.
Random builder failures, capacity issues in regions, random DNS failures, things like these… I know you guys doing a very good job on developing your own software to orchestrate all the things, and I really appreciate your work, but when I need to deploy my stuff and something is not working makes me super disappointed.
I have successfully deploy my app using fly deploy --local-only, this will use local docker to build the image instead of remote builder. If you want to try it, make sure you have docker running in your machine.
so after destroying the builder 100 times, now am able to update my machines…
i tried pushing manually to fly registry and update the image through cli, but it’s a pain in the ass since am on osx and fly won’t accept arm64 builds. had to set up docker buildx.
anyway, the whole thing was a waste of time. this is just disappointing even though it worked after a few hours.
I have the same error in a GitHub Actions deploy. You can see the full run here:
WARN Failed to start remote builder heartbeat: You hit a Fly API error with request ID: 01GREZ8KPGWD4KYFE9DBB5KJA3-iad
Error failed to fetch an image or build from source: error connecting to docker: You hit a Fly API error with request ID: 01GREZ8MY6R7Y3QME9KYAPT6NH-iad
