Ah. Well this caused me some confusion too!
I think, unless it has changed, that their docker daemon is not available in the way fly needs it to be.
In that … Codefresh can build docker images and deploy them, but only to a registry. And so under that set up, the flyctl would need to support being passed an already-made image (in a remote registry). So, not a fly-managed registry. And I don’t believe that currently is allowed? At least it wasn’t supported a while back.
The docker daemon within Codefresh is apparently not intended to be used via a system-style call, ie directly e.g I noticed they say “By default, and for security reasons, the Docker Daemon is not exposed to freestyle steps running on our SaaS environments. In other words, this approach cannot be used in our SaaS Runtime Environments.”
So maybe it is causing flyctl confusion too.
But the good news is that I’ve tried another deploy, which will have made a new remote builder to replace that one I just destroyed, and the deploy worked