3 ms·
Well yeah, because blindly killing the process that's listening on the port will do the wrong thing for Docker and you can't predict without asking Docker what
by Spivak 4y ago
Well yeah, because blindly killing the process that's listening on the port will do the wrong thing for Docker and you can't predict without asking Docker what container/process is the one that owns the port.
- xorcist 4y agoOnly because Docker is broken. No other process manager would be confused by that. Maybe we should patch kill itself? It wouldn't surprise me one bit if that pull request exists.