lscr.io/linuxserver/scrutiny:latest
should retrieve the correct image for your arch, but you can also pull specific arch images via tags.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
).scrutiny-collector-metrics run
for your first job or wait until around midnight for it to kick off./config
.--cap-add
for this container:SYS_RAWIO
is necessary to allow smartctl permission to query your device SMART data.<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.-p
)8080
-e
)PUID=1000
PGID=1000
TZ=Europe/London
SCRUTINY_API_ENDPOINT=http://localhost:8080
SCRUTINY_WEB=true
SCRUTINY_COLLECTOR=true
-v
)/config
/run/udev:ro
--device
)/dev/sda
/dev:/dev
instead for all devices./dev/sdb
/dev/nvme1n1
--cap-add=SYS_ADMIN
.cap_add
or sysctl
to work properly. This is not implemented properly in some versions of Portainer, thus this image may not work if deployed through Portainer.FILE__
.PASSWORD
based on the contents of the /run/secrets/mysecretpassword
file.-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.-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
.PUID=1000
and PGID=1000
, to find yours use id user
as below:docker exec -it scrutiny /bin/bash
docker logs -f scrutiny
docker inspect -f '{{ index .Config.Labels "build_version" }}' scrutiny
docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/scrutiny:latest
nsswitch.conf
to resolve local hosts