-
Notifications
You must be signed in to change notification settings - Fork 33
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
Server returning error when running docker-compose up #14
Comments
Hi! Thanks for posting the issue. Can you also post the output of |
I see. The mongo container is up and running but there is no collection. This is weird. Maybe the set up process for mongo is somehow bugged. For now, can you manually import all the collections from https://github.com/YuqiHuai/SORA-SVL/tree/master/mongo/setup? |
Yes, the mongodb is also empty for my instance.
The import method:
Done. |
Thanks for the response @umdreamer. I am not sure why the Mongo container setup may not work sometimes. I'll try to figure it out. |
I suggest using mongo compass to check whether the database is empty first. |
My bad, I somehow didn't get notified when you replied. The screenshot shows the database is up and running. |
Hi, this problem is caused by MongoDB not correctly starting up. |
@zhang291 @s0966066980 How are things going for you guys? Did you manage to resolve the issue? |
sorry,I forget to modify the |
Hi @zhang291, sorry I do not understand what you mean by
As far as I am aware the |
I've followed all the steps in the documentation, but after running docker-compose up --build -d, each of the tabs in http://localhost is empty (see image below for example) despite all the assets being appropriately located in the server/assets directory. The server is also returning an error when I run docker-compose up that can be seen in the second image below. I believe I have setup everything correctly in accordance with the documentation, so I would appreciate any insight as to what could be causing the issue. Thanks!
The text was updated successfully, but these errors were encountered: