In reply to @zsuper:matrix.org
and disko will still take care of formatting for you right? because thats the main part about minimal installers that im still uncomfortable with

im thinking of making the switch to colmena soon, but seeing the use of the function colmena.lib.mkHive worries me. will i still be able to access the raw nixosConfiguration closure in the flake's outputs?

the reason i ask is because nixos-anywhere reads nixosConfigurations.<name> when remote installing to a new machine, and id like to write the spec for each node/machine once in the flake and then have its NixOS configuration attribute set accessible

for example, with deploy-rs right now, i managed to write a helper function that allows me to define nodes like:

{
    deploy = {
      user = "root";
      sshUser = "root";
      nodes = self.armada.mkNodes {
        thinkpad = {
          hostname = "10.0.0.162";
          system = "x86_64-linux";
          modules = [
            ./modules/mc-server-host
            ./modules/cluster-server
            ./modules/starfish
          ];
        };
        t5 = {
          hostname = "10.0.0.249";
          system = "x86_64-linux";
          modules = [
            ./modules/cluster-agent
            ./modules/adguardhome
          ];
        };
        t4 = {
          hostname = "10.0.0.23";
          system = "x86_64-linux";
          modules = [
            ./modules/cluster-agent
          ];
        };
      };
    };

but this simply passes the inner arguments to lib.nixosSystem, which in turn gets passed to deploy.nodes.<name>.profiles.system.path. So this means I cannot access the "config" of thinkpad, for example

I'm having trouble deploying from amd64 to an arm64 machine. Seems like colmena build --on kaldir --build-on-target ignores both --build-on-target and colmena.kaldir.deployment.buildOnTarget properties. Any hints what could cause this?

error: a 'aarch64-linux' with features {} is required to build '/nix/store/7qk9db8vr6hkav0q3hkdbd742dz70zd3-cabal2nix-arion-compose.drv', but I am a 'x86_64-linux' with features {benchmark, big-parallel, kvm, nixos-test, uid-range}