Sign in

Is It A Zombie Container Or Something Else Holding 8080 On A Fresh Ubuntu Box??

Solvedcomposedockerports3 replies · 317 views · started
Reply
Accepted solution by Arjun P. — ok so a natively installed service is a common culprit: local Postgres on 5432, Redis on 6379, Apache or IIS on 80. systemctl status…
  1. Kira B.
    @cobaltloop

    CI pipeline went red overnight. The job that spins up the dev API on a fresh Ubuntu box fails with:

    it passes on retry sometimes, which makes it even worse. i suspect leftovers from earlier jobs but i can't prove it.

    Our pipeline runs several jobs at once on the same runner and they all use the same compose file. i have a feeling that's related, but i don't know how other teams handle this cleanly. Any patterns that actually hold up?

    2
  2. Liv Nakamura
    @liv_rusty

    ok but do you have other compose projects on a git-based pages host? what does docker compose ls say? ??

    0 2 helpful
  3. Kira B.
    @cobaltloop
    in reply to @liv_rusty

    docker compose ls lists a second project from an old branch folder... it's been holding 8080 teh whole time.

    1 3 helpful
  4. Arjun P.
    @packet_monk810
    Accepted solution

    ok so a natively installed service is a common culprit: local Postgres on 5432, Redis on 6379, Apache or IIS on 80. systemctl status postgresql or Get-Service on Windows will tell you. stop it or map the container to another host port ("5433:5432"). good luck man!

    1 3 helpful

Reply to this topic

Sign in or create an account to reply.