-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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 kube ignores hostNetwork directive in pod description #4432
Comments
@haircommander Or anyone else. Seems like this would be a good fist issue. |
I hope the work beginning in #2957 will solve this |
Note that this isn't "just" a |
It looks like this was also requested in #3837. |
This issue had no activity for 30 days. In the absence of activity or the "do-not-close" label, the issue will be automatically closed within 7 days. |
@larsks @haircommander Is this fixed now? Can we close? |
nope, still not fixed |
@mheon Could you mark this on as fixed by your PR? |
I got everything except |
Added to #5241 |
Enables most of the network-related functionality from `podman run` in `podman pod create`. Custom CNI networks can be specified, host networking is supported, DNS options can be configured. Also enables host networking in `podman play kube`. Fixes containers#2808 Fixes containers#3837 Fixes containers#4432 Fixes containers#4718 Fixes containers#4770 Signed-off-by: Matthew Heon <[email protected]>
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
podman play kube
does not respect thehostNetwork
parameter in a pod spec.Steps to reproduce the issue:
hostNetwork
parameter:Describe the results you expected:
I expected the container to run in the host network namespace.
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):The text was updated successfully, but these errors were encountered: