[Bug 1988300] Re: systemd-resolved is not installable in Docker images

[Nick Rosbrook]

The bug is in the systemd packaging, and we have cherry-picked a fix [1]
from Debian that will be included in the next kinetic upload.

[1] https://salsa.debian.org/systemd-
team/systemd/-/commit/5d8a69933df0e9ce9e02ff07baed916ddc5af35e

** Changed in: dpkg (Ubuntu)
       Status: New => Invalid

** Changed in: ubuntu-docker-images
       Status: New => Invalid

** Changed in: systemd (Ubuntu)
       Status: New => Fix Committed

** Changed in: systemd (Ubuntu)
       Status: Fix Committed => In Progress

** Changed in: systemd (Ubuntu)
     Assignee: (unassigned) => Nick Rosbrook (enr0n)

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

Title:
  systemd-resolved is not installable in Docker images

Status in Ubuntu Docker Images:
  Invalid
Status in dpkg package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Since 30 August (going by my daily CI builds, I do see the changelog
  entry for resolved is a few days older), I get this:

  Selecting previously unselected package systemd-resolved.
  Preparing to unpack .../321-systemd-resolved_251.4-1ubuntu1_amd64.deb ...
  Unpacking systemd-resolved (251.4-1ubuntu1) ...
  dpkg: error processing archive /tmp/apt-dpkg-install-NS2Yvi/321-systemd-resolved_251.4-1ubuntu1_amd64.deb (--unpack):
   unable to make backup link of './etc/resolv.conf' before installing new version: Invalid cross-device link

  The reason this fails is that Docker mounts resolv.conf, readonly,
  from the host system, so dpkg is not allowed to move/replace it.

  (To be clear, I do not need systemd-resolved in my container. "apt
  install devscripts" pulled it in, and debtree does not tell me why.
  "apt install --no-install-recommends devscripts" does not pull it in,
  and I'll likely adjust my builds [for PowerDNS] to do that because
  it's a good idea anyway).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-docker-images/+bug/1988300/+subscriptions