search

FusionAuth / fusionauth-containers

Container definitions for docker, kubernetes, helm, and whatever containers come next!
https://fusionauth.io/
219 stars 68 forks source link

No need for the search container name #88

Closed mooreds closed 1 year ago

mooreds commented 1 year ago

We don't need to hardcode the search container name.

If you want to run more than one fusionauth instance at a time, it collides, I think.

I've removed it in my docker compose examples and FusionAuth starts up fine.

ColinFrick commented 1 year ago

Just stumbled upon this. When trying to create a separate FusionAuth instance I received the following error message: Error response from daemon: Conflict. The container name "/search" is already in use by container "85493e96395a85e4a36ec3d60da01456c3e9e153f44c5b855a2f3a2769390041". You have to remove (or rename) that container to be able to reuse that name.

robotdan commented 1 year ago

LGTM