25.03.2021 16:33, Silvano Cirujano Cuesta wrote:
Package: qemu-user-static
Version: 1:5.2+dfsg-9
Severity: wishlist
X-Debbugs-Cc: [email protected]
Current packaging of qemu-user-static is providing two different things
at once and without any declared configuration possibility (no .conffiles):
* QEMU-User statically linked binaries.
* binfmt_misc configuration
Yes, it's been this way since forever.
From release "buster" upwards the binfmt_misc configuration being
provided by this package is registering the qemu-user-static binaries
with the flag "fix_binary". This configuration might be convenient in
most cases (suppose that's was it's so now), but is a problem in some
others.
Not being able to configure binfmt_misc is a blocker for this package in
the scenarios where that default configuration doesn't fit. The
So far I don't see where it doesn't fit.
configuration can be changed providing different update-binfmts
templates than those provided by this package and running
update-binfmts. But qemu-user-static upgrades overwrite the changes.
I don't know which is the best solution, but one possible is putting
the update-binfmts templates now available in /usr/share/binfmts under
/etc and making them configuration files (adding a .conffiles).
It seems like way too much trouble for both the maintainer and the user.
Just for those curious when this might be an issue. Containers trying to
use new syscalls not provided by the QEMU-User binaries provided by the host
require newer QEMU-User binaries.
How about installing latest qemu-user-static on host instead? It is a
self-contained package (as all binaries are statically linked). This way
all your containers will benefit immediately, too.
Thanks,
/mjt
