Comment 1 for bug 1766872

I did some progress...

I was able to make a few 'enabled|static' services to start such as :
dbus.socket
networking.service
system-resolved.service

NetworkManger doesn't seems to start well.

By making the following changes :

# /lib/recovery-mode/options/network
--------------------------------------
if [ -d /run/systemd/system ]; then
- for i in dbus.socket systemd-resolved.service networking.service systemd-networkd.service NetworkManager.service; do
+ for i in dbus.socket networking.service systemd-networkd.service systemd-resolved.service NetworkManager.service; do
- systemctl is-enabled -q $i && systemctl start $i
+ systemctl is-enabled -q $i && systemctl --job-mode=ignore-dependencies --no-ask-password start $i
    done
    /lib/systemd/systemd-networkd-wait-online && exit 0
fi
--------------------------------------

* Changed the order to start systemd-resolved.service as mentioned in:

# /lib/systemd/system/systemd-resolved.service
After=systemd-networkd.service network.target

to be after systemd-networkd.service

* Add "--no-ask-password" to avoid systemd-tty-ask-password-agent to block
* Add "--job-mode=ignore-dependencies" has most of the service are not running and waiting.