Ioanna Alifieraki
2019-Apr-15 09:52 UTC
[Libguestfs] supermin (chroot+systemd.resolved) - network cannot be configured on Ubuntu
Hi, I am facing the following bug while runnign guestfish on Ubuntu Bionic onward, where the network cannot be configured : https://bugs.launchpad.net/ubuntu/+source/supermin/+bug/1824236 The actual problem is the combination of (a) supermin and the fact that it does chroot and (b) a dhclient hook present in Bionic (/etc/dhcp/dhclient-eneter-hooks.d/resolved) that overwrites the make_resolv_conf function of dhclient_script with one that in the end restarts the systemd.resolved service. Being, however in chroot, the new make_resolv_conf function fails with "System has not been booted with systemd as init system (PID 1). Can't operate." and the network is left unconfigured. Although there is a workaround for this, I am seeking for a better solution. I would like to ask you if this is the expected behaviour of supermin or something that needs fixing. Thank you in advance. Best, Jo
Richard W.M. Jones
2019-Apr-16 07:53 UTC
Re: [Libguestfs] supermin (chroot+systemd.resolved) - network cannot be configured on Ubuntu
On Mon, Apr 15, 2019 at 10:52:40AM +0100, Ioanna Alifieraki wrote:> Hi, > > I am facing the following bug while runnign guestfish on Ubuntu Bionic > onward, > where the network cannot be configured : > https://bugs.launchpad.net/ubuntu/+source/supermin/+bug/1824236 > > The actual problem is the combination of (a) supermin and the fact that it > does chroot > and (b) a dhclient hook present in Bionic > (/etc/dhcp/dhclient-eneter-hooks.d/resolved)Does it work if you add this early on to appliance/init [1]: rm -f /etc/dhcp/dhclient-eneter-hooks.d/resolved There is no systemd in the appliance so anything that tries to run systemd service is going to fail anyway. Rich. [1] https://github.com/libguestfs/libguestfs/blob/master/appliance/init> that overwrites the make_resolv_conf function of dhclient_script with one > that > in the end restarts the systemd.resolved service. > Being, however in chroot, the new make_resolv_conf function fails with > "System has not been booted with systemd as init system (PID 1). Can't > operate." > and the network is left unconfigured. > > Although there is a workaround for this, I am seeking for a better solution. > I would like to ask you if this is the expected behaviour of supermin or > something > that needs fixing. > > Thank you in advance. > > Best, > Jo> _______________________________________________ > Libguestfs mailing list > Libguestfs@redhat.com > https://www.redhat.com/mailman/listinfo/libguestfs-- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-builder quickly builds VMs from scratch http://libguestfs.org/virt-builder.1.html
Ioanna Alifieraki
2019-Apr-17 16:47 UTC
Re: [Libguestfs] supermin (chroot+systemd.resolved) - network cannot be configured on Ubuntu
Hi, Thank you very much for your suggestion. I've tested it and it works fine. Thanks, Jo On Tue, Apr 16, 2019 at 8:53 AM Richard W.M. Jones <rjones@redhat.com> wrote:> On Mon, Apr 15, 2019 at 10:52:40AM +0100, Ioanna Alifieraki wrote: > > Hi, > > > > I am facing the following bug while runnign guestfish on Ubuntu Bionic > > onward, > > where the network cannot be configured : > > https://bugs.launchpad.net/ubuntu/+source/supermin/+bug/1824236 > > > > The actual problem is the combination of (a) supermin and the fact that > it > > does chroot > > and (b) a dhclient hook present in Bionic > > (/etc/dhcp/dhclient-eneter-hooks.d/resolved) > > Does it work if you add this early on to appliance/init [1]: > > rm -f /etc/dhcp/dhclient-eneter-hooks.d/resolved > > There is no systemd in the appliance so anything that tries to run > systemd service is going to fail anyway. > > Rich. > > [1] https://github.com/libguestfs/libguestfs/blob/master/appliance/init > > > that overwrites the make_resolv_conf function of dhclient_script with one > > that > > in the end restarts the systemd.resolved service. > > Being, however in chroot, the new make_resolv_conf function fails with > > "System has not been booted with systemd as init system (PID 1). Can't > > operate." > > and the network is left unconfigured. > > > > Although there is a workaround for this, I am seeking for a better > solution. > > I would like to ask you if this is the expected behaviour of supermin or > > something > > that needs fixing. > > > > Thank you in advance. > > > > Best, > > Jo > > > _______________________________________________ > > Libguestfs mailing list > > Libguestfs@redhat.com > > https://www.redhat.com/mailman/listinfo/libguestfs > > > -- > Richard Jones, Virtualization Group, Red Hat > http://people.redhat.com/~rjones > Read my programming and virtualization blog: http://rwmj.wordpress.com > virt-builder quickly builds VMs from scratch > http://libguestfs.org/virt-builder.1.html >
Maybe Matching Threads
- Re: supermin (chroot+systemd.resolved) - network cannot be configured on Ubuntu
- [PATCH] appliance: Remove /etc/dhcp/dhclient-enter-hooks.d/resolved.
- Re: [PATCH] appliance: Remove /etc/dhcp/dhclient-enter-hooks.d/resolved.
- Re: [PATCH] appliance: Remove /etc/dhcp/dhclient-enter-hooks.d/resolved.
- replication fails