| 14 Mar 2026 |
 matthewcroughan | disko.devices = {
disk = {
disk1 = {
device = "/dev/disk/by-id/usb-Realtek_RTL9210B-CG_012345679039-0:0";
type = "disk";
content = {
type = "gpt";
partitions = {
ESP = {
type = "EF00";
size = "2G";
content = {
type = "filesystem";
format = "vfat";
mountpoint = "/boot";
};
};
| 17:14:04 |
| matthewcroughan | Then, after that, the xargs copy step is still broken, and results in infinite ed-disko-images> cp: cannot create directory '/mnt/nix/store/xcz1hz25slaasb7xi3glbzxbf5c56dkv-tree-sitter-snl-0.0.0+rev=846e2d6': No space left on device | 17:14:35 |
| matthewcroughan | I've set disko.memSize = 32768, and it hasn't helped | 17:16:38 |
| matthewcroughan | something else is going wrong, it's not actually memory | 17:16:44 |
| matthewcroughan | Ah, okay, this error doesn't happen with the installtest | 17:33:25 |
| matthewcroughan | * Ah, okay, this error doesn't happen with the installTest | 17:33:30 |
| matthewcroughan | So, me trying to get the installTest to fail, was futile | 17:33:40 |
| matthewcroughan | this only happens with the image builder code, and not with the testing code | 17:33:52 |
| matthewcroughan | so the installTest for my config succeeds, whereas diskoImages fails with kernel panic | 17:34:15 |
| matthewcroughan | any ideas given that Mic92 ? | 17:34:19 |
| 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 |
