Catch-up runs triggered shortly after boot by Persistent=true were failing with DNS resolution errors because NetworkManager had not yet finished bringing up the network. Add network-online.target ordering plus a DNS poll for api.github.com so the service starts once name resolution actually works. |
||
|---|---|---|
| .. | ||
| service-update-alerts.service | ||
| service-update-alerts.timer | ||