Skip to content

After the open-source mem0 was redeployed based on k8s, the memory data was cleared? Why? #3717

Description

@orcharddd2024

Issue with current documentation:

After the open-source mem0 was redeployed based on k8s, the memory data was cleared? Why?

Is it because this “HISTORY_DB_PATH” is not configured correctly?

HISTORY_DB_PATH = os.environ.get("HISTORY_DB_PATH", "/app/data/history.db")

server/Dockerfile ,the content is as follows

FROM python:3.12-slim

WORKDIR /app

RUN mkdir -p /app/data && chmod 755 /app/data

COPY server/requirements.txt .
RUN pip install --no-cache-dir -r requirements.txt

COPY . .

RUN pip install -e .

EXPOSE 8000
ENV PYTHONUNBUFFERED=1

CMD ["uvicorn", "server.main:app", "--host", "0.0.0.0", "--port", "8000"]

After deleting the local image, I rebuilt the image and container, and the memory is still there, except for the historical records that do not exist. This is because HISTORY_DB_PATH is only stored in the container. The container was rebuilt, and of course, there is no data, but why is all the data lost remotely

Metadata

Metadata

Assignees

Labels

documentationImprovements or additions to documentation

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions