well, my chroot is run inside qemu userspace emulation and it tries to execute a mono binary, i wonder if either influences this.
could you try with qemu-arm-static and using the build-arm-chroot to create your chroot env ? it might not be binfmt itself being at fault but the mono interpreter or the detector ... o...@osiris:~$ cat /usr/share/binfmts/cli package mono-common detector /usr/lib/cli/binfmt-detector-cli interpreter /usr/bin/cli magic MZ -- binfmt allows breaking out of chroots due to not respecting namespaces https://bugs.launchpad.net/bugs/427863 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
