[Bug 1713212] Re: changes in >= 234-2ubuntu7 for artful breaks kubuntu CI image build in docker

[Philip Muškovac]

For clarification, the environment the containers run with is:

privileged: false,
cap_add: ['SYS_ADMIN'],
security_opts: ['apparmor:unconfined']

(see https://git.launchpad.net/~kubuntu-ci-admins/kubuntu-ci/+git
/pangea-tooling/tree/kci/imager.rb)

what's not helpful is that running debootstrap in a container started on the shell with
run --cap-add SYS_ADMIN --privileged=false --security-opt 'apparmor:unconfined'
seems to work fine... (result: artful/etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf)

so this might be related to some of the environment setup before live-
build starts running - or that fact that it's running headless, but I
did not have time to take a closer look at that.

As for touching resolv.conf, live-build does mess with it later on in
some way during the chroot build, but that happens far later during the
build.

-- 
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/1713212

Title:
  changes in >= 234-2ubuntu7 for artful breaks kubuntu CI image build in
  docker

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Our live image build in kubuntu CI using docker, now fails since
  changes in 234-2ubuntu7 onwards.

  log: https://kci.pangea.pub/job/iso_artful_stable_amd64/4/console

  14:52:28 ln: cannot remove '/etc/resolv.conf': Device or resource busy
  14:52:28 dpkg: error processing package systemd (--configure):
  14:52:28  subprocess installed post-installation script returned error exit status 1

  234-2ubuntu7 changes:
  https://launchpad.net/ubuntu/+source/systemd/234-2ubuntu7

    * Always setup /etc/resolv.conf on new installations.
      On new installations, /etc/resolv.conf will always exist. Move it to /run
      and replace it with the desired final symlink. (LP: #1712283)
    * Create /etc/resolv.conf on resolved start, if it is an empty file.

  I doubt eventually we will be the only ones to hit the issue.

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