search for: dhclient_script

...onfigured : 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...

...[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. &...