Birbla

Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

Sign in
  • Hacker News
  • Thanks for sharing, saving this for when I get a DGX Spark
    by haunter
  • This is incredible. I have a Jetson lying around and will try to it out on this. I use it to play with vision models, not LLMs, and have been wanting a better way to manage the machine.
    by thenobsta
  • you probably want this if you have a jetson vs this spark repo:

    https://github.com/anduril/jetpack-nixos

    by reasonabl_human
  • Huge plus to anyone interested in the space to check out what Graham built here!

    If anyone is also interested on Nix/CUDA/Capital Markets/Flox, we recently did another case study in the space - https://flox.dev/blog/deploying-hardened-flox-nvidia-cuda-st...

    by ronef
  • There is also a microvm.nix project which helped us support sandboxes with firecracker. So, whole ai workflow pipeline can now be nixos.
    by mkagenius
  • This has been amazingly helpful for managing my DGX Spark! Thank you for all your time and effort into this project!
    by nixie-tubes
  • Good to hear, thanks!
    by graham33
  • Been running this on a few Asus GX10 machines with k3s on top, it’s been great. I’m running the new deepseek.

    Thank you for your work!

    by redrove
  • i also used nixos as the base, but i went a little overboard with it, this is 7.1.2 supporting all devices and a custom driver that fixes the UMA page leak issues, and the wallpapers are all kernels at or above parity with what you can get out of the box.

    i'm not quite ready to OSS the whole thing, it's got a few rough edges, but if anyone wants to alpha test, caveat emptor and it's yours.

    https://www.youtube.com/shorts/mCUZ9XHIogw

    by reinitctxoffset
  • What quant are you using, and what tps are you getting with K3?
    by pixelesque
  • Just curious, has suspend (to RAM) been working for you?

    For me the nvidia driver just keeps waking up the system instantly - but my setup is deviating from the upstream flake in a few ways, so I'm just wondering if it's worth setting up the system from scratch if it's working for other people.

    Other than that, can fully second that the flake is working great. Only gotcha is that CUDA-enabled packages (including Firefox) require using the flox binary cache unless you want to compile them from source, but then the package versions can lag behind a bit (and debugging nix cache issues is surprisingly difficult).

    by neobrain
  • Slightly off topic, but Claude Code (and likely other models/harnesses) are incredibly effective at Nix. It can trivially self-verify, without side effects, which is a perfect match for an LLM.

    If you've ever been put off by the difficulty of the language, it's worth checking it out again with AI assistance.

    by hamandcheese
  • Agreed, Claude has helped a lot with this project, and being able to iterate without side effects for system configuration changes is really a game changer for agents.
    by graham33
  • This. One of the surprising delights of coding models has been trivially reworking my homelab into proxmox and nixos. It's a very good testable, repeatable flow for LLMs.
    by glaslong
  • I also love how with the right system prompt they can pull in tooling for what they currently need via a nix shell
    by Loeffelmann
  • Same for Bazel. It has historically been a very difficult to understand/adopt/rollout tool for a lot of engineering orgs but is going swimmingly for the organization I currently work for.
    by mbo
  • I set up my homelab server running NixOS entirely using Claude and what would have likely taken me months (if not years) doing it the old fashioned way, got reduced to a few hours of back and forth iteration.
    by sohrob
  • I got curious one Saturday and ported our monorepo to use Nix for build and test and release. It was a very pleasant process. I had to put aside to tackle more pressing things but I'm all in on using Nix in that capacity.
    by aomix
  • And to add to that, LLMs start with fresh context on each conversation, so they don't have the understanding of your system that human employees do. Nix lets you naturally encode that understanding in code (and in comments), making sure it never drifts from what the state of the system really is.

    I never saw much point in Nix, but if you put it like that... now I want to try.

    by miki123211
  • Absolutely. Running NixOS is a wonderful experience for this reason. NixOS + LLMs make it a breeze to make changes to your system, install and configure new software, and debug issues. Having every aspect of your system defined in a git repo is the perfect fit for agent harnesses.

    I'll admit, even with LLMs to help, the Nix language and NixOS did have a rather steep learning curve, because it's quite different from anything I'd experienced before. But after getting the hang of it, I can't imagine going back to a "normal" OS and I'm very happy I put in the time to get over the initial friction.

    by HellsMaddy