On running multiple instances, name conflict for elasticsearch

[kkdg]

When running multiple VS API, there is no problem except elasticsearch, CLI complaints there is naming conflict with elasticsearch because it's explicitly defined inside docker-compose.yml, they can't arbitrarily add new name for new instance.

Solution would be removing container_name node from docker-compose.yml

Is there any reason for elasticsearch explicitly named so?

If this is OK, I will make a PR of this. Thanks!

[lukeromanowicz]

I don't see any reason for that. While doing that PR please carefully test if ES is still reachable from nodejs container after implementing your changes.

[kkdg]

On hearing from Sander that it'd cause more harm than good, I am on a research which way is better or find a 3rd way. I will be back with other solutions, Thanks @lukeromanowicz