Confusing `fly deploy --remote-only` error with fly.toml `[build]` entry

[ignoramous]

vvishnu-indian

Hi @andig ,

I was finally able to recreate your exact errors.

• Deleted my remote builder
• Added in my fly.toml

  •  +    [build]
     +    image = “evcc/evcc:latest”

    • 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.

---

From: https://community.fly.io/t/10600/17

[andig]

It seems that the behaviour is such that when image is specified, no build will run? If that's the case, then:

• any use of the remote/local builder command line options should be an error (specifying builder when no build required)

If it's only the builder (here: a remote builder) that notices the problem that there's nothing to build then the builder should probably not error at all?