Patricol

+1 to this. I have the same use case of wanting to expose many different containers to nginx but not to each other or the rest of the network. Note that the docker developers have voiced intentions not to add the ability to specify multiple networks on the run command. A quick solution to this would be a field in the template for commands to run after the container is (re)started. e.g.: docker network connect bridge2 container && docker network connect bridge3 container Prioritizing creating a good UI for this function might be harder than the size of its audience justifies; but adding that run-after field is much simpler and likely covers other use cases.