Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Show what process is occupying ports we want to use #10

Open
rwstauner opened this issue Mar 19, 2021 · 0 comments
Open

Show what process is occupying ports we want to use #10

rwstauner opened this issue Mar 19, 2021 · 0 comments

Comments

@rwstauner
Copy link
Contributor

rwstauner commented Mar 19, 2021

to help people debug.
This would probably involve shelling out to lsof and/or ps and might be different for mac vs linux.
If you have another process using *:port docker will fail instantly when it can't bind to the port.
However, if you have a process using 127.0.0.1:port docker will work and then when you try to connect to lvh.me it will use the process specifically sitting on 127.0.0.1:port (it will go to docker only if there is no conflict).
This situation is much more confusing than "docker won't start".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant