Commit a52d6f0
committed
install: Don't require the network by default
The `Wants=network-online.target` predates the osmet work which enabled
the now default fully offline install flow.
It also predates the addition of fetch retries. So even in an online
flow, now that we retry HTTP requests indefinitely, we don't really
need this.
Let's follow best practices and stop pulling in `network-online.target`.
We still need to keep pulling in `NetworkManager.service`
though. It's enabled by default in `multi-user.target` but not
`coreos-installer-post.target` (which is what we boot to in an automated
install).
NetworkManager is capable of handling offline environments just fine and
won't block the install just because a connection isn't available (yet
or ever).
Related: coreos/fedora-coreos-config#1088
Related: #565 (comment)
Related: https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/
Closes: https://github.com/coreos/coreos-installer/issues/13341 parent d8c6a21 commit a52d6f0
2 files changed
+3
-2
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
11 | 11 | | |
12 | 12 | | |
13 | 13 | | |
| 14 | + | |
14 | 15 | | |
15 | 16 | | |
16 | 17 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
2 | 2 | | |
3 | 3 | | |
4 | | - | |
5 | | - | |
| 4 | + | |
| 5 | + | |
6 | 6 | | |
7 | 7 | | |
8 | 8 | | |
| |||
0 commit comments