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

FTL should fail to start if a port is already in use #4798

Open
stuartwdouglas opened this issue Mar 6, 2025 · 2 comments
Open

FTL should fail to start if a port is already in use #4798

stuartwdouglas opened this issue Mar 6, 2025 · 2 comments
Assignees

Comments

@stuartwdouglas
Copy link
Collaborator

No description provided.

@github-actions github-actions bot added the triage Issue needs triaging label Mar 6, 2025
@alecthomas alecthomas mentioned this issue Mar 6, 2025
@bradleydwyer bradleydwyer added the next Work that will be be picked up next label Mar 24, 2025
@github-actions github-actions bot removed the triage Issue needs triaging label Mar 24, 2025
@alecthomas alecthomas self-assigned this Mar 25, 2025
@github-actions github-actions bot removed the next Work that will be be picked up next label Mar 25, 2025
@alecthomas
Copy link
Collaborator

This is a MacOS limitation, where it allows binding of more specific addresses iff the socket options are identical, which is absolutely insane to me:

Image

I think we just need to make sure that k3d doesn't bind to 0.0.0.0

@alecthomas
Copy link
Collaborator

Okay it's even more insane than I thought...

listening.mov

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

3 participants