Package: docker.io Version: 20.10.2+dfsg1-2 Severity: minor X-Debbugs-Cc: d...@vollmann.ch
Dear Maintainer, * What led up to the situation? On system startup, dockerd starts a container with a single S/390 binary. Via binfmt this starts qemu-s390x-static with this binary, and that segfaults: kernel: check[2481]: segfault at 2346320 ip 000000000043afa0 sp 00007ffdb3fc62c8 error 4 in qemu-s390x-static[401000+2b0000] I don't know what dockerd does on startup, but I assume that it tries which architectures work. If I run the qemu manually in my normal root fs, it simply returns: /usr/bin/qemu-s390x-static check This is probably the correct behaviour. My suspicion is that this docker container doesn't mount /proc correctly, but I haven't checked this. This started with docker.io 20.10.1+dfsg1-1. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages docker.io depends on: ii adduser 3.118 ii containerd 1.4.3~ds1-1+b1 ii init-system-helpers 1.60 ii iptables 1.8.7-1 ii libc6 2.31-9 ii libdevmapper1.02.1 2:1.02.175-2 ii libsystemd0 247.2-5 ii lsb-base 11.1.0 ii runc 1.0.0~rc92+dfsg1-5+b1 ii tini 0.19.0-1 Versions of packages docker.io recommends: ii apparmor 2.13.6-7 ii ca-certificates 20210119 pn cgroupfs-mount <none> ii git 1:2.30.0-1 pn needrestart <none> ii xz-utils 5.2.5-1.0 Versions of packages docker.io suggests: pn aufs-tools <none> ii btrfs-progs 5.10-1 ii debootstrap 1.0.123 pn docker-doc <none> ii e2fsprogs 1.45.7-1 pn rinse <none> pn rootlesskit <none> ii xfsprogs 5.10.0-2 pn zfs-fuse | zfsutils-linux <none> -- no debconf information
