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 <noreply@anthropic.com>

* 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 <noreply@anthropic.com>
Co-authored-by: CanbiZ (MickLesk) <47820557+MickLesk@users.noreply.github.com>
This commit is contained in:
TowyTowy
2026-07-13 11:12:10 +02:00
committed by GitHub
parent 4a98e86db1
commit f828e629b5
+6
View File
@@ -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 <<EOF >/etc/systemd/system/hyperion@.service.d/override.conf
[Unit]
Requisite=
EOF
systemctl daemon-reload
systemctl enable -q --now hyperion@root
msg_ok "Installed Hyperion"