do i put docker ip or system ip in caddy

If I start the second application now, it starts a second network app2_network 172.19.0.0/16, but still tries to bind every exposed port on all interfaces. Every exposed port is exposed on 0.0.0.0, i.e. Running the first one with docker-compose creates a network called something like app1_network with an IP range of 172.18.0.0/16. Is there a way or is this something yet to be implemented?ĮDIT: An example of a port conflict: imagine two projects, each with an application server running on port 8080 and a MySQL database running on port 3306, both respectively exposed as '8080:8080' and '3306:3306'. docker-compose should both know which network it created as well as its IP, so this shouldn't be a problem, however I couldn't find an easy way to do it. It's be great to define the IP to bind the containers to in terms of the network created for this particular project. It is possible to put the bind IP into docker-compose.yml, however this is a killer for portability - not every developer on the team uses the same OS or works on the same projects, therefore it's not clear which IP to configure.

However, this does not work as intended: every exposed port is still exposed on 0.0.0.0 and thus there are port conflicts with multiple projects. I can run multiple nginx projects at the same time on port 8080 on different interfaces) This is great when developing multiple projects at the same time, since there is then no need to change the ports in docker-compose.yml (i.e. Basically, every docker-compose setup is getting its own IP range, so that in theory I could call my services on the network's IP address with the predefined ports. In recent versions docker-compose automatically creates a new network for the services it creates.

Do i put docker ip or system ip in caddy