Bug#964289: systemd-container: armhf countainer cannot be started on amd64 host

[Michael Biebl]

Am 05.07.20 um 07:48 schrieb Ryutaroh Matsumoto:
> Package: systemd-container
> Version: 245.6-1
> Severity: normal
> 
> Dear Maintainer,
> 
> I installed
> # dpkg-query -W | grep qemu-user-static
> qemu-user-static	1:5.0-5
> 
> Then I built a root directory as
> 
> # mmdebstrap --components="main contrib non-free" --architectures=armhf --variant=important bullseye /var/lib/machines/armhf-bullseye
> 
> Then 
> # systemd-nspawn -D /var/lib/machines/armhf-bullseye -a
> works fine.
> 
> But I got the following error and could not start the container...
> # systemd-nspawn -D /var/lib/machines/armhf-bullseye   -b
> Spawning container armhf-bullseye on /var/lib/machines/armhf-bullseye.
> Press ^] three times within 1s to kill container.
> systemd 245.6-1 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid)
> Detected virtualization systemd-nspawn.
> Detected architecture arm.
> 
> Welcome to Debian GNU/Linux bullseye/sid!
> 
> Set hostname to <armhf-bullseye>.
> Failed to enqueue loopback interface start request: Operation not supported
> Caught <SEGV>, core dump failed (child 3, code=killed, status=11/SEGV).
> Exiting PID 1...
> Container armhf-bullseye failed with error code 255.
> 
> Best regards, Ryutaroh Matsumoto
> 

Hm, I'm not sure if this is supported and supposed to work.
But you can ask upstream.

Regards,
Michael


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20200705/f44fe3f3/attachment.sig>