Error deploying from GitHub Action

I randomly get deployment issues from GitHub Action, and it’s getting frustrating. It works for a while, then I come back several days later with a new deployment, and it fails. Then I have to wait a while longer, and it starts working again.

I understand that this is a shared remote builder, but it seems really flakey to me. Is this something I should expect? And if so, is there a way to pay for a dedicated builder?

==> Building image
WARN Failed to start remote builder heartbeat: server returned a non-200 status code: 500
Error: failed to fetch an image or build from source: error connecting to docker: server returned a non-200 status code: 500
Error: Process completed with exit code 1.

We’ve also experience deployment issues today. I have assumed it’s related in some way to the current outage, but I would have liked to have seen an update by now Fly.io Status - State Issues

Yes, I saw that status entry. But it’s kind of vague and alludes to newly provisioned resources which I assumed meant new apps/machines and not deployments to existing apps.

Agreed, we were unsure of what these “new resources” were exactly. We were having similar issues deploying.

Fwiw, deploys seem to be working now.

1 Like

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