Since quite a while qemu-user-static uses the "fix binary" flag (see https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1815100 and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868030). This means that the qemu-user-static executable will get used that got registered during the binfmt registration process even if QEMU is being used within the container. Therefore there is no need anymore to copy qemu-user-static into the container. Like this it is possible to simplify the whole cross architecture setup quite a bit. On the other hand side it is no longer possible to inject a newer variant of qemu-user-static using edi. As an alternative a Docker/Podman container could be used to overrule the qemu-user-static binary: https://github.com/multiarch/qemu-user-static
Since quite a while qemu-user-static uses the "fix binary" flag (see https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1815100 and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868030). This means that the qemu-user-static executable will get used that got registered during the binfmt registration process even if QEMU is being used within the container. Therefore there is no need anymore to copy qemu-user-static into the container. Like this it is possible to simplify the whole cross architecture setup quite a bit. On the other hand side it is no longer possible to inject a newer variant of qemu-user-static using edi. As an alternative a Docker/Podman container could be used to overrule the qemu-user-static binary: https://github.com/multiarch/qemu-user-static