You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the repository's docker-compose.yml file an aliasing trick is used so that the default rita.yaml config works out-of-the-box. This linking seems to generally work as intended with other aliases, except for the use of localhost and therefore the backend connection still breaks with an Failed to connect to database: no reachable servers-error. Not sure how to properly fix it, or what the underlying root cause exactly is though.
I tested this with Docker Compose version v2.17.3, docker version 24.0.2. Rita version v4.8.0.
# docker-compose.yamllinks:
# give db an alias of "localhost" so that RITA's default config works unchanged
- db:localhost
# rita.yamlMongoDB:
# See https://docs.mongodb.com/manual/reference/connection-string/ConnectionString: mongodb://localhost:27017
The text was updated successfully, but these errors were encountered:
I came across the same issue as you and it seems like the best practice would be to have rita reference the db container directly by its name "db," leaving the docker-compose.yaml the same but changing the ConnectionString to mongodb://db:27017. This is reflected in a separate config specifically for docker compose use that was created it seems after your issue. I created a pull request to specify this explicitly in the documentation.
In the repository's docker-compose.yml file an aliasing trick is used so that the default rita.yaml config works out-of-the-box. This linking seems to generally work as intended with other aliases, except for the use of
localhost
and therefore the backend connection still breaks with anFailed to connect to database: no reachable servers
-error. Not sure how to properly fix it, or what the underlying root cause exactly is though.I tested this with Docker Compose version v2.17.3, docker version 24.0.2. Rita version v4.8.0.
The text was updated successfully, but these errors were encountered: