Felix Uhl

Okay that makes sense as a historical explanation, but do you think that is still an important goal? From my PoV it seems we can just do patch releases for...

> It would be helpful if the examples showcased simpler use cases by default, moving the more complex cases currently covered by examples into dedicated tests. What brings you to...

I'm not sure I understand the issue 100%, but wouldn't it be enough to set [`disko.imageBuilder.qemu`](https://github.com/nix-community/disko/blob/master/module.nix#L17)? If so, we can definitely change the default value of that to use qemu...

Another solution could be to busy-wait in a loop and wait for the creation of the symlink that way before continuing.

> Disko can run incrementally Yes, with `--mode format`. But that mode isn't very dangerous anyway, it will never delete anything. The issue mentions `--mode disko`, which wipes everything without...

@adam248 your ticket was not a duplicate of this one. Please re-open it. This ticket is about a clearly-defined, simple solution for `--mode disko` to simply ask for confirmation once...

> I tried setting initrd.luks.devices.CRYPT.device as described [here](https://nixos.wiki/wiki/Full_Disk_Encryption#Enter_password_on_Boot_.28LVM_on_LUKS.29) but this conflicts with Disko's generated config. You can remove parts of disko's config temporarily. The other solution would be to use...

Hmm, I'm not sure why this happens. I can definitely confirm that: 1. running `nom build .#checks.x86_64-linux.make-disk-image` causes the qemu process to use up to 2.1GB of RAM 2. before...

It would be nice if we could fix this issue. I'm wondering how option documentation is usually generated, I haven't looked into that yet.

@tim-elmer you're right. I actually merged a change recently that should enable us to work on this without hitting the recursion issue: #874