Disable systemd-networkd-wait-online.service to prevent boot delays#645
Merged
dhh merged 1 commit intoAug 11, 2025
Merged
Conversation
dhh
pushed a commit
to ryanrhughes/omarchy
that referenced
this pull request
Aug 22, 2025
marcinczenko
pushed a commit
to marcinczenko/omarchy
that referenced
this pull request
Sep 23, 2025
chriopter
pushed a commit
to chriopter/omarchy
that referenced
this pull request
Nov 18, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The default networkd config inserts systemd-networkd-wait-online.service into the critical boot chain. We can see this consistently by analyzing
systemd-analyze critical-chain. I suspect this is a remnant of networkd being primarily designed for server environments where you would want to ensure network online before proceeding to boot.While we've resolved anything in the boot chain requiring this as a dependency in the core of Omarchy, we can't control every app so we have a number of users who have encountered the issue recurring.
Eg. Zerotier from someone in Discord https://discord.com/channels/1390012484194275541/1390012487000395859/1404167814947934259.
Some have inserted a lower arbitrary timeout of 30sec vs the default 120sec but I dislike this because if a user is impacted, they're still required to wait an unnecessary amount of time to boot.
After searching about for a while, a common practice is to just disable and mask it so it moves on. This appears to be our ticket.
In my own testing, with Omarchy + Tailscale, I've not encountered any issue. All systems continue to come online just fine after booting to the desktop environment, which is what we want.
Submitting PR to get extra eyes and testing on this one.
Fixes #632