# צירוף קונטיינר למספר רשתות Docker

**URL:** <https://meta.discourse.org/t/joining-container-to-multiple-docker-networks/256260>\
**Category:** Self-hosting\
**Tags:** unsupported-install\
**Created:** [25 בפברואר,‏ 2023,‏ 8:46pm UTC](https://meta.discourse.org/t/joining-container-to-multiple-docker-networks/256260 "2023-02-25T20:46:17Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![shyguy](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/shyguy/32/295079_2.png) [@shyguy](https://meta.discourse.org/u/shyguy)\
**Post date:** [25 בפברואר,‏ 2023,‏ 8:46pm UTC](https://meta.discourse.org/t/joining-container-to-multiple-docker-networks/256260/1 "2023-02-25T20:46:17Z")

</div>

what is the ‘blessed by discourse’ method to use **multiple** docker networks? multiple `--network` invocations aren’t supported in `docker run`, so i don’t think i can specify multiple networks using `docker_args`.

i tunnel user requests to the edge via an `--internal` docker network, but having that as the only network causes `launcher rebuild` to fail since it needs internet. so i would want to have a `wan` network (i guess just for building?) and an internal `tunnel` network (real traffic).

do i really have to come up with something to `docker network connect tunnel app` after every build/start? can i have the discourse `launcher` do it?

thanks

---

_[View the full topic](https://meta.discourse.org/t/joining-container-to-multiple-docker-networks/256260)._