GitLab

Commit 680b40d3 in repository git://
git.alpinelinux.org/aports seems to have broken ISO builds with aports in a
docker container.

I cannot link to build logs or source of what I’m doing as it’s in a
private gitlab repository, however I can attach my dockerfile, gitlab CI
build (basically the commands to run), and the log output (the last two for
both successful and failing) and whatever else is needed to recreate.

That may not be necessary however - the relevant error I’m getting is:

>>>mkimage-x86_64: —>kernel x86_64 vanilla
b010bf8b3d61857350920040dfeb904d5ca48e6b linux-vanilla linux-firmware
wireless-regdb
update-kernel: unrecognized option: modloopfw

Syntax: update-kernel [-F ]… [-p ]… [[-a ]
<dest_dir>]
update-kernel -f [-F ]… [-p ]… [-a ]
<dest_dir>
update-kernel -b <build_dir> [-F ]… [-p ]… [[-a
] <dest_dir>]

Options: -a|—arch Install kernel for specified architecture
-b|—build <build_dir> Install custom-built kernel
-f|—flavor Install kernel of specified flavor
-F|—feature Enable initfs feature
-p|—package Additional module or firmware package
-s|—modloopsign Sign modloop with abuild key
-v|—verbose Verbose output
-k|—apk-pubkey Include given key in initramfs
-K|—hostkeys Include host keys in initramfs
-C|—compression Initramfs compression (see mkinitfs for options)
-M|—media Boot media directory layout
—repositories-file apk repositories file

And it appears I am getting that error because on line 6 in mkimg.base.sh
now uses a flag (—modloopfw) that doesn’t appear to work with
update-kernel when alpine-conf is installed in a docker container.

I’ve added a step to my CI to checkout the git commit before for now, and
if this does not get fixed may instead revert that commit, but would rather
see it get fixed properly

Thanks!

—
Jack Hayhurst

(from redmine: issue id 10001, created on 2019-02-21, closed on 2019-06-19)