Stockholm NixOS meetup group | 49 Members | |
| Monthly meetups in Stockholm, Sweden around Nix releated topics(nixos.org) | 14 Servers |
| Sender | Message | Time |
|---|---|---|
| 1 Sep 2025 | ||
| The GC could do with a bit more "intelligence". The current one is honestly dumb as WORDS | 19:58:17 | |
| 2 Sep 2025 | ||
| Are any of you coming to nixcon? :) | 14:21:03 | |
| not me | 14:32:04 | |
| I have to skip this year unfortunately. | 14:50:00 | |
| 14 Sep 2025 | ||
| 08:39:46 | ||
| 17:36:41 | ||
| 16 Sep 2025 | ||
| markuskowa: I notice you haven't scheduled a next meetup ;) | 16:03:36 | |
In reply to @lillecarl:matrix.orgYou got me π« . It was quite busy. What about Tuesday 30th of September? | 16:08:11 | |
| Sounds good to me! π | 16:11:59 | |
| Redacted or Malformed Event | 17:26:06 | |
| We were alternating between Tuesday and Wednesday to make it the decision easier. | 18:15:49 | |
| 18 Sep 2025 | ||
| https://github.com/Lillecarl/dinix I wrote a little thing that generates dinit (the init system) configuration from Nix (using the module system). Dinit is VERY light, the overhead is ~4MB RAM and "no CPU". This enables writing OS and init independent "service collections". It can run as pid1 in Linux (but don't try this), pid1 in containers (reaps zombies and such) or random pid in user mode where it's just a process supervisor. Also works on MacOS (I don't have a Mac machine so I can't verify though). So you could create a service collection with nginx, postgres, whatever and run it from a single nix command. You could even run dinit from a systemd unit if you'd want. So you can run the same service collection from: Containers, Systemd, commandline and Nix brings the executables π Here's an example nginx module that runs on 8080 and presents "Hello World" https://github.com/Lillecarl/dinix/blob/main/config.nix | 06:57:54 | |
| * https://github.com/Lillecarl/dinix I wrote a little thing that generates dinit (the init system) configuration from Nix (using the module system). Dinit is VERY light, the overhead is ~4MB RAM and "no CPU". This enables writing OS and init independent "service collections". It can run as pid1 in Linux (but don't try this), pid1 in containers (reaps zombies and such) or random pid in user mode where it's just a process supervisor. Also works on MacOS (I don't have a Mac machine so I can't verify though). So you could create a service collection with nginx, postgres, whatever and run it from a single nix command. You could even run dinit from a systemd unit if you'd want. So you can run the same service collection from: Containers, Systemd, commandline and Nix brings the executables π Here's an example nginx module that runs on 8080 and presents "Hello World" https://github.com/Lillecarl/dinix/blob/main/config.nix Edit:
| 07:19:54 | |
| * https://github.com/Lillecarl/dinix I wrote a little thing that generates dinit (the init system) configuration from Nix (using the module system). Dinit is VERY light, the overhead is ~4MB RAM and "no CPU". This enables writing OS and init independent "service collections". It can run as pid1 in Linux (but don't try this), pid1 in containers (reaps zombies and such) or random pid in user mode where it's just a process supervisor. Also works on MacOS (I don't have a Mac machine so I can't verify though). So you could create a service collection with nginx, postgres, whatever and run it from a single nix command. You could even run dinit from a systemd unit if you'd want. So you can run the same service collection from: Containers, Systemd, commandline and Nix brings the executables π Here's an example nginx module that runs on 8080 and presents "Hello World" https://github.com/Lillecarl/dinix/blob/main/config.nix Edit:
| 07:20:26 | |
| * https://github.com/Lillecarl/dinix I wrote a little thing that generates dinit (the init system) configuration from Nix (using the module system). Dinit is VERY light, the overhead is ~4MB RAM and "no CPU". This enables writing OS and init independent "service collections". It can run as pid1 in Linux (but don't try this), pid1 in containers (reaps zombies and such) or random pid in user mode where it's just a process supervisor. Also works on MacOS (I don't have a Mac machine so I can't verify though). So you could create a service collection with nginx, postgres, whatever and run it from a single nix command. You could even run dinit from a systemd unit if you'd want. So you can run the same service collection from: Containers, Systemd, commandline and Nix brings the executables π Here's an example nginx module that runs on 8080 and presents "Hello World" https://github.com/Lillecarl/dinix/blob/main/config.nix Edit:
| 07:20:37 | |
| If the generation of config files would be reusable (I.e. separated in the module system), we could reuse them for dinix, or container image generation. | 09:37:16 | |
| Hi, all! I am currently trying to build a stateless cluster using Nixos. The main thing is that I want all things to be wiped on each boot. The idea is to have one management node serving an ipxe image over pxe, a kernel, and an initrd. The ipxe would pull the kernel and initrd, which would then torrent a root tarball, extract it, and kexec/switch_root into it. Does anyone have an idea where to even start with this? I did try nix-generators for the root kexec tarball, but that doesn't seem to work well when you already have a /nix in root already... Any suggestions would be most appreciated! :) | 10:45:05 | |
In reply to @markuskowa:matrix.orgYep, reusable across local dev and in containers, but also if someone makes a dinix module for the "LAMP" stack we could easily stick it into systemd on a VM of your choice | 13:23:30 | |
In reply to @kacper.uminski:matrix.orgSounds like you've made a few "too many" decisions already. I couldn't help you, I would probably try to make a nixos iPXE image and make the iPXE server a nix build cache instead, build new images when you need new systemd or kernel | 13:25:57 | |
| nixos-anywhere does the kexec thing already work to install nixos over "any" Linux distro, so you could investigate their thing. If you wanna use nix, use nix :p torrents don't belong in Nix (even though they map well to the store immutability) | 13:27:19 | |
| Maybe some simple stuff that could work is to setup syncthing on the nixos machine such that when itβs brought up it downloads P2P all the state of the machine | 13:29:39 | |
| https://github.com/markuskowa/nix-system/blob/master/modules%2Fkea.nix Kacper Uminski: you can generate pxe capable image directly with nixos (see my example above) | 13:30:05 | |
| (ask in #users:nixos.org too, we're a small community) | 13:31:26 | |
In reply to @markuskowa:matrix.orgI love you man! β€οΈβ€οΈπ | 13:32:00 | |
In reply to @julienmalka:matrix.orgYes, let nix do the nixy bits, how you manage state is free-for-all π | 13:33:14 | |
| Yes, I realize the idea is quite cursed. The main idea is to minimize stress on the control node, so a centralized cache or pxe server for the full filesystem is a no-no. All filesystems have to be reformatted on reboot, including /nix/store. We already have a setup like this working with Debian, but it's hacked together using shell-scripts, python, and preseed files. Hence I am investigating alternatives. :) | 13:35:28 | |
| Thanks! I will investigate this, at least for the minimal bootup. :) | 13:36:27 | |
| @kacper.uminski:matrix.org: do you work for a VPN company perhaps? π | 13:37:46 | |