Connect Application to DB from another ServiceStack

[m-stokowski]

Hi,
I'm trying to connect an App to DB from another service stack on the same server without making DB accessible over the internet.

My config looks like this:

• service stack "A" based on docker-composefile with 2 containers: "app1" and "mysql" in it. DB container exposes port 3306.
• network "netA" that was created automatically by Coolify with service stack "A" - I've added "netA" to Coolify server destinations.
• "app2" built with Nixpack that is set-up to connect to network/destination "netA" created by previous stack.

I would like to connect "app2" to DB from service stack "A" ("mysql" container) but every time i try to deploy "app2" build process fails when it tries to pull data from DB.

In environment variables of "app2" i tried setting DB_HOST to:

• mysql
• mysql-netA (container name with uuid set by default by coolify. Uuid is the same as network name)
• host.docker.internal

DB_PORT is set to 3306.

What am I doing wrong and what is the proper way to connect both containers?

[softwaretirol]

Same question here...

[andrasbacsai]

If you are using Nixpacks build pack, the db needs to be publicly available unfortunately. There is an open issue at Nixpacks, that will probably solve the issue.

Another workaround is to use Dockerfile based deployment.

[apolostudio]

so this means i cant use postgres internal url with uptime kuma? im having problems

[mutonby]

and with a docker compose? what internal dns can I use? localhost not working mapping the ports

[mk3-14159]

Any news on this?