| 8 Feb 2024 |
 aanderse | i can't at the moment, though I'm sure there are a number | 01:28:44 |
 adamcstephens | I’m not sure what the impact to releases is. mkg20001initially created the lxc-container file it seems :) | 01:29:09 |
| aanderse | ah
they would have something useful to say I'm sure
ping mkg20001 ... whenever you have a chance to comment i would greatly appreciate it, specifically why lxc-container.nix is a file to be imported rather than a nixos module | 01:30:57 |
 mkg20001 | the import idea came from qemu doing something similar | 01:33:35 |
| mkg20001 | there's no real reason why it's not just virtualisation.lxc.container-guest.enable = true; or similar | 01:33:57 |
| aanderse | ah so it was precedent based
thank you for the information! | 01:34:22 |
| aanderse | ok so if i were to turn lxc-container.nix into a module i have everyone's support? | 01:35:19 |
| mkg20001 | yes. we can make the file a stub that issues a warning and sets the required options | 01:35:51 |
| aanderse | great
thanks everyone | 01:36:38 |
| adamcstephens | Yes I’m on board. I don’t love the UX of requiring an import from modulesPath | 01:36:48 |
| aanderse | yeah, it is a little bit jarring compared to the rest of the system | 01:37:47 |
| adamcstephens | As mkg mentioned, it’s a common pattern for these profiles, but that doesn’t mean it needs to stay that way | 01:38:54 |
| aanderse | yeah, good point | 01:39:08 |
| aanderse | btw, is anyone using the combination of terraform/opentofu, lxd/incus, and nixos here? | 01:41:27 |
| adamcstephens | I use opentofu with incus (and was using it either lxd too) | 01:44:34 |
| adamcstephens | * I use opentofu with incus (and was using it with lxd too) | 01:46:09 |
| aanderse | how much friction do you find in combing these technologies together?
at work we are using this and the friction has been higher than i would like | 01:46:27 |
| adamcstephens | I would rather not use opentofu if I had a native nix alternative. | 01:47:24 |
| aanderse | you mean like nixops-ish, right? | 01:47:58 |
| adamcstephens | I actually use terranix though so I’m still writing nix code | 01:48:02 |
| aanderse | does terranix integrate nicely? | 01:48:32 |
| adamcstephens | In reply to @aanderse:nixos.dev
you mean like nixops-ish, right? I’ve never used nixops, so I’m not too sure about it | 01:48:42 |
| mkg20001 | nixos-rebuild --flake .#host --target-host root@your-machine is what I use for my machines after they're created | 01:50:24 |
| adamcstephens | I think I envision something like microvm.nix that configures what resources incus should have, but then also doesn’t tightly couple the guest configs to the host | 01:50:43 |
| adamcstephens | I have a homegrown deployment tool but it’s effectively using nixos rebuild target host | 01:51:18 |
| mkg20001 | In reply to @adam:robins.wtf
I think I envision something like microvm.nix that configures what resources incus should have, but then also doesn’t tightly couple the guest configs to the host there is already have the virtualisation.diskSize, etc options from qemu which may be what you want. that could be generalized. | 01:52:01 |
| aanderse | ah | 01:52:12 |
| aanderse | yeah so i found myself needing terraform resource values in my nixos config... but at the same time needing nixos values inside my terraform config | 01:53:15 |
| aanderse | this is something nixops did well | 01:53:32 |
| aanderse | i hacked a little script together and am trying it out for deployments | 01:53:59 |
