How to change default PostgreSQL container network/port mapping?

[ellnamin]

Hi, I’m using Dokploy with two VPSs on a private network:

VPS A: App server (public)

VPS B: DB server (private, only accessible to VPS A)

I’m using the multiserver feature, and I want my app to connect to the DB via the private IP of VPS B.

By default, Dokploy uses a standard PostgreSQL container, but I need to expose its port only on the private network, not 0.0.0.0 or 127.0.0.1.
To do that, I usually define a custom service in docker-compose.yml like:

ports:
  - "10.0.0.3:5432:5432"

But if I use Dokploy’s built-in PostgreSQL, I can't change its network bindings.

Question:
Can I still use Dokploy’s built-in PostgreSQL, but configure it to bind only to the private IP?
Or must I create a custom container instead?

Thanks!

[Siumauricio]

No, currently you can't change that, however you can create a database in docker-compose and do that and you should have no problem as we now support backups and restore for docker compose.