On Tue, Mar 05, 2024 at 12:00:15PM +0000, Mathias Gibbens wrote: > to add iproute2. I would be interested to know more about what > environment Incus is being used in that doesn't have the `ip` command > available.
debvm-create --include=incus # This should have created a file named rootfs.ext4. debvm-run > My normal testing setup for Incus is a fresh, minimal expert install > of sid via the netinst iso. During the install of the VM, I only > install the base system and deselect the "standard system utilities" > group. I do use DHCP, which looks like that might be responsible for > pulling in iproute2 for me. If there's a way to create an even more > minimal install, I'd be happy to incorporate that into my testing > routine. Turns out your minimal expert install is not so minimal. debvm tends to give you a smaller but still functional installation. I think adding --variant=important to debvm-create roughly gets you the minimal expert installation, but creating the machine takes slightly longer and uses more disk space of course. Rather than adding debvm on top of your testing, I think adding autopkgtests with isolation-machine should get you more automatic coverage. Possibly such tests need to be explicitly allowed by debci folks and currently are only available on amd64. Helmut
