| 17 Oct 2025 |
 lillecarl | * Woooo! I've even deployed nix-csi on an external cluster today so I know the images work 😄 Thanks! | 15:05:19 |
 Claes | what I think I would need to wrap my head around it would be some diagram to illustrate how it works together with k8s nodes, pods, deployments | 15:05:41 |
| lillecarl | Soon ™️! I've still got bugs to fix with the garbage collector 😸 | 15:08:04 |
| lillecarl | * Soon ™️! I've still got bugs to fix with the garbage collector 😸 Then there will be docs | 15:08:17 |
| lillecarl | (I need to import the nix database from the containerimage that's bootstrapping the DaemonSet CSI every time the container starts since the image could change and reference new storePaths. Goshdarn state always being a b-word | 15:11:36 |
| lillecarl | fixed! 😄 | 15:46:03 |
| lillecarl | https://github.com/Lillecarl/nix-csi/commit/accb7b86d3c41f17bee9d45816d910545b403ef9 | 15:48:07 |
| lillecarl | (Setup "fakeNss") in the init container so we can run nix_init_db which merges the statefulset database with the one from the image. Same command that's used to initialize nixdb for the CSI /nix volumes 😄 | 15:51:37 |
| 18 Oct 2025 |
| lillecarl | This works now 😄 | 12:24:28 |
| 20 Oct 2025 |
|  monotux joined the room. | 12:03:04 |
| lillecarl | Does anyone else have the struggle that they built a lot of their NixOS configuration when they were too stupid to do so properly but it keeps working and you're too lazy to do something about it? 😆 | 15:31:22 |
 markuskowa | Yep, got a lot of legacy config and luckily they are still working great. | 15:32:44 |
| lillecarl | My entire thing is a goshdarn mess. I was gaslit by "statix" back in the days that repeating attribute keys are an antipattern and should be avoided, group everything under systemd= or whatever. Also statix doesn't understand shadowing bindings with multiple let blocks. I don't use statix anymore 💩 | 15:34:58 |
| 21 Oct 2025 |
| Claes | Mine isn't too bad. I have been aware of the worst parts and tried to fix them over time, as I learn more. Perhaps it is quite primitive in some ways but that has its advantages too | 06:54:03 |
| lillecarl | https://nixos.org/branding/ I think the O looks unproportionally huge somehow in this new branding package #bikeshed | 10:31:41 |
| markuskowa | That's the wow factor: Nix"Oh"S | 10:47:28 |
|  xin joined the room. | 20:40:12 |
| 22 Oct 2025 |
| lillecarl | "I couldn't sleep" AKA I just implemented running Nix builds in Kubernetes jobs instead of in the DaemonSet. Only partially true because it'll talk to the Nix daemon in the DaemonSet but it can be any node in the cluster, node is selected by label nix.csi/builder but also prioritizes Kubernetes.io/hostname that's the same as the node requesting the build 😄 | 02:51:34 |
| monotux | where do store the artifacts? pvc or s3 or..? | 08:20:24 |
| lillecarl | monotux: The Job reuses the hostPath mount of the CSI (/var/lib/nix-csi/nix) as an optimization, the default labelselector prioritizes building on the node selected to run the pod but if it can't it must go to a binary cache, I didn't finish that bit yet. I did implement an in-cluster cache using openssh and nix-store-ng but the idea is that you'll be able to supply your own build script and upload script along with your own nix.conf to choose where artifacts go yourself so you'll be able to use nix copy, cachix, attic or any other solution (soon ™️) 😄
The initial "paved path" will be the in-cluster nix-store-ng that stores the entire cache on a PVC of your choosing, that bit is implemented within the CSI as an async task running after volume is mounted but I haven't thought made the final decision for where the uploads should happen "in the future". I don't want to upload in the build job since it'll stall volume creation for longer.
The jobs source a build script from a ConfigMap that you can edit, so you can already do the upload in there by overriding the build script to both build and upload 😄
I THINK i'll settle on doing uploads in separate jobs that has the node picked as the same one who ran the build, it's very fast enough to create that run with a scratch image that's already cached and reuse the same hostPath mounted store for that operation too. | 10:25:27 |
| lillecarl | Short answer: It'll be your choice eventually 😄 | 10:25:41 |
| monotux | I'm still just building locally on each machine like a caveman, I should look into something better for my pi's i | 10:28:22 |
| monotux | Last time I needed something robust on a rpi I went with alpine Linux running memory semi-immutable | 10:29:13 |
| lillecarl | I haven't tried out S3 caching yet but it seems simple enough for a private cache, you set object lifetime to a month and sign the packages before you ship 😄 | 10:33:00 |
 I use NixOS btw | Yo is it meetup today? | 10:54:34 |
| lillecarl | In reply to @ahbk:matrix.org
Yo is it meetup today? Yes! | 12:53:30 |
| I use NixOS btw | When and where? | 12:54:14 |
| lillecarl | @room time for meet-up today, same place, same time [forum post](https://discourse.nixos.org/t/nix-meetup-in-stockholm-sweden/32867/70)! See you there 🤩 | 13:03:21 |
| lillecarl | * @room time for meet-up today, same place, same time [forum post](https://discourse.nixos.org/t/nix-meetup-in-stockholm-sweden/32867/70) ! See you there 🤩 | 13:03:43 |
| lillecarl | * @room time for meet-up today, same place, same time https://discourse.nixos.org/t/nix-meetup-in-stockholm-sweden/32867/70 See you there! 🤩 | 13:05:00 |
