From 6a8d5ba86e0572df87abc5a1dc503e5e00911ce6 Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 5 Nov 2026 22:41:30 +0000 Subject: [PATCH] ci(scaffold-e2e): give the image run an explicit database (Refs #30120) The "Docker build and run (scaffolded Dockerfile)" step starts the scaffolded image with only OS_SECRET_KEY and OS_AUTH_SECRET. Once the official image refuses to start without an explicit OS_DATABASE_URL, this health-only probe would go red. Pass an explicit SQLite file URL; until then the variable is simply unused. Co-authored-by: Claude Claude-Session: https://claude.ai/code/session_016WV4cytQjG9X1CrCgytUM5 --- .github/workflows/scaffold-e2e.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/workflows/scaffold-e2e.yml b/.github/workflows/scaffold-e2e.yml index 8e0444ca7c2..367aeb76280 100644 --- a/.github/workflows/scaffold-e2e.yml +++ b/.github/workflows/scaffold-e2e.yml @@ -511,6 +511,7 @@ jobs: # and then died at second 3 cost the full 60s and reported "never # became healthy" instead of "it is not running, here is why". docker run -d --name e2e -p 18080:8080 \ + -e OS_DATABASE_URL="file:/tmp/e2e.db" \ -e OS_SECRET_KEY="$(openssl rand -hex 32)" \ -e OS_AUTH_SECRET="$(openssl rand -hex 32)" \ e2e-app