#!/bin/sh # Runs Chronos Server as PUID:PGID (Unraid/NAS convention). The data folder is owned by that user. The archive is left # as mounted (it may hold terabytes) and only checked for write access; only when that user cannot write it and the # folder is empty or owned by root (Docker creates a missing bind source or a fresh volume that way) is the folder # itself, never its contents, given to PUID:PGID. set -eu PUID="${PUID:-1000}" PGID="${PGID:-1000}" DATA="${CHRONOS_DATA_PATH:-/data}" ARCHIVE="${CHRONOS_ARCHIVE_PATH:-/archive}" umask 002 # Help and the health probe touch neither folder. case "${1:-}" in --help | -h | -\? | /\? | --healthcheck) exec dotnet /app/Chronos.Server.dll "$@" ;; esac as_user() { setpriv --reuid="$PUID" --regid="$PGID" --clear-groups -- "$@" } if [ "$(id -u)" = "0" ]; then mkdir -p "$DATA" "$ARCHIVE" chown -R "$PUID:$PGID" "$DATA" if ! as_user test -w "$ARCHIVE"; then if [ -z "$(ls -A "$ARCHIVE")" ] || [ "$(stat -c %u "$ARCHIVE")" = "0" ]; then owner="$(stat -c %u:%g "$ARCHIVE")" if chown "$PUID:$PGID" "$ARCHIVE" 2>/dev/null; then echo "chronos: $ARCHIVE belonged to $owner; it now belongs to $PUID:$PGID (the folder only, not its contents)" fi fi if ! as_user test -w "$ARCHIVE"; then echo "error: $ARCHIVE is not writable by $PUID:$PGID; give that user write access to the archive folder on the host, or set PUID and PGID to its owner" >&2 exit 1 fi fi # The server writes into the archive's .chronos folders at once (staging, trash, locks); one left to root by an # earlier run as root, or copied in by root, would stop it in a restart loop. Reported, never chowned. for dir in "$ARCHIVE/.chronos" "$ARCHIVE/.chronos"/*/; do if [ -d "$dir" ] && ! as_user test -w "$dir"; then echo "error: ${dir%/} is not writable by $PUID:$PGID; give that user write access to it on the host (for example chown -R $PUID:$PGID /.chronos)" >&2 exit 1 fi done exec setpriv --reuid="$PUID" --regid="$PGID" --clear-groups -- dotnet /app/Chronos.Server.dll "$@" fi exec dotnet /app/Chronos.Server.dll "$@"