 | NixOS systemd | 626 Members |
| NixOS ❤️ systemd | 171 Servers |
| NixOS systemd | 626 Members |
| NixOS ❤️ systemd | 171 Servers |
| Sender | Message | Time |
|---|---|---|
| 2 Oct 2021 | ||
 Arian | Didn't know about nspawn.org | 19:30:38 |
 genofire | which image? | 19:31:31 |
| Arian | Nixos containers are actually systemd-nspawm behind the scenes | 19:31:35 |
| Arian | In reply to @genofire:matrix.sum7.euI don't think we have a system tarball published on the website that works out of the box. Though I suppose you could probably boot the ISO with nspawn? S But we do use nspawn as a building block extensively | 19:32:47 |
| Arian | * I don't think we have a system tarball published on the website that works out of the box. Though I suppose you could probably boot the ISO with nspawn? S But we do use nspawn as a building block extensively for the Nixos containers functionality | 19:32:57 |
| Arian | https://nixos.org/manual/nixos/stable/#ch-containers | 19:33:58 |
| Arian | (but those only work on Nixos not on arch.. so doesn't help you much in this case) | 19:34:14 |
| genofire | 6 years ago, there was one ;( - https://hydra.nixos.org/job/nixos/release-14.12/nixos.system_tarball_pc.x86_64-linux | 19:58:53 |
 moleksiak joined the room. | 20:01:56 | |
| Arian | Wouldn't be too hard to re-add | 20:03:59 |
| genofire | jippie i got an old tar (17.09) which works | 20:13:43 |
| Arian | Feel free to open an issue for that genofire btw | 20:16:19 |
| genofire | sorry, not yet - still exploring | 20:33:20 |
| genofire | found the image here in this issue: https://github.com/NixOS/nixpkgs/issues/9884 | 20:36:09 |
| genofire | another systemd offtopic question - has nixos dropin files like in systemd? (for easy manage by ansible e.g.) | 21:12:42 |
| genofire | okay, nixos make his /nix/store readonly and is not possible to change it afterwards ;( - make it useless for running in container on other distros | 21:17:07 |
| genofire | so i believe it is not possible to run from other nspawn - so maybe i take another maschine and make a zfs send/recv for a nice migration | 21:18:48 |
| Arian | In reply to @genofire:matrix.sum7.euDrop in files youd manage with Nixos configuration syntax as opposed to ansible. Nixos manages files in /etc | 21:21:05 |
| Arian | You can however put dropin in /run if you'd want | 21:21:24 |
| Arian | But I'd advise against writing unit files by hand. You ought to use the Nixos config language for this. Nixos will then place the unit files for you | 21:22:22 |
| Arian | ( Nixos is a competitor to ansible. It's a configuration management tool first and foremost) | 21:22:52 |
| genofire | i do not like to write own unitfiles - i would like to extend existing unit file by a dropin | 21:23:19 |
| genofire | or in systemd-networkd | 21:23:46 |
| genofire | sorry, maybe i just misunderstand nixos on some points | 21:24:17 |
| Arian | you'd use the nixos config syntax for this. e.g. you can extend the nginx service like this: in your configuration.nix and nixos will then create a drop-in file that extends the | 21:25:25 |
| genofire | nice | 21:26:05 |
| genofire | but could i dropin into configuration.nix ? so i deploy my default one an on specifical machines - i add some things? | 21:26:45 |
| Arian | for sure | 21:27:05 |
| Arian | NixOS will merge multiple config files into one if you import them | 21:27:26 |
| genofire | could i create a configuration.nix.d and put there nother .nix file into it? | 21:27:27 |