# Starting Discourse on a Specific Docker Network

**URL:** <https://meta.discourse.org/t/starting-discourse-on-a-specific-docker-network/49401>\
**Category:** Support\
**Created:** [August 29, 2016, 6:32pm UTC](https://meta.discourse.org/t/starting-discourse-on-a-specific-docker-network/49401 "2016-08-29T18:32:21Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![deargle](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/deargle/32/120295_2.png) [@deargle](https://meta.discourse.org/u/deargle)\
**Post date:** [January 31, 2019, 6:53am UTC](https://meta.discourse.org/t/starting-discourse-on-a-specific-docker-network/49401/5 "2019-01-31T06:53:00Z")

</div>

I just got this working with a web\_only container, a data container, and nginx-proxy in front, all on the same user-defined network.

With the web\_only template, the network needs to be specified in the user args on the command line because at least [one of the lines](https://github.com/discourse/discourse_docker/blob/737e65344795e592ca053908269819b93804720d/launcher#L640) that runs the base docker image does not include $docker\_args, while that line does include $user\_args.

Like: `./launcher rebuild web_only --docker-args '--network nginx-proxy'`

I also had that set in `docker_args:` in web\_only.yml:

```plaintext
docker_args:
  - '--network nginx-proxy'

```

I know this is an old topic, but google brought me here, and google knows all.

@mpalmer would it be not good to include $docker\_args on L640?

---

_[View the full topic](https://meta.discourse.org/t/starting-discourse-on-a-specific-docker-network/49401)._