linuxserver/scrutiny

​​
​ ​
​ ​
​ ​
​ ​
​ ​
​ ​
​ ​
​ ​
​​
​Scrutiny WebUI for smartd S.M.A.R.T monitoring. Scrutiny is a Hard Drive Health Dashboard & Monitoring solution, merging manufacturer provided S.M.A.R.T metrics with real-world failure rates from Backblaze.
Supported Architectures
Our images support multiple architectures such as x86-64, arm64 and armhf. We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.
Simply pulling lscr.io/linuxserver/scrutiny should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
Architecture
Tag
x86-64
amd64-latest
arm64
arm64v8-latest
armhf
arm32v7-latest
Application Setup
This container can be run as an 'all-in-one' deployment or as a hub / spoke deployment. Use the environment variables SCRUTINY_WEB and SCRUTINY_COLLECTOR to control the mode of the container. Setting both to true will deploy the container as both a collector and the web UI - this is the simplest and most straightforward deployment approach. To make use of the hub and spoke model, run this container in "collector" mode by specifying SCRUTINY_API_ENDPOINT. Set this to the host that is running the API. For this to work, you will need to expose the API port directly from the container (by default this is 8080).
You may need to manually enter the container to run scrutiny-collector-metrics run for your first job or wait until around midnight for it to kick off.
A fully commented example configuration yaml file can be found in the original project repository here. Place this file in the location mounted to /config.
A note on --cap-add for this container:
SYS_RAWIO is necessary to allow smartctl permission to query your device SMART data.
SYS_ADMIN is required for NVMe drives as per upstream issue #26.
Usage
To help you get started creating a container from this image you can either use docker-compose or the docker cli.
docker-compose (recommended, click here for more info)
1
---
2
version: "2.1"
3
services:
4
  scrutiny:
5
    image: lscr.io/linuxserver/scrutiny
6
    container_name: scrutiny
7
    cap_add:
8
      - SYS_RAWIO
9
      - SYS_ADMIN #optional
10
    environment:
11
      - PUID=1000
12
      - PGID=1000
13
      - TZ=Europe/London
14
      - SCRUTINY_API_ENDPOINT=http://localhost:8080
15
      - SCRUTINY_WEB=true
16
      - SCRUTINY_COLLECTOR=true
17
    volumes:
18
      - /path/to/config:/config
19
      - /run/udev:/run/udev:ro
20
    ports:
21
      - 8080:8080
22
    devices:
23
      - /dev/sda:/dev/sda
24
      - /dev/sdb:/dev/sdb
25
      - /dev/nvme1n1:/dev/nvme1n1
26
    restart: unless-stopped
Copied!
docker cli (click here for more info)
1
docker run -d \
2
  --name=scrutiny \
3
  --cap-add=SYS_RAWIO \
4
  --cap-add=SYS_ADMIN `#optional` \
5
  -e PUID=1000 \
6
  -e PGID=1000 \
7
  -e TZ=Europe/London \
8
  -e SCRUTINY_API_ENDPOINT=http://localhost:8080 \
9
  -e SCRUTINY_WEB=true \
10
  -e SCRUTINY_COLLECTOR=true \
11
  -p 8080:8080 \
12
  -v /path/to/config:/config \
13
  -v /run/udev:/run/udev:ro \
14
  --device /dev/sda:/dev/sda \
15
  --device /dev/sdb:/dev/sdb \
16
  --device /dev/nvme1n1:/dev/nvme1n1 \
17
  --restart unless-stopped \
18
  lscr.io/linuxserver/scrutiny
Copied!
Parameters
Docker images are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate <external>:<internal> respectively. For example, -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 outside the container.
Ports (-p)
Parameter
Function
8080
Port for scrutiny's web interface and API.
Environment Variables (-e)
Env
Function
PUID=1000
for UserID - see below for explanation
PGID=1000
for GroupID - see below for explanation
TZ=Europe/London
Specify a timezone to use EG Europe/London.
SCRUTINY_API_ENDPOINT=http://localhost:8080
# optional - API endpoint of the scrutiny UI. Do not change unless using as a remote collector
SCRUTINY_WEB=true
# optional - Run the web service.
SCRUTINY_COLLECTOR=true
# optional - Run the metrics collector.
Volume Mappings (-v)
Volume
Function
/config
Where config is stored.
/run/udev:ro
Provides necessary metadata to Scrutiny.
Device Mappings (--device)
Parameter
Function
/dev/sda
This is how Scrutiny accesses drives. Optionally supply /dev:/dev instead for all devices.
/dev/sdb
A second drive.
/dev/nvme1n1
An NVMe drive. NVMe requires --cap-add=SYS_ADMIN.
Miscellaneous Options
Parameter
Function
Environment variables from files (Docker secrets)
You can set any environment variable from a file by using a special prepend FILE__.
As an example:
1
-e FILE__PASSWORD=/run/secrets/mysecretpassword
Copied!
Will set the environment variable PASSWORD based on the contents of the /run/secrets/mysecretpassword file.
Umask for running applications
For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional -e UMASK=022 setting. Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up here before asking for support.
User / Group Identifiers
When using volumes (-v flags), permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user PUID and group PGID.
Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.
In this instance PUID=1000 and PGID=1000, to find yours use id user as below:
1
  $ id username
2
    uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)
Copied!
Docker Mods
​​
​ ​
​​
We publish various Docker Mods to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.
Support Info
Shell access whilst the container is running:
docker exec -it scrutiny /bin/bash
To monitor the logs of the container in realtime:
docker logs -f scrutiny
Container version number
docker inspect -f '{{ index .Config.Labels "build_version" }}' scrutiny
Image version number
docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/scrutiny
Versions
17.09.20: - Initial Release.