network-online.target as prerequisite in the systemd units it creates. This in turn pulls
systemd-networkd-wait-online.service, which calls
This command waits for interfaces managed by
networkd to be up, with a timeout of 2 minutes. In case any of those interfaces is not brought up, there will be a 2 minute delay for the service to be started.
It is strongly recommended not to pull in this target too liberally: for example network server software should generally not pull this in (since server software generally is happy to accept local connections even before any routable network interface is up), it’s primary purpose is network client software that cannot operate without network.
it looks like this target should not be usually needed. Note also that this target does not provide a lot of guarantees, as for instance in systems where the
network-manager snap is installed, when it finishes there will not be any interface configured anyway, as
networkd does not manage them.
I suggest to either remove this target or maybe substitute with one with softer requirements, like