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

[Michael Biebl]

Am 10.11.2017 um 23:05 schrieb Alex King:
> $ sudo systemctl status systemd-resolved.service
> ● systemd-resolved.service - Network Name Resolution
>    Loaded: loaded (/lib/systemd/system/systemd-resolved.service;
> disabled; vendo
>   Drop-In: /usr/lib/systemd/system/systemd-resolved.service.d
>            └─resolvconf.conf

Hm, where is this file coming from? It's certainly not from systemd. It
doesn't seem to be coming from Debian either (at least apt-file search
/usr/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf does
not yield any results).

Do you have any custom packages/software in that VPS which might interfere?

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/20171110/2fb43f69/attachment-0002.sig>