Paul S.

I think arrays should be completely ignored, maybe they should be replaced by the underlying class.

> ```shell > curl -fsL "https://raw.githubusercontent.com/jinkang23/unifios-utilities/main/on-boot-script/remote_install.sh" | > ``` This worked for me, thanks.

More details here: https://discourse.nixos.org/t/podman-docker-in-nixos-container-ideally-in-unprivileged-one/22909/3

Yes, I'm running it under nested systemd. As I said before, almost all the cgroup hierarchy is readonly under nspawn and docker can't handle that. Presence/absense of SYSTEMD_NSPAWN_USE_CGNS doesn't make...

Well. Maybe something is wrong with nixos, I'll try to investigate.

I understand. Though some scalers (e.g. VanCryst) have almost perfect heuristics which never failed (for me). And displays are generally very good at auto adjustment. So it should be possible.

There might be a good solution for this problem: ``` age.secrets.hostkey-initrd = { file = "${paths.agenix}/hostkey--initrd.age"; path = "/etc/initrd-hostkey"; symlink = false; }; ... boot.initrd.network.ssh.hostKeys = [ "/etc/initrd-hostkey" ]; ```...

Maybe the initrd builder just reuses the file which persists between builds? Obviously, if the hostkey persists between builds and reboots, you have to deploy twice only the first time...

When it fails, the log looks like ``` updating systemd-boot from 253.3 to 253.6 cp: cannot stat '/etc/initrd-hostkey': No such file or directory failed to create initrd secrets! warning: error(s)...

This looks like https://github.com/hyprwm/Hyprland/issues/3012 but it worked for me before