Add 'sysctl' option support

[jtakkala]

PR moby/moby#19265 merged 'sysctl' support into docker, but there seems to be no way to use this feature with docker-compose. Has anyone started work on such a feature? If not, I will attempt to patch docker-compose and create a PR. Are there any suggestions on how to implement it? I was thinking of starting with something similar to how the environment or cap_add options work.

[NoamB]

+1

[jtakkala]

I've submitted a PR for this to docker-py in docker/docker-py#1145. I have a patch for docker-compose in my tree at 87ea3c4. Will submit my patch here once docker-py support is accepted.

[ebr]

+1

[alexandrebini]

+1

[timgriffiths]

+1

[vingrad]

+1

[bmicha4]

+1

[codepunkt]

Anything happening here?

[jtakkala]

#3798 closes this. docker-py version 1.10.0 added support for sysctls, so I hope we can get this merged soon.

[yingdi11]

I followed instruction https://docs.docker.com/compose/gettingstarted/ . but it does not work ......

Has anyone got the instruction working?

[Hronom]

Guys any progress? Need this feature to run latest version of Elasticsearch from docker-compose...

[GuillaumeMartial]

+1

[jonathas]

Also waiting for this to make our lives easier :)

[Aimsam]

+1

[lambrojos]

+1

[Hronom]

Guys sorry for annoying, when it becomes available in release?

[AnatolyRugalev]

FYI

There is sysctls option starting from docker-compose 2.1

[agiUnderground]

Docker-compose 3.0+ support this feature (sysctls)?

[AnatolyRugalev]

@agiUnderground, yes

[agiUnderground]

@AnatolyRugalev can you give me a link or some example please? I trying to start redis as docker service in docker stack and i wanna change /proc/sys/net/core/somaxconn option.

I found this message, that make me sad(
"Note: This option is ignored when deploying a stack in swarm mode with a (version 3) Compose file."

[marzlarz]

+1

[farwish]

How to fix error below.

Error Message:

ubuntu@VM-0-10-ubuntu:~/dk$ docker-compose up redis
Starting redis-con ... error

ERROR: for redis-con  Cannot start service redis: OCI runtime create failed: container_linux.go:348: starting container process caused "process_linux.go:402: container init caused \"open /proc/sys/net/core/somaxcomm: no such file or directory\"": unknown

ERROR: for redis  Cannot start service redis: OCI runtime create failed: container_linux.go:348: starting container process caused "process_linux.go:402: container init caused \"open /proc/sys/net/core/somaxcomm: no such file or directory\"": unknown
ERROR: Encountered errors while bringing up the project.

docker-compose.yml:

version: '3'
services:
  redis:
    image: redis:3.2.12
    container_name: redis-con
    privileged: true
    sysctls:
      net.core.somaxcomm: '511'

[jtakkala]

Typo? Should be somaxconn, not ‘comm’?

…

On Jul 6, 2018, at 07:29, ercom ***@***.***> wrote: How to fix error below. Error Message: ***@***.***:~/dk$ docker-compose up redis Starting redis-con ... error ERROR: for redis-con Cannot start service redis: OCI runtime create failed: container_linux.go:348: starting container process caused "process_linux.go:402: container init caused \"open /proc/sys/net/core/somaxcomm: no such file or directory\"": unknown ERROR: for redis Cannot start service redis: OCI runtime create failed: container_linux.go:348: starting container process caused "process_linux.go:402: container init caused \"open /proc/sys/net/core/somaxcomm: no such file or directory\"": unknown ERROR: Encountered errors while bringing up the project. docker-compose.yml: version: '3' services: redis: image: redis:3.2.12 container_name: redis-con privileged: true sysctls: net.core.somaxcomm: '511' — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.