rinigus
commented
3 years ago Kiwi
This seems to be workable solution.
-
host and image should be the same arch: https://osinside.github.io/kiwi/image_types_and_results.html#architectures
-
supports x86_64, arm, aarch64
-
is supported by OBS: we can create images at OBS
-
supports generation of filesystem image
-
supports generation of virtual appliances
-
supports generation of tarballs with root packed
-
supports generation of LVM, but with postprocessing
-
allows to set repo priorities
-
allows to customize via scripts at different stages of image building
LVM
LVM looks to be possible through use of "oem" type. That will generate whole partitioned disk with LVM in use in partition 2. So, would have to mount raw image using loop device, rename logical volume with root (fixed on LVRoot) to root, and then dump partition 2 to raw image.
neochapay
We need to select a tool to build images for Nemo. It is due to the current issues with mic (see below).
Requirements
generate images for
support for images with boot sector (virtual box) and without (arm)
generate image file with LVM inside:
generate image with a filesystem only
ability to specify multiple repositories with their priorities
support Fedora as a base
running customization scripts
select packages for installation
ability to generate ARM images on x86_64 host
good-to-have: support for virtual box images
Issues with mic
mic(https://github.com/mer-tools/mic/tree/jolla) is based on python2 and is using deprecated libzypp bindings (https://github.com/openSUSE/libzypp-bindings). These limitations prevent building libzypp bindings lib (fails in compilation of generated code), problems when using on Fedora 32 (lots of python2 libs were dropped). As Sailfish OS SDK is using older rpm library (or it is compiled with incompatible settings), we cannot generate images on SFOS SDK either.Possible alternatives
Alternatives based from messages in fedora-arm mailing list and some searches