-
-
Notifications
You must be signed in to change notification settings - Fork 255
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: Support for binfmt-misc F flag #1361
Comments
I've tried inserting the F flag in the
After restart systemd-binfmt, box64 works, but in a limited way:
Can't really get what file is it talking about. Ubuntu crashes because of #1531 , while alpine just crashes:
So if we understand how to fix the "things not found" problem then box64 would be able to work (normal incompatibilities apart) as a drop-in for qus and that means fast amd64 containers on aarch64 :) |
We now have instructions for building a "highly experimental" static binary for use in a chroot, similar to what qemu can provide.
In the case of deploying chroots using debootstrap, Debian provides a tool called qemu-debootstrap to automatically perform the multi-step process of building these for foreign architectures. I believe this would previously embed the static qemu binary into the chroot half way through the build process. The tool is currently deprecated because qemu now supports the binfmt F flag and deploys the binfmt config using this by default, so a qemu binary in the chroot is no longer required.
It would be nice if box64 could also work this way, so it could function like a drop-in replacement, and require fewer steps for these kinds of tasks.
The text was updated successfully, but these errors were encountered: