Hi folks,
tl;dr to fix this, run fly deploy from your laptop or other machine where you’ve done a full fly auth login authentication.
Explanation:
We’ve tracked this down to the following: Inactive builders are deleted after several days. When you run a deploy a new builder is created, so typically this behavior is transparent.
However, we’ve noticed that when there are no active builders and a deploy is started with a deploy-only token (typically seen in CI like Github, CircleCI and others), that token doesn’t have authorization to create a new builder. The error you see actually refers to being unable to deploy the builder app, not your own app.
The workaround we’ve identified is for you to run fly deploy --build-only from e.g. your laptop using a fully-authenticated fly session; i.e. one where you log in using fly auth login . That will create a new builder, and CI-driven deploys should then work.
We’re looking at fixing this so a deploy is always able to create a new builder so this doesn’t impact you or other users again.
- Daniel