# Discourse\_docker: discourse-setup depende incorrectamente de "addr:" en la salida de ipconfig

**URL:** <https://meta.discourse.org/t/discourse-docker-discourse-setup-incorrectly-relies-on-addr-in-ipconfig-output/73389>\
**Category:** Product Support\
**Created:** [3 Noviembre, 2017 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:** 1

<div class="post-metadata">

**Author:** ![tomreyn](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tomreyn/32/120428_2.png) [@tomreyn](https://meta.discourse.org/u/tomreyn)\
**Post date:** [3 Noviembre, 2017 21:02 UTC](https://meta.discourse.org/t/discourse-docker-discourse-setup-incorrectly-relies-on-addr-in-ipconfig-output/73389/1 "2017-11-03T21:02:27Z")

</div>

I previously posted this on the GitHub issue tracker which has now been removed (including my post), so I’m posting it here again.

On a Debian GNU/Linux 9.0 “stretch” VM runing in a KVM environment, the output of the ipconfig command does not return a string containing a pattern such as

` inet addr:123.123.123.123`

but just

` inet 123.123.123.123`

As a result, discourse-setup sets the IP variable to an empty string and the installation fails with

` mydomain.net does not appear to resolve to .`

A better approach would be to use something similar to

`ip -f inet addr show $IFACE | grep -Po 'inet \K[\d.]+' | head -n1`

---

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