How to push to Fly Registry via GitHub Action?

[brody-next-tms]

Hello all,

I’m currently reworking a GitHub Action that deploys an app on Fly.io. I’m now looking to push to the Fly Registry instead, then notifying another app that the image was pushed.

I’m unsure whether the superfly/flyctl-actions/setup-flyctl Action contains the docker command. If not, I imagine that I’d need to pass the Docker configuration from fly auth to the next build step.

Is this currently possible?

Here’s where I’m at so far:

name: Push Image
on:
  push:
    branches:
      - master
env:
  FLY_API_TOKEN: ${{ secrets.FLY_API_TOKEN }}
jobs:
  checks:
    uses: ./.github/workflows/checks.yml
  deploy:
    name: Push
    needs: checks
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - run: export BUILD_NUMBER=$(git rev-list --count HEAD)
      - uses: superfly/flyctl-actions/setup-flyctl@master
      - name: Configure Docker via Fly
        run: flyctl auth docker
      - name: Push
        run: docker push registry.fly.io/<app name>:master-${BUILD_NUMBER}
     # Notify other app of new image here

[jsierles]

docker should be available in Actions. Have you tried this config yet?

[thewilkybarkid]

Not sure if it’s entirely what you mean, @brody-next-tms, but we push an image to the registry and then deploy it as two separate apps:

PREreview/prereview.org/blob/0864a9beb3ee6d2090b1a294dfff5c6c0fa97701/.github/workflows/ci.yml#L285-L350

[ignoramous]

@brody-next-tms

If not, I imagine that I’d need to pass the Docker configuration from fly auth to the next build step.

Yes; see:

Deployment in CI issue

Not familiar with gitlab CI, but you should ref this GitHub Actions usage with flyctl auth docker: kentcdodds.com/deployment.yml at 61923537967f5f488ca2e9af690163194c09fd98 · kentcdodds/kentcdodds.com · GitHub Specifically note, username is set to x, docker image tag set to git tip, and deploys done with -i switch linking to a docker/runc image in registry.fly.io.

and:

No such image error

Will you try building and pushing the image manually to see if you have the same issue? You can do something like this: docker build . -t registry.fly.io/testing-the-hellofly-app:testing flyctl docker auth docker push registry.fly.io/testing-the-hellofly-app:testing flyctl deploy -i registry.fly.io/testing-the-hellofly-app:testing

[brody-next-tms]

My apologies is not accepting a solution and/or responding for some time now; I ran into another roadblock that prevented me from testing this.

Just wanted to let everyone know I haven’t gone away. I really do appreciate the responses! I hope to be able to get this going soon.

[brody-next-tms]

Oh I see, that’s right. And no I hadn’t tried the configuration yet.

[brody-next-tms]

I’ve got this working; thanks!