Bug#881310: systemd-container: systemd-nspawn containers get non-functioning /etc/resolv.conf
Michael Biebl
biebl at debian.org
Sat Nov 11 11:53:22 GMT 2017
Hi Alex
Am 11.11.2017 um 00:33 schrieb Alex King:
> looks like everything that should be in /lib/systemd and
> /usr/lib/systemd is duplicated in both places?! I guess that is most
> likely a sysadmin typo, although the system was reloaded relatively
> recently and I have no idea how this could have happened.
That sounds like you might have usrmerge enabled, i.e. /lib is a symlink
to /usr/lib etc. This would explain the resolv.conf in both locations.
Can you post the output of "ls -la /"
Such a system can be created by using debootstrap's --merged-usr or
installing the usrmerge package in the final system.
Michael
--
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: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20171111/b18ccce4/attachment-0002.sig>
More information about the Pkg-systemd-maintainers
mailing list