Sign in

my web container refuses to start on the ci runner. the port thief was hiding

Solvedcomposedockerports8 replies · 252 views · started
Reply
Accepted solution by Lars T. — If docker proxy itself holds the port after a crash, restarting the daemon (sudo systemctl restart docker) releases it. Check ps aux grep…
  1. Hugo
    @hugoy723

    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 🙏

    2
  2. Yara A.
    @yadler

    hmmmm quick q what does ss -ltnp or netstat -ano show for 8080? ??

    8 3 helpful
  3. Hugo
    @hugoy723
    in reply to @yadler

    sorry forgot to say on Windows, 80 is inside an excluded port range. i didnt even know that was a thing.

    2 0 helpful
  4. Ash Petrov
    @ash.petrov
    in reply to @hugoy723

    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

    0 2 helpful
  6. Hugo I.
    @earlyden

    lol same thing happened to me docker ps only shows running containers of the current context. try docker ps -a --filter publish=<port> and check other compsoe projects: docker compose ls. A container from a different folder can hold teh same port.

    1 0 helpful
  7. Yara A.
    @yadler

    have u checked your docker settings? mine were reset after an update. is ports even worth bothering with or should i just leave it hope that helps :)

    0 2 helpful
  8. Lars T.
    @vector_fox
    Accepted solution

    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.

    13 5 helpful
  9. Hugo
    @hugoy723
    in reply to @vector_fox

    @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

    4 1 helpful

Reply to this topic

Sign in or create an account to reply.