# Come avviare Discourse all'interno di un contenitore Linux?

**URL:** <https://meta.discourse.org/t/how-to-start-discourse-inside-a-linux-container/79757>\
**Category:** Self-hosting\
**Tags:** unsupported-install\
**Created:** [4 Febbraio 2018, 1:38pm UTC](https://meta.discourse.org/t/how-to-start-discourse-inside-a-linux-container/79757 "2018-02-04T13:38:57Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![Corsterix](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/corsterix/32/135849_2.png) [@Corsterix](https://meta.discourse.org/u/Corsterix)\
**Post date:** [2 Aprile 2019, 1:53am UTC](https://meta.discourse.org/t/how-to-start-discourse-inside-a-linux-container/79757/8 "2019-04-02T01:53:05Z")

</div>

I just installed Discourse in a Docker container inside an LXD container, which may seem weird but it’s something LXD was intentionally designed to support.

[How to Install Discourse in an LXD / Docker Container](https://arador.com/how-to-install-discourse-in-an-lxd-docker-container/)

If you encounter problems with Docker / Discourse failing to run in LXD then you’ll likely need to tweak some settings in your host’s **/etc/sysctl.conf** namely:

```
kernel.keys.maxkeys=2000
kernel.keys.maxbytes=200000
net.ipv4.tcp_mem=182757 243679 365514
net.core.netdev_max_backlog=182757

```

These are production values for LXD and for me they were neccessary to get Discourse running.

---

_[View the full topic](https://meta.discourse.org/t/how-to-start-discourse-inside-a-linux-container/79757)._