Can't pull docker image from fly.io registry after github actions outage

[gyowanny]

Hi,
Today there was a Github actions outage and after that my deploys stopped working even after the issue was fixed. Now I’m getting the following error:

Searching for image 'registry.fly.io/canvc-0f4c:main-1a6d052ba73e51d7e34ac130955ed46b218ca080' remotely...
Error failed to fetch an image or build from source: Could not find image "registry.fly.io/canvc-0f4c:main-1a6d052ba73e51d7e34ac130955ed46b218ca080"

Can someone help me? I’m blocked.

[wjordan]

We’re still working on this:

Deploying to Fly via GitHub Action failing

We’re still working on this. One thing we’re investigating is whether the “current” Ubuntu runner generates images differently. We’ve managed to replicate some of the errors with different buildkit/oci flags, so it’s possible a default changed.

[gyowanny]

Oh, cool thanks for the heads up. Good luck !

[michael]

Deploying to Fly via GitHub Action failing

We may have found the issue and a workaround. It looks like sometime earlier today GitHub updated the ubuntu runner which bumped the version of BuildKit from 0.9.1 to 0.10.0. Images built with this version of BuildKit are returning a 404 when our backend attempts to fetch the image manifest from the target registry before a deployment. This is happening for both registry.fly.io and Docker Hub. Now, I don’t see anything in the BuildKit 0.10.0 release notes that looks related, but something chang…

[gyowanny]

It worked now! I updated the definition with the version property. Thanks for the support.