# Failed to install

**URL:** https://meta.discourse.org/t/failed-to-install/273479
**Category:** Self-hosting
**Created:** [August 1, 2023, 12:32pm UTC](https://meta.discourse.org/t/failed-to-install/273479 "2023-08-01T12:32:18Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![Ed\_S](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ed_s/32/134015_2.png) [@Ed\_S](https://meta.discourse.org/u/Ed_S)
#### Post date: [August 3, 2023, 12:37pm UTC](https://meta.discourse.org/t/failed-to-install/273479/6 "2023-08-03T12:37:22Z")

</div>

The `git clone` action is taken in the host, so that shows the host is OK, but the subsequent actions take place in the container. If they fail, it indicates trouble within the container (docker) and in this case, DNS (name resolution) trouble.

There have been situations before where people report this kind of connectivity problem inside docker. Perhaps [see](https://meta.discourse.org/t/issue-when-installing-new-discourse-instance/259617/7)

> [@Issue when installing new Discourse instance](https://meta.discourse.org/t/issue-when-installing-new-discourse-instance/259617/7):
>
> try lowering the MTU of the Docker interface

It might be useful to have details of your provider and the location. It might be useful to test inside the container using commands something like this:

```plaintext
./launcher enter app 
ping -c2 github.com
exit

```

---

_[View the full topic](https://meta.discourse.org/t/failed-to-install/273479)._