setup-qemu-action VS docker-dogecoin

To be clear, that article does NOT provide a solution for avoiding QEMU. I suggested it because it describes "the hard way" to get a single image multi-arch image. The github action crazy-max/ghaction-docker-buildx has been archived and replaced by docker/setup-qemu-action and docker/setup-buildx-action, which it seems like you were already using.

Second step is docker/setup-qemu-action which installs QEMU static binaries, which are used to run builders for architectures other than the host.

docker/setup-buildx-action and docker/setup-qemu-action to add support for building multi-architecture images.

# Get the repository's code - name: Checkout uses: actions/checkout@v2 # https://github.com/docker/setup-qemu-action - name: Set up QEMU uses: docker/setup-qemu-action@v1 # https://github.com/docker/setup-buildx-action - name: Set up Docker Buildx id: buildx uses: docker/setup-buildx-action@v1

docker/setup-qemu-action (This is needed for building images for other platforms)

docker/setup-qemu-action Configure QEMU to be able to compile for ARM and install the QEMU static binaries

In Docker-Dogecoin's Dockerfile there's an example of how to write conditional logic as part of the docker build process depending on the target architecture to install different binaries for each.