| 14 Mar 2026 |
 matthewcroughan | Any initial feeling as to why the image builder is so different from the testing? | 17:34:49 |
| matthewcroughan | Okay, it's pretty easy to make this happen in nix build -f tests/make-disk-image.nix | 18:16:53 |
| matthewcroughan | you just increase the closure size of your toplevel a tiny bit, and it begins to happen | 18:17:04 |
| matthewcroughan | e.g by adding to environment.systemPackages some big packages | 18:17:28 |
| matthewcroughan | like chromium, firefox, etc | 18:17:31 |
 lassulus | did you increase the image size as well? | 18:17:43 |
| matthewcroughan | 0.0 | 18:18:59 |
| matthewcroughan | I guess that could also cause these issues | 18:19:03 |
| matthewcroughan | bad UX | 18:19:05 |
| matthewcroughan | I think we should trace if it's left as default | 18:19:15 |
| matthewcroughan | having to set it, and it not be auto calculated, is definitely counter intuitive | 18:19:33 |
| matthewcroughan | Especially since it's not possible to throw an error when out of space, the VM just sorta does what it wants | 18:19:54 |
| matthewcroughan | sometimes kernel panic, sometimes cp fails | 18:20:00 |
| lassulus | well auto calculating it is hard, you can adjust the outer image size, but arranging the partitions is a pretty hard problem :D | 18:20:32 |
| matthewcroughan | Auto calculating it is half of what systemd-repart's logic is for yeah | 18:20:41 |
| matthewcroughan | it's very hard | 18:20:44 |
| matthewcroughan | and a lot of postmarketOS code exists to do the smae | 18:20:53 |
| matthewcroughan | * and a lot of postmarketOS code exists to do the same | 18:20:55 |
| matthewcroughan | perhaps we could have an auto calculating implementation for each supported FS in disko | 18:21:18 |
| matthewcroughan | and if your FS doesn't support auto calculation, then tough luck, set the imageSize | 18:22:06 |
| lassulus | question is where the size is allocated, is it only /nix/store? what happens if you have something like size = "10%" in there? do we make the diskImage 10x your close size? | 18:22:52 |
| matthewcroughan | imageSize = "10%" ? | 18:23:29 |
| lassulus | what happens if you have size = "1G" for your /nix/store partition? just error out? | 18:23:40 |
| matthewcroughan | ah I see, uh | 18:24:02 |
| matthewcroughan | zfs = {
size = "100%";
content = {
type = "zfs";
pool = "edpool";
};
};
| 18:24:11 |
| matthewcroughan | is what I have right now | 18:24:14 |
| matthewcroughan | * zfs = {
size = "100%";
content = {
type = "zfs";
pool = "edpool";
};
};
| 18:24:19 |
| lassulus | yes, that is the trivial case :) | 18:24:24 |
| matthewcroughan | error: A definition for option disko.devices.disk.disk1.content.partitions.zfs.size' is not of type value "100%" (singular enum) or str… ┃ - In /nix/store/g8pkz1bxk5n7vvicr9nk0wklgrqp0k9y-source/hosts/ed/disko.nix': "10%` | 18:24:43 |
| lassulus | don't think zfs can do other sizes than 100% or fixed block size | 18:25:25 |
