Microservice port conflict at localhost

Not sure it’s a bug or a ‘feature’ ERROR: for customergateway-postgresql Cannot start service customergateway-postgresql: b'driver failed programming external connectivity on endpoint docker_customergateway-postgresql_1 (7e89d2b724f17888bd1097ac2dd3acda2abcbaee5f0641a8361dca01da1d2495): Bind for 0.0.0.0:5432 failed: port is already allocated' An attempt to create a simple microservice app with the same DB type. It can be easily solved by setup DB ports for each microservice in JDL. Or even better do not use localhost at all! Use just hostnames like customergateway-postgresql:5432 instead of localhost:5432 I this case ports will never collide for services also it’s obvious by name ‘which-is-which’.

[pascalgrimaud]

I had a look at https://hub.docker.com/r/strm/dnsmasq/ and indeed, it could be a solution. But not sure it will work well for users with Windows.

Then, after thinking more about this feature request, I don’t think we will change something in our main generator-jhipster as the change is trivial and can be done in less than 30sec.

Adding a new option would be overkill, and we’ll have to do the same think for all database, all other services, and maintain it.

What can be done are:

• a new module for using strm/dnsmasq -> feel free to code your own module and maintain it. I’ll be happy to test and play with it
• add a new tips at https://www.jhipster.tech/tips/

For now, let’s close this.

[pascalgrimaud]

@mmuruev :

• with dev profile, you shouldn’t have problem as your gateway uses h2disk and your microservice psql
• you can have problem with prod profile as you need to start each psql (1 for gateway, 1 microservice)

To resolve this, IMO, the best would be:

• create a separate project, use jhipster docker-compose, it will generate a big docker-compose file
• clean all app, keep only database and services
• expose port, differently for psql, 5432, then 5433, 5434 etc
• then, change the default port of psql in appropriate microservice

I think it’s the best solution because when I start to dev, I launch this big docker-compose, instead of thinking about which services inside each microservices (consul, keycloak, kafka, psql etc etc)

Then, I don’t think we should include your feature in main generator, as we will need to do the same for all databases, store the config in yo-rc.json, add the option in JDL, maybe change all config in docker-compose, heroku, gcp, openshift, aws etc etc… Too much work for 1 or 2 minutes with sub generator docker-compose

Hope my solution will help you