-
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 machine] Port auto-forwarding does not work in macOS when used with podman play kube #12248
Comments
Facing the same issue. |
Can you try with |
I got the following error
According to https://docs.podman.io/en/latest/markdown/podman-play-kube.1.html#network-mode-net, the network mode bridge needs to be defined in k8s yaml — how do I define that in my |
I do not think you can set bridge explicitly. Unless host networking is set in the yaml it should use bridge. |
Output from
|
The podman inspect output is from the working pod, right? |
Yep! |
We need to use the config network mode when no network mode was set. To do so we have to keep the nsmode empty, MakeContainer() will use the correct network mode from the config when needed. Fixes containers#12248 Signed-off-by: Paul Holzinger <[email protected]>
We need to use the config network mode when no network mode was set. To do so we have to keep the nsmode empty, MakeContainer() will use the correct network mode from the config when needed. Fixes containers#12248 Signed-off-by: Paul Holzinger <[email protected]> <MH: Fixed cherry-pick conflicts> 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
I run podman machine on MacOS. When I try to spin up containers by using
podman play kube
on k8s yaml file, I cannot seem to access my rootless container - automatic port forwarding by gvproxy does not work when I start the container and expose the port.Steps to reproduce the issue:
Start the podman machine.
podman machine start
Start the containers defined in k8s yaml below.
podman play kube pod.yaml
Describe the results you received:
Containers are spun up, but I cannot access the port exposed on localhost.
Describe the results you expected:
Able to connect to localhost port 8080.
Additional information you deem important (e.g. issue happens only occasionally):
I am facing the same situation as described here (#11396 (comment)). Setting the rootless_networking = "cni" in the local containers.conf doesn't work also.
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/master/troubleshooting.md)
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
macOS Monterey version 12.0.1
The text was updated successfully, but these errors were encountered: