&gt; From my own experience with docker in production, I&#x27;m yet to see any of the described scenarios crop up. Has anyone else, or is this solving an extreme edge case?<p>The biggest issue we see at Yelp is leaking containers in test (e.g. Jenkins aborting a job but leaving the containers it spawned still running).<p>Depending on how you orchestrate containers, you might not encounter the issue in prod. If you&#x27;re using something like Kubernates or Marathon or Paasta, they&#x27;re probably going to do the &quot;right thing&quot; and ensure the containers are actually stopped.<p>We also use containers a lot in development. For example, we might put a single tool into a container, and then when developers call that tool, they&#x27;re actually spawning a container without realizing it. For this use case, it&#x27;s really important that signals are handled properly so that Ctrl-C (and similar) continues working.