Would it be possible to allow a container on a non-default bridge network (–net my_bridge) to connect to a TCP port running on a container that shares the same network namespace as the host (–net host)? The service that needs to be accessed by the bridged container is not exposed at the moment as it’s not very well secured, I was thinking maybe I could use socat and shared volumes to proxy the port via the filesystem. Any ideas?