Feature Request: Allow Host IP Binding Control for Port Exposure (Especially for Databases)

[ellnamin]

Hi Dokploy team,

I'd like to request a feature that allows us to specify which host IP/interface a container’s port should bind to.

This could be beneficial in general, but is especially important for databases. A common use case is when the database server runs on a separate host and the app server communicates with it over a private network. In that case, we want to bind the container's port to the host’s private IP (e.g., 10.10.0.1) — not to 0.0.0.0 or 127.0.0.1.

[Siumauricio]

I have a similar case, what I did was I have a server that has a database and is on a private network then I expose the database with some port like 5432, and then block the firewall so that no traffic comes out, and with my other applications as they are connected to a shared private network, I simply connect through the private network of the database server plus the port that I exposed.

Although if you don't want to do that, you can use docker compose and have a database there, since we now support backups and restore you could use it!

[ellnamin]

Thank you for your answer. I didn't know you had added backups to composes! Which version did you add this feature to?

[dmatora]

I'm shocked both coolify and dokploy don't support port mapping to 127.0.0.1, making databases unusable, unless you want to mess with firewall

[djsisson]

they both do, you add a compose with your db and set port bindings in there to host loopback or private network ip etc

[dmatora]

@djsisson that's what I currently do, but it's not the same
Compose app doesn't have all the features database app does.
On the bright side, at least Dokploy allows backups on these