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

2015-09-24 Thread Ralf Mardorf
On Thu, 24 Sep 2015 13:03:32 -0400, Tom H wrote: > chroot_add_mount /etc/resolv.conf "$resolv_conf" --bind >} > >So they mount the host's resolv.conf on the chroot's. > >And there's the following patch in lxc 0.7.5-3ubuntu69: > ># cat 0031-ubuntu-template-resolvconf.patch >Description: handle /etc

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

2015-09-24 Thread Tom H
On Thu, Sep 24, 2015 at 10:18 AM, Tom H wrote: > > You need to ensure that a proper resolv.conf exists in a chroot before > switching to it. When installing Gentoo, for example, you "cp -L > /etc/resolv.conf $chroot/etc" before chrooting because the > installation tarball doesn't have a resolv.con

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

2015-09-24 Thread Tom H
On Tue, Sep 22, 2015 at 10:19 AM, Ralf Mardorf wrote: > On Tue, 22 Sep 2015 08:36:27 -0400, Tom H wrote: > Thank you Tom for taking the time. You're welcome. >> So it works when using "-b". >> >> But you're right, it doesn't when not using "-b". >> >> Ubuntu decided to default to using resolv

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

2015-09-22 Thread Ralf Mardorf
Thank you Tom for taking the time. On Tue, 22 Sep 2015 08:36:27 -0400, Tom H wrote: >systemd-resolved is a service not a package. Ok, I didn't know it. [rocketmouse@archlinux ~]$ systemctl status systemd-resolved ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/usr/lib/sy

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

2015-09-22 Thread Tom H
On Tue, Sep 22, 2015 at 4:16 AM, Ralf Mardorf wrote: > On Mon, 21 Sep 2015 21:51:35 -0400, Tom H wrote: >> On Sun, Sep 20, 2015 at 1:11 PM, Ralf Mardorf >> wrote: >>> by default Wily's /etc/resolv.conf is a link against >>> ../run/resolvconf/resolv.conf. If you want to maintain Wily from >>> a

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

2015-09-22 Thread Ralf Mardorf
On Tue, 22 Sep 2015 10:19:11 +0200, Ralf Mardorf wrote: >On Mon, 21 Sep 2015 21:51:35 -0400, Tom H wrote: >>"systemd-nspawn -bD ...". > >I missed this. > > -b --boot > >I'll test it now ... [rocketmouse@archlinux ~]$ sudo mv -i /mnt/moonstudio/etc/resolv.conf /mnt/moonstudio/etc/resolv.conf.fix

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

2015-09-22 Thread Ralf Mardorf
On Mon, 21 Sep 2015 21:51:35 -0400, Tom H wrote: >"systemd-nspawn -bD ...". I missed this. -b --boot I'll test it now ... -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-disc

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

2015-09-22 Thread Ralf Mardorf
On Mon, 21 Sep 2015 21:51:35 -0400, Tom H wrote: >On Sun, Sep 20, 2015 at 1:11 PM, Ralf Mardorf > 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

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

2015-09-21 Thread Tom H
On Sun, Sep 20, 2015 at 1:11 PM, Ralf Mardorf 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 i