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!
1 Like
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.
1 Like
Also confirming that this worked for me!
2 Likes
The fix also worked for me. Should this be added to the Remix Stacks now to prevent others from running into the same issue @michael @kentcdodds ?
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.
1 Like
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 provenance: false
- 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.
2 Likes
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.
1 Like
I just experienced this now and was able to resolve the issue using the previous fix:
with:
version: v0.9.1
1 Like
Hey folks. This is fixed: Images built with the latest docker buildx and or github actions work again
2 Likes
Just wanted to say that the fix is not working for me.
Here is my action definition:
build-base-image:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- uses: superfly/flyctl-actions/setup-flyctl@master
- name: Log in to the Container registry
run: flyctl auth docker
- name: Extract metadata (tags, labels) for Docker
id: meta
uses: docker/metadata-action@v5.0.0
with:
images: ${{ env.REGISTRY }}/${{ env.BASE_IMAGE_NAME }}
- name: Set up Docker Buildx
uses: docker/setup-buildx-action@v2
with:
version: v0.9.1
- name: Build and push Docker image
uses: docker/build-push-action@v5
with:
context: .
push: true
tags: ${{ steps.meta.outputs.tags }}
labels: ${{ steps.meta.outputs.labels }}
and the error:
buildx failed with: ERROR: failed to solve: failed to push registry.fly.io/mi-gestor-app/base-image:main: unexpected status from POST request to https://registry.fly.io/v2/mi-gestor-app/base-image/blobs/uploads/: 404 Not Found