Bug#989078: several SIGABRT in containers

[Simon Richter]

Hi Michael,

On Tue, May 25, 2021 at 11:39:35PM +0200, Michael Biebl wrote:

> Am 25.05.21 um 15:29 schrieb Simon Richter:

> >To reproduce, build the Debian systemd package inside a docker container,
> >e.g. using

> >     FROM debian:buster
> >     RUN echo "deb-srchttp://deb.debian.org/debian/  buster main" >>/etc/apt/sources.list
> >     RUN apt-get update
> >     RUN apt-get -y install build-essential
> >     RUN apt-get -y build-dep systemd
> >     RUN apt-get -y source systemd
> >     RUN apt-get -y -b source systemd

> Running this on a Debian sid system, the build completes
> successfully (log attached).

Interesting, for me the build stopped during dh_auto_test -- but your log
contains several test failures where programs stopped with SIGABRT, just
apparently not enough to fail the build.

To run systemd-detect-virt, I have to install the systemd package inside
the container (the "debian" image does not contain an init system at all).

systemd-detect-virt reports "microsoft", even inside the container.
Explicitly asking for the container gives "none". Should that make a
difference for libudev?

   Simon