image-builder issueshttps://source.puri.sm/Librem5/image-builder/-/issues2023-08-11T09:57:14Zhttps://source.puri.sm/Librem5/image-builder/-/issues/41Switch away from vmdebootstrap2023-08-11T09:57:14ZGuido GuntherSwitch away from vmdebootstrapFeature: https://source.puri.sm/Librem5/use-cases/issues/19
No urgency here, just since this came up a couple of time. vmdeboostrap is unmaintained upstream which isn't a big issue since we could pick it up but since there are alternati...Feature: https://source.puri.sm/Librem5/use-cases/issues/19
No urgency here, just since this came up a couple of time. vmdeboostrap is unmaintained upstream which isn't a big issue since we could pick it up but since there are alternatives we might also pick something more featureful. Candidates are
- [fai](https://fai-project.org/) (used for e.g. debian's cloud images, robust, has classes for different image types)
- [vmdb2](https://liw.fi/vmdb2/) (same upstream as vmdeboostrap so it might get dropped again)
- [debos](https://github.com/go-debos/debos) - looks well maintained
- [debspawn](https://github.com/lkorigin/debspawn) PureOS uses Debspawn to build images which are then used in reproducible testing.https://source.puri.sm/Librem5/image-builder/-/issues/29Use upstream vmdebootstrap2019-03-26T13:04:34ZZoltan GyarmatiUse upstream vmdebootstrapWhen i try to build an image for the devkit on my Ubuntu 18.04 host, it fails with the following error:
`ERROR: Only UEFI is supported on arm64`
A quick Google loo.kup shows that the reason is that vmdebootstrap doesn't support buildin...When i try to build an image for the devkit on my Ubuntu 18.04 host, it fails with the following error:
`ERROR: Only UEFI is supported on arm64`
A quick Google loo.kup shows that the reason is that vmdebootstrap doesn't support building arm64 image without uefi, which is a known issue[1] Turned out that the vmdebootstrap version used in the docker image is patched[2] to bypass this, so after I patched my host's vmdebootstrap version as well, the image builder works, although it's a rather hackish workaround.
I think this should be at least documented (gonna send a PR soon to cover this in the ReadMe), or migrating away from vmdebootstrap to vmdb2, as vmdebootstrap is abandonware anyway. Is there any plan to do this migration?
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845439
[2] https://source.puri.sm/Librem5/image-builder/commit/e28ecaf55ef3f13890193b7c22b069cc97e58627
EDIT: The proper solution is to use an upstream version of vmdebootstrap, like described above.