fix: resolve connect-sqlite3 v0.9.17 breaking change causing Docker startup crash (#6688) - #6706
Conversation
….17 compatibility (FlowiseAI#6688)
Upstream issue FlowiseAI#6688 reports that flowiseai/flowise:3.1.4 fails to start. The real cause is not 3.1.4 code. It is an unpinned transitive dependency. connect-sqlite3@0.9.17 changed its constructor so `this.db.exec` is no longer a function, so session-store setup throws during boot: TypeError: this.db.exec is not a function at new SQLiteStore (connect-sqlite3/lib/connect-sqlite3.js:56:17) at initializeDBClientAndStore (dist/enterprise/middleware/passport/SessionPersistance.js:96) Because the dependency is unpinned, this affects ANY Flowise container built after 0.9.17 was published -- not just 3.1.4. Reproduced 2026-08-05: official flowiseai/flowise:3.1.3, built earlier -> connect-sqlite3 0.9.16 -> boots fresh build of that same flowise@3.1.3, today -> connect-sqlite3 0.9.17 -> crashes So the "3.1.3 works, 3.1.4 is broken" split people observed is an artifact of WHEN each image was built, not of what changed between the two releases. Pinning to 0.9.16 -- the last working constructor, and what every functioning official image actually shipped -- makes container builds reproducible again. Verified: a fresh flowise@3.1.3 image with this pin reaches "Flowise Server is listening at :3000". Upstream PR FlowiseAI#6706 (PiedPiper911) fixes the same defect in the TypeScript source for source builds. This pin covers npm-installed container builds. Both should land; they address different install paths.
|
Confirming this diagnosis independently — Reproduced 2026-08-05:
Because the dependency is unpinned, every Flowise container built after Your fix is the correct one for source builds. For npm-installed container builds the equivalent is pinning at install time: RUN npm --prefix "$(npm root -g)/flowise" install --no-save connect-sqlite3@0.9.16Both are needed — they cover different install paths. Given upstream froze on 2026-07-29 and this repository is archived on 2026-08-10, this PR is unlikely to be merged here. I've carried the fix into a community continuation fork at https://github.com/dblagbro/flow-wiser, with attribution to this PR and to you in the changelog and release notes. If you'd like it applied as your commit rather than referenced, open a PR there and it will land with you as author — that's how the two adopted CVE fixes from @anupamme (#6682, #6683) were handled. Unofficial fork, not affiliated with FlowiseAI or Workday. Thanks for tracking this down. |
2 participants
Problem
v0.9.17 changed its API: must now be an already-opened instance instead of a string filename. This causes the Docker image to crash on startup with a fatal error (#6688).
Solution
Updated to create an opened instance before passing it to .
Changes
Fixes #6688