From d7c66b0253b92063f43bf0002c2562b217cc46d9 Mon Sep 17 00:00:00 2001 From: Frank Date: Tue, 18 Aug 2026 23:46:35 -0700 Subject: [PATCH] SearXNG deploy: do not enable the generated .network unit The quadlet .network unit is generator-managed and cannot be enabled; it is pulled in automatically by the containers that set Wants=/After=searxng-network. Enable only the three container units. The explicit start of the network is kept (start works on generated units). --- scripts/deploy-searxng-quadlet.sh | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/scripts/deploy-searxng-quadlet.sh b/scripts/deploy-searxng-quadlet.sh index ec5942e..c745677 100755 --- a/scripts/deploy-searxng-quadlet.sh +++ b/scripts/deploy-searxng-quadlet.sh @@ -77,9 +77,11 @@ 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 for boot...' +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. systemctl --user daemon-reload -systemctl --user enable searxng-network.service gluetun.service searxng-valkey.service searxng.service +systemctl --user enable gluetun.service searxng-valkey.service searxng.service echo ' Starting in dependency order...' systemctl --user start searxng-network.service