From f828e629b5c6ceb1a583ae992d5039740b8da433 Mon Sep 17 00:00:00 2001 From: TowyTowy <85077986+TowyTowy@users.noreply.github.com> Date: Mon, 13 Jul 2026 11:12:10 +0200 Subject: [PATCH] fix(hyperion): keep service running after container reboot (#15653) * fix(hyperion): keep service running after container reboot The packaged hyperion@.service declares "Requisite=network.target" but is not ordered After=network.target. Inside an LXC the unit's start job can be evaluated before network.target is active, and because Requisite= is stricter than Requires= (it does not pull the unit in or wait for it) the job fails with "Dependency failed", so Hyperion does not start after a reboot. Add a systemd drop-in that clears Requisite=; ordering is still provided by the base unit's Wants=/After=network-online.target. Co-Authored-By: Claude Fable 5 * Fix Hyperion service startup issue in LXC Remove Requisite from Hyperion service to ensure it starts correctly in LXC environments. --------- Co-authored-by: Claude Fable 5 Co-authored-by: CanbiZ (MickLesk) <47820557+MickLesk@users.noreply.github.com> --- install/hyperion-install.sh | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/install/hyperion-install.sh b/install/hyperion-install.sh index db5bf301f..b58798f96 100644 --- a/install/hyperion-install.sh +++ b/install/hyperion-install.sh @@ -24,6 +24,12 @@ msg_ok "Set up Hyperion repository" msg_info "Installing Hyperion" $STD apt install -y hyperion +mkdir -p /etc/systemd/system/hyperion@.service.d +cat </etc/systemd/system/hyperion@.service.d/override.conf +[Unit] +Requisite= +EOF +systemctl daemon-reload systemctl enable -q --now hyperion@root msg_ok "Installed Hyperion"