Open yhyu13 opened 1 year ago
Let me know if your idea. Is it a bug or is it a feature that I did not setup correctly in my workspace?
Hello @yhyu13 could you retry the setup script? we have made some changes that may resolve this issue!
Hello @yhyu13 could you retry the setup script? we have made some changes that may resolve this issue!
@jasangill1 Sure, I will try it with latest AgentGPT version
@yhyu13 whereabouts are you located? and have you had any luck!!
Fixed in my PR https://github.com/reworkd/AgentGPT/pull/1335
@darkanubis0100 While your pr on custom network group reamains open,
here is my solution again for v1.0.0 local deployment. Added local startup scripts and made chage to "agent_db" (how does that even work? I don't believe "agent_db" could translate to 127.0.0.1 or 0.0.0.0 automatically just like localhost)
https://github.com/yhyu13/AgentGPT/commit/09e1e0447b1a5619e3a333668c1bb251d1007db3
PS: Local AgentGPT works best on mozzilla (Edge sometimes rants "Network Error" which equals to not be able to connect to 8000 python backend, hope to save your hours of wasted debugging time)
@darkanubis0100 While your pr on custom network group reamains open,
here is my solution again for v1.0.0 local deployment. Added local startup scripts and made chage to "agent_db" (how does that even work? I don't believe "agent_db" could translate to 127.0.0.1 or 0.0.0.0 automatically just like localhost)
PS: Local AgentGPT works best on mozzilla (Edge sometimes rants "Network Error" which equals to not be able to connect to 8000 python backend, hope to save your hours of wasted debugging time)
Unfortunately that's not functional when you use Windows and Edge, my solution worked on any system and with any browser, which is why I still have the PR
Please check that this issue hasn't been reported before.
Expected Behavior
It may affect other users, in my case I could not start agentgpt at v0.7 beta release due to the database host address issues I found.
Note, I am running with docker in
host network
mode, so every database host points to 127.0.0.1 in my setup. I am not sure if the bug only happen to me because of host network mode setup or not.Current behaviour
In three places I found "db" is misused:
1, docker-compose.yml :
2, .env.example :
3, , use variable db which not defined, and hardcoded database port
next/entrypoint.sh,
platform/entrypoint.sh, OMG the port is not correct, and we should make
platform
waiting for database in principleSteps to reproduce
just run docker compose w/o -d (detachment)
And see the output, it shows
next
andplatform
is stuck waiting for database, because "db" is not defined to a valid URLNot only that, if you skip the waiting for server and enter localhost:3000, you cannot login because the server cannot reach "db" (it is expected to be a URL, not "db")
Possible solution
I've proposed several changes regard to the three places mentioned previously:
https://github.com/yhyu13/AgentGPT/commit/9d2b2bd96bc0ff941f1fb1b289549a91012585ee
env.example
https://github.com/yhyu13/AgentGPT/commit/03be1c3b2f19df83b0bab4ab3920d7be71b618cd
docker-compose.yml
next/entrypoint.sh
platform/entrypoint.sh
Which Operating Systems are you using?
Acknowledgements