Przemek Wesołek

Sorry, but this is not a graceful shutdown. No matter how much `time` is given with `docker stop -t time`, SQL Server never stops within this time period. It has...

OK, I dig a bit and here's a solution. The problem is this line in `Dockerfile` CMD /opt/mssql/bin/sqlservr According to [the Docker docs](https://docs.docker.com/engine/reference/builder/#cmd) its "shell syntax" causes Docker daemon to...

@twright-msft Any idea how this will be solved? Do you need a PR?

Probably other issue?

Did you destroy the old containers and created new ones with `command:` workaround? Once created, containers can't change their command to be executed. What does `docker inspect -f '{{ .Config.Cmd...

@kevin-brown So this issue is not the one you are experiencing. This issue is about wrong image's `CMD` construction, where signals are not propagated to child processes. Sending signals directly...

Anyone having problems with CTRL+C that *are not* solved by correcting ENTRYPOINT (as described in comment https://github.com/Microsoft/mssql-docker/issues/171#issuecomment-346133376), please test 2017-CU5. According to https://support.microsoft.com/en-us/help/4093805/fix-can-t-stop-sql-server-linux-docker-container-via-docker-stop it's solved there.

OK, I did some random "peek and poke" today. Some findings below. The offending network is named `X`. It has no containers, according to `docker inspect X`. The containers were...

When I skimmed over other issues mentioning this error, there are a lot reports dating as far as 2016. For example, #19261 people's workaround was to remove/correct the faulty `Count`...

Probably a duplicate of #42119