Release Notes for Alpine 3.13.0
- 1 aports
- 2 busybox
- 3 apk-tools
- 4 Known issues
musl has been upgraded to 1.2. This release changes the definition of
time_t on 32-bit systems. See the musl time64 release notes for more details.
The following important information applies for users of x86, armv7, and armhf (currently supported 32-bit architectures), including 32-bit Docker containers on 64-bit hosts.
All self-compiled packages must be manually rebuilt after upgrading, even if relocation/SONAME errors are not encountered.
musl 1.2 uses new time64-compatible system calls. Due to runc issue 2151, these system calls incorrectly returned EPERM instead of ENOSYS when invoked under a Docker or libseccomp version predating their release. Therefore, Alpine Linux 3.13.0 requires one of the following:
- runc v1.0.0-rc93
- if using Docker's Debian repositories, this is part of containerd.io 1.4.3-2
- if using Docker Desktop for Windows or Mac, this is part of Docker Desktop 3.3.0
- Docker 19.03.9 (which contains backported moby commit 89fabf0) or greater, AND libseccomp 2.4.2 (which contains backported libseccomp commit bf747eb) or greater. In this case, to check if your host libseccomp is time64-compatible, invoke
scmp_sys_resolver -a x86 clock_gettime64for x86 containers, or
scmp_sys_resolver -a arm clock_gettime64for armhf or armv7 containers. If 403 is returned, time64 is supported. If -1 is returned, time64 is not supported. Note that if runc is older than v1.0.0-rc93, Docker must still be at least version 19.03.9, regardless of the result of this command.
In order to run under old Docker or libseccomp versions, the moby default seccomp profile should be downloaded and on line 2,
defaultAction changed to
--seccomp-profile=default.json can be passed to dockerd, or
--security-opt=seccomp=default.json passed to
docker create or
docker run. This will cause the system calls to return ENOSYS instead of EPERM, allowing the container to fall back to 32-bit time system calls. In this case, the container will not be compatible with dates past 2038.
--security-opt=seccomp=unconfined can be passed with no
default.json required, but note that this will reduce the security of the host against malicious code in the container.
Deprecation of Berkeley DB (BDB)
Oracle has changed the license of BDB to AGPL-3.0, making it unsuitable to link to packages with GPL-incompatible licenses. Since the old version is no longer maintained, the
db package is now deprecated. Alpine Linux packages are being transitioned to alternatives or, where no alternatives exist, removed entirely.
Support for Postfix
btree databases has been removed.
lmdb is the recommended replacement. Before upgrading, all tables in
btree must be changed to a supported alternative. See the Postfix lookup table documentation for more information.
cyrus sasldb now uses
gdbm instead of
db. The database must be created from scratch or manually migrated after upgrading to Alpine Linux 3.13.
Switching from busybox ifupdown to ifupdown-ng
The default ifupdown implementation has been switched from busybox to ifupdown-ng. ifupdown-ng is intended to be compatible with debian ifupdown and busybox ifupdown, but all users of
/etc/network/interfaces should read the ifupdown-ng readme and the ifupdown-ng admin guide before upgrading.
ifupdown-ng has native vlan support, so the
vlan package is no longer required and can be uninstalled. The
bond packages are still required.
GCC has been upgraded to version 10. GCC 10 sets the
-fno-common option by default. All Alpine Linux packages have been fixed, but users compiling other software on Alpine Linux may need to make changes to their code. For more information, see the GCC 10 porting guide.
PHP 8.0 with a common set of extensions is now available as
php8. PHP 7.4 (
php7) remains the default.
xorg-server has moved to community
xorg-server and related packages have been moved from main to community. To install it, ensure /etc/apk/repositories contains the community repository.
setup-xorg-base will automatically enable the community repo before installing xorg-server.
Nextcloud has been updated to version 20. As a direct upgrade from 18 to 20 is not supported by nextcloud, Nextcloud 19 must be temporarily installed.
- Take a note and remove all nextcloud-* aports
- Install corresponding the nextcloud19-* aports
occ upgradeas any regular update
- Verify everything still works
- Remove the nextcloud19-* aports again
- Install the regular nextcloud-* aports again
- Run Steps 3 and 4 again
- The upgrade should now be finished
As the last step you should visit your administrator settings overview page and run any missing db-updates as shown (e.g.
db:add-missing-indices db:add-missing-primary-keys db:add-missing-columns db:convert-filecache-bigint)
/etc/conf.d/spamd has been moved from the
spamassassin to the
WireGuard is now included in the standard Linux kernel since version 5.6, so the
wireguard-virt packages have been removed.
QEMU packages split
Several features previously in the standard qemu package have been split into subpackages, including qemu-audio-*, qemu-block-*, qemu-hw-display-*, and qemu-ui-*. The metapackage qemu-modules installs all of these.
The following applets have been removed:
- hdparm: Missing many features. Use
- fdformat: Rarely used. Use
- readprofile: Rarely used. Consider
- lspci: Missing many features, such as hwdb support. Use
grep . /sys/bus/pci/devices/*/*instead.
- conspy: Rarely used.
- smemcap: Rarely used.
- dumpleases: Rarely used.
Alternatives for conspy, smemcap, and dumpleases are not currently packaged due to a lack of interest. If you require these programs, please file an issue at Alpine GitLab.
The following applets now support long options:
apk-tools now has an official man-page:
apk-tools-docs. If the
docs package is installed, man pages will automatically be installed and updated for all installed packages.
LVM boot scanning
Some users are reporting a regression in Alpine Linux 3.13 where nlplug-findfs fails to detect LVM PVs at boot. The current workaround is to temporarily downgrade to Linux 5.4 from Alpine Linux 3.12. This issue is being tracked in aports issue 12325.