Comment # 6 on bug 1143725 from Arnav Singh

(qemu-linux-user 7.0.0-55.1)

I had the same issue with binaries exiting with code 255. I found that
using qemu-aarch64 instead works perfectly:

    $ echo
':qemu-aarch64:M::\x7fELF\x02\x01\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x00\xb7\x00:\xff\xff\xff\xff\xff\xff\xff\x00\xff\xff\xff\xff\xff\xff\xff\xff\xfe\xff\xff\xff:/usr/bin/qemu-aarch64:POCF'
> /proc/sys/fs/binfmt_misc/register

    $ cat /proc/sys/fs/binfmt_misc/qemu-aarch64 

    enabled
    interpreter /usr/bin/qemu-aarch64
    flags: POCF
    offset 0
    magic 7f454c460201010000000000000000000200b700
    mask ffffffffffffff00fffffffffffffffffeffffff

Now Docker containers are able to run aarch64 binaries just fine.

I did not test with a chroot to see if it behaves differently.