If Alpine Linux packages disappear after reboot on your computing device which is diskless, especially on devices such as Raspberry Pi, it's likely because Alpine is designed to be diskless, meaning changes are stored in an overlay file (apkovl) and not directly on the SD card. To make changes persistent, you need to use the lbu commit command before rebooting.
Here's a breakdown of the issue and how to fix it:
Understanding the Problem:
Diskless by Default:
Alpine Linux, especially on Raspberry Pi, is designed to be diskless, meaning it doesn't write changes directly to the SD card.
Overlay File (apkovl):
Instead, changes, including installed packages, are stored in an overlay file, often named apkovl.
Reboot and Changes Lost:
When you reboot, the overlay file is cleared, and the changes (including installed packages) are lost because they haven't been committed to the SD card.
How to Fix It (Make Changes Persistent):
- Commit Changes: Before rebooting, use the lbu commit -d command to commit the changes to the SD card.
- lbu commit: This command tells Alpine to save the changes in the overlay file to the SD card.
- -d: This option specifies that you want to commit the changes to the default storage location (usually the SD card).
- Example:
- Post Installation:
- After installation, make sure your system is up-to-date: apk update && apk upgrade.
- Don't forget to save the changes: lbu commit -d.
apk add <package_name> # Install a package
lbu commit -d # Commit the changes
reboot # Reboot the system
Additional Tips:
Check Date and Time:
Ensure the date and time are correct on your Raspberry Pi, as this can affect the setup-alpine process.
Setup Alpine:
If you are setting up Alpine for the first time, run setup-alpine to configure the system.
Commit Regularly:
It's a good practice to commit changes regularly, especially after installing multiple packages or making significant configuration changes.
Terminologies:
apk - Alpine Package Keeper
ovl - Overlay