[Bug 1990187] Re: systemd-resolved recommends libnss-resolve in kinetic, pulls it into minimal system where it was explicitly excluded before

[Heinrich Schuchardt]

** Tags added: foundations-todo

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1990187

Title:
  systemd-resolved recommends libnss-resolve in kinetic, pulls it into
  minimal system where it was explicitly excluded before

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  In kinetic, systemd-resolved now Recommends: libnss-resolve, pulling
  it into the ubuntu-minimal seed.

  In the past we briefly had libnss-resolve seeded (between xenial and
  bionic LTSes but not in any LTS) but it was removed because:

   - it was redundant; /etc/resolv.conf was consistent and correct.
   - its presence could mask wrong DNS configuration resulting in difficult-to-debug differences in behavior between applications that did use nss_resolved via /etc/nsswitch.conf and those that did not (examples: i386 binaries that could not use nss_resolved because it was not installed; statically-linked go implementations that parsed /etc/resolve.conf directly and did not load NSS modules)

  This new recommends was noticed specifically because of some broken
  kinetic container images where /etc/resolv.conf was broken (empty) and
  *some* applications still worked via nss but others failed by trying
  to use the DNS protocol directly.  (I.e.: 2nd point above)

  I believe systemd-resolved should drop its recommends on libnss-
  resolve for Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1990187/+subscriptions