[repeat of an email sent to support late last night]
Hey Fly!
I’m attempting to deploy from a GitHub action and running into a permanently (?) dead remote builder.
Removing --remote-only
lets me through. I can provide the builder app name in DMs.
In .github/workflows/staging.yml
deploy:
name: Deploy app
# needs: [tests, static_code_analysis]
runs-on: ubuntu-latest
steps:
[...]
- name: Checkout
uses: actions/checkout@v2
- name: Deploy to Fly
uses: superfly/flyctl-actions@1.1
with:
args: "deploy --app ${{ secrets.APP_NAME }} --build-arg FONT_AWESOME_TOKEN=${{ secrets.FA_TOKEN }} --remote-only"
[...]
…leads to…
==> Validating app configuration
--> Validating app configuration done
Services
TCP 80/443 ⇢ 4000
Waiting for remote builder fly-builder-REDACTED...
WARN Remote builder did not start on time. Check remote builder logs with `flyctl logs -a fly-builder-REDACTED`
Error error connecting to docker: remote builder app unavailable