Skip to content
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

🤔 [ISSUE] - <container mongo is unhealthy error> #310

Open
moaadzraig opened this issue Nov 2, 2024 · 11 comments
Open

🤔 [ISSUE] - <container mongo is unhealthy error> #310

moaadzraig opened this issue Nov 2, 2024 · 11 comments

Comments

@moaadzraig
Copy link

Description

i've installed ubunu 20.04, nodejs and docker and cloned the hexabox from github and followed the instructions mentioned in the installation guide of hexabox. everything worked. when i try to start hexabox using hexabot dev or start command, it starts pulling the container images and at the end it says "dependency failer to start: container mongo is unhealthy".

Error image:

Reproduction steps

1. sudo npm install -g hexabot-cli
2. hexabot create my-chatbot
3. cd my-chatbot/
4. npm i
5. hexabot init
6. sudo hexabot dev --services nlu,ollama

Logs

No response

Browsers

No response

OS

Linux

@moaadzraig
Copy link
Author

err

@yassinedorbozgithub
Copy link
Collaborator

yassinedorbozgithub commented Nov 2, 2024

Hi @moaadzraig, thank you for reporting the issue.
It will be helpful if you can provide the Hexabot Team with more details about the issue.
For example, if you can share the container logs, OS version, node version ...

@moaadzraig
Copy link
Author

moaadzraig commented Nov 2, 2024 via email

@marrouchi
Copy link
Contributor

Hello @moaadzraig Can you do docker logs -f mongo ? Do you have another mongo database installed on your machine or any other service that is using the port "27017" ?

@moaadzraig
Copy link
Author

moaadzraig commented Nov 2, 2024 via email

@marrouchi
Copy link
Contributor

As it shows in the logs :
WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that!

Can I ask what CPU are you using ?

@moaadzraig
Copy link
Author

moaadzraig commented Nov 2, 2024 via email

@marrouchi
Copy link
Contributor

I cannot see the image you attachment, I guess you replied by email. Can you rather reply in github to upload the image?

Otherwise, if you are on Windows, I would advise to install Docker + WSL rather than using VirtualBox.

@moaadzraig
Copy link
Author

img1
img2

@marrouchi
Copy link
Contributor

marrouchi commented Nov 30, 2024

Hello @moaadzraig Any update on this issue? Were you able to resolve it?

@deepakitkar
Copy link

I am also getting same network error. is there a fix?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants