6 ms·

I had to chattr +i /etc/resolv.conf because my resolv.conf would keep getting truncated (as in empty) every time I restarted an lxd container. Rock solid my ass

• boudin 4y ago
  lxd is not part of systemd.
• Avamander 4y ago
  Why is lxd touching that file?
• chris_wot 4y ago
  How is that a systemd issue?
  • tyingq 4y ago
    systemd-resolved
    • encryptluks2 4y ago
      Never had this issue. Sounds like they need to recreate the symlink.
      • tyingq 4y ago
        It apparently needs specific tweaking for lxd: https://linuxcontainers.org/lxd/docs/master/howto/network_bridge_resolved/ https://linuxcontainers.org/lxd/docs/master/howto/network_br...
        • lmz 4y ago
          Maybe I'm wrong, but that just seems to show that if you want to resolve lxd domains (hostnames?), you need to inform systemd-resolved to ask lxd for those domains, which is... sensible? > you should notify resolved of the domains that LXD can resolve You'd have the same issues if you replaced systemd-resolved with e.g. dnsmasq. Split DNS always needs resolver configuration.
          • tyingq 4y ago
            I think it's just someone unhappy that they used to be able to edit resolve.conf before systemd-resolved took it over. I recall being annoyed about it as well, but that was some time ago.
            • lmz 4y ago
              It was always a contended file, before systemd e.g. https://wiki.debian.org/resolv.conf https://wiki.debian.org/resolv.conf names two software packages (choose one) to manage that file.
              • tyingq 4y ago
                >It was always a contended file For people using dhcp, yes. The surprise of systemd-resolved was it taking over the file on a typical server that didn't use dhcp.
            • dsr_ 4y ago
              Other direction: people used to feel secure that nothing was going to edit resolv.conf away from what they set up.