Bug#881310: systemd-container: systemd-nspawn containers get non-functioning /etc/resolv.conf

[Michael Biebl]

Am 11.11.2017 um 00:33 schrieb Alex King:
> Looking at the code ("src/nspawn/nspawn.c" in v232), it appears that the 
> existence of /usr/lib/systemd/resolv.conf, which exists on the 
> problematic system, is triggering the problem.

Actually, that points at another problem:
With split-usr (as Debian/Ubuntu uses), the location of resolv.conf is
/lib/systemd/resolv.conf. Which in turn means, systemd-nspawn should not
hard-code that and use /lib/systemd/resolv.conf for split-usr systems.
Either that, or we need to fix the build system to always install
resolv.conf at /usr/lib/systemd/resolv.conf.

As for your question, how this file got there: Did you install systemd
from source in the past?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20171111/8b99870d/attachment-0002.sig>