Package: src:runit Followup-For: Bug #950851 Control: severity -1 normal Hi,
I'm downgrading the severity of this because there is consensus on Debian-devel that the policy-rc.d mechanism is not the right tool to achieve what you're asking for. See [1] for details About your request, with the next runit Debian release (2.1.2-37), you will be able to skip all sysvinit scripts in /etc/rc2.d/ and have runit manage only selected services by setting the 'runitdir' environment variable to 'isolation'. This will be documented in the runit(8) manpage. I've tested in docker and using the 'env runitdir=isolation' option works as expected. Of course, in your Dockerfile, you need to symlink your runit service into /etc/runit/runsvdir/isolation/ otherwise runsvdir will have nothing to supervise. Hope this will solve your problem, feedback is welcome. Regards, Lorenzo [1] https://lists.debian.org/debian-devel/2020/04/msg00231.html -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.5.9-van (SMP w/4 CPU cores; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit)
