Colmena - Public Room Timeline

	Colmena	290 Members
	A simple, stateless NixOS deployment tool - https://github.com/zhaofengli/colmena	99 Servers

Load older messages

Sender	Message	Time
14 Jan 2022
Buckley	FWIW, I have not fully looked into the performance implications of doing it this way. Some quick testing indicated that there may be a slight penalty for doing it that way, since its sort of building the systems twice.	22:29:08
Buckley	my (non-scientific) test indicated that doing it this way takes 36 seconds to build, whereas doing it the "normal' colmena way takes 32 seconds	22:30:09
Buckley	small enough that I called it "good enough" and didnt really test further	22:30:42
Zhaofeng Li	The main problem with this is that you cannot take advantage of the `name` and `nodes` module arguments without breaking `nixosConfigurations`	22:31:09
Buckley	there is that. although you can overlay nixosConfigurations and then you can call `pkgs.nixosConfigurations.<node>.config.whatever`	22:32:46
Buckley	* there is that. although you can overlay nixosConfigurations and then you can call `pkgs.nixosConfigurations.<node>.config.whatever` from machine configs	22:33:00
Buckley	I'm just too used to being able to poke around my configs with a repl to give it up :)	22:34:32
Naota	In reply to @zhaofeng:zhaofeng.li The main problem with this is that you cannot take advantage of the `name` and `nodes` module arguments without breaking `nixosConfigurations` My setup is relatively simple so this is not an issue for me.	22:34:49
Naota	I am trying out flake-utils-plus, but was struggling to workout how to integrate that with Colmena.	22:39:51
Naota	I was initially using `deploy-rs`, in which case it's dead simple. But it doesn't support `buildOnTarget` like Colmena.	22:42:00
Buckley	What we’re you trying to actually do with utils?	23:05:20
15 Jan 2022
Naota	I'm trying out using `mkFlake` from FUP to define my set of hosts. I'm taking advantage of `hostDefaults`, `sharedOverlays` in generating my system configurations. So I was trying to work out a clean way to use the output of `mkFlake` in colmena (or nixops or morph).	00:05:45
angerman	After yet another nixops failure, I've tried colmena, but I'm stuck due to nix being killed? [INFO ] Enumerating nodes... [INFO ] Selected all 1 nodes. helios64 \| Evaluating helios64 helios64 \| trace: warning: The following Nixpkgs configuration keys set in meta.nixpkgs will be ignored: allowBroken allowUnsupportedSystem helios64 \| Evaluation failed: Nix was killed by signal 11 \| Failed: Nix was killed by signal 11 [ERROR] Failed to complete requested operation - Last 1 lines of logs: [ERROR] failure) Nix was killed by signal 11 [ERROR] Failed to evaluate helios64 - Last 4 lines of logs: [ERROR] created) [ERROR] state) Running [ERROR] stderr) trace: warning: The following Nixpkgs configuration keys set in meta.nixpkgs will be ignored: allowBroken allowUnsupportedSystem [ERROR] failure) Nix was killed by signal 11 [ERROR] ----- [ERROR] Operation failed with error: Nix was killed by signal 11 how do I debug what's going on here	09:29:33
angerman	I'm trying to build for aarch64-linux, on macOS. I do have a aarch64-linux builder in my machines file.	09:32:30
	Mick joined the room.	10:27:46
Zhaofeng Li	In reply to @angerman:matrix.org After yet another nixops failure, I've tried colmena, but I'm stuck due to nix being killed? [INFO ] Enumerating nodes... [INFO ] Selected all 1 nodes. helios64 \| Evaluating helios64 helios64 \| trace: warning: The following Nixpkgs configuration keys set in meta.nixpkgs will be ignored: allowBroken allowUnsupportedSystem helios64 \| Evaluation failed: Nix was killed by signal 11 \| Failed: Nix was killed by signal 11 [ERROR] Failed to complete requested operation - Last 1 lines of logs: [ERROR] failure) Nix was killed by signal 11 [ERROR] Failed to evaluate helios64 - Last 4 lines of logs: [ERROR] created) [ERROR] state) Running [ERROR] stderr) trace: warning: The following Nixpkgs configuration keys set in meta.nixpkgs will be ignored: allowBroken allowUnsupportedSystem [ERROR] failure) Nix was killed by signal 11 [ERROR] ----- [ERROR] Operation failed with error: Nix was killed by signal 11 how do I debug what's going on here Interesting, 11 is a segfault. What Nix version are you running?	12:39:34
angerman	I’ll check in a bit.	12:46:36
angerman	There is no way to see the raw nix commands Coleman is calling?	12:47:02
Zhaofeng Li	In reply to @angerman:matrix.org There is no way to see the raw nix commands Coleman is calling? Not at the moment and I really should add a bunch of debug prints. You can manually evaluate from the repo with `nix-instantiate -E 'let eval = import ./src/nix/hive/eval.nix; hive = eval { rawHive = import ./path/to/your/hive.nix; }; in hive.nodes.helios64.config.system.build.toplevel'`	12:53:51
angerman	Zhaofeng Li: what I did try was `-v2` but there seem to be no verbosity levels.	13:34:24
angerman	If I run `NIX_PATH=nixpkgs=https://github.com/NixOs/nixpkgs/archive/nixpkgs-21.11-darwin.tar.gz colmena build` I get [INFO ] Using configuration: /Users/angerman/Projects/zw3rk/nixos-docker-sd-image-builder/hive.nix [INFO ] Enumerating nodes... error: The option `services.getty' defined in `/nix/store/c39y3z66vmr5q152998wymdi0zk7q8hh-source/nixos/modules/profiles/installation-device.nix' does not exist. (use '--show-trace' to show detailed location information) [ERROR] ----- [ERROR] Operation failed with error: Nix exited with error code: 1	13:34:54
angerman	If I run it with the same pin I set in the meta.nixpkgs attribute I get the segfault. The pin is from 20.09 or so, so somewhat older.	13:35:43
angerman	I'm not sure how that service.getty is getting in there though.	13:36:07

There are no newer messages yet.

Back to Room ListRoom Version: 6