# Discourse\_docker: discourse-setup 错误地依赖于 ipconfig 输出中的“addr:”。

**URL:** <https://meta.discourse.org/t/discourse-docker-discourse-setup-incorrectly-relies-on-addr-in-ipconfig-output/73389>\
**Category:** Product Support\
**Created:** [2017 年11 月 3 日 21:02 UTC](https://meta.discourse.org/t/discourse-docker-discourse-setup-incorrectly-relies-on-addr-in-ipconfig-output/73389 "2017-11-03T21:02:27Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

作者： ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
发布日期： [2017 年11 月 3 日 21:55 UTC](https://meta.discourse.org/t/discourse-docker-discourse-setup-incorrectly-relies-on-addr-in-ipconfig-output/73389/4 "2017-11-03T21:55:11Z")

</div>

> [@tomreyn](#):
>
> It would not realiably work in a load balancing scenario where HTTP(S) requests to a single IP address may end up on different servers to the backend (LB pool).

I don’t think that acme would work in that scenario, but in any case, if you’re capable of doing that kind of work, you can probably crank up `vim` and edit the file by hand.

It also won’t work if you use a domain name that resolves only from inside the container.

---

_[View the full topic](https://meta.discourse.org/t/discourse-docker-discourse-setup-incorrectly-relies-on-addr-in-ipconfig-output/73389)._