A port is already in use
Diagnoses an "address already in use" error, distinguishing a Docker container publishing the port from a stray local process, and routes to the right way to free it.
Run this
Read-onlyList everything currently listening, to see whether the port belongs to a Docker-published container or a plain local process
lsof -i tcp -sTCP:LISTENMatched against this step's known patterns to pick the next step.
View full flow
- find_ownerkind: recipe_ref
- outcome: success → confirm_kill
- default → unknown_owner
- port_freedkind: outcome
- confirm_killkind: outcome
- unknown_ownerkind: outcome
- node_owns_portkind: recipe_ref
- outcome: success → port_freed
- default → unknown_owner
- check_port_owner (entry)kind: diagnostic
- match "docker-proxy|com\.docker" → docker_owns_port
- match "node|npm" → node_owns_port
- default → find_owner
- docker_owns_portkind: outcome