# How do you set net.core.somaxconn in the docker container?

**URL:** <https://meta.discourse.org/t/how-do-you-set-net-core-somaxconn-in-the-docker-container/64577>\
**Category:** Self-hosting\
**Created:** [15 Junio, 2017 21:29 UTC](https://meta.discourse.org/t/how-do-you-set-net-core-somaxconn-in-the-docker-container/64577 "2017-06-15T21:29:34Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![squidboylan](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/squidboylan/32/120930_2.png) [@squidboylan](https://meta.discourse.org/u/squidboylan)\
**Post date:** [15 Junio, 2017 21:29 UTC](https://meta.discourse.org/t/how-do-you-set-net-core-somaxconn-in-the-docker-container/64577/1 "2017-06-15T21:29:34Z")

</div>

How do you set net.core.somaxconn in the docker container so that Redis doesn’t complain that somaxconn is less than 511? Using sysctl doesnt work inside of the container and setting it on the host doesn’t affect the container. Perhaps the launcher script should know to run docker with the `--sysctl net.core.somaxconn=512` option?

---

_[View the full topic](https://meta.discourse.org/t/how-do-you-set-net-core-somaxconn-in-the-docker-container/64577)._