| 8 May 2022 |
 dantefromhell | In reply to @zhaofeng:zhaofeng.li
When renaming machines, you can override which node apply-local selects with --node. For fresh installs, you need to run the activation script when chrooted into the new root (ex: the external script I linked) and the normal logic doesn't work. Thx for the details. Will check them out ASAP | 11:21:57 |
| 10 May 2022 |
|  andi- left the room. | 18:56:41 |
| 13 May 2022 |
|  snartvellental joined the room. | 08:02:27 |
| snartvellental | hey folks, using colmena with joy, i am using it in CI and was wondering how people cache colmena builds on CI servers? | 08:03:02 |
 Linux Hackerman | snartvellental: you can use a Nix binary cache. Unfortunately there's no stable interface for populating a binary cache currently, but you can put `extra-substituters = file:///path/to/persistent/cache/dir/?trusted=1` in a nix.conf that gets picked up for the build, and use `nix copy --option experimental-features nix-command --all --to file:///path/to/persistent/cache/dir/` at the end of the build | 08:07:35 |
| Linux Hackerman | You can also use some S3-compatible storage rather than local storage if you prefer | 08:08:10 |
| snartvellental | I have played around with cachix in the past, thanks for your message Linux Hackerman , I will have a look :) | 08:08:58 |
| Linux Hackerman | Oh yeah you can use cachix too, but I was assuming that local storage without bandwidth restrictions might be preferable | 08:09:32 |
| Linux Hackerman | Also, sooner or later you're probably going to want to clean the storage up. There's currently no good mechanism for this, the easiest way is to just delete everything, but of course that means everything's gone... | 08:11:35 |
| snartvellental | yeah, then most likely one would resort to S3 with proper lifecycle rules in place | 08:14:19 |
| snartvellental | nix copy sounds like a new command, haven't seen that one | 08:16:20 |
| Linux Hackerman | there used to be nix-push, but that was removed in favour of the unstable nix copy interface 🙃 | 08:36:14 |
| snartvellental | why is nix such a big ocean lol :D sometimes I feel like i've seen 5% or 0,05% | 11:23:03 |
 Buckley | Because nix invites the user to jump into the whole stack and mess around :o | 13:05:35 |
 CRTified | Interesting. I'm currently not at home and tried apply-local for the first time to update my laptop. It fails and claims my machine isn't a NixOS machine 🤔 | 13:48:31 |
 Zhaofeng Li | Which versions of nixpkgs and Colmena? It doesn't look like they changed the format of /etc/os-release again | 18:59:04 |
| 18 May 2022 |
 Jane Jasperous | hi, im configuring my systems using colmente to deploy in my network. I'd like to have some machines running 21.11 others 22.05 other unstable. I get working this for packages, but not for full nixos system (modules,...) | 12:27:06 |
| Jane Jasperous | * hi, im configuring my systems using colmena to deploy in my network. I'd like to have some machines running 21.11 others 22.05 other unstable. I get working this for packages, but not for full nixos system (modules,...) | 12:27:13 |
| Jane Jasperous | i expected declare machines as server1 = inputs.nixpkgs-2305.lib.nixosSystem { (...) | 12:29:26 |
| Jane Jasperous | * i expected declare machines as server1 = inputs.nixpkgs-2205.lib.nixosSystem { (...) | 12:29:35 |
| Jane Jasperous | * i expected declare machines as server1 = inputs.nixpkgs-2205.lib.nixosSystem { (...) to work | 12:29:58 |
 phaer | In reply to @janejasperous:one.ems.host
i expected declare machines as server1 = inputs.nixpkgs-2205.lib.nixosSystem { (...) to work You don't need lib.nixosSystem for colmena, just the config | 15:01:51 |
| phaer | server1 = inputs.nixpkgs-2205.lib.nixosSystem { (...) }.config could also work, i think? But haven't tested this | 15:03:21 |
| CRTified | In reply to @phaer:matrix.org
server1 = inputs.nixpkgs-2205.lib.nixosSystem { (...) }.config could also work, i think? But haven't tested this Kind of - I'm using such a shim to use nixosConfigurations and colmena together: https://github.com/zhaofengli/colmena/issues/60#issuecomment-1047199551 | 15:04:14 |
| phaer | Ah, good to know. I personally just keep my stuff in the nixosModules output of my flake and can then put them into colmena configs for hosts I deploy with colmena or nixosConfigurations as needed | 15:05:44 |
| Jane Jasperous | Effectively im using colmena + nixos-rebuild | 19:57:00 |
| Jane Jasperous | In reply to @phaer:matrix.org
You don't need lib.nixosSystem for colmena, just the config ok that work locally with nixos-rebuild. This piece of code fails becuase overwrite nixpkgs-2205 for nixpkgs | 21:43:00 |
| Jane Jasperous | colmena = {
meta = {
nixpkgs = import nixpkgs { system = "x86_64-linux"; };
specialArgs = { inherit inputs; };
};
} // builtins.mapAttrs (name: value: {
nixpkgs.system = value.config.nixpkgs.system;
imports = value._module.args.modules;
}) (self.nixosConfigurations);
| 21:43:21 |
| Jane Jasperous | In reply to @phaer:matrix.org
You don't need lib.nixosSystem for colmena, just the config * ok that works locally with nixos-rebuild. This piece of code fails makes colmena overwrite nixpkgs-2205 for nixpkgs | 21:43:48 |
| Jane Jasperous | * ok server1 = inputs.nixpkgs-2205.lib.nixosSystem { (...) } that works locally with nixos-rebuild. This piece of code fails makes colmena overwrite nixpkgs-2205 for nixpkgs | 21:44:21 |
