setup-buildx-action

Is it this? This is happening in github-actions https://github.com/docker/setup-buildx-action/issues/358

This sounds fine and well, but it's not how Github Actions work (or at least, not the encouraged workflow). Let's have a look at the snippet from one of the projects I work on: - name: Set up Docker Buildx uses: docker/setup-buildx-action@v2 - name: Build and push mwdb-core image uses: docker/build-push-action@v4 with: file: ./deploy/docker/Dockerfile tags: | certpl/mwdb:${{ github.sha }} certpl/mwdb:master cache-from: | type=registry,ref=certpl/mwdb:buildcache outputs: type=docker,dest=./mwdb-image - name: Upload mwdb-core image uses: actions/upload-artifact@v3 with: name: mwdb-image path: mwdb-image Good luck running this locally. There's no script code to speak of, just references to external "actions" and parameters (for example, https://github.com/

> you can build arm Docker images in QEMU super easy on GHA if you need hosted agents Yeah, you nailed it: it's fairly trivial to create cross architecture images -- my preferred tool is Docker's buildx plugin[1]. I have an M1 Mac, Raspberry Pi 4 running 64 bit Ubuntu Server and multiple x86_64 bit machines. I try to exclusively use Docker images that are cross-architecture. When they are not cross-architecture I usually just build the project's Dockerfile using the Docker Buildx Github Action[2]. The majority of the time most projects' stock Dockerfile works on all architectures. The few times they don't work are usually when a Dockerfile grabs an x86_64 binary and downloads it. I feel like that is bad practice so I usually just write my own Dockerfile when I encounter that. A recent image I did this with was Gitleaks[3] (link goes to my