-
Notifications
You must be signed in to change notification settings - Fork 875
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dependency failed to start: container genai-stack-api-1 is unhealthy #142
Comments
Tried again and again. Finally the installation seemed to be OK even with the INFO messages which would stop after perhaps 30+. |
I have installed genai stack many times but it has failed. The error situation is as follows:
How should we solve it? |
I am using a personal desktop computer and Clash, 127.0.0.1:7890 |
This is opening http://localhost:8501/ The display shows that Python 3.11 was not found locally (only Python 3.10 was found locally), I don't know where all the Python packages installed in the requirements. |
I'm also getting an "dependency failed to start: container genai-stack-api-1 is unhealthy" error on Mac M1 Max:
|
I encounter same problem !
|
I was experiencing the same issue :(
I managed to resolve this issue by using the Neo4j Sandbox.(https://sandbox.neo4j.com/) The same error persisted locally, but upon checking the detailed logs, it seemed that the problem was related to the NEO4J_URI. I created a Neo4j Sandbox, then updated the .env file with the generated URL, username, and password, which fixed the issue. |
I just solved this issue!
and then it works!
then you can check your database :) |
I get the same issue. Setting those .env variables does not fix the issue. Those are the defaults. Your successful build was incidental. |
have some one solve it? I encountered similar problems |
First ran into /data problem. Followed the thread #134 and implemented three changes: (a) chown /home/casev/../genai-stack/data directory to casev for userID and groupID. (2) added to /home/casev/.profile two statements: export USER_ID=$(id -u) and export GROUP_ID=$(id -g). (3) modified docker-compose.yml to set database: user: ${USER_ID}:${GROUP_ID}.
Next, run docker compose --profile linux up again. This time, the /data file error did not appear, and installation went further.
However, it still stopped with an error message: dependency failed to start: container genai-stack-api-1 is unhealthy.
Even after shutdown and restart, docker compose seemed to be stuck for hours displaying with different port numbers:
INFO: 127.0.0.1:xxxxxx - "GET / HTTP/1.1" 200 OK with different port numbers.
The text was updated successfully, but these errors were encountered: