rocky-kiwi-descriptions

Kiwi descriptions for Rocky Linux 9.

config.xml is a symlink to rocky.xml. this way the symlink can just be changed to deal with live images (as kiwi doesn't seem to support using the --kiwi-file option for iso).

Can't you use the same config.xml? Why are you symlinking?

Yes and the reason why we're symlinking is that "name" and "displayname" are not flexible. They are only set/read at the very top level <image> (at least from testing at the time of this writing). As our images and volume names (at least for live images) have a very specific format, and we want it to be easy to rename them, we did it this way.

Cloud, container, vagrant images can all use the first config, likely just fine. The live images were the problematic ones, thus, symlinks with a default to the rocky.xml config.

I found an issue...

Please fork and make a PR! We're still learning how this tool works ourselves.

How to try it out

You can actually do this in mock pretty easily. You could also probably get this running in a podman container or otherwise. As of this writing, we haven't tried it yet. Theory says it should work.

Note that selinux must be set to permissive.

Live Image Example (EPEL)

The below makes an XFCE live image using EPEL packages.

% mock -r rocky+epel-9-x86_64 --init
% mock -r rocky+epel-9-x86_64 --install kiwi-cli \
  dracut-kiwi-live \
  kiwi-systemdeps-{bootloaders,containers,core,disk-images,filesystems,image-validation,iso-media} \
  distribution-gpg-keys \
  epel-release

% sudo setenforce 0
# Some builds require --isolation=simple -- Add it if you have issues
% mock -r rocky+epel-9-x86_64 --shell --enable-network
% git clone https://git.resf.org/sig_core/rocky-kiwi-descriptions -b r9
% cd rocky-kiwi-descriptions
% sed -i 's/ZZVOLVERZZ/9/g ; s/ZZVERZZ/9/g' $(find . -name "*.xml")
% ln -sf configs/live-xfce.xml config.xml
% kiwi-ng --debug --type="iso" \
  --profile="XFCE-Live" \
  --color-output system \
  build \ 
  --description="./" \
  --target-dir /builddir/lmc