| 5 Apr 2026 |
 magic_rb | Really? Id expect that to not be the case since the mac should be stable, so id expect the router to hand back the same ip | 22:45:11 |
| magic_rb | Though i havent tested this | 22:45:18 |
| magic_rb | But ig the router can just decide to give back another one cause why the fuck not. Not sure if anything can really done about that | 22:45:54 |
 Chris P Bacon | Depends on how the dhcp server and client handle the lease. | 22:46:50 |
| magic_rb | Well id expect the lease to last :P but ig not | 22:47:09 |
| magic_rb | I do wonder why the servers switching ips is a problem and if it is a problem, why are they using dhcp with non-static leases at all | 22:47:53 |
| Chris P Bacon | But, why not disable dhcp if you want static adresses? | 22:47:59 |
| magic_rb | That seems like relying on finicky behavior | 22:48:06 |
| magic_rb | Yeah exactly my point, or just static leases. But somehow pin the damn thing | 22:48:23 |
| magic_rb | There are 3 options imo:
- Dont use dhcp
- Use static leases
- Build a overlay network
Anything else will be finicky
| 22:50:29 |
| 6 Apr 2026 |
|  @haruki7049:matrix.org left the room. | 09:42:52 |
 Eli Saado | then machine onboarding is still clunky since you'd have to manually assign an ip adress either:
- on the routers side using the MAC (pretty clean) and then still use DHCP with that static DHCP allocation (but not all routers support this and you'd need to log in to your router each time)
- or on the machine during the installation and enable an option in the NixOS config to make that same IP adress also it's IP after installation
| 09:57:54 |
| Eli Saado | having an overlay network is nice but you'd still need to bootstrap it (and have ways around it when you're messing with its options and it restarts during a rebuild or whateverK | 09:58:36 |
| Eli Saado | * | 09:58:40 |
| Eli Saado | I'm going to experiment some more tonight, have to study for an exam first :S | 09:58:58 |
| Eli Saado changed their profile picture. | 10:36:18 |
| Eli Saado changed their profile picture. | 10:42:14 |
| Eli Saado changed their profile picture. | 11:03:14 |
| Eli Saado changed their profile picture. | 11:04:08 |
| Eli Saado changed their profile picture. | 11:05:02 |
| 7 Apr 2026 |
|  @oleg20082009:matrix.org joined the room. | 21:17:34 |
| @oleg20082009:matrix.org left the room. | 21:38:35 |
| 8 Apr 2026 |
|  johnhamelink joined the room. | 07:31:59 |
| johnhamelink | Hey folks, I wrote a nix flake for https://crowci.dev/ (a woodpeckerCI fork). My flake uses podman quadlets using quadlet-nix. I'm coming across an issue when building that I'm hoping someone might be able to shed light on: when an agent (runner) container runs nix build, it seems to be able to surpass resource restrictions set in the quadlet configuration (using PodmanArgs). The result is that long builds get OOM killed. What I really want is for the container to be constrained to its resource requirements. My /etc/containers/systemd container configuration (generated by quadlet-nix) looks like this: https://gist.github.com/johnhamelink/80995130d2afc1cedee31b501cb3e689 | 07:51:29 |
| johnhamelink | * Hey folks, I wrote a nix flake for https://crowci.dev/ (a woodpeckerCI fork). My flake uses podman quadlets using quadlet-nix. I'm coming across an issue when building that I'm hoping someone might be able to shed light on: when an agent (runner) container runs nix build, it seems to be able to surpass resource restrictions set in the quadlet configuration (using PodmanArgs). The result is that long builds get OOM killed. What I really want is for the container to be constrained to its resource requirements. My /etc/containers/systemd container configuration (generated by quadlet-nix) looks like this: https://gist.github.com/johnhamelink/80995130d2afc1cedee31b501cb3e689
My nix flake is here in case you are interested https://codefloe.com/crowci/crowci-flake
| 07:52:40 |
| johnhamelink | With the above container configuration, you can see here that the nix process run by conmon bursts right past 2G of memory: | 08:50:29 |
| johnhamelink | 
Download screenshot-20260408-09:48:09.png | 08:50:32 |
| johnhamelink | * With the above container configuration, you can see here that the nix process run by conmon bursts right past 2G of memory (PID 133965): | 08:51:09 |
| johnhamelink | 
Download screenshot-20260408-09:51:29.png | 08:52:01 |
| johnhamelink | Meanwhile podman stats shows only 17-19MB of memory usage | 08:52:12 |
