I did manage to reproduce this after all. First thing: 234-2ubuntu10 indeed solves the problem in my manual test at least.
All you need to do to reproduce this is start an artful container: docker run -ti ubuntu:artful bash then install systemd in it: Setting up systemd (234-2ubuntu9) ... ln: cannot remove '/etc/resolv.conf': Device or resource busy which I'm not really suprised about as the file is managed by docker. Debootstrap itself isn't directly affected by this when you run it yourself as it creates its own resolv.conf in the chroot, so I guess live-build had it's hand in this failure. In the builds for older releases this was a non-issue because we never install 'resolvconf' during the build, once you try to do this in the docker container itself, it crashes the same way. Xenial: Setting up resolvconf (1.78ubuntu4) ... ln: cannot remove '/etc/resolv.conf': Device or resource busy dpkg: error processing package resolvconf (--configure): so what happened here is really just that systemd started doing something it wasn't responsible for in the past. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
