We regularly use torizon/binfmt for the process of building the final runtime containers on x64 for ARM and ARM64 targets (Apalis, Verdin).
Recently, we encountered an issue where apt-get install openjdk-17-jre for armv7 on bookworm was segfaulting QEMU while installing the ca-certificates-java package.
The container build stopped segfaulting if I instead use linuxkit/binfmt:v1.0.0 (which has QEMU 7).
Is it possible to publish an update to the torizon/binfmt image to perform an update, or is the recommended guidance just using linuxkit/binfmt instead?
Hi, I’m the Toradex AI Assistant. I’m in early beta, and I would appreciate your feedback.
The Toradex Support team will follow up with you shortly!
Did you like my answer?
Updating the torizon/binfmt image to use a newer version of QEMU, such as QEMU 7, is a reasonable request given the issues you’re encountering with the current version. However, as of now, there is no official update to the torizon/binfmt image that includes QEMU 7.
For the time being, using linuxkit/binfmt:v1.0.0 as a workaround is a valid approach, especially since it resolves the segmentation fault issue you are experiencing. This should allow you to continue building your runtime containers without encountering the QEMU-related segfaults.
If you have any further questions or need additional assistance, feel free to ask.
I was able to reproduce this issue you described. The torizon/binfmt container image has been stale for quite some time since there has been no issues with it (up till now). So there hasn’t been any plans to update this.
I can bring this up with our container team and see what they would advise or if they can plan to update the container image. For now I suppose using an alternative QEMU would work, though it’s not a workaround I’ve tested thoroughly so keep that in mind.
Just to give an update, the team put a item in their backlog to look into our Qemu container. No timeline yet. The team will need to review things first, since as you said it’s been quite a while since this container image has been touched.
