 | NixOS systemd | 622 Members |
| NixOS ❤️ systemd | 168 Servers |
| NixOS systemd | 622 Members |
| NixOS ❤️ systemd | 168 Servers |
| Sender | Message | Time |
|---|---|---|
| 15 Oct 2021 | ||
 andi- | That worked for me | 12:50:00 |
| andi- | I've been using that for all the new feeatures I added to networkd on older NixOS | 12:50:14 |
 ajs124 | 🤔 let me check again | 12:50:24 |
| ajs124 | So: assuming that a section cannot be defined twice, which I haven't found a good source for and have not verified, [https://github.com/NixOS/nixpkgs/blob/release-21.05/nixos/modules/system/boot/networkd.nix#L1568] inserts extraConfig all the way at the end.So if you've defined a network unit with the module and need something in the [Network] section, but are also using some of the declarative options, extraConfig cannot be used. | 14:21:33 |
| ajs124 | * So: assuming that a section cannot be defined twice, which I haven't found a good source for and have not verified, this inserts extraConfig all the way at the end.So if you've defined a network unit with the module and need something in the [Network] section, but are also using some of the declarative options, extraConfig cannot be used. | 14:21:47 |
| andi- | why do you say that? It is the same unit logic parsing that is done with regular systemd units. You can have the same section multiple times (e.g. various files) and it'll be merged. A section doesn't really cause any kind of initialization they are just used to group options. | 14:49:32 |
 Xe (xe/they) changed their profile picture. | 19:14:41 | |
 genofire | hmm i also miss option to set properties e.g. CPUQuota and MemoryMax -> this could maybe be part of container(ing) by set it at container@NAME.service ;) | 22:02:01 |
| genofire | or is there any solution? | 22:02:09 |
| 16 Oct 2021 | ||
| andi- | services."container@NAME.service".serviceConfig.CPUQuota = "0": ? | 11:21:02 |
| andi- | * systemd.services."container@NAME.service".serviceConfig.CPUQuota = "0": ? | 11:21:09 |
 Janne Heß | In reply to @andi:kack.itI don't think you need that .service. Or is that different for insantiated units? | 11:22:09 |
| Janne Heß | In reply to @andi:kack.it* I don't think you need that .service. Or is that different for instantiated units? | 11:22:30 |
| andi- | ahh yes ofc | 11:22:30 |
 eyJhb | A annoying thing with netdevs is, that if you remove a netdev config from your configuration, then it will still be active on the server (ie. the device will still be there etc.). Is there a nice way to ensure that if a netdev is removed, it will be destroyed from the server? | 12:14:08 |
| andi- | mhm | 12:14:24 |
| andi- | networkctl reconfigure doesn't discard it? | 12:14:33 |
| andi- | I could see how a restart of networkd wouldnt | 12:14:43 |
| andi- | but perhaps it knows it generated it on reconfigure? | 12:14:55 |
| Janne Heß | ajs124: didn't we have a workaround for that? Or do we just live with the pain? | 12:26:50 |
| eyJhb | In reply to @andi:kack.itUnsure, didn't try that and no longer use the config. As it was quite the pain :/ | 12:30:32 |
| eyJhb | Please do ping me if you had the same issue Janne Heß && ajs124 | 12:30:49 |
| eyJhb | Seems like networking.wireguard is the "better" option for now | 12:35:18 |
| ajs124 | don't remember, tbh | 12:43:09 |
| eyJhb |
| 15:17:27 |
| eyJhb | *
https://www.freedesktop.org/software/systemd/man/networkctl.html | 15:17:45 |
| eyJhb | *
https://www.freedesktop.org/software/systemd/man/networkctl.html
Sadly it doesn't delete anything.... :/ | 15:18:12 |
| 17 Oct 2021 | ||
 mars joined the room. | 18:53:34 | |
| 18 Oct 2021 | ||
| genofire | Is there a better network management for containers in a roadmap, it is really hacky to define localAddress and then two times systemd.networks ... (Why is the privatNetwork not eought) | 14:36:07 |
 Arian | Yes there's an RFC for that | 15:44:59 |