Podman 5.0.1 can no longer connect to services running on container host on the default route IP address about podman HOT 5 CLOSED

see the pasta section here https://blog.podman.io/2024/03/podman-5-0-breaking-changes-in-detail/

Although I thought I fixed the host.containers.internal problem but I guess it was only fixed for --network pasta and not bridge networks. And also in order to have this work you would need to have a second ip on the host because pasta by default will always pick the ip from the default interface so it can never be reachable.

from podman.

I close this a dup of #19213 as it has much more info on what needs to be done to fix it properly but it will need pasta fixes if there are no other ips on the host

from podman.

Thanks @Luap99! I will subscribe to #19213 for updates.

from podman.

@Luap99 isn't #19213 exclusively around DNS issues? I didn't quite grasp the problem here yet, but I'm wondering if this one could be worked around by some explicit -t / -T options.

from podman.

@Luap99 isn't #19213 exclusively around DNS issues?

No it is for both host.containers.internal host entry which needs a 1 to 1 ip mapping to the actual host ip. And resolv.conf which already works ok with --dns-forward today.

from podman.