You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know, if this is the right place to ask for it, but we don't have any further ideas how to handle this problem.
We have a virtual machine for development with some podman pods. A couple of days ago, we migrated from Debian 11 to Debian 12 and from now on, we are using the newest podman, netavark and aardvark-dns versions. And since the migration we face the problem, that the dns resolution still works as you can see in the tshark/tcpdump. But the container reacts with an unreachable port. We also tested it, after a podman system reset. We dont' have a specific containers.conf. We use the default one under /usr/share/containers/.
The setup is as follows: We have a bridge network and a container which has to reach example.domain. This domain is only resolvable by our internal dns internal-dns.server and resolves to <ipv6-of-example.domain>. As I said, the resolution works, our internal dns resolves to the right address. But however the container reacts with an unreachable port icmp packet.
On Debian 11 with older versions (podman 5.3.0, netavark 1.13.0, aardvark-dns 1.16.0.) it worked and currently works on test machines which we not yet migrated.
The following shows what we are doing.
podman network create --subnet '10.90.1.0/24' --gateway 10.90.1.1 --ipv6 test
podman run --rm -it --network test docker.io/library/alpine:3.23.2
getent ahosts example.domain
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I don't know, if this is the right place to ask for it, but we don't have any further ideas how to handle this problem.
We have a virtual machine for development with some podman pods. A couple of days ago, we migrated from Debian 11 to Debian 12 and from now on, we are using the newest podman, netavark and aardvark-dns versions. And since the migration we face the problem, that the dns resolution still works as you can see in the tshark/tcpdump. But the container reacts with an unreachable port. We also tested it, after a
podman system reset. We dont' have a specificcontainers.conf. We use the default one under/usr/share/containers/.The setup is as follows: We have a bridge network and a container which has to reach
example.domain. This domain is only resolvable by our internal dnsinternal-dns.serverand resolves to<ipv6-of-example.domain>. As I said, the resolution works, our internal dns resolves to the right address. But however the container reacts with an unreachable port icmp packet.On Debian 11 with older versions (podman 5.3.0, netavark 1.13.0, aardvark-dns 1.16.0.) it worked and currently works on test machines which we not yet migrated.
The following shows what we are doing.
Here is the filter table while the container is running:
This is the
resolv.conffrom within the container:We appreciate it, if you have any idea what happens here. If you need more information, please let me know :)
Beta Was this translation helpful? Give feedback.
All reactions