I'd be greateful for some preliminary feedback on these two PRs that go hand in hand:

• https://github.com/divnix/devos/pull/338/commits/fb67fc51cc44ce685f99cbdc40d359cc501d427d
• https://github.com/divnix/digga/pull/84/commits/e2c862ddbec87fe7c2e675ab06c4d50d8800abe0

before I (hopefully) finish those PRs off tonight.

I'd be greateful for some preliminary feedback on these two commits that go hand in hand:

• https://github.com/divnix/devos/pull/338/commits/fb67fc51cc44ce685f99cbdc40d359cc501d427d
• https://github.com/divnix/digga/pull/84/commits/e2c862ddbec87fe7c2e675ab06c4d50d8800abe0

before I (hopefully) finish those PRs off tonight.

Does someone else get this, too? (on Devos master branch and with nixpkgs commit 53079ed913181b2f945cf1580746828b57d47edb)

error: value is null while a set was expected

       at /nix/store/9vividw3p8cqwndq7k1sqknnsvinh1ql-source/flake.nix:52:19:

           51|                 moduleDeclarationFile =
           52|                   (builtins.unsafeGetAttrPos "modules" args).file;
             |                   ^
           53|
(use '--show-trace' to show detailed location information)

In reply to @blaggacao:matrix.org
This issue is also reported here: https://github.com/divnix/digga/issues/87

So I haven't made an iso with flk for while but there seems to be a regression (at least in terms of how I was using it. I have a basic host I use for a super slim iso that pulls in one of my VM users that has some packages + my ssh keys in authorizedKeys. It looks like this:

{ lib, suites, profiles, ... }:
{
  imports = lib.flatten [
    suites.base
    profiles.users.operator
  ];
  services.openssh.enable = true;

  boot.loader.systemd-boot.enable = true;
  boot.loader.efi.canTouchEfiVariables = true;
  networking.interfaces.enp1s0.useDHCP = true;

  fileSystems."/" = { device = "/dev/disk/by-label/nixos"; };
}

Previously this worked fine, and I could ssh into the VM/machine as my operator user, however in the most recent develop branches of devos/digga, the operator user is no longer included when creating an iso with flk iso, I cannot see anything obvious that removes my user, other than perhaps the disabledModules config in isoConfig in digga.

My question would be, is there an easy way to include certain profiles/suites in the iso?

In reply to @blaggacao:matrix.org
I think the reason is that all profiles that are incorporated within a suite are disabled by default. So if a user is incorporated into a suite, that would be disabled as well. The reason for disabling is to avoid systemd startups that you don't need on a minimal boostrap image.

In reply to @blaggacao:matrix.org
So I guess if users.operator is also within suites (anywhere) it will get filtered.

In reply to @b12f:pub.solar
I'm with you that stuff is so slow. We've stopped doing automated ISO builds and instead only do them manually in our CI because it just hogs server resources