Could not find image "registry.fly.io"

Questions / Help
1

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?

3 Likes
2

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?

3

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:

4

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.

1 Like
5

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

2 Likes
6

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

7

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 so it reports that the image cannot be found.

8

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-93f0d69e85f0c7f6c5784a10fcd3ecd622167679' remotely...
Error failed to fetch an image or build from source: Could not find image "registry.fly.io/[name of project]"
2 Likes
9

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

4 Likes
10

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.

11

Iā€™m having this exact same problem. Not sure what to do.

12

Weā€™re looking into this. Itā€™s intermittent and only impacting some images. How are you building and pushing the problematic images?

13

So Iā€™m now seeing a slightly different error from what everyone else is seeing, but suspect weā€™re all using roughly the same Github Actions ā€œtemplateā€ for a lot of this:

#25 exporting to image
#25 pushing layers 4.5s done
#25 ERROR: failed to push registry.fly.io/cp-ontolio-dev:44458d386930d31a2fcb20cbc0ad6027fbf6c226: failed to copy: io: read/write on closed pipe
------
 > exporting to image:
------
ERROR: failed to solve: failed to push registry.fly.io/cp-ontolio-dev:44458d386930d31a2fcb20cbc0ad6027fbf6c226: failed to copy: io: read/write on closed pipe
Error: buildx failed with: ERROR: failed to solve: failed to push registry.fly.io/THIS_IS_MY_IMAGE:44458d386930d31a2fcb20cbc0ad6027fbf6c226: failed to copy: io: read/write on closed pipe

Github Action code:

      - name: Build image šŸ³
        uses: docker/build-push-action@v3
        with:
          context: .
          push: true
          tags: registry.fly.io/THIS_IS_MY_IMAGE:${{ github.sha }},registry.fly.io/SAME_IMAGE_DIFFERENT_TAG:${{ github.sha }}
          target: MY_SOURCE_LOCATION
          cache-from: type=gha
          cache-to: type=gha,mode=max
14

That looks like this issue, which is also related to a buildkit upgrade: https://github.com/docker/build-push-action/issues/761

15

Iā€™m following the instructions in the Indie Stack readme:

  1. fly apps create project-name

  2. Create a token and add to my Github repo

  3. Add a SESSION_SECRET to your fly app secrets: fly secrets set SESSION_SECRET=$(openssl rand -hex 32) --app project-name

  4. Create a persistent volume for the sqlite database: fly volumes create data --size 1 --app project-name

  5. Commit and push changes to my repo which results in a failed deploy

16

Iā€™m also hitting this issue, following along with the Indie Stack Remix appā€¦

17

Thanks @michael , seems that one was a one off (which I might have to deal with at some point in time), seeing this as everyone else on other deploys:

Run flyctl deploy --config fly.api.toml --image registry.fly.io/qw-agent-api-dev:80bdd1df47cf7a9a5c1914e0312baddf605574a2
==> Verifying app config
--> Verified app config
==> Building image
Searching for image 'registry.fly.io/MY_APP-dev:80bdd1df47cf7a9a5c1914e0312baddf605574a2' locally...
Searching for image 'registry.fly.io/MY_APP-dev:80bdd1df47cf7a9a5c1914e0312baddf605574a2' remotely...
Error failed to fetch an image or build from source: Could not find image "registry.fly.io/MY_APP-dev:80bdd1df47cf7a9a5c1914e0312baddf605574a2"

Publish step:

#25 exporting to image
#25 pushing layers 17.7s done
#25 pushing manifest for registry.fly.io/MY_APP-dev:80bdd1df47cf7a9a5c1914e0312baddf605574a2@sha256:8a352b33a839c75f454604ea9ec8a31a658b700e324b536a9e19c50276373175
#25 pushing manifest for registry.fly.io/MY_APP-dev:80bdd1df47cf7a9a5c1914e0312baddf605574a2@sha256:8a352b33a839c75f454604ea9ec8a31a658b700e324b536a9e19c50276373175 4.0s done
#25 pushing layers 2.8s done
#25 pushing manifest for registry.fly.io/MY_APP-prod:80bdd1df47cf7a9a5c1914e0312baddf605574a2@sha256:8a352b33a839c75f454604ea9ec8a31a658b700e324b536a9e19c50276373175
#25 pushing manifest for registry.fly.io/MY_APP-prod:80bdd1df47cf7a9a5c1914e0312baddf605574a2@sha256:8a352b33a839c75f454604ea9ec8a31a658b700e324b536a9e19c50276373175 3.3s done
#25 DONE 69.8s

I donā€™t happen to have a non-ARM64 machine handy to validate that the image is indeed pullable (when I try to pull I get the common error about:

no matching manifest for linux/arm64/v8 in the manifest list entries
cannot fetch image
18
1 Like
19

Thank you, Michael! Changing docker/setup-buildx-action@v2 worked for me! Finally deployed :grin:

1 Like