Skip to content

fix: container crash when started with --user flag (Unraid) #49

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
GeiserX merged 1 commit into from
May 13, 2026
Merged

fix: container crash when started with --user flag (Unraid) #49

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 11 additions & 5 deletions entrypoint.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,15 @@
#!/bin/sh
# Already running as non-root (e.g. Unraid --user flag) — skip privilege setup
if [ "$(id -u)" != "0" ]; then
exec "$@"
fi

# Ensure data and fleet directories are writable by cashpilot
chown cashpilot:root /data 2>/dev/null || true
if [ -d "/fleet" ]; then
chown cashpilot:root /fleet 2>/dev/null || true
fi

# If Docker socket exists, ensure the cashpilot user can access it
SOCK=/var/run/docker.sock
if [ -S "$SOCK" ]; then
Expand All @@ -12,9 +23,4 @@ if [ -S "$SOCK" ]; then
fi
fi

# Ensure fleet key directory is writable by cashpilot
if [ -d "/fleet" ]; then
chown cashpilot:root /fleet 2>/dev/null || true
fi

exec su-exec cashpilot "$@"
Loading