qus

I just used https://github.com/dbhi/qus to enable it for all docker containers on the system (alternatively you can do the binfmt config manually, eg https://wiki.debian.org/QemuUserEmulation) However to have it more tightly integrated, you'd want an arm image at /, mount the original warrior image at /warrior, then you could do something like `qemu-user-amd64 /warrior/bin/chroot /warrior/entrypoint` - Updating all paths as relevant

You can do that without the GUI: https://github.com/dbhi/qus

qemu-user-static (qus) is a compilation of utilities, examples and references to build and execute OCI images (aka Docker images) for foreign architectures, using QEMU’s user-mode emulation. Ready-to-use docker images are provided for each of seven host architectures officially supported by Docker, Inc. or built by official images: amd64, i386, arm64v8, arm32v7, arm32v6, s390x and ppc64le. Multiple minimal working setups to build and execute arm64v8 containers on amd64 are configured and tested on Continuous Integration (CI) services (GitHub Actions and Travis CI). The full flow is public, for other users to learn and adapt these resources to their needs. See github.com/dbhi/qus/actions and/or travis-ci.com/dbhi/qus/builds. For instance, qus has been reported to work for running x86 applications on Raspberry Pi. Now, the docs (which were