systemd-nspawn and /run/resolvconf/resolv.conf

Tom H tomh0665 at
Tue Sep 22 01:51:35 UTC 2015

On Sun, Sep 20, 2015 at 1:11 PM, Ralf Mardorf
<ralf.mardorf at> wrote:
> by default Wily's /etc/resolv.conf is a link against
> ../run/resolvconf/resolv.conf. If you want to maintain Wily from another
> install in a systemd-nspawn container, the link needs to be replaced by a
> file /etc/resolv.conf. Since Wily is based on systemd by itself, it IMO
> should care about systemd-nspawn compatibility and by default not link
> against /run.
> Assumed nobody should be aware about a reason that a link is a better
> solution, I would report it as a bug.

If you were to set up the "full systemd upstream experience", you'd be
using systemd-resolved and "/etc/resolv.conf" would be a symlink to
"/run/systemd/resolve/resolv.conf", so there's no reason why Ubuntu's
default resolvconf setup shouldn't work, at least when using
"systemd-nspawn -bD ...".

More information about the Ubuntu-devel-discuss mailing list