# \[Решено\] Недавнее изменение нарушает подключение в Docker (+ вне Docker)

**URL:** <https://meta.discourse.org/t/resolved-recent-change-breaks-connectivity-in-docker-non-docker/132498>\
**Category:** Development\
**Created:** [03.Ноябрь.2019 21:33:24 UTC](https://meta.discourse.org/t/resolved-recent-change-breaks-connectivity-in-docker-non-docker/132498 "2019-11-03T21:33:24Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [04.Ноябрь.2019 01:53:31 UTC](https://meta.discourse.org/t/resolved-recent-change-breaks-connectivity-in-docker-non-docker/132498/2 "2019-11-04T01:53:31Z")

</div>

Конечно, это отличное замечание, которое уже исправлено здесь:

> <https://github.com/discourse/discourse/commit/ff33899323f71ca750c0e555ce8f71d8896a3b3a>
>
> Previously we had no control over how internal ports in the containter got
> publi…shed.
> 
> Following UNICORN\_BIND\_ALL=true setting this broke docker dev env and exposed
> this weakness.
> 
> The new \`d/boot\_dev\` will only export on localhost, if you wish to export
> network with use \`d/boot\_dev -p\`

Если вы хотите глобально открыть порты контейнера для сети (по умолчанию отключено), используйте:

```plaintext
d/boot_dev -p

```

---

_[View the full topic](https://meta.discourse.org/t/resolved-recent-change-breaks-connectivity-in-docker-non-docker/132498)._
