Set SEARXNG_SETTINGS_PATH at runtime, not build time

SearXNG's setup.py imports searx during metadata generation, which reads
SEARXNG_SETTINGS_PATH. Pointing it at /etc/searxng/settings.yml via ENV made
the editable install fail (file not present yet at that build step). Set the
var in start.sh instead; during build SearXNG uses its packaged defaults.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Dockerfile

@@ -8,7 +8,6 @@ FROM python:3.11-slim
 ENV PIP_NO_CACHE_DIR=1 \
     PIP_DISABLE_PIP_VERSION_CHECK=1 \
     PYTHONUNBUFFERED=1 \
-    SEARXNG_SETTINGS_PATH=/etc/searxng/settings.yml \
     SEARXNG_URL=http://127.0.0.1:8080 \
     DATA_DIR=/data \
     HOME=/app

start.sh

@@ -9,9 +9,13 @@ APP_PY=/opt/appenv/bin/python
 SEARXNG_HOST="127.0.0.1"
 SEARXNG_PORT="8080"
 
+# Point SearXNG at our settings at runtime only (not during the image build, where
+# the file doesn't exist yet and would break metadata generation).
+export SEARXNG_SETTINGS_PATH="${SEARXNG_SETTINGS_PATH:-/etc/searxng/settings.yml}"
+SETTINGS="$SEARXNG_SETTINGS_PATH"
+
 # A settings.yml secret_key must be set. If the shipped one is still the
 # placeholder, generate one at runtime (settings dir is made writable in the image).
-SETTINGS="${SEARXNG_SETTINGS_PATH:-/etc/searxng/settings.yml}"
 if grep -q 'ultrasecretkey_change_me' "$SETTINGS" 2>/dev/null; then
     KEY="$("$APP_PY" -c 'import secrets; print(secrets.token_hex(32))')"
     sed -i "s/ultrasecretkey_change_me/${KEY}/" "$SETTINGS" || true