This bug was fixed in the package systemd - 234-2ubuntu10
---
systemd (234-2ubuntu10) artful; urgency=medium
* Do not fail debootstrap if /etc/resolv.conf is immutable. (LP: #1713212)
* Revert "Create /etc/resolv.conf on resolved start, if it is an empty file."
As it is
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:
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
Inside the old kubuntu-ci image I see:
# ls -latr squashfs-root/etc/resolv.conf
lrwxrwxrwx 1 root root 29 Aug 29 12:54 squashfs-root/etc/resolv.conf ->
../run/resolvconf/resolv.conf
I am confused how resolvconf managed to replace /etc/resolv.conf, yet systemd
did not.
Do you somewhere later
A bit old, as we were not able to run the builds for artful while we had
the Qt 5.9 landing PPA enabled to test build our packages against.
https://kci.pangea.pub/job/iso_artful_stable_amd64/3/consoleFull
http://kci.pangea.pub/images/iso_artful_stable_amd64/20170722-2012/
--
You received this
I'm not sure how to fix this, or rather how to make src:systemd match
what src:resolvconf used to do.
In the end the system should end up with /etc/resolv.conf pointing at
/run/systemd/resolve/stub-resolv.conf. Yet from the log, it seems that
debootstrap (?!) is running, however, one is not
No, builds are still failing with the same issue.
--
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
Has this still been an issue since resolvconf and ifupdown were re-
promoted to Priority: important?
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
8 matches
Mail list logo
