2 ms·

I love how there's a special case behavior for the hardcoded process name "docker." Just incredible: https://github.com/jkfran/killport/blob/main/src/linux.rs#L

I love how there's a special case behavior for the hardcoded process name "docker." Just incredible: https://github.com/jkfran/killport/blob/main/src/linux.rs#L97 https://github.com/jkfran/killport/blob/main/src/linux.rs#L9... But seriously kids, take the time to learn Unix tools so you can save yourself from needing to write hundreds of lines of Rust when one shell command will do the same thing.

deleted 4y ago
[deleted]
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 ago
  Only 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.