RSS Bot Posted May 12 Share Posted May 12 Description systemd-resolved is installed and enabled by default - unfortunately a static /etc/resolv.conf nameserver 1.0.0.1 set up during debootstrap phase is preventing systemd-resolved to do its job Removing the file after chroot has been finalized in post-tweaks.sh enables systemd-resolved to symlink /etc/resolv.conf to /run/systemd/resolved/stub-resolv.conf on first boot How Has This Been Tested? [x] Rebuilt an booted an Orangepi5-plus debian trixie image from trunk Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] My changes generate no new warnings View the full article Link to comment Share on other sites More sharing options...
Recommended Posts