You hit docker stop . Nothing happens. You wait ten seconds. Docker eventually sends SIGKILL . The container disappears, but only after a frustrating timeout. Your CI pipeline is slower than it should be, your Kubernetes pod terminations are sluggish, and you have a vague feeling something is wrong. I hit this exact issue last month while debugging a deployment that took 90 seconds to roll out a single replica. Turned out to be the same boring culprit I've seen on at least four other projects: the PID 1 problem. Let me walk you through what's actually happening, why it bites so many teams, and how to fix it properly. The frustrating symptom Here's what it usually looks like. You've got a Node app, a Python service, or whatever. You build it, run it, and try to stop it: docker run --name myapp -d my-image:latest # ... later ... time docker stop myapp # real 0m10.234s Enter fullscreen mode Exit fullscreen mode Ten seconds. Every. Single. Time.…