Something weird is happening with the registry. I can publish an image but when I try to pull the same image I just pushed, it says it cannot be found. Is this a known issue?

There is some “stuff” going on: https://status.flyio.net/ That could be related! How are you pushing/pulling to the registry in your case?

I’m using github actions. Here is an example: indie-stack/deploy.yml at main · remix-run/indie-stack · GitHub to publish and for deploy: remix-run/indie-stack/blob/main/.github/workflows/deploy.yml#L208-L214 - name: 🚀 Deploy Production if: ${{ github.r…

Fly issues are all operational and this still seems to be broken. Weird thing is that I didn’t change anything regard how we do deployments.

We have also been getting this error today, it seems there is quite an important delay before an image is actually available.

We are currently getting this error. It blocks our entire deployment pipeline.

Cross posting: I investigated this error for quite awhile and while I don’t have anything concrete, I think the issue involves the Github action building the docker image for the “linux/amd64” platform (correctly) but when the fly cli is called, it’s not specifically looking for that platform and s…

I’m dealing with this same issue. I’m also using the Remix Indie Stack and am unable to deploy to production. This is the error I’m getting and I see no way around it. I’ve tried deleting and creating the images but it’s not helping. Searching for image 'registry.fly.io/[name of project]:main-93f0d…

Yep same for us, we’re using the deployment action based on the remix indie stack which has been working perfectly fine until today

First time deploying to Fly.io and I get this issue. Is there any fix or sign of communication from Fly.io ? It seems that this has been going on for 9 days without a solution. Honestly, doesn’t make me feel confident.

I’m having this exact same problem. Not sure what to do.

Fly.io

Could not find image "registry.fly.io"

Questions / Help

michael January 20, 2023, 12:55am 18

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…

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled