# Cannot deploy docker app: Could not find image **URL:** \ **Category:** Questions / Help\ **Created:** [February 6, 2023, 12:34pm UTC](https://community.fly.io/t/cannot-deploy-docker-app-could-not-find-image/10600 "2023-02-06T12:34:12Z")\ **Posts on this page:** 1\ **Showing post:** 16
**Author:** ![Sam-Fly](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/sam-fly/32/48731_2.png) [@Sam-Fly](https://community.fly.io/u/Sam-Fly)\ **Post date:** [February 7, 2023, 4:33pm UTC](https://community.fly.io/t/cannot-deploy-docker-app-could-not-find-image/10600/16 "2023-02-07T16:33:14Z")
Hey @andig and @trevorm, it sounds like you may be running into the Buildkit issue described in this thread: > [@Deploying to Fly via GitHub Action failing](https://community.fly.io/t/deploying-to-fly-via-github-action-failing/10171/19): > > 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](https://github.com/actions/runner-images/commit/aeda6d33e8c58f4e6a3d7af0148e9ed3fda93e75#diff-d3f496e99457b699df2a5621c8f59cb52f60a050e1a88318af7d6f7069c12b2eL74-L78). 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](http://registry.fly.io) and Docker Hub. Now, I don’t see anything in the [BuildKit 0.10.0 release notes](https://github.com/docker/buildx/releases/tag/v0.10.0) that looks related, but something chang… Images built using buildkit v 0.10.0 return a 404 error when we try to pull the image from [docker.io](http://docker.io), or from our registry. That post describes a work around to force buildkit to use an older version when building an image. Since you’re using a prebuilt public image that won’t necessarily help in this case. As you’ve found out already, running `fly deploy` with the `--local-only` flag will work, because this uses your local docker daemon. If a local build isn’t an option for you, you can try downloading their public dockerfile and using `fly launch` to generate a fly.toml and build the image. If you don’t have an active remote builder on your org we automatically create one during the `fly deploy` process. Since your deploy is failing before we create the builder, you won’t see it listed. --- _[View the full topic](https://community.fly.io/t/cannot-deploy-docker-app-could-not-find-image/10600)._