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 …

What’s that supposed to mean: that ignoring the warning will blow up your site? Or that the warning is a joke? PS Sarcasm doesn’t transfer over TCP/IP :slight_smile:

Can we ever truly know what anything means, really? What I meant was that you can ignore the warning, it’s just Redis being finicky.

I have found the solution: ./launcher rebuild <container> --docker-args "--sysctl net.core.somaxconn=65535" launcher e9505520 echo " --docker-args Extra arguments to pass when running docker" « docker run »…

I noticed the following warning in my rebuild log: # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128. I was doing some reading and found some suggestions to raise this value . Should I? Will this help performance of o…

Thanks for moving my post to the right topic guys, it was kinda hard to find as the keyword appears in many search results :vulcan_salute: So there’s no apparent advantage to tweaking this value? That’s one thing off my todo list then!

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

Product Support Self-hosting

mpalmer (Matt Palmer) 16 Junho , 2017 01:27 2

2 Curtiram

Tópico		Respostas	Vistas
How to resolve the warning message? Self-hosting	1	4104	26 Novembro , 2015
Discourse docker redis warning messages Self-hosting	2	1221	12 Maio , 2021
Discourse_docker redis overcommit_memory Self-hosting docker	6	14959	2 Janeiro , 2018
Redis connection timed out Self-hosting	29	10260	2 Julho , 2018
Getting 502 Bad Gateway after attempting upgrade Self-hosting	2	247	30 Dezembro , 2024

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

Related topics