Could you give it another go? We aren’t 100% sure that error isn’t a one-off.
I re-ran the last workflow and wasn’t watching the logs so I’m not sure exactly what happened, but it got a rollback: use workaround for github actions on fly · kentcdodds/kentcdodds.com@90b9d4c · GitHub
That change to specifying the buildkit version worked great for me. Thanks @michael
The only change that might look suspicious in the buildkit changes was this one:
Which adds labels to the published docker image, would that affect Fly in any way?
The deploy eventually went through, but it looks like it took longer than expected in one region (maa) which is why the deploy was marked as failed. The maa VM did start eventually though. That’s a separate issue, but at least the image pull worked. Thanks for checking for us!
Great to hear. And thanks for the pointer, we’re looking into it.
Hi I can confirm it worked for me by specifying the version! Thanks a lot for your investigation.
Also confirming that this worked for me!
Also works for me - just deployed 5 minutes ago
My own investigation led me to the same change that @mikeglazer identified. For me, adding
provenance: false under
with: did the trick and allowed me to continue using the newest version of the action.
This fix stopped working for us (it worked before) today with:
Download and install buildx Error: Cannot find buildx v0.9.1 release
Which is weird because it definitely wasn’t unpublished.
Had the same problem today, I was following @jeyj0’s hint and stumbled on this thread
What I changed is
build-push-action’s config by adding
- name: 🐳 Docker build uses: docker/build-push-action@v3 with: ... provenance: false
I don’t really understand the details, but at least I’m unblocked now.
Did you keep the version property?
I did not and the deploy worked for me just now:
--- a/.github/workflows/_build.yaml +++ b/.github/workflows/_build.yaml @@ -41,8 +41,6 @@ jobs: - uses: superfly/flyctl-actions/setup-flyctl@master - uses: docker/setup-qemu-action@v2 - uses: docker/setup-buildx-action@v2 - with: - version: v0.9.1 - run: pnpm i -w --frozen-lockfile - run: flyctl auth docker - uses: docker/build-push-action@v3 @@ -53,3 +51,4 @@ jobs: platforms: linux/amd64 push: true cache-from: type=gha + provenance: false
I feel that I should point out that you might not need
docker/setup-buildx-action at all: Why bother with Docker buildx?
So if this is giving you grief, give that a look.