From 9f4c0d4175bc8dec9ac600acf4d24bb4eed18750 Mon Sep 17 00:00:00 2001 From: Frank Date: Wed, 19 Aug 2026 00:05:25 -0700 Subject: [PATCH] SearXNG deploy: do not systemctl enable the generated units Quadlet units are generator-managed; systemctl enable fails on them ('transient or generated'). The [Install] WantedBy=default.target in each .container file is itself the enablement (is-enabled reports 'generated'), and with user linger on they start at boot. Drop the enable step; daemon-reload and start are enough. --- scripts/deploy-searxng-quadlet.sh | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/scripts/deploy-searxng-quadlet.sh b/scripts/deploy-searxng-quadlet.sh index c745677..d63a906 100755 --- a/scripts/deploy-searxng-quadlet.sh +++ b/scripts/deploy-searxng-quadlet.sh @@ -77,11 +77,13 @@ echo ' Copying quadlet units into ~/.config/containers/systemd/ ...' mkdir -p ~/.config/containers/systemd cp ${QDIR}/*.container ${QDIR}/*.network ~/.config/containers/systemd/ -echo ' daemon-reload + enable the container units for boot...' -# The .network unit is generator-managed: it cannot be enabled, and it is pulled -# in automatically by the containers that set Wants=/After=searxng-network.service. +echo ' daemon-reload (generates the units)...' +# Quadlet units are generator-managed: systemctl enable fails on them ("transient +# or generated"). The [Install] WantedBy=default.target in each .container file is +# itself the enablement (is-enabled reports "generated"), and with user linger on +# they start at boot. The .network unit is pulled in by the containers that set +# Wants=/After=searxng-network.service. So: daemon-reload, then start. systemctl --user daemon-reload -systemctl --user enable gluetun.service searxng-valkey.service searxng.service echo ' Starting in dependency order...' systemctl --user start searxng-network.service