Providing even an empty apkovl seems to break init
I am netbooting Alpine Linux 3.12.0 with the following kernel command line:
initrd=initramfs-lts
ip=[...]
modloop=http://.../modloop-lts
modules=igb,xhci_pci
alpine_repo=http://nl.alpinelinux.org/alpine/v3.12/main
apkovl=http://.../empty.apkovl.tar.gz
Here, empty.apkovl.tar.gz
is an empty tarball. Yet the presence of this argument causes problems when Alpine initializes, seemingly preventing it from running any initialization scripts in /etc/init.d
. (Pardon any typos, I had to re-type this.)
* Loading user settings from /tmp/empty.apkovl.tar.gz: 0%
ok.
* Installing packages to root file system: fetch http://nl.alpinelinux.org/alpine/v3.12/main/x86_64/APKINDEX.tar.gz
...
ok.
OpenRC 0.42.1.9028084776 is starting up Linux 5.4.43-1-lts (x86_64)
* /proc is already mounted
* Mounting /run ...
* /run/openrc: creating directory
* /run/lock: creating directory
* /run/lock: correcting owner
* Caching service dependencies ...
* Loading modules ...
modprobe: can't change directory to `/lib/modules`: No such file or directory
modprobe: can't change directory to `/lib/modules`: No such file or directory
* Setting system clock using the hardware clock [UTC] ...
Welcome to Alpine Linux 3.12
kernel 5.4.43-1-lts on an x86_64 (/dev/tty1)
(none) login:
Without the apkovl
parameter, it does this:
* Caching service dependencies ...
* Remounting devtmpfs on /dev ...
* Mounting /dev/mqueue ...
[downloads modloop-lts from network]
* Mounting modloop /lib/modloop-lts ...
...
* Starting first boot
Welcome to Alpine Linux 3.12
Kernel 5.4.43-1-lts on an x86_64 (/dev/tty1)
localhost login:
Something is going awry between downloading/unpacking the apkovl
tarball and OpenRC initialization that prevents it from enumerating the service scripts.