Files
Chronos/deploy/docker/entrypoint.sh
T
Alby96 20d64af4a4
CI / Build and test (push) Successful in 11m36s
CI / Windows tests and installer (push) Skipped
CI / YAML check (push) Successful in 12s
Release / Build, test and publish (push) Successful in 14m56s
CI / PostgreSQL 16 integration (push) Successful in 10m11s
CI / PostgreSQL 17 integration (push) Successful in 10m15s
CI / Docker image (push) Successful in 45s
Release / Server image (push) Successful in 4m55s
feat: single setup, mass-pass progress, per-server homes, Desktop shares its library (owner review 5, v1.1.0) (#68)
Co-authored-by: Alberto Balbo <alberto.balbo.96@gmail.com>
2026-11-15 18:11:43 +01:00

69 lines
3.2 KiB
Bash
Executable File

#!/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}"
VIDEOS="${CHRONOS_VIDEOS_PATH:-}"
umask 002
# Help and the health probe touch neither folder.
case "${1:-}" in
--help | -h | -\? | /\? | --healthcheck) exec dotnet /app/Chronos.Server.Host.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 <archive>/.chronos)" >&2
exit 1
fi
done
# The videos folder (optional) is treated as the archive is, except that a problem only warns: copying fails with its
# reason in the admin panel until it is fixed, and everything else runs.
if [ -n "$VIDEOS" ] && [ -d "$VIDEOS" ]; then
if command -v mountpoint >/dev/null 2>&1 && ! mountpoint -q "$VIDEOS"; then
echo "warning: $VIDEOS is not a mounted volume: copies to the videos folder stay inside the container and are lost when it is replaced; map a host folder to $VIDEOS" >&2
fi
if ! as_user test -w "$VIDEOS"; then
if [ -z "$(ls -A "$VIDEOS")" ] || [ "$(stat -c %u "$VIDEOS")" = "0" ]; then
owner="$(stat -c %u:%g "$VIDEOS")"
if chown "$PUID:$PGID" "$VIDEOS" 2>/dev/null; then
echo "chronos: $VIDEOS belonged to $owner; it now belongs to $PUID:$PGID (the folder only, not its contents)"
fi
fi
if ! as_user test -w "$VIDEOS"; then
echo "warning: $VIDEOS is not writable by $PUID:$PGID; copies to the videos folder fail until that user can write it" >&2
fi
fi
fi
exec setpriv --reuid="$PUID" --regid="$PGID" --clear-groups -- dotnet /app/Chronos.Server.Host.dll "$@"
fi
exec dotnet /app/Chronos.Server.Host.dll "$@"