Sign in

Bind For 0.0.0.0:6379 Failed: Port Is Already Allocated. By WHAT?

Solvedcomposedockerports7 replies · 360 views · started
Reply
Accepted solution by Elena Yilmaz — lol same thing happened to me if docker proxy itself holds the port after a crash, restarting teh daemon (sudo systemctl restart docker)…
  1. Zora Gill
    @tensor_den-zl

    this worked fine last week, today, on my laptop, the reverse proxy dies right away:

    This app can't run on your PC

    This app can't run on your PC

To find a version for your PC, check with the
software publisher.

    i didn't change the compose file. Port 6379. i've checked Task Manager and htop and i can't find anything obvious. Is Docker keeping a ghost reservation?

    ive already run docker compose down in teh project folder, restarted Docker Desktop and checked that no other termnial is running teh stack. the error comes back instantly every time. is there a command that just tells me who owns a port?

    1
  2. Silas Moreau
    @silas.moreau

    hmmmm quick q is there a native install of teh same software outside Docker??

    1 0 helpful
  4. Zora Gill
    @tensor_den-zl
    in reply to @hdalton_10

    sorry forgot to say docker compose ls lists a second project from an old branch folder. its been holding 6379 the whole time. sorry for the wall of text lol

    2 0 helpful
  5. Liv
    @quiet_sage420

    hmmm find who owns the port first:

    sudo ss -ltnp 'sport = :6379'
# or
sudo lsof -i :6379

    On Windows: netstat -ano | findstr :6379 and then look up the PID in Task Manager. lmk how it goes

    3 0 helpful
  6. Wren Vance
    @wren.vance

    On Windows, Hyper-V/WSL reserves dynamic port ranges. Check with netsh interface ipv4 show excludedportrange protocol=tcp. If 6379 falls in an excluded range you'll get this error even with nothing listening.

    0 2 helpful
  7. Elena Yilmaz
    @elenay77
    in reply to @wren.vance Accepted solution

    lol same thing happened to me if docker-proxy itself holds the port after a crash, restarting teh daemon (sudo systemctl restart docker) releases it. Check ps aux | grep docker-proxy first. worked for me anyway 🤷

    0 5 helpful
  8. Zora Gill
    @tensor_den-zl
    in reply to @elenay77

    @elenay77 dude stopped the forgotten native service and teh reverse proxy came right up on 6379. demo saved with ten minutes to spare. thank u thank u thank u

    mindblown

    0 2 helpful

Reply to this topic

Sign in or create an account to reply.