The dmraid package executes udevadm in its postinst script: | jenkins@jenkins-slave11:/tmp/grml-live/deployment-iso$ docker run --rm -it -v "$(pwd)":/deployment-iso/ -v "$(pwd)/grml_build/":/grml/ docker.mgm.sipwise.com:5000/grml-build-bullseye:latest /bin/bash | root@fa6b983da364:/code/grml-live# apt install dmraid | [...] | Setting up dmraid (1.0.0.rc16-8+b1) ... | Failed to write 'change' to '/sys/devices/pci0000:00/0000:00:17.0/ata1/host0/target0:0:0/0:0:0:0/block/sda/uevent': Read-only file system | dpkg: error processing package dmraid (--configure): | installed dmraid package post-installation script subprocess returned error exit status 1 | Processing triggers for libc-bin (2.31-4) ... | Errors were encountered while processing: | dmraid | E: Sub-process /usr/bin/dpkg returned an error code (1) Also see https://bugs.debian.org/962300. Installing the dmraid package on bullseye requires execution of docker containers with privileged mode, which is something we would like to avoid. dmraid also had its latest Debian upload in 2017, the last upstream release dates back to 2010 (see http://people.redhat.com/~heinzm/sw/dmraid/src/) and it has plenty of bugs. It's furthermore relevant for so called fake RAIDs only, something we don't support and therefore shouldn't matter for us. Change-Id: I7ed50d8d732f75c56e94b8bfd97a71613577f3bdmr9.5.1
parent
0a827525c6
commit
b368d86558
Loading…
Reference in new issue