Expected behavior
/dev/vg2/lvol0 should be mounted at /data before k3s-service starts
Actual behavior
During the sysinit phase of boot up, loadkmap requires and runs the localmount service.
localmount fails to find /dev/vg2/lvol0 as lvm has not started yet.
In the boot phase, lvm starts but since localmount has already started in the previous phrase, it no longer runs. /dev/vg2/lvol0 is now present but not mounted to /data.
Additional context
I downloaded Alpine Linux 3.14.2, and notice that its loadkmap service is in the boot runlevel, not in the sysinit runlevel. While I update my config.yaml accordingly, it is working:
Version (k3OS / kernel) k3os version v0.22.2-k3s2r0 5.4.0-88-generic _99 SMP Tue Oct 5 16:53:38 UTC 2021
Architecture x86_64
Describe the bug I need to mount a LVM disk before
k3s-service
starts, so I did the following:lvm
to boot runlevelThinking that service
localmount
will auto mount the entry in /etc/fstabTo Reproduce
Expected behavior /dev/vg2/lvol0 should be mounted at /data before
k3s-service
startsActual behavior During the
sysinit
phase of boot up,loadkmap
requires and runs thelocalmount
service.localmount
fails to find /dev/vg2/lvol0 aslvm
has not started yet.In the
boot
phase,lvm
starts but sincelocalmount
has already started in the previous phrase, it no longer runs. /dev/vg2/lvol0 is now present but not mounted to /data.Additional context I downloaded Alpine Linux 3.14.2, and notice that its
loadkmap
service is in theboot
runlevel, not in thesysinit
runlevel. While I update myconfig.yaml
accordingly, it is working: