Podman 5.0.1 can no longer connect to services running on container host on the default route IP address #22502
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
network
Networking related issue or feature
pasta
pasta(1) bugs or features
Issue Description
I have a service that runs in a different set of containers on my workstation and I can no longer connect to it's ports that are bound to the main network interface when using a pod or container that is connected to shared podman network.
This all broke when I upgraded to Fedora 40 which has podman 5.0.1. Everything worked as expected with Fedora 39 with podman
podman-4.9.4-1.fc39
You can see the port is closed when trying to scan it with nmap:
When you nmap the default route IP you only see open ports from the containers and pods that are attached to the podman network.
If you hit an IP address on a different interface you can access the port just fine:
Steps to reproduce the issue
Steps to reproduce the issue
Describe the results you received
I am unable to connect to services running on the default route IP address on the container host from containers.
Describe the results you expected
The same behavior as in
podman-4.9.4-1.fc39
.podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
Here is the podman network I am using:
Additional information
No response
The text was updated successfully, but these errors were encountered: