Alpine Linux needs to be able to pull packages from local media on boot. (You can't download packages from the net before you have a network connection.) Using remote repositories presents a problem. If the config files have been modified for a newer version of a package, and the older package is on local media, all sorts of fun can result.

The solution is a local cache of updated packages. This cache can be stored on any r/w media, typically the same location as the apkovl.

The cache is enabled by creating a symlink named /etc/apk/cache that points to the cache directory.

To enable local cache run:

setup-apkcache

To enable Local Cache on releases prior v2.3

Alpine Linux version prior to v2.3 does not have the setup-apkcache tool so the symlink needs to be set up manually.

To manually enable Local Cache on HDD install

If you've installed Alpine to your hard drive (as 'sys'), then create a cache dir and then an /etc/apk/cache symlink pointing to that dir:

mkdir -p /var/cache/apk ln -s /var/cache/apk /etc/apk/cache

You normally don't need apk cache on HDD 'sys' installs but it might be handy if you re-install from net to have the packages cached.

To manually enable Local Cache on run-from-RAM installs

Create a cache directory on the device you store your lbu backups (typically, /dev/sda1.)
mkdir /media/sda1/cache

Tip: If you get an error that says "mkdir: can't create directory '/media/usbdisk/cache': Read-only file system", then you probably need to remount your disk read-write temporarily. Try

mount -o remount,rw /media/sda1

and then don't forget to run

mount -o remount,ro /media/sda1

when you are done with the following commands

Create a symlink to this directory from /etc/apk/cache.
ln -s /media/sda1/cache /etc/apk/cache
Run an lbu commit to save the change (/etc/apk/cache is in /etc and is automatically backed up.)
lbu commit
Done. Now whenever you run an apk command that pulls a new package from a remote repository, The package is stored on your local media. On startup, Alpine Linux will check the local cache for new packages, and will install them in preference.

So you now have a run-from-RAM distro that can do a yum upgrade or apt-get dist-upgrade

Cache maintenance

Over time, newer packages will replace older ones; the cache directory will contain all older versions of packages.

Delete old packages

To clean out older versions of packages, run the clean command.

apk cache clean

or to see what is deleted

apk -v cache clean

Download missing packages

If you accidentally delete packages from the cache directory, you can make sure they are there with the download command,

apk cache download

Delete and download in one step

You can combine the two steps into one with the sync command - this cleans out old packages and downloads missing packages.

apk cache -v sync

Automatically Cleaning Cache on Reboot

To automatically attempt to validate your cache on reboot, you can add the above command to a /etc/local.d/*.stop file:

Contents of /etc/local.d/cache.stop

#!/bin/sh
# verify the local cache on shutdown
apk cache -v sync

# We should always return 0
return 0

Tip: Usually the only time you need to reboot is when things have gone horribly wrong; so this is a "best effort" to cover forgetting to sync the cache; It is much better to run sync immediately after adding or upgrading packages.

Note: Custom shutdown commands were formerly added to a /etc/conf.d/local; but that method is now deprecated.