Sender | Message | Time |
---|---|---|
13 Apr 2025 | ||
Great, thanks a lot, I'll try that! However I still think it'd be somehow more elegant to have a NixOS base image. Not? Is that too hard to do for some reason? | 09:23:31 | |
For sure, but infect is easier and I’m lazy | 09:25:04 | |
;) | 09:26:18 | |
There’s also another tool called nixos anywhere which can do partitioning aswell | 09:26:21 | |
Cool, thanks for the hints, they'll probably give me a lot more tinkering pleasure ;) | 09:27:29 | |
Sure thing!🌞 | 09:30:05 | |
In reply to @dish1892:matrix.orgusing this for all my servers cause it can do partitioning & formatting. also has an easy way to upload ssh host keys so agenix works on first boot | 11:39:30 | |
15 Apr 2025 | ||
I proposed adding a reboot subcommand to colmena to see what people think about the idea. If you have thoughts, please share them here or on the issue. Thanks! | 16:13:43 | |
Hey there! The nixos-infect works quite nicely, thanks again! Now when I try to apply to the aarch64-linux node from my aarch64-darwin using colnema (using deployment.buildOnTarget), it will somehow not "activate the profile". I don't quite get what that means :-/ I tried: colmena apply --reboot --force-replace-unknown-profiles I get: failure) Unexpected active profile: Profile(StorePath("/nix/store/0pi9dwfl661k77k8zvacz1h7ikj2hlsi-nixos-system-arm-1-24.11.716947.26d499fc9f1d")) Any ideas? Maybe this is a noob-trap? If I run without "--force-replace-unknown-profiles" then it will reboot, but none of my changes seems to get applied. | 16:49:24 | |
* Hey there! The nixos-infect works quite nicely, thanks again! Now when I try to apply to the aarch64-linux node from my aarch64-darwin using colnema (using deployment.buildOnTarget), it will somehow not "activate the profile". I don't quite get what that means :-/ I tried: colmena apply --reboot --force-replace-unknown-profiles I get: failure) Unexpected active profile: Profile(StorePath("/nix/store/0pi9dwfl661k77k8zvacz1h7ikj2hlsi-nixos-system-arm-1-24.11.716947.26d499fc9f1d")) Any ideas? Maybe this is a noob-trap? If I run without "--reboot" then colmena will finish without errors, but none of my changes seems to get applied. | 16:58:29 | |
In reply to @ststefa:matrix.orgShouldn’t matter but try set the ”replace unknown profile” setting in the config instead | 18:13:00 | |
In reply to @gmacon:matrix.orgIf i understand it right you want to run pre-apply commands? | 18:15:33 | |
In reply to @ststefa:matrix.org* | 18:17:26 | |
I don't think so... Did you have something specific in mind for a pre-apply command? | 18:17:43 | |
My intention was just to configure the remote with some packages and settings. | 18:36:14 | |
If I may, I could post my flake.nix | 18:36:29 | |
* Hey there! The nixos-infect works quite nicely, thanks again!
Now when I try to apply to the aarch64-linux node from my aarch64-darwin using colnema (using deployment.buildOnTarget), it will somehow not "activate the profile".
I don't quite get what that means :-/
Any ideas? Maybe this is a noob-trap? If I run without "--reboot" then colmena will finish without errors, but none of my changes seems to get applied. | 18:40:57 | |
* Hey there! The nixos-infect works quite nicely, thanks again!
Now when I try to apply to the aarch64-linux node from my aarch64-darwin using colnema (using deployment.buildOnTarget), it will somehow not "activate the profile".
I don't quite get what that means :-/ Any ideas? Maybe this is a noob-trap? If I run without "--reboot" then colmena will finish without errors, but none of my changes seems to get applied. | 18:41:30 | |
Ah, I think I'm a step closer. After the apply, sshd gets killed on the remote. But if I try a command which I declared in colmena (using a console), it's available. However, after a reboot, everything is back to the state before colmena ran. Looks like the new profile is somehow not set as the active profile? | 18:57:42 | |
Hm, is grub somehow hardcoded in colmena? Asking because I did my experiments with systemd-boot systems | 19:17:29 | |
Ah, I think I did a mess with systemd-boot (on the system) vs. grub (in my flake) | 19:31:07 | |
Did you use the hardware-config.nix from the system where you installed nix on? (With nixinfect) | 19:54:33 | |
No, I didn‘t grasp that the colmena deployment process is entirely unrelated to the „nixos-rebuild approach. Now that makes sense. But it also means that I should somehow collect the /etc/nixos/configuration.nix plus imported files and base my colmenas input on that, no? Is there maybe a clever workflow to do that? Or is there a better approach? | 21:04:12 | |
My goal would be to build a fully automated workflow which is agnostic to any pre-existing state/config | 21:09:14 | |
16 Apr 2025 | ||
i can build this configuration with
… while evaluating the module argument `inputs' | 22:21:50 | |
* i can build this nixos host configuration with
… while evaluating the module argument `inputs' | 22:22:00 | |
18 Apr 2025 | ||
18:03:45 | ||
19 Apr 2025 | ||
17:36:43 | ||
20 Apr 2025 | ||
20:22:14 | ||
21 Apr 2025 | ||
10:24:43 |