diff options
| author | Dan McArdle <d@nmcardle.com> | 2025-07-27 17:31:09 -0400 |
|---|---|---|
| committer | Dan McArdle <d@nmcardle.com> | 2025-07-27 17:41:34 -0400 |
| commit | 04d17561186dc7a7e8a8fa4fd87e3e5b6220a68f (patch) | |
| tree | adf071ae56896786485c277ca5821c0632493166 /pkgs/development/python-modules/termplotlib/gnuplot-subprocess.patch | |
| parent | 8331663fa9a74927136758a930d278b594cf615d (diff) | |
nixos/vaultwarden: Start after network-online.target
On my system, Vaultwarden fails on boot with an AddrNotAvailable error,
presumably because `services.vaultwarden.config.ROCKET_ADDRESS` is not
available yet.
Here's an example of the startup error in journalctl:
```
Jul 26 21:56:48 banana vaultwarden[2514]: Error: Rocket.
Jul 26 21:56:48 banana vaultwarden[2514]: [CAUSE] Bind(
Jul 26 21:56:48 banana vaultwarden[2514]: Os {
Jul 26 21:56:48 banana vaultwarden[2514]: code: 99,
Jul 26 21:56:48 banana vaultwarden[2514]: kind: AddrNotAvailable,
Jul 26 21:56:48 banana vaultwarden[2514]: message: "Cannot assign requested address",
Jul 26 21:56:48 banana vaultwarden[2514]: },
Jul 26 21:56:48 banana vaultwarden[2514]: )
```
According to systemd docs [1], `network.target` has little meaning
during startup, but `network-online.target` actually waits until an IP
address is available. The docs recommend putting `network-online.target`
in both `After=` and `Wants=`.
[1]: https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/
Diffstat (limited to 'pkgs/development/python-modules/termplotlib/gnuplot-subprocess.patch')
0 files changed, 0 insertions, 0 deletions