-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Podman play|generate kube isn't creating a pod with the equivalent of the -p option #5964
Comments
@haircommander WDYT? |
We have the hostPort options wired up, but it's possible there's somewhere it's dropped. I'll try to look at this later today |
I remember from working on #5642, port parsing should be fine, but there's no bind to individual IP supported. As of 1.9 it's not supported https://github.com/containers/libpod/blob/d985723506a29766ed21585ba8541033db6bd572/pkg/adapter/pods.go#L798 Where did pkg/adapter go in v2? |
I can confirm this.
This yaml create a container like:
|
We should fix this for v2.0 |
@ashley-cui PTAL |
@mheon Unfortunately it is not fixed in v2.0. This is a real problem. It is currently not possible to use a port twice if you have multiple IPs on the host. |
A friendly reminder that this issue had no activity for 30 days. |
@ashley-cui Did you ever get a chance to look at this? |
@rhatdan Didn't get a chance to look at it, but should be free to take it today, unless @ryanchpowell wants it |
@ashley-cui you take it. |
@rhatdan How do I write tests for this? Since IP's change from machine to machine |
This issue seems to be fixed with the PR. In which version will this be shipped? |
I test it , it's ok in
|
@zhangguanzhang What did you exactly test? The problem here is that podman listen on all adresses instead of the defined one.
That is my kubernetes.yaml:
|
Looks like it didn't get into 2.0.4 but is in master |
Well, then lets hope for 2.0.5 🤞 |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
podman generate kube doesn't seem to create any kube yaml which would run the equivalent of
podman pod create -p 192.168.1.239:5000:5000/tcp
Or podman play kube doesn't create the pod with the hostIP assigned to the container.
Describe the results you received:
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Additional environment details (AWS, VirtualBox, physical, etc.):
VM on Proxmox
The text was updated successfully, but these errors were encountered: