Closed soulzzz closed 2 months ago
sudo docker-compose ps
NAME IMAGE COMMAND SERVICE CREATED STATUS PORTS
docker-db-1 postgres:15-alpine "docker-entrypoint.s…" db 48 minutes ago Up 48 minutes 0.0.0.0:5432->5432/tcp, :::5432->5432/tcp
docker-redis-1 redis:6-alpine "docker-entrypoint.s…" redis 48 minutes ago Up 48 minutes 0.0.0.0:6379->6379/tcp, :::6379->6379/tcp
docker-sandbox-1 langgenius/dify-sandbox:0.2.1 "/main" sandbox 48 minutes ago Up 48 minutes
docker-ssrf_proxy-1 ubuntu/squid:latest "sh -c 'cp /docker-e…" ssrf_proxy 48 minutes ago Up 48 minutes 0.0.0.0:3128->3128/tcp, :::3128->3128/tcp, 0.0.0.0:8194->8194/tcp, :::8194->8194/tcp
Hey there, @soulzzz! I'm Dosu, a bot here to help you with bugs, questions, and contributions while you wait for a human maintainer. Let's tackle this together! 🤖
To resolve the issue where the Weaviate container does not start and is not listed after running docker compose up
, ensure that the Weaviate service is correctly defined in your docker-compose.middleware.yaml
file. It appears that the Weaviate service definition is incomplete. Here is the corrected section for the Weaviate service:
services:
# The Weaviate vector store.
weaviate:
image: semitechnologies/weaviate:1.19.0
restart: always
volumes:
- ./volumes/weaviate:/var/lib/weaviate
environment:
PERSISTENCE_DATA_PATH: ${WEAVIATE_PERSISTENCE_DATA_PATH:-/var/lib/weaviate}
QUERY_DEFAULTS_LIMIT: ${WEAVIATE_QUERY_DEFAULTS_LIMIT:-25}
AUTHENTICATION_ANONYMOUS_ACCESS_ENABLED: ${WEAVIATE_AUTHENTICATION_ANONYMOUS_ACCESS_ENABLED:-false}
DEFAULT_VECTORIZER_MODULE: ${WEAVIATE_DEFAULT_VECTORIZER_MODULE:-none}
CLUSTER_HOSTNAME: ${WEAVIATE_CLUSTER_HOSTNAME:-node1}
AUTHENTICATION_APIKEY_ENABLED: ${WEAVIATE_AUTHENTICATION_APIKEY_ENABLED:-true}
AUTHENTICATION_APIKEY_ALLOWED_KEYS: ${WEAVIATE_AUTHENTICATION_APIKEY_ALLOWED_KEYS:-WVF5YThaHlkYwhGUSmCRgsX3tD5ngdN8pkih}
AUTHENTICATION_APIKEY_USERS: ${WEAVIATE_AUTHENTICATION_APIKEY_USERS:-hello@dify.ai}
AUTHORIZATION_ADMINLIST_ENABLED: ${WEAVIATE_AUTHORIZATION_ADMINLIST_ENABLED:-true}
AUTHORIZATION_ADMINLIST_USERS: ${WEAVIATE_AUTHORIZATION_ADMINLIST_USERS:-hello@dify.ai}
ports:
- "${EXPOSE_WEAVIATE_PORT:-8080}:8080"
Ensure the following:
weaviate
service is correctly defined in your docker-compose.middleware.yaml
.middleware.env
file or directly in the docker-compose.middleware.yaml
.volumes
directory exists and has the correct permissions.Additionally, ensure that your Docker environment is properly set up. If the container still does not start, you can check the logs for more information by running:
docker compose logs weaviate
This command will provide detailed logs that can help identify the issue [1][2][3].
To continue talking to Dosu, mention @dosu.
works and thanks!
I found that when I forgot to add --profile weaviate
, the Weaviate container was not launched but everything seemed like still going well, even the features related to RAG / knowledge base. As far as I know, when we create a knowledge base, embeddings will be stored to the vector database. I want to know what happens when no vector database is specified in this case? Thx!
I found that when I forgot to add
--profile weaviate
, the Weaviate container was not launched but everything seemed like still going well, even the features related to RAG / knowledge base. As far as I know, when we create a knowledge base, embeddings will be stored to the vector database. I want to know what happens when no vector database is specified in this case? Thx!
Reply to myself: I have figured out the reason, embeddings are stored to vector database only if "high quality" index method is chosen when creating a knowledge base. So if we only use the "economic" index method, the system works well even if there is not any vector database running.
Self Checks
Dify version
0.6.16
Cloud or Self Hosted
Self Hosted (Source)
Steps to reproduce
when i run the steps below
the weaviate container is not showing up instead of showing below
My docker-compose.middleware.yaml is blow
docker-compose.yaml is
and middleware.env is
✔️ Expected Behavior
weaviate container shows up after docker compose up
❌ Actual Behavior
weaviate container not shows up after docker compose up