Sender | Message | Time |
---|---|---|
7 Aug 2024 | ||
10:07:26 | ||
20:54:48 | ||
if anyone has any experience with flake-utils or trying to make a colmena flake work on multiple architectures, please let me know! https://github.com/zhaofengli/colmena/issues/221 | 21:23:24 | |
8 Aug 2024 | ||
01:27:22 | ||
In reply to @dazai:matrix.orgI'm sorry I don't see your specific issue but you may want to look into: https://flake.parts/ https://std.divnix.com/ and eventually https://github.com/divnix/hive | 15:15:40 | |
I'm using hive and have colmena building x86_64-linux, aarch64-linux, and aarch64-darwin. | 15:16:41 | |
15:57:47 | ||
hey folks, does colmena supports auto rollback on failure? | 15:58:27 | |
I haven't seen anything like --magic-rollback in deploy-rs , but I also don't think I've needed it. | 16:12:27 | |
hanleym: so if i'm running colmena apply does it not matter whether x86_64-linux or aarch64-linux is defined for nixpkgs? like can it be in my flake:meta.nixpkgs = import nixpkgs { system = "x86_64" }; even if i'm running colmena apply on an aarch64 machine? | 18:56:56 | |
i guess my question is how can i run colmena apply, with the same flake on both aarch64 and x86_64 | 18:57:25 | |
* hanleym: so if i'm running colmena apply does it not matter whether x86_64-linux or aarch64-linux is defined for nixpkgs? like can it be in my flake:meta.nixpkgs = import nixpkgs { system = "x86_64-linux" }; even if i'm running colmena apply on an aarch64 machine? | 18:58:04 | |
right now i just have 2 copies of my flake that i maintain with the only difference being meta.nixpkgs being set to that system's architecture | 18:58:26 | |
also sometime magic rollback is annoying, sometimes networkmanager fails to restart for no reason | 18:59:15 | |
dazai: this is how you would do it: https://colmena.cli.rs/unstable/examples/multi-arch.html | 19:18:15 | |
In reply to @dazai:matrix.orgI think this was finally fixed. | 19:18:50 | |
I disabled my hotfix for that a few weeks ago and it has been working. | 19:19:39 | |
hanleym: that page only shows how to build remotely on target, or how to cross build from x86_64 to aarch64. I have an aarch64 deployment server and a x86_64 deployment server that I want to deploy natively from, but with the same flake file | 19:23:43 | |
I don't want to build on target since I don't want builds to interrupt my production services | 19:24:07 | |
also good to know that that was finally fixed it was annoying me haha | 19:24:29 | |
https://colmena.cli.rs/unstable/reference/deployment.html#deploymentbuildontarget | 19:24:54 | |
Set that to false and it will build on the host. | 19:25:08 | |
That should be the default though. | 19:25:48 | |
dazai: ^ | 19:27:55 | |
yeah I know but i still need to specify architecture for colmena.meta.nixpkgs right? | 19:28:32 | |
https://colmena.cli.rs/unstable/tutorial/flakes.html | 19:28:56 | |
in the flake tutorial it has this
meaning i have to change my flake depending what machine i'm deploying on, does that make sense? | 19:29:24 | |
In reply to @hanleym:matrix.org IIRC the boot counting feature was recently comitted to nixpkgs. I havent checked it in detail, but my understanding was that it allows you doing automated rollbacks (at least) if boot fail. Not sure if that's what you had in mind? | 19:50:45 | |
In reply to @dazai:matrix.org interestimg issue 🤔 Essentially you would need to figure out the architecture of the system colmena/nix is running on and use that in the import statement. | 19:56:29 | |
* interestimg issue 🤔 I might have a similar one when I get my rpis... Essentially you would need to figure out the architecture of the system colmena/nix is running on and use that in the import statement. me trying to rephrase the problem.for clarity... | 19:57:02 |