If docker-proxy itself holds the port after a crash, restarting the daemon (sudo systemctl restart docker) releases it. Check ps aux | grep docker-proxy first.
long time lurker first post lol just trying to start the web container with docker compose up on teh CI runner and i get:
docker ps shows nothing running. i rebooted Docker. still the same. i need this running for a demo in an hour and i'm getting desperate.
im not a Docker expert, i mostly copy compose files from the team wiki and they usually just work. rebooting the whole machine is my next step, but Id rather understand whats going on before i lose all my open windows. pls help 馃檹
sorry forgot to say on Windows, 80 is inside an excluded port range. i didnt even know that was a thing.
oof find who owns the port first:
sudo ss -ltnp 'sport = :<port>'
# or
sudo lsof -i :<port>
on Windows: netstat -ano | findstr :<port> and then look up the PID in Task Manager. if nothing owns it, check netsh interface ipv4 show excludedportrange protocol=tcp, Hyper-V/WSL can reserve whole port ranges. lmk how it goes
any update on this? ??
@vector_fox omg finally moved the mapping to a port outside teh excluded range. Everything works on the CI runner now. Thanks for the netsh tip! cant believe it was that simple lol
Sign in or create an account to reply.
