!oNSIfazDqEcwhcOjSL:matrix.org

disko

365 Members
disko - declarative disk partitioning - https://github.com/nix-community/disko93 Servers

Load older messages


SenderMessageTime
15 Sep 2024
@colemickens:matrix.orgcolemickens well I don't know why ESP is being made first, maybe it's alpha sorted by default (since I'm using EF00 not EF02). anyway, I'll set priority. Now just looking for growpart. 22:18:42
@colemickens:matrix.orgcolemickensI keep doing it by hand and forgetting to set the part label and causing myself a lot of pain.22:18:59
@colemickens:matrix.orgcolemickensoh I guess that's a system-level nixos option. hm22:34:51
@colemickens:matrix.orgcolemickensI seriously love disko so much. I wish I could fund someone to make a non-VM install process, with lanzaboote, bootspec, etc. I don't think it's that outlandish. If one could compose images with cross-compiled systems without needing to involve qemu, that would just be "end-game".22:51:10
@colemickens:matrix.orgcolemickensstill, doing a native build, using disko, and then pivoting to a cross-built system is still such a nicer experience than sdcard or other things people do to get nixos on weird platforms. I'm excited to use it for ec2 image as well.22:52:21
16 Sep 2024
@arjan5:matrix.orgarjan5 colemickens Not sure if it's what you're looking for, but nixos-anywhere can install different-arch systems remotely, even for configs containing disko, lanzaboote, impermanence, etc. I have done this before. 09:12:30
@lassulus:lassul.uslassulusLanzaboote needs interaction with the efi/bios to deploy your keys there. But I guess everything else could be done by the image builder12:43:32
@janik0:matrix.orgJanik (they/them)
In reply to @lassulus:lassul.us
Lanzaboote needs interaction with the efi/bios to deploy your keys there. But I guess everything else could be done by the image builder
I have done that once
12:44:35
@janik0:matrix.orgJanik (they/them)https://github.com/nix-community/disko/pull/38312:45:24
@lassulus:lassul.uslassulusah nice, thanks for the link12:46:56
@matthewcroughan:defenestrate.itmatthewcroughan
error:
       … in the condition of the assert statement
         at /nix/store/l3amk5lsakpc93him5kry24kax23sn4h-source/lib/customisation.nix:365:17:
          364|     in commonAttrs // {
          365|       drvPath = assert condition; drv.drvPath;
             |                 ^
          366|       outPath = assert condition; drv.outPath;

       … while calling the 'seq' builtin
         at /nix/store/l3amk5lsakpc93him5kry24kax23sn4h-source/lib/customisation.nix:80:32:
           79|       newDrv = derivation (drv.drvAttrs // (f drv));
           80|     in flip (extendDerivation (seq drv.drvPath true)) newDrv (
             |                                ^
           81|       { meta = drv.meta or {};

       (stack trace truncated; use '--show-trace' to show the full, detailed trace)

       error: attribute 'diskoScript' missing
       at /nix/store/w4k2mviwfgnqf7bpq3j725b4wghgc2yx-source/lib/make-disk-image.nix:81:7:
           80|     ''}
           81|     ${systemToInstall.config.system.build.diskoScript}
             |       ^
           82|   '';
17:10:10
@matthewcroughan:defenestrate.itmatthewcroughan Maybe due to refactors lately? Enzime 17:10:21
@matthewcroughan:defenestrate.itmatthewcroughan This happens by accessing config.system.build.diskoImages 17:12:41
@matthewcroughan:defenestrate.itmatthewcroughan Ah was it changed to diskoImagesScript now? 17:13:21
@matthewcroughan:defenestrate.itmatthewcroughanOooh it's because I didn't import my disko.nix, but this wasn't caught by the module system17:16:06
@matthewcroughan:defenestrate.itmatthewcroughan Odd how the diskoImages attribute still gets made 17:16:16
@silentlurker:matrix.orgsilentlurker joined the room.20:02:34
17 Sep 2024
@vandycarlos:matrix.orgvandycarlos joined the room.01:25:44
@enzime:nixos.devEnzime
In reply to @matthewcroughan:defenestrate.it
Odd how the diskoImages attribute still gets made
fixed here https://github.com/nix-community/disko/pull/776 :)
02:03:57
@enzime:nixos.devEnzime Mic92 lassulus what's the difference between merging with the GitHub UI and using mergify queue? should I prefer one or the other? 03:27:13
@joerg:thalheim.ioMic92 @enzime:nixos.dev: mergify builds pull requests with the latest master and merges after ci succeeds. So master should be always green doing this minus flaky tests. That's why this is our preferred merge method. 04:46:07
@lassulus:lassul.uslassulusSometimes it's easier to press the button if everything is already green06:20:08
@magic_rb:matrix.redalder.orgmagic_rbIf you do that you can still end up with a broken master after the merge06:51:04
@phaer:matrix.orgphaertrue, but unlikely for i.e. documentation-only merges :)11:52:12
@joerg:thalheim.ioMic92lassulus: always these lazy smart-phone merges.12:24:36
@lassulus:lassul.uslassulus changed their profile picture.14:38:22
@matthewcroughan:defenestrate.itmatthewcroughan Enzime: since disko is the wild west there are no crumbs to figure out where extraPostVM went 15:30:25
@matthewcroughan:defenestrate.itmatthewcroughanthe image builder has been made into its own module now which is fine and overdue, but what is the module name now?15:30:55
@matthewcroughan:defenestrate.itmatthewcroughanSince there is no documentation I'm reading the code instead,15:31:20
@matthewcroughan:defenestrate.itmatthewcroughan * Since there is no documentation I'm reading the code instead15:31:21

Show newer messages


Back to Room ListRoom Version: 10