Luap99
commented
1 year ago Maybe lets take a step back first. And try to reproduce with something simple. Ideally reboot first to prevent any temporary state from conflicting.
After the start does the following work?
$ podman network create testnet
testnet
$ podman run --network testnet --name c1 -d alpine sleep inf
dc517d9f188e51479e127776549d120fc117443e0920b1b74cd86da3e310b0de
$ podman run --network testnet --rm alpine nslookup c1
Server: 10.89.0.1
Address: 10.89.0.1:53
Non-authoritative answer:
Name: c1.dns.podman
Address: 10.89.0.2
Non-authoritative answer:
$ podman run --network testnet --rm alpine nslookup google.com
Server: 10.89.0.1
Address: 10.89.0.1:53
Non-authoritative answer:
Name: google.com
Address: 142.250.184.206
Non-authoritative answer:
Name: google.com
Address: 2a00:1450:4001:812::200eIf you suspect namespace issues then you should check this:
$ podman unshare --rootless-netns readlink /proc/self/ns/net
net:[4026536046]
$ readlink /proc/$(pgrep aardvark-dns)/ns/net
net:[4026536046]The values must match otherwise it would be totally expected that dns fails.
In general adding --log-level debug to all your podman commands should give much more clues what is going on during network setup. And aardvark-dns logs to the syslog so if you run systemd you should be able to see the message with journalctl --user SYSLOG_IDENTIFIER=aardvark-dns
deliciouslytyped
github-actions[bot]
Issue Description
Sorry for the vague title, It can be made specific if we can figure out something more concrete. I spend a lot of time in the past few weeks fiddling with various podman problems and gotten a bit tired and burned out on it. It would be nice to have some guidance on how to go forward from here. Sorry for the low quality issue filing, if I have some more energy later I will improve it.
I last tried this with podman 4.5.0 .
I've thrown nsenter, pwru, some iptables tracing tools, looking at the debug output of podman at this and figured some things out.
I have a fairly vanilla rootless podman-compose configuration along with a network configured for it, and I'm having DNS issues with it: the containers cannot reach aardvark-dns, the port is not there. DNS is enabled on the network.
Basically I have confirmed that the reason that DNS replies are not received is because the packet are either going to the wrong place, or aardvark isnt listening on an interface that it should be listening on. aardvark itself works, because I was able to enter it's namespace and talk to it.
I managed to figure out a workaround which consists of bringing up the containers, killing aardark-dns and then restarting any container to bring aardvark-dns back up.
Using one of (I don't currently remember, I will test it later I guess) podman unshare --rootless-netns or using nsenter to attach to the network namespace of the aardvark process, or something like that, shows that the interfaces used to wire up podman's networking are missing until I kill and start aardvark.
Is there any way to debug aardvark bringup specifically?
podman info output