From 15bc1635c25690460b1d70ffdacfb15b3b9a1fb9 Mon Sep 17 00:00:00 2001 From: Adam Outler Date: Sun, 26 Oct 2025 12:45:42 -0400 Subject: [PATCH] Update install/production-filesystem/services/scripts/check-root.sh Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> --- .../production-filesystem/services/scripts/check-root.sh | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/install/production-filesystem/services/scripts/check-root.sh b/install/production-filesystem/services/scripts/check-root.sh index 32f04b7f..8c292872 100755 --- a/install/production-filesystem/services/scripts/check-root.sh +++ b/install/production-filesystem/services/scripts/check-root.sh @@ -20,9 +20,9 @@ if [ "${CURRENT_UID}" -eq 0 ]; then * Keep the default USER in the image (20211:20211), or * In docker-compose.yml, remove any 'user:' override that sets UID 0. - Note: As a courtesy, this special mode is only used to set the permissions - of /app/db and /app/config to be owned by the netalertx user so future - runs work correctly. + Note: As a courtesy, this special mode is only used to set the permissions + of /app/db and /app/config to be owned by the netalertx user so future + runs work correctly. Bottom line: never run security tooling as root unless you are actively trying to get pwned.