systemd-resolved recommends libnss-resolve in kinetic, pulls it into minimal system where it was explicitly excluded before
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
Fix Released
|
Low
|
Unassigned |
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.
Related branches
- Steve Langasek: Approve
-
Diff: 117 lines (+51/-5)4 files modifieddebian/changelog (+28/-0)
debian/control (+4/-5)
debian/patches/lp1989969-test-deny-list-TEST-36-NUMAPOLICY-on-ppc64el.patch (+18/-0)
debian/patches/series (+1/-0)
Changed in systemd (Ubuntu): | |
status: | New → Confirmed |
tags: | added: foundations-todo |
Changed in systemd (Ubuntu): | |
status: | Triaged → Fix Committed |
tags: | removed: foundations-todo |
Jammy's systemd 249.11-0ubuntu3.6 does not provide package systemd-resolved at all.
Could we drop systemd-resolved from ubuntu-minimal?