docker compose up worked yesterday. today: 'port is already allocated'???

composedockerports1 replies · 188 views · started
  1. long time lurker first post lol CI pipeline went red overnight. the job that spins up the Redis container on a fresh Ubuntu box fails with:

    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.
    

    it passes on retry sometimes, which makes it even worse. I suspect leftovers from earlier jobs but I cant 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 thats related, but idk how other teams handle this cleanly. Any patterns that actually hold up?

    6
  2. lol same thing happened to me 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 youll get this error even with nothing listening.

    1 0 helpful

Reply to this topic

Sign in or create an account to reply.