© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
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.