Warning: Make sure that you have a backup of your important data.

Upgrading an Alpine Linux Hard-disk installation

When Alpine Linux is installed to hard drive, upgrading the installation is simple.

Upgrading to latest release

Update Repositories File

The Repositories file /etc/apk/repositories can be updated using one of the following methods.

Using setup-apkrepos script

Launch the setup-apkrepos script:

# setup-apkrepos

Pressing e will open the file to edit using vi editor. Edit the repository lines to reflect the new version number.

Using sed command

Use a one-line command to edit all version numbers in the file "in place". Here's how you'd change v3.19 to v3.20:

# sed -i -e 's/v3\.19/v3\.20/g' /etc/apk/repositories

Manual editing of /etc/apk/repositories

Edit the /etc/apk/repositories file using any editor of your choice (nano for instance) to edit the Alpine Linux package repositories.

Contents of /etc/apk/repositories

http://dl-3.alpinelinux.org/alpine/v3.19/main
http://dl-3.alpinelinux.org/alpine/v3.19/community

In the above file, to upgrade Alpine Linux from version 3.19 to 3.20, simply replace the number 3.19 by 3.20 in all the places, so that the updated repositories file looks like below:

Contents of /etc/apk/repositories

http://dl-3.alpinelinux.org/alpine/v3.20/main
http://dl-3.alpinelinux.org/alpine/v3.20/community

Using latest-stable instead of version number

Note, subsequent manual changes of the version numbers in /etc/apk/repositories may be avoided for future release upgrades by having the repository lines refer to "latest-stable" instead of an absolute value:

Contents of /etc/apk/repositories

http://dl-3.alpinelinux.org/alpine/latest-stable/main
http://dl-3.alpinelinux.org/alpine/latest-stable/community

Warning: Changing the repositories to latest-stable may initiate unexpected release upgrades. So beware of the consequences of unexpected release upgrades, when using latest-stable.

Updating package lists

With the correct repositories file in place, the latest index list of available packages can be obtained with:

# apk update

Tip: Adding the --update-cache or -U to another apk command, as in apk add -U ... or apk upgrade -U, has the same effect as always running apk update immediately before the other apk command. Instead of auto-update it only if the index has not been updated recently.

Upgrading packages

At times it is required to first upgrade just the Alpine Linux Package Manager itself to the latest available version, before upgrading any other package. This was the case, for example, when upgrading from a version of Alpine before 2.3.0_rc1. But simply always doing so shouldn't hurt, either:

# apk add --upgrade apk-tools

Next, to upgrade all installed packages:

# apk upgrade --available

The --available switch is used to force all packages to be upgraded, even if they have the same version numbers. Sometimes changes in musl require doing this.

Note: All services that have been upgraded need to be restarted, to begin using the upgraded version. If the kernel is upgraded, it's required to reboot to begin using the upgraded version:

sync reboot

Upgrading to Edge

An upgrade of Alpine Linux from a stable version to the rolling development version edge basically requires the same steps as Upgrading to latest release.

The crucial difference is, that when editing the /etc/apk/repositories file, all referenced repository versions (such as v3.2 or latest-stable) therein need to be pointing to edge.

When using edge branch, testing repository can be added if the packages that one needs are available only in testing repository.

Note: Remember that, packages in testing repository have no support.

Contents of /etc/apk/repositories

#/media/cdrom/apks
http://dl-cdn.alpinelinux.org/alpine/edge/main
http://dl-cdn.alpinelinux.org/alpine/edge/community
http://dl-cdn.alpinelinux.org/alpine/edge/testing

After upgrading to edge, the currently installed edge version may be checked with

$ cat /etc/alpine-release

and referring to the build date that is attached to the release.

Warning: Do not enable stable and edge repos at the same time. This can break your system. Either use edge or stable. If you mix stable and edge repositories, you're on your own.