Fix aarch64 startup loop: /proc/1/fd/1 + notification-fd guard

Two independent failure modes can cause the restart loop on arm64:

1. /dev/stdout may be inaccessible in some ARM container runtimes; replaced
   with /proc/1/fd/1 which LSIO images already use for direct container stdout.

2. s6-notifyoncheck writes to fd 3 on check success, but s6-rc only opens
   that fd when notification-fd exists in the service directory. LSIO arm64
   images ship svc-qbittorrent without it, so s6-notifyoncheck exits with
   EBADF and s6 restarts the service in a loop. Guard with a file check and
   fall back to exec'ing qbittorrent-nox directly when the file is absent.

https://claude.ai/code/session_01F16ThtZyfXj6ZKFPkrSAAq
This commit is contained in:
Claude
2026-05-11 05:19:13 +00:00
parent 862097d6bd
commit f5328b6d66

View File

@@ -44,6 +44,10 @@ fi
bashio::log.info "Starting qBittorrent..."
exec \
s6-notifyoncheck -d -n 300 -w 1000 -c "nc -z localhost ${WEBUI_PORT}" \
s6-setuidgid abc /app/qbittorrent-nox --webui-port="${WEBUI_PORT}" > "${QB_OUTPUT}"
if [ -f /etc/s6-overlay/s6-rc.d/svc-qbittorrent/notification-fd ]; then
exec \
s6-notifyoncheck -d -n 300 -w 1000 -c "nc -z localhost ${WEBUI_PORT}" \
s6-setuidgid abc /app/qbittorrent-nox --webui-port="${WEBUI_PORT}" > "${QB_OUTPUT}"
else
exec s6-setuidgid abc /app/qbittorrent-nox --webui-port="${WEBUI_PORT}" > "${QB_OUTPUT}"
fi