Hello Michael, For some reason, I did not receive any messages about this bug until the closure. Apologies for the previous lack of follow-up.
I tried running an armhf container on a newer system with QEMU + binfmt-support, *without* copying the QEMU interpreter into the image, and have confirmed that this works correctly. The documentation I had read on this must have been out of date. Thank you for setting me straight! I have removed the QEMU copying step from my container-creation scripts. --Daniel
