Hi @andig ,
I was finally able to recreate your exact errors.
- Deleted my remote builder
- Added
[build]
image = “evcc/evcc:latest”
in my fly.toml
- Did a fly deploy
App is not running, deploy…
==> Building image
Searching for image ‘evcc/evcc:latest’ remotely…
Error failed to fetch an image or build from source: Could not find image “docker.io/evcc/evcc:latest”
It can be noted that fly is not launching a new remote builder in this case and is failing.
To fix this, I removed
[build]
image = “evcc/evcc:latest”
from my fly.toml and did a deploy and a new builder got created and the image from docker.io got pulled successfully.
==> Verifying app config
→ Verified app config
==> Building image
Remote builder fly-builder-old-cloud-5251 ready
==> Creating build context
→ Creating build context done
==> Building image with Docker
→ docker host: 20.10.12 linux x86_64
[+] Building 0.3s (0/1)
[+] Building 4.7s (6/6) FINISHED
=> [internal] load remote build context 0.0s
=> copy /context / 0.1s
=> [internal] load metadata for docker.io/evcc/evcc:latest 1.2s
=> [1/2] FROM docker.io/evcc/evcc:latest@sha256:92554c8e0f4ec89abf679062ac56941b13554ba03692a13b0040190686a11dfe 3.1s
Without a remote builder --remote-only flag during deployment is of no use. May be flyctl can provide a better error message.
→ Pushing image done
image: registry.fly.io/**************
The Dockerfile for my app has the following and the dockerfile builder is the only option that can work for your case.
FROM evcc/evcc:latest
It has also been noted that the flyctl image builder is only working for public images in DH and not for all.
This image works andig/evcc:latest
==> Building image
Searching for image ‘andig/evcc:latest’ remotely…
image found: img_xdkzvqmmwddp9nmw
But not with evcc/evcc:latest
Searching for image ‘evcc/evcc:latest’ remotely…
Error failed to fetch an image or build from source: Could not find image “docker.io/evcc/evcc:latest”
Looks like an issue with the evcc user on DH.