Bug Description

The Dockerfile creates a volume mount at /app/data but the Basic Memory config.json is configured to look for data in /root/basic-memory, causing a path mismatch that prevents the application from finding its data directory.

Steps To Reproduce

1. Build the Docker image from the current Dockerfile
2. Run the container with a volume mount: docker run -v mydata:/app/data basic-memory
3. Basic Memory will look for data in /root/basic-memory instead of /app/data
4. Application fails to access persisted data

Expected Behavior

Basic Memory should use the /app/data directory that is defined as a VOLUME in the Dockerfile.

Actual Behavior

Basic Memory looks for data in /root/basic-memory, ignoring the Docker volume mount at /app/data.

Environment

• Docker version: Various
• Basic Memory version: Latest
• Installation method: Docker

Additional Context

The Dockerfile contains:

VOLUME ["/app/data"]

But the config.json uses:

{
  "default_project_path": "/root/basic-memory"
}

Possible Solution

Either:

1. Update the Dockerfile to set VOLUME to /root/basic-memory
2. Update the config.json to use /app/data as the default_project_path
3. Add an environment variable override for the data path in Docker contexts

🤖 Generated with Claude Code

Co-Authored-By: Claude noreply@anthropic.com