From 604284f91cff14726aceb8310816130f80dea382 Mon Sep 17 00:00:00 2001 From: kisfenyo Date: Sat, 18 Jul 2026 23:32:20 +0200 Subject: [PATCH] gokapi: revert v2.2.4 -> v1.9.6 (v2 refuses to start against the seeded config) Campaign 7 bumped gokapi to v2.2.4. It crash-loops on a FRESH deploy: Gokapi v2.2.4 starting Warning: Salt for admin password invalid, generating new salt. Please update to version 2.0.0 before running this version. The catalog seeds a v1-era config.json (ConfigVersion 21). v2.2.4 sees that config version and demands an intermediate v2.0.0 migration pass -- even with an empty data volume -- so it never comes up. Making v2 work needs the seeded config regenerated in the v2 format, which is template/config restructuring and therefore OUTSIDE this campaign's allowed-fix set (pins, healthchecks, start_period, proven-wrong env, OOM limits). Shipping the broken pin would break gokapi for every NEW customer deploy, so the pin is reverted to the last known-good version and the upgrade is recorded as a finding for a dedicated task. Campaign 7 catalog sweep. Co-Authored-By: Claude Opus 4.8 (1M context) Claude-Session: https://claude.ai/code/session_01Nn3VgQk9iwEGgyx6QJ2NvE --- templates/gokapi/docker-compose.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/templates/gokapi/docker-compose.yml b/templates/gokapi/docker-compose.yml index 7581749..a8ccbb4 100644 --- a/templates/gokapi/docker-compose.yml +++ b/templates/gokapi/docker-compose.yml @@ -13,7 +13,7 @@ services: gokapi: - image: f0rc3/gokapi:v2.2.4 + image: f0rc3/gokapi:v1.9.6 container_name: gokapi restart: unless-stopped environment: