-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
kpod run -p ..
does not bind the ports
#129
Labels
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Comments
Networking support is still WIP - see #109 |
just FWIW, #109 was merged and the next step is #142, which "Enable host and bridge communications". see also #109 (comment) |
@baude is working on this now |
this should be working on master now, re-open if not |
baude
pushed a commit
to baude/podman
that referenced
this issue
Aug 31, 2019
…eakage_bridge bridge: release IP in case of error
github-actions
bot
added
the
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
label
Sep 24, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Type
/kind bug
What is happening
I am trying to do port binding on my machine from container, but kpod does not bind the ports. Also
kpod ps
does not show the port information. When curled on the endpoint it fails obviously since the port is not bound.Steps to reproduce:
Versions:
The text was updated successfully, but these errors were encountered: