I am running Docker on my Synology NAS and I just ran into the issue that I can’t stop a specific container.
I have “stopped” and “killed” it multiple times and the output is always the container’s hash as if the command succeeded, but ps and status show that darn container as still running! And removing the network (as part of docker-compose down) fails because that network still “has active endpoints”
The container has a restart policy of “unless-stopped”, so it definitely should be stoppable!
Even stopping and restarting Docker didn’t fix the issue! That container got immediately restarted.
Do I now really need to restart my server just for this? This is SOOOO annoying!
How can that be? Is there no other method to kill such a zombie?