On Wed, 17 Jul 2024 14:35:11 +0200 Linus Lüssing <linus.luess...@c0d3.blue>
wrote: > Hi, > > Can't reproduce this issue. Can only force this issue by emptying > my /etc/resolv.conf. > > What are the contens and permissions of your /etc/resolv.conf? > $ cat /etc/resolv.conf; ls -lah /etc/resolv.conf > > Also, do you use/have a /etc/nsswitch.conf? > ($ dpkg -l | grep libnss; cat /etc/nsswitch.conf) > > Regards, Linus > > uhmmm... I append "... --share-net \ --ro-bind /etc/ssl/certs/ /etc/ssl/certs/ \ --ro-bind /run/systemd/resolve /run/systemd/resolve \ ...." in the bwrap sequence, and it allows dns resolve and then a connection to the lobby. it works then for this systemd/resolve case (still I am not sure that alll the lines are necessary). in my caase the resolve conf is a link to /run/systemd/resolve/stub-resolv.conf ls -la /etc/resolv.conf : "... /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf ..." and my /etc/nsswitch.conf snipet is...: "... hosts: files myhostname mdns4_minimal [NOTFOUND=return] resolve [! UNAVAIL=return] dns networks: files ..." hope you manage a switch case to allow wrapped connections to the lobby back again...!
