Closed NilsXitaso closed 1 week ago
Hello everyone,
after we updated our docker image (discovery service) from 4 weeks ago to the new one. The discovery service has following startup error.
Here is our docker compose configuration for the discovery service which was working just fine before we updated:
Unfortunately right now it is just possible to run it InMemory instead of in MongoDB.
Configure newest discovery service docker image to use MongoDB instead of InMemory (look at our configuration)
Thank you for raising this issue. We are aware of it and will update all BaSyx images again today.
New Images are online. Please check if this is resolved now.
Hello everyone,
after we updated our docker image (discovery service) from 4 weeks ago to the new one. The discovery service has following startup error.
Here is our docker compose configuration for the discovery service which was working just fine before we updated:
Unfortunately right now it is just possible to run it InMemory instead of in MongoDB.
To reproduce:
Configure newest discovery service docker image to use MongoDB instead of InMemory (look at our configuration)
Version we are talking about