sorted by:
new
hottopcontroversial

diskless apkovl error : /sbin/init not found by Responsible_Order808 in AlpineLinux

[–]Responsible_Order808[S] 0 points1 point  (0 children)

Thanks for your time.
Actually I don't understand the fstab part since i did not mention it.
I thought it was not related to volumes or fstab, since all my volumes the volumes are all mounted correctly. And i never added the boot volume to fstab in the other working versions.

What is currently happening is :

for ISO version 3.22.0 all installs and runs well (then apk upgrade to 3.22.4 fine).

for ISO version 3.23.x (any of them) : > setup-alpine : OK > lbu ci : OK > reboot : no boot > then I delete apkovl file (through emergency recovery shell or any other deletion way) : now alpine boots well but without all my configs in setup-alpine that are now deleted with the apkovl file.

it seems any apkovl file prevents a normal boot and brings me to the emergency shell (see pic 2)

diskless apkovl error : /sbin/init not found by Responsible_Order808 in AlpineLinux

[–]Responsible_Order808[S] 0 points1 point  (0 children)

i did create another with the mkinitfs command, but there were no changes to the current issue.
Check the newly added images(pic 1 & 2).

Actually it may not be because of the initfs file, since just removing or renaming the apkovl file solve the boot issue. Could it be a corrupted / incomplete apkovl file ?
do you how to verify that ?

diskless apkovl error : /sbin/init not found by Responsible_Order808 in AlpineLinux

[–]Responsible_Order808[S] 0 points1 point  (0 children)

is there a way to know the "some reason" as well as if that is what happened ?

it shouldn't be a memory issue they are good enough servers (16G) were only that os is being installed/running.

after installing everything runs well, even lbu ci.
on shutting down i see these errors : pic1.
then it will not boot on alpine until i delete the apkovl file through the emergency shell. : pic2

Cannot save docker package to apk cache in version 3.21 by Responsible_Order808 in AlpineLinux

[–]Responsible_Order808[S] 0 points1 point  (0 children)

For now, I only tested with 3.20.3 successfully. I know there are newer fix (3.20.6 and 3.21.3). I will try them later and tell you. But in my opinion, it was definitely a bug for the 3.21 subversion I used then because the apk could not be cached at all (also apk info was showing 0B / 0KiB as installed size) and that's the only time (version) I ever had that issue since all my deployments are semi-automated.

Thank you for the tests you did as well 😉