this post was submitted on 02 May 2024
8 points (100.0% liked)

Docker

1104 readers
1 users here now

founded 1 year ago
MODERATORS
 

I have my main compose file which has a bunch of services in and while it makes it easier to manage, it's also limiting when I wanna use postgres:// to access a database rather than exposing a port. I'm wondering if I can remedy this by moving it to a new network and(?) stack?

If so, is it just as simple as adding

networks
  - new network name
stacks
  - new stacks name

I'm still curious as to the answer, but it's not something I need.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 2 points 6 months ago (1 children)

Try using the postgres hostname instead of "ipaddress", it should work. Postgres doesn't have to be exposed on host for this to work, and all compose files will automatically create a bridge network for all services defined in it so you don't technically need to make an explicit network (unless you really need to define IPs or MACs or some other parameters).

[โ€“] [email protected] 1 points 6 months ago

I'll give it a go. Thank you.