Hi,
(installing Bionic here)
a possible solution is to make sure, /target/run is already mounted
(bind-mount to /run) when debootstrap is running which will make systemd
create its resolv.conf copy in the correct /run-filesystem. Otherwise,
it would write to the /target-partition and in-target
@vlee please open a new bug report, and please extract and attach
debian-installer logs, e.g. /var/log/syslog from the d-i environment.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
** Changed in: systemd (Ubuntu)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1713149
Title:
resolv.conf symlink is broken after
artful preseed installs are still failing for me because of hostname
resolutions during in-target.
After base-installer completes, the in-target installation fails to
resolve the artful repositories. The target has /etc/resolv.conf but
/etc/resolv.conf is not working or available through
This bug was fixed in the package resolvconf - 1.79ubuntu8
---
resolvconf (1.79ubuntu8) artful; urgency=medium
* Dereference /etc/resolf.conf when creating runtime configuration when
migrating to resolvconf managed /etc/resolv.conf. The contents of
/etc/resolv.conf (rather
Adding resolvconf task as well, since now:
$ sudo debootstrap --include=resolvconf artful artful
is broken.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1713149
** Also affects: resolvconf (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1713149
Title:
resolv.conf symlink is
Correct that there is a bug with debootstrap above, if both this new
systemd & resolvconf are being bootstrapped together. (as both
src:systemd and src:resolvconf try to setup /etc/resolv.conf symlink)
Dropping resolvconf from important should resolve this.
The ExecStartPre change should then be
This may have been fixed just now by demoting resolvconf from important
to extra. If the next image build is still broken after this change,
please shout.
Ideally the debootstrap would have worked at all points without archive
override changes, but having missed that, we should just get
Bug introduced with this commit.
https://git.launchpad.net/~usd-import-
team/ubuntu/+source/systemd/commit/?id=76e5adfa6d1fb60e9622ca4b0d03a5b4f130885a
** Tags added: artful
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
11 matches
Mail list logo
