Run `docker compose up -d` and confirm with `docker compose exec <service> sysctl net.core.somaxconn`.
Official docs: https://docs.docker.com/reference/compose-file/services/#sysctls and https://docs.docker.com/engine/reference/commandline/run/ (namespaced-kernel-parameters)
Known gotchas
Only kernel parameters that are NAMESPACED in the kernel can be set inside a container; sysctls that would modify the host system are rejected.
Map and array forms are equivalent - pick one; do not mix both for the same key.
A sysctl that the host kernel or the container runtime does not permit produces a runtime error when the container starts.
sysctls is a mapping-type key for merge purposes (extends merges rather than replaces).
Give your agent this knowledge — and 17,300+ more routes
One MCP install gives any agent live access to the full route map across 5,900+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?