On 5/29/23 05:59, lejeczek via Podman wrote:
Hi guys.
--dns=none renders what expected but with an actual server, say: --dns=10.3.1.200 resolve.conf seems to be the one of the host's, as if --dns did not happen. Can anybody else say that is the case? Am I missing something? I'm on Centos 9 stream with all bits up-to-date. many thanks, L.
_______________________________________________ Podman mailing list --podman@lists.podman.io To unsubscribe send an email topodman-leave@lists.podman.io
Here is what I am getting? ``` # podman run --dns=10.3.1.200 alpine cat /etc/resolv.conf nameserver 10.3.1.200 # podman run --dns=none alpine cat /etc/resolv.conf cat: can't open '/etc/resolv.conf': No such file or directory ``` Rootless ``` $ podman run --dns=10.3.1.200 alpine cat /etc/resolv.conf nameserver 10.3.1.200 $ podman run --dns=none alpine cat /etc/resolv.conf cat: can't open '/etc/resolv.conf': No such file or directory ```