fix: FalkorDB data not persisting across restarts

[jescalan]

Problem

FalkorDB's entrypoint script (run.sh) always appends --dir $FALKORDB_DATA_PATH after $REDIS_ARGS, so the --dir /data in REDIS_ARGS is silently overridden by the default FALKORDB_DATA_PATH=/var/lib/falkordb/data.

This means Redis writes its RDB dumps and AOF files to /var/lib/falkordb/data (ephemeral container filesystem) instead of /data (the Docker volume). On any container restart or recreate, all FalkorDB graph data is lost.

The failure is silent — FalkorDB comes back healthy with memory_count=0 while Qdrant still has all vectors, making it look like a FalkorDB bug rather than a persistence misconfiguration.

Fix

• Remove --dir /data from REDIS_ARGS (it was being ignored anyway)
• Set FALKORDB_DATA_PATH=/data so the entrypoint's own --dir flag points to the volume mount

Verification

After this change:

• redis-cli CONFIG GET dir returns /data (the volume) instead of /var/lib/falkordb/data
• BGSAVE writes to the volume-mounted path
• Data survives container restarts

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 958da72 and 3bbc834.

📒 Files selected for processing (1)

• docker-compose.yml

---

📝 Walkthrough

Summary by CodeRabbit

Release Notes

• Chores
  • Updated data persistence configuration to improve flexibility in how database paths are handled during startup.

Walkthrough

A configuration change to docker-compose.yml that separates Redis persistence path configuration by removing --dir /data from REDIS_ARGS and introducing a distinct FALKORDB_DATA_PATH=/data variable, with explanatory comments about FalkorDB's run script behavior.

Changes

Cohort / File(s)	Summary
Docker Configuration docker-compose.yml	Removed --dir /data from REDIS_ARGS environment variable and added separate FALKORDB_DATA_PATH=/data variable. Added explanatory comments noting that FalkorDB's run.sh script appends the directory path independently.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main fix: resolving FalkorDB data persistence across container restarts by correcting Redis configuration.
Description check	✅ Passed	The description clearly explains the problem, the root cause, the implemented fix, and verification steps—all directly related to the changeset in docker-compose.yml.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}