level=fatal msg="store.type must be set"
Describe the bug I'm trying to add Zep to my service from inside docker-compose but always get this error: level=fatal msg="store.type must be set"
To Reproduce my docker-compose.yml:
version: '3.8'
services:
zep_memory:
image: ghcr.io/getzep/zep:latest
container_name: zep-memory
environment:
- ZEP_MEMORY_STORE=postgres
- ZEP_POSTGRES_DSN=postgres://${POSTGRES_USER}:${POSTGRES_PASSWORD}@db:5432/${POSTGRES_DB}
- ZEP_OPENAI_API_KEY=${OPENAI_API_KEY}
- ZEP_STORE_TYPE=postgres
ports:
- "${ZEP_MEMORY_PORT}:8000"
healthcheck:
test: ["CMD", "curl", "-f", "http://localhost:8000/healthz"]
interval: 30s
timeout: 10s
retries: 3
volumes:
postgres_data:
networks:
default:
name: aipa_network
(I removed all of my services from it for the sake of clean experiment, but I get the same error whether I have my services in the file or not)
Logs
2024-07-09 12:38:09 time="2024-07-09T04:38:09Z" level=warning msg=".env file not found or unable to load. This warning can be ignored if Zep is run using docker compose with env_file defined or you are passing ENV variables."
2024-07-09 12:38:09 time="2024-07-09T04:38:09Z" level=info msg="Log level set to: info"
2024-07-09 12:38:09 time="2024-07-09T04:38:09Z" level=info msg="Starting Zep server version 0.26.0-415979b (2024-07-09T04:19:41+0000)"
2024-07-09 12:38:12 time="2024-07-09T04:38:12Z" level=fatal msg="store.type must be set"
This https://github.com/getzep/zep/issues/253 didn't help btw.
I have the same error!
Please ensure you're using the zep-cloud container and not the zep container. The latter expects a config file loaded from the directory from which the container is run.
I just tried running the docker compose up in this tutorial and it still didn't work, do I need to change something?
https://github.com/getzep/zep
Do you have the config.yaml file from the repo present in the directory from which you ran docker compose? Do the logs mention the file is missing?
Yes, I just downloaded the repository, added a .env with the open AI key and ran docker compose.
Can you share your logs?
On Thu, Jul 18 2024 at 9:51 AM, franklin390 < @.*** > wrote:
Yes, I just downloaded the repository, added a .env with the open AI key and ran docker compose.
— Reply to this email directly, view it on GitHub ( https://github.com/getzep/zep/issues/350#issuecomment-2237072063 ) , or unsubscribe ( https://github.com/notifications/unsubscribe-auth/AABAAZ4LZTFE2VHQWFV2ED3ZM7XBLAVCNFSM6AAAAABKSBVJFGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZXGA3TEMBWGM ). You are receiving this because you commented. Message ID: <getzep/zep/issues/350/2237072063 @ github. com>
docker compose should use Dockerfile.cloud, not Dockerfile when deploying with Dockerfile.cloud it works for me
Closing as a new Server and set of SDKs is now available.