scanelf: enabling seccomp failed output when using aarch64 or armv7 chroot on x86_64 (via qemu user)
I build aarch64, armv7, x86, and x86_64 Alpine disk images via chroot and use qemu-user & binfmt to do so for aarch64, armv7, and x86 on a x86_64 host machine.
I am now seeing that on Alpine Edge whenever, inside the chroot, mkinitfs is run to generate/regenerate a initramfs file multiple messages are output of the form:
scanelf: enabling seccomp failed
This is happening for both aarch64 and armv7 chroots, it is not happening for both x86 (which does use qemu-user/binfmt) or x86_64 (which does not use qemu-user/binfmt) chroots.
Looking back through logs of previous runs this change in behaviour started occurring some time between 8th Aug and 28th Aug. This appears to coincide with the Alpine upgrade of pax-utils (including the scanelf sub-package) on 26th August to a new version, 1.3.5, and so I can only assume it is due to a change in scanelf behaviour introduced by the new version or else in the way the new version is built.