From b6bc227d2839c949fa1ef5c21f01f6600f72f55b Mon Sep 17 00:00:00 2001 From: "Simon L." Date: Mon, 3 Aug 2026 15:25:42 +0200 Subject: [PATCH] scrutiny: fix access to nvme drives Signed-off-by: Simon L. --- php/src/Docker/DockerActionManager.php | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/php/src/Docker/DockerActionManager.php b/php/src/Docker/DockerActionManager.php index 539f01db..a7666d34 100644 --- a/php/src/Docker/DockerActionManager.php +++ b/php/src/Docker/DockerActionManager.php @@ -480,8 +480,11 @@ readonly class DockerActionManager { } // Special things for the scrutiny container which should not be exposed in the containers.json } elseif ($container->identifier === 'nextcloud-aio-scrutiny') { - // Allow it to access block devices - $requestBody['HostConfig']['DeviceCgroupRules'] = ["b *:* rmw"]; + // Allow it to access block devices (e.g. /dev/sda for SATA drives) and + // character devices (needed for NVMe drives: smartctl reads their SMART data + // via admin passthrough ioctls on the NVMe controller character device + // /dev/nvme0 and not via the block device /dev/nvme0n1) + $requestBody['HostConfig']['DeviceCgroupRules'] = ["b *:* rmw", "c *:* rmw"]; // Special things for the makemkv container which should not be exposed in the containers.json } elseif ($container->identifier === 'nextcloud-aio-makemkv') { // Allow it to access block devices