Add an option to the YAML file to specify an alternative signal to stop containers

[GaretJax]

It would be great if we could specify a signal number in the fig.yml file. Fig would then use it with docker kill -s SIGNAL instead of docker stop when stopping a container.

[tomfotherby]

I would love this too. memcache needs SIGINT but docker gives SIGTERM see #273 .

[clemtibs]

Definitely +1. The trend is more and more toward complicatedly intertwined and heterogeneous clusters of containers consisting of many different apps, but that all must operate harmoniously as a single service. I think this feature is extremely important to ensuring this.

The implications too are not just for docker-compose, but also because the docker-compose yaml syntax is becoming the standard for other orchestration platforms such as Rancher and this would be a good habit to enforce in the yaml files all around.

[deminoth]

+1. MongoDB has same issue.

[thaJeztah]

I think this is currently worked on in Docker, see this pull request; moby/moby#15307

[dnephin]

The cli now supports -s http://docs.docker.com/compose/reference/kill/

I don't think it makes sense to add an option to the yaml config. Containers should respond to signals in an expected way. There's no good reason to send anything besides SIGTERM to stop a container.

[thaJeztah]

There's no good reason to send anything besides SIGTERM to stop a container.

Docker will be adding this though, see moby/moby#15307. IIRC, this came up a few times, because some packages/services didn't work well with SIGTERM

[aanand]

Interesting, I can see the argument for it. I guess we should implement stop_signal then.

[thaJeztah]

FYI, docker moby/moby#15307 was just merged, so this will be in the Docker 1.9 release.