Alpine Linux - User contributions [en]

Template:AlpineLatest

2026-04-15T11:59:25Z

Ncopa:

<noinclude>{{Template}}
</noinclude>3.23.4

Template:AlpineLatest

2026-01-27T21:50:03Z

Ncopa: 3.23.3

<noinclude>{{Template}}
</noinclude>3.23.3

Template:AlpineLatest

2025-12-17T07:13:50Z

Ncopa: bump 3.23.2

<noinclude>{{Template}}
</noinclude>3.23.2

Template:AlpineLatest

2025-12-03T16:51:12Z

Ncopa: bump 3.23.0

<noinclude>{{Template}}
</noinclude>3.23.0

Template:AlpineLatest

2025-10-08T11:24:47Z

Ncopa: 3.22.2

<noinclude>{{Template}}
</noinclude>3.22.2

Template:AlpineLatest

2025-07-15T13:22:04Z

Ncopa: 3.22.1

<noinclude>{{Template}}
</noinclude>3.22.1

Release Notes for Alpine 3.22.0

2025-06-12T18:16:43Z

Ncopa: /* Note-worthy updates */ add note about dovecot

As always, make sure to read [[Upgrading Alpine to a new major release]] when upgrading to a new release.

If you experience any issues with the upgrade, please let us know and file an issue in our repositories.

== Important changes ==

=== Preparations for /usr-merge ===

The work on /usr-merge has continued since last release. Precaution from [https://wiki.alpinelinux.org/wiki/Release_Notes_for_Alpine_3.21.0#Preparations_for_/usr-merge previous release] still apply.

== Significant changes ==

=== apk-tools ===

This release is the last release using apk-tools v2.14. The next Alpine v3.23 will include apk-tools v3. The packages and index format are still using the legacy v2 format.

There are a number of new changes in the new apk-tools release. To test apk-tools v3, [https://wiki.alpinelinux.org/wiki/Upgrading_Alpine_Linux_to_a_new_release_branch#Upgrading_to_Edge upgrade to Alpine edge, enable the testing repository] and install {{pkg|apk-tools3}}.

=== KDE Plasma ===

The X11 session for KDE Plasma has been removed. If you had {{pkg|plasma-workspace-x11|branch=v3.21|arch=}} installed make sure to remove it from {{path|/etc/apk/world}}. Wayland is the only available option now.

=== SDL ===

{{pkg|sdl3}} and {{pkg|sdl2-compat}} were moved to the community repository and are now the default SDL provider. To force the installation of {{pkg|sdl2}}, use <code>apk add sdl2</code>.

=== Adwaita Fonts ===

As a result of [https://release.gnome.org/48/#new-fonts GNOME's switch] to {{pkg|adwaita-fonts}}, the default font for GTK-based applications (e.g. {{pkg|vte3}} or {{pkg|libadwaita}} Applications) was changed. If you want to revert or override the fonts, you can use:

<pre>
$ apk add font-cantarell font-adobe-source-code-pro
$ gsettings set org.gnome.desktop.interface font-name 'Cantarell 11'
$ gsettings set org.gnome.desktop.interface monospace-font-name 'Source Code Pro 11'
</pre>

{{pkg|adwaita-fonts}} is pulled in as a dependency of some packages since it broke the default behaviour for various applications.

=== GeoClue ===

Since Mozilla Location Services (MLS), which were used as the geolocation service in geoclue, [https://discourse.mozilla.org/t/retiring-the-mozilla-location-service/128693 has been retired by Mozilla], Alpine switched to [https://beacondb.net/ beaconDB] as the default geolocation provider. ({{MR|76764}})

=== BIRD Routing Daemon ===

The {{pkg|bird|repo=community}} routing daemon package has been upgrade to version 3 which introduces a new multi-threaded architecture. A side effect of this change is [https://trubka.network.cz/pipermail/bird-users/2024-December/017973.html significantly increased memory consumption] of the daemon. This update is configuration-compatible with BIRD v2 but there are some behavioral backwards incompatibilities. Users should read the [https://gitlab.nic.cz/labs/bird/-/blob/stable-v3.0/doc/migration-bird3.md migration guide]. Notably the format of <tt>show route all</tt> has changed as has the format of the logs, which may impact scripts and automation that consume those outputs. Users who require BIRD v2 should install the {{pkg|bird2|repo=community}} package instead.

=== Secure Boot and Gummiboot ===

{{pkg|secureboot-hook|repo=main}} (and its dependency {{pkg|efi-mkuki|repo=main}}), which is used to build and sign an Unified Kernel Image for Secure Boot, no longer works with {{pkg|gummiboot-efistub|repo=testing}}. The default EFI stub is now {{pkg|systemd-efistub|repo=main}} (don’t worry, it provides just the EFI stub files, nothing more), but you can also use {{pkg|stubbyboot-efistub|repo=community}}.

Provided you haven’t overwritten the <code>efistub_file</code> parameter in {{path|/etc/kernel-hooks.d/secureboot.conf}}, you won’t need to take any action when upgrading – it should install {{pkg|systemd-efistub|repo=main}} automatically and everything should work fine. Otherwise, check the configuration carefully.

The {{pkg|gummiboot-efistub|repo=testing}} package has been moved to the testing repository and it no longer provides the <code>efistub</code> provider. The Gummiboot upstream is gone (it was absorbed by systemd a long time ago) and some users have reported that it has not worked since Alpine v3.21.

=== nginx built with pcre2 ===

Since this release, {{pkg|nginx|repo=main}} and {{pkg|njs|repo=community}} are built with pcre2 (10.x) instead of the old pcre (8.x).

=== OpenRC User services ===

Experimental support for User services are currently available in [[OpenRC#User services|OpenRC]].

== Note-worthy updates ==

As always, many packages were upgraded. Make sure to read the individual release notes of the projects you use.

* BIRD 3.1
* busybox 1.37.0
* Deno 2.3.1
* dovecot 2.4
* GCC 14.2.0
* GNOME 48
* Go 1.24
* ISC BIND 9.20
* KDE Plasma 6.3
* Linux 6.12
* LLVM 20
* LXQt 2.2.0
* nginx 1.28
* NodeJS 22.16 (LTS)
* PHP 8.4
* Qt 6.8
* Ruby 3.4
* Rust 1.87
* wlroots 0.18
* zigbee2mqtt 2.3.0

=== LLVM ===

LLVM 20 is available as {{pkg|llvm}}/{{pkg|clang}} (or {{pkg|llvm20}}/{{pkg|clang20}} explictly) additionally to LLVM 19, 18, 17, 16 and 15. ({{MR|80901}}, {{MR|82502}})

LLD is now also splitted per version and is available as {{pkg|lld20}} (default for {{pkg|lld}}), {{pkg|lld19}} and {{pkg|lld18}}. ({{MR|81774}})

=== woodpecker ===

The {{pkg|woodpecker|repo=community}} CI/CD package has been upgraded from 2.8.0 to 3.6.0. Between version 2.x -> 3.x several changes were made to Woodpecker's API and configuration.

[https://woodpecker-ci.org/migrations#300 2.x -> 3.x migration information can be found here.]

=== dovecot ===

The dovecot package have been upgraded from 2.3 to 2.4 which introduces breaking changes in the configuration format. See [https://doc.dovecot.org/2.4.1/installation/upgrade/2.3-to-2.4.html dovecot documentation] how to migrate.

== Significant removals ==

=== LXD ===

LXD was moved to the testing repository and is therefore not available on Alpine Linux 3.22. It was deprecated in favor of {{pkg|incus}} and {{pkg|incus-feature}} (feature branch).

Take a look at the [https://linuxcontainers.org/incus/docs/main/howto/server_migrate_lxd/ Migration Guide] on how to migrate from LXD to Incus using the {{pkg|incus-conversion}} or {{pkg|incus-feature-conversion}} package.

=== Qt 5 ===

On 26th of May 2025, Qt 5 will be unmaintained upstream. Therefore we're removing unused libraries from our repositories and are migrating the remaining packages to Qt 6.

Applications that still use Qt 5 libraries won't be removed, but libraries without consumers in our repository will.

For more information, see Issue {{Issue|17114}}.

=== Meilisearch ===

<code>meilisearch</code> in aports has not been maintained for a long time. It's removed from Alpine 3.22.

=== Botan 2 ===

Botan2 has reached End of Life and will not be part of 3.22 release

=== pcc (portable C compiler) ===

Unfortunately, upstream's website [https://marc.info/?l=pcc-list&m=170541815829299&w=2 has been offline since 2023-12-11] and hasn't come back online since. AFAIK, there isn't any good alternative source that we can use. The best one we were able to find is an unofficial [https://repo.or.cz/pcc.git repo.or.cz mirror].

As a consequence, other distros (e.g. [https://src.fedoraproject.org/rpms/pcc/c/6e04a3afcbdca49cb4f117e7febdf5ae67a3bed1?branch=rawhide Fedora]) have orphaned pcc and other distros (e.g. Debian) archive very ancient versions of pcc.

=== ruby-grpc ===

GRPC is a huge mess, and we lack the resources to support all its language bindings.

Due to this, we had to also remove ruby-pg_query and sqlint.

[[Category:News]]

Template:AlpineLatest

2025-05-30T13:27:11Z

Ncopa:

<noinclude>{{Template}}
</noinclude>3.22.0

Draft Release Notes for Alpine 3.22.0

2025-05-30T10:40:47Z

Ncopa: Ncopa moved page Draft Release Notes for Alpine 3.22.0 to Release Notes for Alpine 3.22.0 over redirect

#REDIRECT [[Release Notes for Alpine 3.22.0]]

Release Notes for Alpine 3.22.0

2025-05-30T10:40:47Z

Ncopa: Ncopa moved page Draft Release Notes for Alpine 3.22.0 to Release Notes for Alpine 3.22.0 over redirect

As always, make sure to read [[Upgrading Alpine to a new major release]] when upgrading to a new release.

If you experience any issues with the upgrade, please let us know and file an issue in our repositories.

== Important changes ==

=== Preparations for /usr-merge ===

The work on /usr-merge has continued since last release. Precaution from [https://wiki.alpinelinux.org/wiki/Release_Notes_for_Alpine_3.21.0#Preparations_for_/usr-merge previous release] still apply.

== Significant changes ==

=== apk-tools ===

This release is the last release using apk-tools v2.14. The next Alpine v3.23 will include apk-tools v3. The packages and index format are still using the legacy v2 format.

There are a number of new changes in the new apk-tools release. To test apk-tools v3, [https://wiki.alpinelinux.org/wiki/Upgrading_Alpine_Linux_to_a_new_release_branch#Upgrading_to_Edge upgrade to Alpine edge, enable the testing repository] and install {{pkg|apk-tools3}}.

=== KDE Plasma ===

The X11 session for KDE Plasma has been removed. If you had {{pkg|plasma-workspace-x11|branch=v3.21|arch=}} installed make sure to remove it from {{path|/etc/apk/world}}. Wayland is the only available option now.

=== SDL ===

{{pkg|sdl3}} and {{pkg|sdl2-compat}} were moved to the community repository and are now the default SDL provider. To force the installation of {{pkg|sdl2}}, use <code>apk add sdl2</code>.

=== Adwaita Fonts ===

As a result of [https://release.gnome.org/48/#new-fonts GNOME's switch] to {{pkg|adwaita-fonts}}, the default font for GTK-based applications (e.g. {{pkg|vte3}} or {{pkg|libadwaita}} Applications) was changed. If you want to revert or override the fonts, you can use:

<pre>
$ apk add font-cantarell font-adobe-source-code-pro
$ gsettings set org.gnome.desktop.interface font-name 'Cantarell 11'
$ gsettings set org.gnome.desktop.interface monospace-font-name 'Source Code Pro 11'
</pre>

{{pkg|adwaita-fonts}} is pulled in as a dependency of some packages since it broke the default behaviour for various applications.

=== GeoClue ===

Since Mozilla Location Services (MLS), which were used as the geolocation service in geoclue, [https://discourse.mozilla.org/t/retiring-the-mozilla-location-service/128693 has been retired by Mozilla], Alpine switched to [https://beacondb.net/ beaconDB] as the default geolocation provider. ({{MR|76764}})

=== BIRD Routing Daemon ===

The {{pkg|bird|repo=community}} routing daemon package has been upgrade to version 3 which introduces a new multi-threaded architecture. A side effect of this change is [https://trubka.network.cz/pipermail/bird-users/2024-December/017973.html significantly increased memory consumption] of the daemon. This update is configuration-compatible with BIRD v2 but there are some behavioral backwards incompatibilities. Users should read the [https://gitlab.nic.cz/labs/bird/-/blob/stable-v3.0/doc/migration-bird3.md migration guide]. Notably the format of <tt>show route all</tt> has changed as has the format of the logs, which may impact scripts and automation that consume those outputs. Users who require BIRD v2 should install the {{pkg|bird2|repo=community}} package instead.

=== Secure Boot and Gummiboot ===

{{pkg|secureboot-hook|repo=main}} (and its dependency {{pkg|efi-mkuki|repo=main}}), which is used to build and sign an Unified Kernel Image for Secure Boot, no longer works with {{pkg|gummiboot-efistub|repo=testing}}. The default EFI stub is now {{pkg|systemd-efistub|repo=main}} (don’t worry, it provides just the EFI stub files, nothing more), but you can also use {{pkg|stubbyboot-efistub|repo=community}}.

Provided you haven’t overwritten the <code>efistub_file</code> parameter in {{path|/etc/kernel-hooks.d/secureboot.conf}}, you won’t need to take any action when upgrading – it should install {{pkg|systemd-efistub|repo=main}} automatically and everything should work fine. Otherwise, check the configuration carefully.

The {{pkg|gummiboot-efistub|repo=testing}} package has been moved to the testing repository and it no longer provides the <code>efistub</code> provider. The Gummiboot upstream is gone (it was absorbed by systemd a long time ago) and some users have reported that it has not worked since Alpine v3.21.

=== woodpecker ===

The {{pkg|woodpecker|repo=community}} CI/CD package has been upgraded from 2.8.0 to 3.6.0. Between version 2.x -> 3.x several changes were made to Woodpecker's API and configuration.

[https://woodpecker-ci.org/migrations#300 2.x -> 3.x migration information can be found here.]

== Note-worthy updates ==

As always, many packages were upgraded. Make sure to read the individual release notes of the projects you use.

* BIRD 3.1
* busybox 1.37.0
* GCC 14.2.0
* GNOME 48
* Go 1.24
* ISC BIND 9.20
* KDE Plasma 6.3
* Linux 6.12
* LLVM 20
* LXQt 2.2.0
* nginx 1.28
* NodeJS 22.16 (LTS)
* PHP 8.4
* Qt 6.8
* Ruby 3.4
* Rust 1.87
* wlroots 0.18

=== LLVM ===

LLVM 20 is available as {{pkg|llvm}}/{{pkg|clang}} (or {{pkg|llvm20}}/{{pkg|clang20}} explictly) additionally to LLVM 19, 18, 17, 16 and 15. ({{MR|80901}}, {{MR|82502}})

LLD is now also splitted per version and is available as {{pkg|lld20}} (default for {{pkg|lld}}), {{pkg|lld19}} and {{pkg|lld18}}. ({{MR|81774}})

== Significant removals ==

=== LXD ===

LXD was moved to the testing repository and is therefore not available on Alpine Linux 3.22. It was deprecated in favor of {{pkg|incus}} and {{pkg|incus-feature}} (feature branch).

Take a look at the [https://linuxcontainers.org/incus/docs/main/howto/server_migrate_lxd/ Migration Guide] on how to migrate from LXD to Incus using the {{pkg|incus-conversion}} or {{pkg|incus-feature-conversion}} package.

=== Qt 5 ===

On 26th of May 2025, Qt 5 will be unmaintained upstream. Therefore we're removing unused libraries from our repositories and are migrating the remaining packages to Qt 6.

Applications that still use Qt 5 libraries won't be removed, but libraries without consumers in our repository will.

For more information, see Issue {{Issue|17114}}.

=== Meilisearch ===

<code>meilisearch</code> in aports has not been maintained for a long time. It's removed from Alpine 3.22.

=== Botan 2 ===

Botan2 has reached End of Life and will not be part of 3.22 release

Template:AlpineLatest

2025-02-14T00:23:07Z

Ncopa: bump 3.21.3

<noinclude>{{Template}}
</noinclude>3.21.3

Template:AlpineLatest

2025-01-08T12:39:01Z

Ncopa:

<noinclude>{{Template}}
</noinclude>3.21.2

Template:AlpineLatest

2025-01-06T19:27:15Z

Ncopa: bump 3.21.1

<noinclude>{{Template}}
</noinclude>3.21.1

Template:AlpineLatest

2024-12-05T18:02:05Z

Ncopa:

<noinclude>{{Template}}
</noinclude>3.21.0

Release Notes for Alpine 3.21.0

2024-12-05T11:07:38Z

Ncopa: /* Preparations for /usr-merge */

As always, make sure to read [[Upgrading Alpine to a new major release]] when upgrading to a new release.

If you experience any issues with the upgrade, please let us know and file an issue in our repositories.

== Important changes ==

=== OpenSSH service requires restart ===

From the <code>9.8_p1</code> release, and on, of {{pkg|openssh}}, {{pkg|openssh-server}} is split into two binaries (<code>/usr/lib/ssh/sshd-session</code> and <code>/usr/sbin/sshd</code>). Due to this change, it will not be possible to <code>ssh</code> into a system that has upgraded from a release prior to <code>9.8_p1</code> to this release or later, without restarting the <code>sshd</code> service.

We have previously brought attention to this - https://alpinelinux.org/posts/2024-07-02-openssh-upgrade-edge.html

Managing services has always been out-of-scope for {{pkg|apk-tools}}, but this one time we will '''make an exception''' when the following conditions are met:
# You have both the {{pkg|openssh-server}} and {{pkg|openssh-server-common-openrc}} packages installed at a version lower than <code>9.8_p1</code>
# The <code>sshd</code> service is started

We will then, post {{pkg|openssh-server}} upgrade, have a <code>post-upgrade</code> script that will:
# Print a message on what is about to happen and why
# Restart the <code>sshd</code> service
# If the command to restart the service fails for any reason, a warning message will be printed and an error code returned to <code>apk</code>, to be noticed by the end of the package upgrades (this will not interrupt the upgrade process).

We have decided to do this in order to help keep you from getting locked out of your system(s) and be able to fix any issues with the upgrade.

See also:
* https://bugzilla.mindrot.org/show_bug.cgi?id=3706
* https://git.alpinelinux.org/aports/commit/?id=6adff08ae09961d4eea66b55a8cca14d3941fb53

=== New loongarch64 architecture ===

Alpine 3.21 is the first release which is available for <code>loongarch64</code>.

Thanks to the support of the team of Loongson dedicated to supporting Alpine Linux and many other contributors.

=== Preparations for /usr-merge ===

Plans for /usr-merge are underway and we should be able to finalize it in Alpine Linux, version 3.22.

Much preparation has gone into this release to ensure that the merge happens as smoothly as possible. That included moving the location of some binaries and many libraries from <code>/bin</code>, <code>/sbin</code>, and <code>/lib</code> to their counterparts in <code>/usr</code>. As part of the merge, <code>/usr</code> will be mounted from the initramfs to make sure everybody has all necessary binaries in place.

'''Users with installations where <code>/</code> and <code>/usr</code> are on separate filesystems (partitions, volumes, disk drives or other) should proceed with care and report any issues.''' They should also ensure that an entry <code>/usr</code> is added to <code>/etc/fstab</code> before upgrading, and all modules required to mount <code>/usr</code> from the initramfs are added to mkinitfs configuration. New/fresh installations of v3.21 will work out of the box without modification. Please note that <code>/</code> on separate filesystem than <code>/usr</code> is not officially supported.

If you have one of these setups, and have doubts about the configuration, you can open an [https://gitlab.alpinelinux.org/alpine/aports/-/issues/new issue] and ping <code>@pabloyoyoista</code>. We will also publish a blog post soon with further information on the timeline and progress of the merge, as well as how the changes may affect users.

== Significant changes ==

=== Jellyfin ===

Jellyfin now uses the recommended fork of ffmpeg called {{pkg|jellyfin-ffmpeg}} by default. If you want to change the default, take a look at the <code>ffmpegpath</code> variable in <code>/etc/conf.d/jellyfin</code>. ({{MR|69924}})

Jellyfin was disabled for ARM architectures (<code>aarch64</code> and <code>armv7</code>) and is only available for <code>x86_64</code>. ({{Issue|16613}})

=== Bats ===

<code>main/bats</code> was renamed to <code>main/bats-core</code>. There is now a meta package <code>community/bats</code> which contains:

* {{pkg|bats-core}}
* {{pkg|bats-file}}
* {{pkg|bats-support}}
* {{pkg|bats-assert}}

=== Xen 4.19 ===

''qemu-traditional'' and ''stubdom'' are removed from the build in this release, see https://git.alpinelinux.org/aports/commit/?id=24217a24da3924039b000eb17c04bf3f01bf1f12

There is still the {{pkg|xen-qemu}} package, but the regular {{pkg|qemu}} aport [https://git.alpinelinux.org/aports/commit/?id=a9249e2e0de827e88d84c01f9731aeebd248be13 is now built with Xen support], so a {{pkg|qemu-system-*}} package can be used instead.

You can choose to use it in your ''xl.cfg(1)'' like so:
<pre>
device_model_override = "/usr/bin/qemu-system-x86_64"
device_model_version = "qemu-xen"
</pre>

=== uutils-coreutils ===

{{pkg|uutils-coreutils}} is repackaged as a sub-package to {{pkg|uutils}} in such a way as to be a drop-in replacement for GNU {{pkg|coreutils}}.

If you have both {{pkg|uutils-coreutils}} and {{pkg|coreutils}} installed, the latter will be '''purged''' and its symlinks replaced with ones pointing to the <code>/usr/bin/uutils</code> binary. The <code>/usr/bin/uutils-*</code> symlinks, previously provided by {{pkg|uutils-coreutils}}, no longer exist.

If you prefer to use GNU {{pkg|coreutils}}, remove the {{pkg|uutils-coreutils}} package before upgrading, and then add the {{pkg|uutils}} package, containing the <code>/usr/bin/uutils</code> binary.

A few parts of the {{pkg|uutils}} aport are also split into {{pkg|uutils-*}} subpackages, to avoid conflicts or other issues.

=== linux-firmware ===

{{pkg|linux-firmware}} is now compressed with ZSTD compression. If you run a custom built Linux kernel, you need to ensure that <code>CONFIG_FW_LOADER_COMPRESS_ZSTD=y</code> is set in your configuration.

== Note-worthy updates ==

As always, a lot of packages were upgraded. Make sure to read the indivdual release notes of the projects you use.

* Linux 6.12
* busybox 1.37
* GCC 14.2
* LLVM 19
* Go 1.23
* Rust 1.83
* PHP 8.4
* GNOME 47
* KDE Plasma 6.2
* LXQt 2.1
* Qt 6.8
* wlroots 18

=== GCC 14 ===

The Gnu Compiler Collection was upgraded to 14.2.0 and as a result, all packages built with {{pkg|gcc}} in Alpine 3.21 are compiled with GCC 14.2.0.

Make sure to read all changes: https://gcc.gnu.org/gcc-14/changes.html

=== LXQt 2.1 ===

LXQt has been updated to release 2.1.0
* It now uses Qt6
* Many parts of LXQt are now Wayland ready¹, but Wayland ports of the following are pending: {{pkg|screengrab}}, {{pkg|lxqt-globalkeys}}, and keyboard indicator, some input settings, as well as settings for monitor, power button, and screen locker.
* LXQt Panel has a new default application menu called Fancy Menu.
¹ [https://github.com/lxqt/lxqt-wayland-session lxqt-wayland-session] has not been packaged yet, but most folks wanting to test on Wayland will want to use it.

=== Linux 6.12 ===

Alpine 3.21.0 ships Linux 6.12.1 in the {{pkg|linux-lts}} package.

=== PostgreSQL 17 ===

This release features {{pkg|postgresql17}}. We dropped support for {{pkg|postgresql14}}, and moved {{pkg|postgreSQL15}} from main to community.

=== LLVM 19 ===

We packaged LLVM 19 in our repositories. A total of 5 LLVM versions are supported: {{pkg|llvm19}}, {{pkg|llvm18}}, {{pkg|llvm17}}, {{pkg|llvm16}}, {{pkg|llvm15}}.

== Significant removals ==

=== Disabled packages due to FTBS ===

The following packages are temporarily disabled because they failed to build. We will try to restore them as soon as possible.

* {{pkg|hplip}} ({{Issue|16685}})
* {{pkg|imageflow}} ({{Issue|16679}})
* {{pkg|kdevelop}} ({{MR|75839}})
* {{pkg|postgresql-citus}} ({{Issue|16580}})
* {{pkg|uvicorn}} ({{Issue|16646}})
* {{pkg|vulkan-validation-layers}} ({{Issue|16686}})

=== ISC DHCP ===

If you are still running an ISC DHCP server, you are advised to migrate to a maintained alternative '''before''' upgrading to the 3.21 release.

ISC DHCP has been EoL since 2022. They have a guide for migrating to {{pkg|kea}} here: https://www.isc.org/dhcp_migration/

Up to, and including, the 3.20 version of Alpine, the {{pkg|dhcp|branch=v3.20}} aport has the subpackage {{pkg|keama|branch=v3.20}} that is a tool for helping with migration from ISC DHCP configuration to ISC Kea configuration.

Alternative DHCP servers packaged in Alpine include:
* {{pkg|kea}}
* {{pkg|freeradius-dhcp}}
* {{pkg|dnsmasq}}
* udhcpd - packaged in {{pkg|busybox-extras}}

=== Gogs ===

<code>gogs</code> was removed due to multiple high-severity vulnerabilities for which issues have remained open for a year. The developers of Gogs were contacted multiple times by the Forgejo team but unfortunately received no response. Therefore we have removed Gogs from our repositories. ({{MR|75304}})

Please consider migrating to {{pkg|forgejo|branch=edge|arch=}} or {{pkg|gitea|branch=edge|arch=}}. Both forks are available in our community repo.

The Gitea fork of Gogs was created in 2016 by contributors who were frustrated with the single-maintainer management model of Gogs. Forgejo is a fork of Gitea which was created as a result of the for-profit company Gitea Ltd taking over maintainership (see also https://forgejo.org/compare-to-gitea/).

=== neofetch ===

The upstream repository was archived in April and became unmaintained, therefore we have removed it from our repositories. {{pkg|fastfetch}} provides similar functionality.

Release Notes for Alpine 3.21.0

2024-12-05T11:03:21Z

Ncopa: /* Preparations for /usr-merge */

As always, make sure to read [[Upgrading Alpine to a new major release]] when upgrading to a new release.

If you experience any issues with the upgrade, please let us know and file an issue in our repositories.

== Important changes ==

=== OpenSSH service requires restart ===

From the <code>9.8_p1</code> release, and on, of {{pkg|openssh}}, {{pkg|openssh-server}} is split into two binaries (<code>/usr/lib/ssh/sshd-session</code> and <code>/usr/sbin/sshd</code>). Due to this change, it will not be possible to <code>ssh</code> into a system that has upgraded from a release prior to <code>9.8_p1</code> to this release or later, without restarting the <code>sshd</code> service.

We have previously brought attention to this - https://alpinelinux.org/posts/2024-07-02-openssh-upgrade-edge.html

Managing services has always been out-of-scope for {{pkg|apk-tools}}, but this one time we will '''make an exception''' when the following conditions are met:
# You have both the {{pkg|openssh-server}} and {{pkg|openssh-server-common-openrc}} packages installed at a version lower than <code>9.8_p1</code>
# The <code>sshd</code> service is started

We will then, post {{pkg|openssh-server}} upgrade, have a <code>post-upgrade</code> script that will:
# Print a message on what is about to happen and why
# Restart the <code>sshd</code> service
# If the command to restart the service fails for any reason, a warning message will be printed and an error code returned to <code>apk</code>, to be noticed by the end of the package upgrades (this will not interrupt the upgrade process).

We have decided to do this in order to help keep you from getting locked out of your system(s) and be able to fix any issues with the upgrade.

See also:
* https://bugzilla.mindrot.org/show_bug.cgi?id=3706
* https://git.alpinelinux.org/aports/commit/?id=6adff08ae09961d4eea66b55a8cca14d3941fb53

=== New loongarch64 architecture ===

Alpine 3.21 is the first release which is available for <code>loongarch64</code>.

Thanks to the support of the team of Loongson dedicated to supporting Alpine Linux and many other contributors.

=== Preparations for /usr-merge ===

Plans for /usr-merge are underway and we should be able to finalize it in Alpine Linux, version 3.22.

Much preparation has gone into this release to ensure that the merge happens as smoothly as possible. That included moving the location of some binaries and many libraries from <code>/bin</code>, <code>/sbin</code>, and <code>/lib</code> to their counterparts in <code>/usr</code>. As part of the merge, <code>/usr</code> will be mounted from the initramfs to make sure everybody has all necessary binaries in place.

'''Users with installations where <code>/</code> and <code>/usr</code> are on separate filesystems (partitions, volumes, disk drives or other) should proceed with care and report any issues.''' They should also ensure that an entry <code>/usr</code> is added to <code>/etc/fstab</code> before upgrading, and all modules required to mount <code>/usr</code> from the initramfs are added to mkinitfs configuration. New/fresh installations of v3.21 will work out of the box without modification. Please note that <code>/</code> on separate filesystem than <code>/usr</code> is not supported.

If you have one of these setups, and have doubts about the configuration, you can open an [https://gitlab.alpinelinux.org/alpine/aports/-/issues/new issue] and ping <code>@pabloyoyoista</code>. We will also publish a blog post soon with further information on the timeline and progress of the merge, as well as how the changes may affect users.

== Significant changes ==

=== Jellyfin ===

Jellyfin now uses the recommended fork of ffmpeg called {{pkg|jellyfin-ffmpeg}} by default. If you want to change the default, take a look at the <code>ffmpegpath</code> variable in <code>/etc/conf.d/jellyfin</code>. ({{MR|69924}})

Jellyfin was disabled for ARM architectures (<code>aarch64</code> and <code>armv7</code>) and is only available for <code>x86_64</code>. ({{Issue|16613}})

=== Bats ===

<code>main/bats</code> was renamed to <code>main/bats-core</code>. There is now a meta package <code>community/bats</code> which contains:

* {{pkg|bats-core}}
* {{pkg|bats-file}}
* {{pkg|bats-support}}
* {{pkg|bats-assert}}

=== Xen 4.19 ===

''qemu-traditional'' and ''stubdom'' are removed from the build in this release, see https://git.alpinelinux.org/aports/commit/?id=24217a24da3924039b000eb17c04bf3f01bf1f12

There is still the {{pkg|xen-qemu}} package, but the regular {{pkg|qemu}} aport [https://git.alpinelinux.org/aports/commit/?id=a9249e2e0de827e88d84c01f9731aeebd248be13 is now built with Xen support], so a {{pkg|qemu-system-*}} package can be used instead.

You can choose to use it in your ''xl.cfg(1)'' like so:
<pre>
device_model_override = "/usr/bin/qemu-system-x86_64"
device_model_version = "qemu-xen"
</pre>

=== uutils-coreutils ===

{{pkg|uutils-coreutils}} is repackaged as a sub-package to {{pkg|uutils}} in such a way as to be a drop-in replacement for GNU {{pkg|coreutils}}.

If you have both {{pkg|uutils-coreutils}} and {{pkg|coreutils}} installed, the latter will be '''purged''' and its symlinks replaced with ones pointing to the <code>/usr/bin/uutils</code> binary. The <code>/usr/bin/uutils-*</code> symlinks, previously provided by {{pkg|uutils-coreutils}}, no longer exist.

If you prefer to use GNU {{pkg|coreutils}}, remove the {{pkg|uutils-coreutils}} package before upgrading, and then add the {{pkg|uutils}} package, containing the <code>/usr/bin/uutils</code> binary.

A few parts of the {{pkg|uutils}} aport are also split into {{pkg|uutils-*}} subpackages, to avoid conflicts or other issues.

=== linux-firmware ===

{{pkg|linux-firmware}} is now compressed with ZSTD compression. If you run a custom built Linux kernel, you need to ensure that <code>CONFIG_FW_LOADER_COMPRESS_ZSTD=y</code> is set in your configuration.

== Note-worthy updates ==

As always, a lot of packages were upgraded. Make sure to read the indivdual release notes of the projects you use.

* Linux 6.12
* busybox 1.37
* GCC 14.2
* LLVM 19
* Go 1.23
* Rust 1.83
* PHP 8.4
* GNOME 47
* KDE Plasma 6.2
* LXQt 2.1
* Qt 6.8
* wlroots 18

=== GCC 14 ===

The Gnu Compiler Collection was upgraded to 14.2.0 and as a result, all packages built with {{pkg|gcc}} in Alpine 3.21 are compiled with GCC 14.2.0.

Make sure to read all changes: https://gcc.gnu.org/gcc-14/changes.html

=== LXQt 2.1 ===

LXQt has been updated to release 2.1.0
* It now uses Qt6
* Many parts of LXQt are now Wayland ready¹, but Wayland ports of the following are pending: {{pkg|screengrab}}, {{pkg|lxqt-globalkeys}}, and keyboard indicator, some input settings, as well as settings for monitor, power button, and screen locker.
* LXQt Panel has a new default application menu called Fancy Menu.
¹ [https://github.com/lxqt/lxqt-wayland-session lxqt-wayland-session] has not been packaged yet, but most folks wanting to test on Wayland will want to use it.

=== Linux 6.12 ===

Alpine 3.21.0 ships Linux 6.12.1 in the {{pkg|linux-lts}} package.

=== PostgreSQL 17 ===

This release features {{pkg|postgresql17}}. We dropped support for {{pkg|postgresql14}}, and moved {{pkg|postgreSQL15}} from main to community.

=== LLVM 19 ===

We packaged LLVM 19 in our repositories. A total of 5 LLVM versions are supported: {{pkg|llvm19}}, {{pkg|llvm18}}, {{pkg|llvm17}}, {{pkg|llvm16}}, {{pkg|llvm15}}.

== Significant removals ==

=== Disabled packages due to FTBS ===

The following packages are temporarily disabled because they failed to build. We will try to restore them as soon as possible.

* {{pkg|hplip}} ({{Issue|16685}})
* {{pkg|imageflow}} ({{Issue|16679}})
* {{pkg|kdevelop}} ({{MR|75839}})
* {{pkg|postgresql-citus}} ({{Issue|16580}})
* {{pkg|uvicorn}} ({{Issue|16646}})
* {{pkg|vulkan-validation-layers}} ({{Issue|16686}})

=== ISC DHCP ===

If you are still running an ISC DHCP server, you are advised to migrate to a maintained alternative '''before''' upgrading to the 3.21 release.

ISC DHCP has been EoL since 2022. They have a guide for migrating to {{pkg|kea}} here: https://www.isc.org/dhcp_migration/

Up to, and including, the 3.20 version of Alpine, the {{pkg|dhcp|branch=v3.20}} aport has the subpackage {{pkg|keama|branch=v3.20}} that is a tool for helping with migration from ISC DHCP configuration to ISC Kea configuration.

Alternative DHCP servers packaged in Alpine include:
* {{pkg|kea}}
* {{pkg|freeradius-dhcp}}
* {{pkg|dnsmasq}}
* udhcpd - packaged in {{pkg|busybox-extras}}

=== Gogs ===

<code>gogs</code> was removed due to multiple high-severity vulnerabilities for which issues have remained open for a year. The developers of Gogs were contacted multiple times by the Forgejo team but unfortunately received no response. Therefore we have removed Gogs from our repositories. ({{MR|75304}})

Please consider migrating to {{pkg|forgejo|branch=edge|arch=}} or {{pkg|gitea|branch=edge|arch=}}. Both forks are available in our community repo.

The Gitea fork of Gogs was created in 2016 by contributors who were frustrated with the single-maintainer management model of Gogs. Forgejo is a fork of Gitea which was created as a result of the for-profit company Gitea Ltd taking over maintainership (see also https://forgejo.org/compare-to-gitea/).

=== neofetch ===

The upstream repository was archived in April and became unmaintained, therefore we have removed it from our repositories. {{pkg|fastfetch}} provides similar functionality.

Draft Release Notes for Alpine 3.21.0

2024-12-05T10:50:13Z

Ncopa: Ncopa moved page Draft Release Notes for Alpine 3.21.0 to Release Notes for Alpine 3.21.0 over redirect

#REDIRECT [[Release Notes for Alpine 3.21.0]]

Release Notes for Alpine 3.21.0

2024-12-05T10:50:13Z

Ncopa: Ncopa moved page Draft Release Notes for Alpine 3.21.0 to Release Notes for Alpine 3.21.0 over redirect

As always, make sure to read [[Upgrading Alpine to a new major release]] when upgrading to a new release.

If you experience any issues with the upgrade, please let us know and file an issue in our repositories.

== Important changes ==

=== OpenSSH service requires restart ===

From the <code>9.8_p1</code> release, and on, of {{pkg|openssh}}, {{pkg|openssh-server}} is split into two binaries (<code>/usr/lib/ssh/sshd-session</code> and <code>/usr/sbin/sshd</code>). Due to this change, it will not be possible to <code>ssh</code> into a system that has upgraded from a release prior to <code>9.8_p1</code> to this release or later, without restarting the <code>sshd</code> service.

We have previously brought attention to this - https://alpinelinux.org/posts/2024-07-02-openssh-upgrade-edge.html

Managing services has always been out-of-scope for {{pkg|apk-tools}}, but this one time we will '''make an exception''' when the following conditions are met:
# You have both the {{pkg|openssh-server}} and {{pkg|openssh-server-common-openrc}} packages installed at a version lower than <code>9.8_p1</code>
# The <code>sshd</code> service is started

We will then, post {{pkg|openssh-server}} upgrade, have a <code>post-upgrade</code> script that will:
# Print a message on what is about to happen and why
# Restart the <code>sshd</code> service
# If the command to restart the service fails for any reason, a warning message will be printed and an error code returned to <code>apk</code>, to be noticed by the end of the package upgrades (this will not interrupt the upgrade process).

We have decided to do this in order to help keep you from getting locked out of your system(s) and be able to fix any issues with the upgrade.

See also:
* https://bugzilla.mindrot.org/show_bug.cgi?id=3706
* https://git.alpinelinux.org/aports/commit/?id=6adff08ae09961d4eea66b55a8cca14d3941fb53

=== New loongarch64 architecture ===

Alpine 3.21 is the first release which is available for <code>loongarch64</code>.

Thanks to the support of the team of Loongson dedicated to supporting Alpine Linux and many other contributors.

=== Preparations for /usr-merge ===

Plans for /usr-merge are underway and we should be able to finalize it in Alpine Linux, version 3.22.

Much preparation has gone into this release to ensure that the merge happens as smoothly as possible. That included moving the location of some binaries and many libraries from <code>/bin</code>, <code>/sbin</code>, and <code>/lib</code> to their counterparts in <code>/usr</code>. As part of the merge, <code>/usr</code> will be mounted from the initramfs to make sure everybody has all necessary binaries in place.

'''Users with installations where <code>/</code> and <code>/usr</code> are on separate filesystems (partitions, volumes, disk drives or other) should proceed with care and report any issues.''' They should also ensure that an entry <code>/usr</code> is added to <code>/etc/fstab</code> before upgrading, and all modules required to mount <code>/usr</code> from the initramfs are added to mkinitfs configuration. New/fresh installations of v3.21 will work out of the box without modification.

If you have one of these setups, and have doubts about the configuration, you can open an [https://gitlab.alpinelinux.org/alpine/aports/-/issues/new issue] and ping <code>@pabloyoyoista</code>. We will also publish a blog post soon with further information on the timeline and progress of the merge, as well as how the changes may affect users.

Please note that this setup is already not supported.

== Significant changes ==

=== Jellyfin ===

Jellyfin now uses the recommended fork of ffmpeg called {{pkg|jellyfin-ffmpeg}} by default. If you want to change the default, take a look at the <code>ffmpegpath</code> variable in <code>/etc/conf.d/jellyfin</code>. ({{MR|69924}})

Jellyfin was disabled for ARM architectures (<code>aarch64</code> and <code>armv7</code>) and is only available for <code>x86_64</code>. ({{Issue|16613}})

=== Bats ===

<code>main/bats</code> was renamed to <code>main/bats-core</code>. There is now a meta package <code>community/bats</code> which contains:

* {{pkg|bats-core}}
* {{pkg|bats-file}}
* {{pkg|bats-support}}
* {{pkg|bats-assert}}

=== Xen 4.19 ===

''qemu-traditional'' and ''stubdom'' are removed from the build in this release, see https://git.alpinelinux.org/aports/commit/?id=24217a24da3924039b000eb17c04bf3f01bf1f12

There is still the {{pkg|xen-qemu}} package, but the regular {{pkg|qemu}} aport [https://git.alpinelinux.org/aports/commit/?id=a9249e2e0de827e88d84c01f9731aeebd248be13 is now built with Xen support], so a {{pkg|qemu-system-*}} package can be used instead.

You can choose to use it in your ''xl.cfg(1)'' like so:
<pre>
device_model_override = "/usr/bin/qemu-system-x86_64"
device_model_version = "qemu-xen"
</pre>

=== uutils-coreutils ===

{{pkg|uutils-coreutils}} is repackaged as a sub-package to {{pkg|uutils}} in such a way as to be a drop-in replacement for GNU {{pkg|coreutils}}.

If you have both {{pkg|uutils-coreutils}} and {{pkg|coreutils}} installed, the latter will be '''purged''' and its symlinks replaced with ones pointing to the <code>/usr/bin/uutils</code> binary. The <code>/usr/bin/uutils-*</code> symlinks, previously provided by {{pkg|uutils-coreutils}}, no longer exist.

If you prefer to use GNU {{pkg|coreutils}}, remove the {{pkg|uutils-coreutils}} package before upgrading, and then add the {{pkg|uutils}} package, containing the <code>/usr/bin/uutils</code> binary.

A few parts of the {{pkg|uutils}} aport are also split into {{pkg|uutils-*}} subpackages, to avoid conflicts or other issues.

=== linux-firmware ===

{{pkg|linux-firmware}} is now compressed with ZSTD compression. If you run a custom built Linux kernel, you need to ensure that <code>CONFIG_FW_LOADER_COMPRESS_ZSTD=y</code> is set in your configuration.

== Note-worthy updates ==

As always, a lot of packages were upgraded. Make sure to read the indivdual release notes of the projects you use.

* Linux 6.12
* busybox 1.37
* GCC 14.2
* LLVM 19
* Go 1.23
* Rust 1.83
* PHP 8.4
* GNOME 47
* KDE Plasma 6.2
* LXQt 2.1
* Qt 6.8
* wlroots 18

=== GCC 14 ===

The Gnu Compiler Collection was upgraded to 14.2.0 and as a result, all packages built with {{pkg|gcc}} in Alpine 3.21 are compiled with GCC 14.2.0.

Make sure to read all changes: https://gcc.gnu.org/gcc-14/changes.html

=== LXQt 2.1 ===

LXQt has been updated to release 2.1.0
* It now uses Qt6
* Many parts of LXQt are now Wayland ready¹, but Wayland ports of the following are pending: {{pkg|screengrab}}, {{pkg|lxqt-globalkeys}}, and keyboard indicator, some input settings, as well as settings for monitor, power button, and screen locker.
* LXQt Panel has a new default application menu called Fancy Menu.
¹ [https://github.com/lxqt/lxqt-wayland-session lxqt-wayland-session] has not been packaged yet, but most folks wanting to test on Wayland will want to use it.

=== Linux 6.12 ===

Alpine 3.21.0 ships Linux 6.12.1 in the {{pkg|linux-lts}} package.

=== PostgreSQL 17 ===

This release features {{pkg|postgresql17}}. We dropped support for {{pkg|postgresql14}}, and moved {{pkg|postgreSQL15}} from main to community.

=== LLVM 19 ===

We packaged LLVM 19 in our repositories. A total of 5 LLVM versions are supported: {{pkg|llvm19}}, {{pkg|llvm18}}, {{pkg|llvm17}}, {{pkg|llvm16}}, {{pkg|llvm15}}.

== Significant removals ==

=== Disabled packages due to FTBS ===

The following packages are temporarily disabled because they failed to build. We will try to restore them as soon as possible.

* {{pkg|hplip}} ({{Issue|16685}})
* {{pkg|imageflow}} ({{Issue|16679}})
* {{pkg|kdevelop}} ({{MR|75839}})
* {{pkg|postgresql-citus}} ({{Issue|16580}})
* {{pkg|uvicorn}} ({{Issue|16646}})
* {{pkg|vulkan-validation-layers}} ({{Issue|16686}})

=== ISC DHCP ===

If you are still running an ISC DHCP server, you are advised to migrate to a maintained alternative '''before''' upgrading to the 3.21 release.

ISC DHCP has been EoL since 2022. They have a guide for migrating to {{pkg|kea}} here: https://www.isc.org/dhcp_migration/

Up to, and including, the 3.20 version of Alpine, the {{pkg|dhcp|branch=v3.20}} aport has the subpackage {{pkg|keama|branch=v3.20}} that is a tool for helping with migration from ISC DHCP configuration to ISC Kea configuration.

Alternative DHCP servers packaged in Alpine include:
* {{pkg|kea}}
* {{pkg|freeradius-dhcp}}
* {{pkg|dnsmasq}}
* udhcpd - packaged in {{pkg|busybox-extras}}

=== Gogs ===

<code>gogs</code> was removed due to multiple high-severity vulnerabilities for which issues have remained open for a year. The developers of Gogs were contacted multiple times by the Forgejo team but unfortunately received no response. Therefore we have removed Gogs from our repositories. ({{MR|75304}})

Please consider migrating to {{pkg|forgejo|branch=edge|arch=}} or {{pkg|gitea|branch=edge|arch=}}. Both forks are available in our community repo.

The Gitea fork of Gogs was created in 2016 by contributors who were frustrated with the single-maintainer management model of Gogs. Forgejo is a fork of Gitea which was created as a result of the for-profit company Gitea Ltd taking over maintainership (see also https://forgejo.org/compare-to-gitea/).

=== neofetch ===

The upstream repository was archived in April and became unmaintained, therefore we have removed it from our repositories. {{pkg|fastfetch}} provides similar functionality.

Release Notes for Alpine 3.21.0

2024-12-05T10:35:09Z

Ncopa: /* Linux 6.12 */ remove irrelevant paragraph about linux-headers

As always, make sure to read [[Upgrading Alpine to a new major release]] when upgrading to a new release.

If you experience any issues with the upgrade, please let us know and file an issue in our repositories.

== Important changes ==

=== OpenSSH service requires restart ===

From the <code>9.8_p1</code> release, and on, of {{pkg|openssh}}, {{pkg|openssh-server}} is split into two binaries (<code>/usr/lib/ssh/sshd-session</code> and <code>/usr/sbin/sshd</code>). Due to this change, it will not be possible to <code>ssh</code> into a system that has upgraded from a release prior to <code>9.8_p1</code> to this release or later, without restarting the <code>sshd</code> service.

We have previously brought attention to this - https://alpinelinux.org/posts/2024-07-02-openssh-upgrade-edge.html

Managing services has always been out-of-scope for {{pkg|apk-tools}}, but this one time we will '''make an exception''' when the following conditions are met:
# You have both the {{pkg|openssh-server}} and {{pkg|openssh-server-common-openrc}} packages installed at a version lower than <code>9.8_p1</code>
# The <code>sshd</code> service is started

We will then, post {{pkg|openssh-server}} upgrade, have a <code>post-upgrade</code> script that will:
# Print a message on what is about to happen and why
# Restart the <code>sshd</code> service
# If the command to restart the service fails for any reason, a warning message will be printed and an error code returned to <code>apk</code>, to be noticed by the end of the package upgrades (this will not interrupt the upgrade process).

We have decided to do this in order to help keep you from getting locked out of your system(s) and be able to fix any issues with the upgrade.

See also:
* https://bugzilla.mindrot.org/show_bug.cgi?id=3706
* https://git.alpinelinux.org/aports/commit/?id=6adff08ae09961d4eea66b55a8cca14d3941fb53

=== New loongarch64 architecture ===

Alpine 3.21 is the first release which is available for <code>loongarch64</code>.

Thanks to the support of the team of Loongson dedicated to supporting Alpine Linux and many other contributors.

=== Preparations for /usr-merge ===

Plans for /usr-merge are underway and we should be able to finalize it in Alpine Linux, version 3.22.

Much preparation has gone into this release to ensure that the merge happens as smoothly as possible. That included moving the location of some binaries and many libraries from <code>/bin</code>, <code>/sbin</code>, and <code>/lib</code> to their counterparts in <code>/usr</code>. As part of the merge, <code>/usr</code> will be mounted from the initramfs to make sure everybody has all necessary binaries in place.

'''Users with installations where <code>/</code> and <code>/usr</code> are on separate filesystems (partitions, volumes, disk drives or other) should proceed with care and report any issues.''' They should also ensure that an entry <code>/usr</code> is added to <code>/etc/fstab</code> before upgrading, and all modules required to mount <code>/usr</code> from the initramfs are added to mkinitfs configuration. New/fresh installations of v3.21 will work out of the box without modification.

If you have one of these setups, and have doubts about the configuration, you can open an [https://gitlab.alpinelinux.org/alpine/aports/-/issues/new issue] and ping <code>@pabloyoyoista</code>. We will also publish a blog post soon with further information on the timeline and progress of the merge, as well as how the changes may affect users.

Please note that this setup is already not supported.

== Significant changes ==

=== Jellyfin ===

Jellyfin now uses the recommended fork of ffmpeg called {{pkg|jellyfin-ffmpeg}} by default. If you want to change the default, take a look at the <code>ffmpegpath</code> variable in <code>/etc/conf.d/jellyfin</code>. ({{MR|69924}})

Jellyfin was disabled for ARM architectures (<code>aarch64</code> and <code>armv7</code>) and is only available for <code>x86_64</code>. ({{Issue|16613}})

=== Bats ===

<code>main/bats</code> was renamed to <code>main/bats-core</code>. There is now a meta package <code>community/bats</code> which contains:

* {{pkg|bats-core}}
* {{pkg|bats-file}}
* {{pkg|bats-support}}
* {{pkg|bats-assert}}

=== Xen 4.19 ===

''qemu-traditional'' and ''stubdom'' are removed from the build in this release, see https://git.alpinelinux.org/aports/commit/?id=24217a24da3924039b000eb17c04bf3f01bf1f12

There is still the {{pkg|xen-qemu}} package, but the regular {{pkg|qemu}} aport [https://git.alpinelinux.org/aports/commit/?id=a9249e2e0de827e88d84c01f9731aeebd248be13 is now built with Xen support], so a {{pkg|qemu-system-*}} package can be used instead.

You can choose to use it in your ''xl.cfg(1)'' like so:
<pre>
device_model_override = "/usr/bin/qemu-system-x86_64"
device_model_version = "qemu-xen"
</pre>

=== uutils-coreutils ===

{{pkg|uutils-coreutils}} is repackaged as a sub-package to {{pkg|uutils}} in such a way as to be a drop-in replacement for GNU {{pkg|coreutils}}.

If you have both {{pkg|uutils-coreutils}} and {{pkg|coreutils}} installed, the latter will be '''purged''' and its symlinks replaced with ones pointing to the <code>/usr/bin/uutils</code> binary. The <code>/usr/bin/uutils-*</code> symlinks, previously provided by {{pkg|uutils-coreutils}}, no longer exist.

If you prefer to use GNU {{pkg|coreutils}}, remove the {{pkg|uutils-coreutils}} package before upgrading, and then add the {{pkg|uutils}} package, containing the <code>/usr/bin/uutils</code> binary.

A few parts of the {{pkg|uutils}} aport are also split into {{pkg|uutils-*}} subpackages, to avoid conflicts or other issues.

=== linux-firmware ===

{{pkg|linux-firmware}} is now compressed with ZSTD compression. If you run a custom built Linux kernel, you need to ensure that <code>CONFIG_FW_LOADER_COMPRESS_ZSTD=y</code> is set in your configuration.

== Note-worthy updates ==

As always, a lot of packages were upgraded. Make sure to read the indivdual release notes of the projects you use.

* Linux 6.12
* busybox 1.37
* GCC 14.2
* LLVM 19
* Go 1.23
* Rust 1.83
* PHP 8.4
* GNOME 47
* KDE Plasma 6.2
* LXQt 2.1
* Qt 6.8
* wlroots 18

=== GCC 14 ===

The Gnu Compiler Collection was upgraded to 14.2.0 and as a result, all packages built with {{pkg|gcc}} in Alpine 3.21 are compiled with GCC 14.2.0.

Make sure to read all changes: https://gcc.gnu.org/gcc-14/changes.html

=== LXQt 2.1 ===

LXQt has been updated to release 2.1.0
* It now uses Qt6
* Many parts of LXQt are now Wayland ready¹, but Wayland ports of the following are pending: {{pkg|screengrab}}, {{pkg|lxqt-globalkeys}}, and keyboard indicator, some input settings, as well as settings for monitor, power button, and screen locker.
* LXQt Panel has a new default application menu called Fancy Menu.
¹ [https://github.com/lxqt/lxqt-wayland-session lxqt-wayland-session] has not been packaged yet, but most folks wanting to test on Wayland will want to use it.

=== Linux 6.12 ===

Alpine 3.21.0 ships Linux 6.12.1 in the {{pkg|linux-lts}} package.

=== PostgreSQL 17 ===

This release features {{pkg|postgresql17}}. We dropped support for {{pkg|postgresql14}}, and moved {{pkg|postgreSQL15}} from main to community.

=== LLVM 19 ===

We packaged LLVM 19 in our repositories. A total of 5 LLVM versions are supported: {{pkg|llvm19}}, {{pkg|llvm18}}, {{pkg|llvm17}}, {{pkg|llvm16}}, {{pkg|llvm15}}.

== Significant removals ==

=== Disabled packages due to FTBS ===

The following packages are temporarily disabled because they failed to build. We will try to restore them as soon as possible.

* {{pkg|hplip}} ({{Issue|16685}})
* {{pkg|imageflow}} ({{Issue|16679}})
* {{pkg|kdevelop}} ({{MR|75839}})
* {{pkg|postgresql-citus}} ({{Issue|16580}})
* {{pkg|uvicorn}} ({{Issue|16646}})
* {{pkg|vulkan-validation-layers}} ({{Issue|16686}})

=== ISC DHCP ===

If you are still running an ISC DHCP server, you are advised to migrate to a maintained alternative '''before''' upgrading to the 3.21 release.

ISC DHCP has been EoL since 2022. They have a guide for migrating to {{pkg|kea}} here: https://www.isc.org/dhcp_migration/

Up to, and including, the 3.20 version of Alpine, the {{pkg|dhcp|branch=v3.20}} aport has the subpackage {{pkg|keama|branch=v3.20}} that is a tool for helping with migration from ISC DHCP configuration to ISC Kea configuration.

Alternative DHCP servers packaged in Alpine include:
* {{pkg|kea}}
* {{pkg|freeradius-dhcp}}
* {{pkg|dnsmasq}}
* udhcpd - packaged in {{pkg|busybox-extras}}

=== Gogs ===

<code>gogs</code> was removed due to multiple high-severity vulnerabilities for which issues have remained open for a year. The developers of Gogs were contacted multiple times by the Forgejo team but unfortunately received no response. Therefore we have removed Gogs from our repositories. ({{MR|75304}})

Please consider migrating to {{pkg|forgejo|branch=edge|arch=}} or {{pkg|gitea|branch=edge|arch=}}. Both forks are available in our community repo.

The Gitea fork of Gogs was created in 2016 by contributors who were frustrated with the single-maintainer management model of Gogs. Forgejo is a fork of Gitea which was created as a result of the for-profit company Gitea Ltd taking over maintainership (see also https://forgejo.org/compare-to-gitea/).

=== neofetch ===

The upstream repository was archived in April and became unmaintained, therefore we have removed it from our repositories. {{pkg|fastfetch}} provides similar functionality.

Release Notes for Alpine 3.21.0

2024-12-05T10:33:19Z

Ncopa: /* Preparations for /usr-merge */

As always, make sure to read [[Upgrading Alpine to a new major release]] when upgrading to a new release.

If you experience any issues with the upgrade, please let us know and file an issue in our repositories.

== Important changes ==

=== OpenSSH service requires restart ===

From the <code>9.8_p1</code> release, and on, of {{pkg|openssh}}, {{pkg|openssh-server}} is split into two binaries (<code>/usr/lib/ssh/sshd-session</code> and <code>/usr/sbin/sshd</code>). Due to this change, it will not be possible to <code>ssh</code> into a system that has upgraded from a release prior to <code>9.8_p1</code> to this release or later, without restarting the <code>sshd</code> service.

We have previously brought attention to this - https://alpinelinux.org/posts/2024-07-02-openssh-upgrade-edge.html

Managing services has always been out-of-scope for {{pkg|apk-tools}}, but this one time we will '''make an exception''' when the following conditions are met:
# You have both the {{pkg|openssh-server}} and {{pkg|openssh-server-common-openrc}} packages installed at a version lower than <code>9.8_p1</code>
# The <code>sshd</code> service is started

We will then, post {{pkg|openssh-server}} upgrade, have a <code>post-upgrade</code> script that will:
# Print a message on what is about to happen and why
# Restart the <code>sshd</code> service
# If the command to restart the service fails for any reason, a warning message will be printed and an error code returned to <code>apk</code>, to be noticed by the end of the package upgrades (this will not interrupt the upgrade process).

We have decided to do this in order to help keep you from getting locked out of your system(s) and be able to fix any issues with the upgrade.

See also:
* https://bugzilla.mindrot.org/show_bug.cgi?id=3706
* https://git.alpinelinux.org/aports/commit/?id=6adff08ae09961d4eea66b55a8cca14d3941fb53

=== New loongarch64 architecture ===

Alpine 3.21 is the first release which is available for <code>loongarch64</code>.

Thanks to the support of the team of Loongson dedicated to supporting Alpine Linux and many other contributors.

=== Preparations for /usr-merge ===

Plans for /usr-merge are underway and we should be able to finalize it in Alpine Linux, version 3.22.

Much preparation has gone into this release to ensure that the merge happens as smoothly as possible. That included moving the location of some binaries and many libraries from <code>/bin</code>, <code>/sbin</code>, and <code>/lib</code> to their counterparts in <code>/usr</code>. As part of the merge, <code>/usr</code> will be mounted from the initramfs to make sure everybody has all necessary binaries in place.

'''Users with installations where <code>/</code> and <code>/usr</code> are on separate filesystems (partitions, volumes, disk drives or other) should proceed with care and report any issues.''' They should also ensure that an entry <code>/usr</code> is added to <code>/etc/fstab</code> before upgrading, and all modules required to mount <code>/usr</code> from the initramfs are added to mkinitfs configuration. New/fresh installations of v3.21 will work out of the box without modification.

If you have one of these setups, and have doubts about the configuration, you can open an [https://gitlab.alpinelinux.org/alpine/aports/-/issues/new issue] and ping <code>@pabloyoyoista</code>. We will also publish a blog post soon with further information on the timeline and progress of the merge, as well as how the changes may affect users.

Please note that this setup is already not supported.

== Significant changes ==

=== Jellyfin ===

Jellyfin now uses the recommended fork of ffmpeg called {{pkg|jellyfin-ffmpeg}} by default. If you want to change the default, take a look at the <code>ffmpegpath</code> variable in <code>/etc/conf.d/jellyfin</code>. ({{MR|69924}})

Jellyfin was disabled for ARM architectures (<code>aarch64</code> and <code>armv7</code>) and is only available for <code>x86_64</code>. ({{Issue|16613}})

=== Bats ===

<code>main/bats</code> was renamed to <code>main/bats-core</code>. There is now a meta package <code>community/bats</code> which contains:

* {{pkg|bats-core}}
* {{pkg|bats-file}}
* {{pkg|bats-support}}
* {{pkg|bats-assert}}

=== Xen 4.19 ===

''qemu-traditional'' and ''stubdom'' are removed from the build in this release, see https://git.alpinelinux.org/aports/commit/?id=24217a24da3924039b000eb17c04bf3f01bf1f12

There is still the {{pkg|xen-qemu}} package, but the regular {{pkg|qemu}} aport [https://git.alpinelinux.org/aports/commit/?id=a9249e2e0de827e88d84c01f9731aeebd248be13 is now built with Xen support], so a {{pkg|qemu-system-*}} package can be used instead.

You can choose to use it in your ''xl.cfg(1)'' like so:
<pre>
device_model_override = "/usr/bin/qemu-system-x86_64"
device_model_version = "qemu-xen"
</pre>

=== uutils-coreutils ===

{{pkg|uutils-coreutils}} is repackaged as a sub-package to {{pkg|uutils}} in such a way as to be a drop-in replacement for GNU {{pkg|coreutils}}.

If you have both {{pkg|uutils-coreutils}} and {{pkg|coreutils}} installed, the latter will be '''purged''' and its symlinks replaced with ones pointing to the <code>/usr/bin/uutils</code> binary. The <code>/usr/bin/uutils-*</code> symlinks, previously provided by {{pkg|uutils-coreutils}}, no longer exist.

If you prefer to use GNU {{pkg|coreutils}}, remove the {{pkg|uutils-coreutils}} package before upgrading, and then add the {{pkg|uutils}} package, containing the <code>/usr/bin/uutils</code> binary.

A few parts of the {{pkg|uutils}} aport are also split into {{pkg|uutils-*}} subpackages, to avoid conflicts or other issues.

=== linux-firmware ===

{{pkg|linux-firmware}} is now compressed with ZSTD compression. If you run a custom built Linux kernel, you need to ensure that <code>CONFIG_FW_LOADER_COMPRESS_ZSTD=y</code> is set in your configuration.

== Note-worthy updates ==

As always, a lot of packages were upgraded. Make sure to read the indivdual release notes of the projects you use.

* Linux 6.12
* busybox 1.37
* GCC 14.2
* LLVM 19
* Go 1.23
* Rust 1.83
* PHP 8.4
* GNOME 47
* KDE Plasma 6.2
* LXQt 2.1
* Qt 6.8
* wlroots 18

=== GCC 14 ===

The Gnu Compiler Collection was upgraded to 14.2.0 and as a result, all packages built with {{pkg|gcc}} in Alpine 3.21 are compiled with GCC 14.2.0.

Make sure to read all changes: https://gcc.gnu.org/gcc-14/changes.html

=== LXQt 2.1 ===

LXQt has been updated to release 2.1.0
* It now uses Qt6
* Many parts of LXQt are now Wayland ready¹, but Wayland ports of the following are pending: {{pkg|screengrab}}, {{pkg|lxqt-globalkeys}}, and keyboard indicator, some input settings, as well as settings for monitor, power button, and screen locker.
* LXQt Panel has a new default application menu called Fancy Menu.
¹ [https://github.com/lxqt/lxqt-wayland-session lxqt-wayland-session] has not been packaged yet, but most folks wanting to test on Wayland will want to use it.

=== Linux 6.12 ===

Alpine 3.21.0 ships Linux 6.12.1 in the {{pkg|linux-lts}} package.

Please note that {{pkg|linux-headers}} is still on 6.6, because the kernel was released after we kicked off our rebuilds and we coudn't ensure that the upgrade doesn't break other packages. (More about the linux-headers 6.12 upgrade: {{MR|75618}})

=== PostgreSQL 17 ===

This release features {{pkg|postgresql17}}. We dropped support for {{pkg|postgresql14}}, and moved {{pkg|postgreSQL15}} from main to community.

=== LLVM 19 ===

We packaged LLVM 19 in our repositories. A total of 5 LLVM versions are supported: {{pkg|llvm19}}, {{pkg|llvm18}}, {{pkg|llvm17}}, {{pkg|llvm16}}, {{pkg|llvm15}}.

== Significant removals ==

=== Disabled packages due to FTBS ===

The following packages are temporarily disabled because they failed to build. We will try to restore them as soon as possible.

* {{pkg|hplip}} ({{Issue|16685}})
* {{pkg|imageflow}} ({{Issue|16679}})
* {{pkg|kdevelop}} ({{MR|75839}})
* {{pkg|postgresql-citus}} ({{Issue|16580}})
* {{pkg|uvicorn}} ({{Issue|16646}})
* {{pkg|vulkan-validation-layers}} ({{Issue|16686}})

=== ISC DHCP ===

If you are still running an ISC DHCP server, you are advised to migrate to a maintained alternative '''before''' upgrading to the 3.21 release.

ISC DHCP has been EoL since 2022. They have a guide for migrating to {{pkg|kea}} here: https://www.isc.org/dhcp_migration/

Up to, and including, the 3.20 version of Alpine, the {{pkg|dhcp|branch=v3.20}} aport has the subpackage {{pkg|keama|branch=v3.20}} that is a tool for helping with migration from ISC DHCP configuration to ISC Kea configuration.

Alternative DHCP servers packaged in Alpine include:
* {{pkg|kea}}
* {{pkg|freeradius-dhcp}}
* {{pkg|dnsmasq}}
* udhcpd - packaged in {{pkg|busybox-extras}}

=== Gogs ===

<code>gogs</code> was removed due to multiple high-severity vulnerabilities for which issues have remained open for a year. The developers of Gogs were contacted multiple times by the Forgejo team but unfortunately received no response. Therefore we have removed Gogs from our repositories. ({{MR|75304}})

Please consider migrating to {{pkg|forgejo|branch=edge|arch=}} or {{pkg|gitea|branch=edge|arch=}}. Both forks are available in our community repo.

The Gitea fork of Gogs was created in 2016 by contributors who were frustrated with the single-maintainer management model of Gogs. Forgejo is a fork of Gitea which was created as a result of the for-profit company Gitea Ltd taking over maintainership (see also https://forgejo.org/compare-to-gitea/).

=== neofetch ===

The upstream repository was archived in April and became unmaintained, therefore we have removed it from our repositories. {{pkg|fastfetch}} provides similar functionality.

Template:AlpineLatest

2024-09-06T12:24:52Z

Ncopa:

<noinclude>{{Template}}
</noinclude>3.20.3

Template:AlpineLatest

2024-07-22T15:41:54Z

Ncopa:

<noinclude>{{Template}}
</noinclude>3.20.2

KVM

2024-06-21T15:20:18Z

Ncopa: /* Provision an Alpine Linux vm with virt-install */

[https://www.linux-kvm.org/page/Main_Page KVM] is an free and open source virtualization solution in a kernel module. Although it is often simply referred to as KVM, the actual hypervisor is [https://www.qemu.org QEMU]. QEMU runs from user-space, but can integrate with KVM, providing better performance by leveraging the hardware from kernel-space. QEMU can virtualize x86, PowerPC, and S390 guests, amongst others. [https://libvirt.org Libvirt] is a management framework that integrates with QEMU/KVM, [[LXC]], [[Xen_Dom0|Xen]] and others.

== Installation ==
The following commands provide '''libvirt''' as well as '''QEMU with emulation for x86_64''' and '''qemu-img''', a necessary component for using various disk formats such as qcow2. Without qemu-img, only raw disks are available. It can also convert images between several formats like vhdx and vmdk. It also provides the metapackage '''qemu-modules''', which provides subpackages needed for special features. In versions of Alpine before 3.13.0 these features were covered by '''QEMU with emulation for x86_64'''.
{{Cmd|<nowiki># apk add libvirt-daemon qemu-img qemu-system-x86_64 qemu-modules openrc
# rc-update add libvirtd</nowiki>}}

== Networking ==
By default, libvirt uses NAT for VM connectivity. If you want to use the default configuration, you need to load the tun module.
{{Cmd|# modprobe tun}}

Add tun to autostart:
{{Cmd|# echo "tun" >> /etc/modules-load.d/tun.conf}}

To make the tun module load on boot, use this command:
{{Cmd|# cat /etc/modules {{!}} grep tun {{!}}{{!}} echo tun >> /etc/modules}}

If you prefer bridging a guest over your Ethernet interface, you need to make a [[Bridge#Configuration_file|bridge]].

It's quite common to use bridges with KVM environments. But when IPv6 is used, Alpine will assign itself a link-local address as well as an SLAAC address in case there's a router sending Router Advertisements. You don't want this because you don't want to have the KVM host an IP address in every network it serves to guests. Unfortunately IPv6 can not just be disabled for the bridge via a sysctl configuration file, because the bridge might not be up when the sysctl config is applied during boot. What works is to put a post-up hook into the /etc/network/interfaces file like this:
auto brlan
iface brlan inet manual
bridge-ports eth1.5
bridge-stp 0
post-up ip -6 a flush dev brlan; sysctl -w net.ipv6.conf.brlan.disable_ipv6=1

== Management ==
For non-root management, you will need to add your user to the libvirt group.
{{Cmd|# addgroup user libvirt}}

You can use libvirt's virsh at the CLI. It can execute commands as well as run as an interactive shell. Read its manual page and/or use the "help" command for more info. Some basic commands are:

{{Cmd|<nowiki>virsh help
virsh list --all
virsh start $domain
virsh shutdown $domain</nowiki>
}}

The libvirt project provides a GUI for managing hosts, called virt-manager. It handles local systems as well as remote ones via SSH.
{{Cmd|<nowiki># apk add dbus polkit virt-manager font-terminus
# rc-update add dbus</nowiki>}}

In order to use libvirtd to remotely control KVM over ssh PolicyKit needs a .pkla informing it that this is allowed.
Write the following file to /etc/polkit-1/localauthority/50-local.d/50-libvirt-ssh-remote-access-policy.pkla
{{Cmd|<nowiki>[Remote libvirt SSH access]
Identity=unix-group:libvirt
Action=org.libvirt.unix.manage
ResultAny=yes
ResultInactive=yes
ResultActive=yes</nowiki>
}}

== Provision an Alpine Linux vm with virt-install ==

You can use {{Path|virt-install}} to install Alpine in a VM. First create the {{ Path | meta-data}} and {{Path | user-data }} files.
{{Path|meta-data}}:
hostname: alpine-vm

{{Path|user-data}}:
<pre>
#alpine-config
ssh_authorized_keys:
- ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIOIiHcbg/7ytfLFHUNLRgEAubFz/13SwXBOM/05GNZe4 ncopa@ncopa-desktop
apk:
repositories:
- base_url: https://dl-cdn.alpinelinux.org/alpine
repos:
- main
- community
packages:
- tmux
- curl
runcmd:
- rm /etc/runlevels/*/tiny-cloud*
- lbu include /root/.ssh /home/alpine/.ssh
- ERASE_DISKS=/dev/vda setup-disk -m sys /dev/vda
- poweroff
</pre>

Then run:
{{Cmd | <nowiki>virt-install --name alpine-vm \
--disk size=4 \
--location $HOME/Downloads/alpine-virt-3.20.1-x86_64.iso,kernel=boot/vmlinuz-virt,initrd=boot/initramfs-virt \
--extra-args console=ttyS0 \
--osinfo alpinelinux3.19 \
--graphics none \
--console pty,target_type=serial \
--cloud-init meta-data=meta-data,user-data=user-data
</nowiki>}}

== Guest lifecycle management ==
The libvirt-guests service (available from Alpine 3.13.5) allows running guests to be automatically suspended or shut down when the host is shut down or rebooted.

The service is configured in /etc/conf.d/libvirt-guests. Enable the service with {{Cmd|# rc-update add libvirt-guests}}

== vfio ==

VFIO is more flexible way to do PCI passthrough. Let's suppose you want to use following ethernet card as PCI device in a VM.

# lspci | grep 02:00.0
02:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
# lspci -n -s 02:00.0
02:00.0 0200: 8086:10c9 (rev 01)

First, create ''/etc/mkinitfs/features.d/vfio.modules'' with the following content, so mkinitfs includes the VFIO modules in the initramfs.

kernel/drivers/vfio/vfio.ko.*
kernel/drivers/vfio/vfio_virqfd.ko.*
kernel/drivers/vfio/vfio_iommu_type1.ko.*
kernel/drivers/vfio/pci/vfio-pci.ko.*

Add ''vfio'' the the list of features in ''/etc/mkinitfs/mkinitfs.conf''.

Modify following file to instruct ''mkinitfs'' to load following module with the options and rebuild kernel ramdisk.

# cat /etc/modprobe.d/vfio.conf <<EOF
options vfio-pci ids=8086:10c9
options vfio_iommu_type1 allow_unsafe_interrupts=1
softdep igb pre: vfio-pci
EOF
# mkinitfs

Now we need to edit the "default_kernel_opts" and "modules" sections in the update-extlinux.conf file. Edit the "default_kernel_opts" to include ''intel_iommu=o iommu=pt'' for Intel platform (AMD uses ''amd_iommu=on''), and add the VFIO modules to the "modules" section.

# grep '^default_kernel_opts\|^modules' /etc/update-extlinux.conf
default_kernel_opts="quiet rootfstype=ext4 intel_iommu=on iommu=pt"
modules=sd-mod,usb-storage,ext4,raid1,vfio,vfio-pci,vfio_iommu_type1,vfio_virqfd

For syslinux/extlinux, run:

# update-extlinux

For GRUB (which [https://web.archive.org/web/20220821140615/https://git.alpinelinux.org/aports/tree/main/grub/alpine-mkconfig.patch#n9 now also uses] the update-extlinux.conf if present), run:

# grub-mkconfig -o /boot/grub/grub.cfg

Reboot and check dmesg.

# grep -i -e DMAR -e IOMMU /var/log/dmesg
[ 0.343795] DMAR: Host address width 36
[ 0.343797] DMAR: DRHD base: 0x000000fed90000 flags: 0x1
[ 0.343804] DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap c90780106f0462 ecap f020e3
[ 0.343806] DMAR: RMRR base: 0x000000000ed000 end: 0x000000000effff
[ 0.343807] DMAR: RMRR base: 0x000000bf7ed000 end: 0x000000bf7fffff
[ 0.553830] iommu: Default domain type: Passthrough (set via kernel command line)
[ 0.902477] DMAR: No ATSR found
[ 0.902563] DMAR: dmar0: Using Queued invalidation
...
[ 0.903256] pci 0000:02:00.0: Adding to iommu group 12
...
[ 0.903768] DMAR: Intel(R) Virtualization Technology for Directed I/O

If you do not run libvirt VMs under ''root'' (''egrep '^#*user' /etc/libvirt/qemu.conf''), then you must have correct permission on ''/dev/vfio/<iommu_group>'', eg. ''/dev/vfio/12''. You have to tune ''/etc/mdev.conf'' or [[udev]] rules. Also note that if there are multiple PCI devices in the same iommu group, you always have to add all of them to the VM otherwise you'll get an error message like "Please ensure all devices within the iommu_group are bound to their vfio bus driver"

# virsh dumpxml vm01 | xmllint --xpath '//*/hostdev' -
<hostdev mode="subsystem" type="pci" managed="yes">
<driver name="vfio"/>
<source>
<address domain="0x0000" bus="0x02" slot="0x00" function="0x0"/>
</source>
<alias name="hostdev0"/>
<address type="pci" domain="0x0000" bus="0x00" slot="0x06" function="0x0"/>
</hostdev>
<hostdev mode="subsystem" type="pci" managed="yes">
<driver name="vfio"/>
<source>
<address domain="0x0000" bus="0x02" slot="0x00" function="0x1"/>
</source>
<alias name="hostdev1"/>
<address type="pci" domain="0x0000" bus="0x00" slot="0x08" function="0x0"/>
</hostdev>

If you directly use QEMU without libvirt and are trying to pass a GPU to your VM, you may get a "VFIO_MAP_DMA failed: Out of memory" error, when starting the VM as a non-root user. One way to fix it is to install the ''shadow'' package, and increase the amount of memory the user can lock via the ''/etc/security/limits.conf'' file:
{{Cmd|<nowiki># apk add shadow
# echo "youruser soft memlock RAMamount \
youruser hard memlock RAMamount" >> /etc/security/limits.conf
# reboot</nowiki>}}

Replace "youruser" with the user you wish to run the VM as, and "RAMamount" with how much RAM your VM will need (in KB). The exact amount may throw the same error in the end, so you probably want to increase this value by a few dozen MB (typically +40).

A lot of info on the [https://wiki.archlinux.org/index.php/PCI_passthrough_via_OVMF Archwiki article for PCI passthrough via OVMF].

[[Category:Virtualization]]

KVM

2024-06-21T15:18:55Z

Ncopa: /* Provision an Alpine Linux vm with virt-install */

[https://www.linux-kvm.org/page/Main_Page KVM] is an free and open source virtualization solution in a kernel module. Although it is often simply referred to as KVM, the actual hypervisor is [https://www.qemu.org QEMU]. QEMU runs from user-space, but can integrate with KVM, providing better performance by leveraging the hardware from kernel-space. QEMU can virtualize x86, PowerPC, and S390 guests, amongst others. [https://libvirt.org Libvirt] is a management framework that integrates with QEMU/KVM, [[LXC]], [[Xen_Dom0|Xen]] and others.

== Installation ==
The following commands provide '''libvirt''' as well as '''QEMU with emulation for x86_64''' and '''qemu-img''', a necessary component for using various disk formats such as qcow2. Without qemu-img, only raw disks are available. It can also convert images between several formats like vhdx and vmdk. It also provides the metapackage '''qemu-modules''', which provides subpackages needed for special features. In versions of Alpine before 3.13.0 these features were covered by '''QEMU with emulation for x86_64'''.
{{Cmd|<nowiki># apk add libvirt-daemon qemu-img qemu-system-x86_64 qemu-modules openrc
# rc-update add libvirtd</nowiki>}}

== Networking ==
By default, libvirt uses NAT for VM connectivity. If you want to use the default configuration, you need to load the tun module.
{{Cmd|# modprobe tun}}

Add tun to autostart:
{{Cmd|# echo "tun" >> /etc/modules-load.d/tun.conf}}

To make the tun module load on boot, use this command:
{{Cmd|# cat /etc/modules {{!}} grep tun {{!}}{{!}} echo tun >> /etc/modules}}

If you prefer bridging a guest over your Ethernet interface, you need to make a [[Bridge#Configuration_file|bridge]].

It's quite common to use bridges with KVM environments. But when IPv6 is used, Alpine will assign itself a link-local address as well as an SLAAC address in case there's a router sending Router Advertisements. You don't want this because you don't want to have the KVM host an IP address in every network it serves to guests. Unfortunately IPv6 can not just be disabled for the bridge via a sysctl configuration file, because the bridge might not be up when the sysctl config is applied during boot. What works is to put a post-up hook into the /etc/network/interfaces file like this:
auto brlan
iface brlan inet manual
bridge-ports eth1.5
bridge-stp 0
post-up ip -6 a flush dev brlan; sysctl -w net.ipv6.conf.brlan.disable_ipv6=1

== Management ==
For non-root management, you will need to add your user to the libvirt group.
{{Cmd|# addgroup user libvirt}}

You can use libvirt's virsh at the CLI. It can execute commands as well as run as an interactive shell. Read its manual page and/or use the "help" command for more info. Some basic commands are:

{{Cmd|<nowiki>virsh help
virsh list --all
virsh start $domain
virsh shutdown $domain</nowiki>
}}

The libvirt project provides a GUI for managing hosts, called virt-manager. It handles local systems as well as remote ones via SSH.
{{Cmd|<nowiki># apk add dbus polkit virt-manager font-terminus
# rc-update add dbus</nowiki>}}

In order to use libvirtd to remotely control KVM over ssh PolicyKit needs a .pkla informing it that this is allowed.
Write the following file to /etc/polkit-1/localauthority/50-local.d/50-libvirt-ssh-remote-access-policy.pkla
{{Cmd|<nowiki>[Remote libvirt SSH access]
Identity=unix-group:libvirt
Action=org.libvirt.unix.manage
ResultAny=yes
ResultInactive=yes
ResultActive=yes</nowiki>
}}

== Provision an Alpine Linux vm with virt-install ==

You can use {{Path|virt-install}} to install Alpine in a VM. First create the {{ Path | meta-data}} and {{Path | user-data }} files.
<pre>
#alpine-config
ssh_authorized_keys:
- ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIOIiHcbg/7ytfLFHUNLRgEAubFz/13SwXBOM/05GNZe4 ncopa@ncopa-desktop
apk:
repositories:
- base_url: https://dl-cdn.alpinelinux.org/alpine
repos:
- main
- community
packages:
- tmux
- curl
runcmd:
- rm /etc/runlevels/*/tiny-cloud*
- lbu include /root/.ssh /home/alpine/.ssh
- ERASE_DISKS=/dev/vda setup-disk -m sys /dev/vda
- poweroff
</pre>

Then run:
{{Cmd | <nowiki>virt-install --name tmp-alp \
--disk size=4 \
--location $HOME/Downloads/alpine-virt-3.20.1-x86_64.iso,kernel=boot/vmlinuz-virt,initrd=boot/initramfs-virt \
--extra-args console=ttyS0 \
--osinfo alpinelinux3.19 \
--graphics none \
--console pty,target_type=serial \
--cloud-init meta-data=meta-data,user-data=user-data
</nowiki>}}

== Guest lifecycle management ==
The libvirt-guests service (available from Alpine 3.13.5) allows running guests to be automatically suspended or shut down when the host is shut down or rebooted.

The service is configured in /etc/conf.d/libvirt-guests. Enable the service with {{Cmd|# rc-update add libvirt-guests}}

== vfio ==

VFIO is more flexible way to do PCI passthrough. Let's suppose you want to use following ethernet card as PCI device in a VM.

# lspci | grep 02:00.0
02:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
# lspci -n -s 02:00.0
02:00.0 0200: 8086:10c9 (rev 01)

First, create ''/etc/mkinitfs/features.d/vfio.modules'' with the following content, so mkinitfs includes the VFIO modules in the initramfs.

kernel/drivers/vfio/vfio.ko.*
kernel/drivers/vfio/vfio_virqfd.ko.*
kernel/drivers/vfio/vfio_iommu_type1.ko.*
kernel/drivers/vfio/pci/vfio-pci.ko.*

Add ''vfio'' the the list of features in ''/etc/mkinitfs/mkinitfs.conf''.

Modify following file to instruct ''mkinitfs'' to load following module with the options and rebuild kernel ramdisk.

# cat /etc/modprobe.d/vfio.conf <<EOF
options vfio-pci ids=8086:10c9
options vfio_iommu_type1 allow_unsafe_interrupts=1
softdep igb pre: vfio-pci
EOF
# mkinitfs

Now we need to edit the "default_kernel_opts" and "modules" sections in the update-extlinux.conf file. Edit the "default_kernel_opts" to include ''intel_iommu=o iommu=pt'' for Intel platform (AMD uses ''amd_iommu=on''), and add the VFIO modules to the "modules" section.

# grep '^default_kernel_opts\|^modules' /etc/update-extlinux.conf
default_kernel_opts="quiet rootfstype=ext4 intel_iommu=on iommu=pt"
modules=sd-mod,usb-storage,ext4,raid1,vfio,vfio-pci,vfio_iommu_type1,vfio_virqfd

For syslinux/extlinux, run:

# update-extlinux

For GRUB (which [https://web.archive.org/web/20220821140615/https://git.alpinelinux.org/aports/tree/main/grub/alpine-mkconfig.patch#n9 now also uses] the update-extlinux.conf if present), run:

# grub-mkconfig -o /boot/grub/grub.cfg

Reboot and check dmesg.

# grep -i -e DMAR -e IOMMU /var/log/dmesg
[ 0.343795] DMAR: Host address width 36
[ 0.343797] DMAR: DRHD base: 0x000000fed90000 flags: 0x1
[ 0.343804] DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap c90780106f0462 ecap f020e3
[ 0.343806] DMAR: RMRR base: 0x000000000ed000 end: 0x000000000effff
[ 0.343807] DMAR: RMRR base: 0x000000bf7ed000 end: 0x000000bf7fffff
[ 0.553830] iommu: Default domain type: Passthrough (set via kernel command line)
[ 0.902477] DMAR: No ATSR found
[ 0.902563] DMAR: dmar0: Using Queued invalidation
...
[ 0.903256] pci 0000:02:00.0: Adding to iommu group 12
...
[ 0.903768] DMAR: Intel(R) Virtualization Technology for Directed I/O

If you do not run libvirt VMs under ''root'' (''egrep '^#*user' /etc/libvirt/qemu.conf''), then you must have correct permission on ''/dev/vfio/<iommu_group>'', eg. ''/dev/vfio/12''. You have to tune ''/etc/mdev.conf'' or [[udev]] rules. Also note that if there are multiple PCI devices in the same iommu group, you always have to add all of them to the VM otherwise you'll get an error message like "Please ensure all devices within the iommu_group are bound to their vfio bus driver"

# virsh dumpxml vm01 | xmllint --xpath '//*/hostdev' -
<hostdev mode="subsystem" type="pci" managed="yes">
<driver name="vfio"/>
<source>
<address domain="0x0000" bus="0x02" slot="0x00" function="0x0"/>
</source>
<alias name="hostdev0"/>
<address type="pci" domain="0x0000" bus="0x00" slot="0x06" function="0x0"/>
</hostdev>
<hostdev mode="subsystem" type="pci" managed="yes">
<driver name="vfio"/>
<source>
<address domain="0x0000" bus="0x02" slot="0x00" function="0x1"/>
</source>
<alias name="hostdev1"/>
<address type="pci" domain="0x0000" bus="0x00" slot="0x08" function="0x0"/>
</hostdev>

If you directly use QEMU without libvirt and are trying to pass a GPU to your VM, you may get a "VFIO_MAP_DMA failed: Out of memory" error, when starting the VM as a non-root user. One way to fix it is to install the ''shadow'' package, and increase the amount of memory the user can lock via the ''/etc/security/limits.conf'' file:
{{Cmd|<nowiki># apk add shadow
# echo "youruser soft memlock RAMamount \
youruser hard memlock RAMamount" >> /etc/security/limits.conf
# reboot</nowiki>}}

Replace "youruser" with the user you wish to run the VM as, and "RAMamount" with how much RAM your VM will need (in KB). The exact amount may throw the same error in the end, so you probably want to increase this value by a few dozen MB (typically +40).

A lot of info on the [https://wiki.archlinux.org/index.php/PCI_passthrough_via_OVMF Archwiki article for PCI passthrough via OVMF].

[[Category:Virtualization]]

KVM

2024-06-21T15:18:10Z

Ncopa: add install alpine with virt-install

[https://www.linux-kvm.org/page/Main_Page KVM] is an free and open source virtualization solution in a kernel module. Although it is often simply referred to as KVM, the actual hypervisor is [https://www.qemu.org QEMU]. QEMU runs from user-space, but can integrate with KVM, providing better performance by leveraging the hardware from kernel-space. QEMU can virtualize x86, PowerPC, and S390 guests, amongst others. [https://libvirt.org Libvirt] is a management framework that integrates with QEMU/KVM, [[LXC]], [[Xen_Dom0|Xen]] and others.

== Installation ==
The following commands provide '''libvirt''' as well as '''QEMU with emulation for x86_64''' and '''qemu-img''', a necessary component for using various disk formats such as qcow2. Without qemu-img, only raw disks are available. It can also convert images between several formats like vhdx and vmdk. It also provides the metapackage '''qemu-modules''', which provides subpackages needed for special features. In versions of Alpine before 3.13.0 these features were covered by '''QEMU with emulation for x86_64'''.
{{Cmd|<nowiki># apk add libvirt-daemon qemu-img qemu-system-x86_64 qemu-modules openrc
# rc-update add libvirtd</nowiki>}}

== Networking ==
By default, libvirt uses NAT for VM connectivity. If you want to use the default configuration, you need to load the tun module.
{{Cmd|# modprobe tun}}

Add tun to autostart:
{{Cmd|# echo "tun" >> /etc/modules-load.d/tun.conf}}

To make the tun module load on boot, use this command:
{{Cmd|# cat /etc/modules {{!}} grep tun {{!}}{{!}} echo tun >> /etc/modules}}

If you prefer bridging a guest over your Ethernet interface, you need to make a [[Bridge#Configuration_file|bridge]].

It's quite common to use bridges with KVM environments. But when IPv6 is used, Alpine will assign itself a link-local address as well as an SLAAC address in case there's a router sending Router Advertisements. You don't want this because you don't want to have the KVM host an IP address in every network it serves to guests. Unfortunately IPv6 can not just be disabled for the bridge via a sysctl configuration file, because the bridge might not be up when the sysctl config is applied during boot. What works is to put a post-up hook into the /etc/network/interfaces file like this:
auto brlan
iface brlan inet manual
bridge-ports eth1.5
bridge-stp 0
post-up ip -6 a flush dev brlan; sysctl -w net.ipv6.conf.brlan.disable_ipv6=1

== Management ==
For non-root management, you will need to add your user to the libvirt group.
{{Cmd|# addgroup user libvirt}}

You can use libvirt's virsh at the CLI. It can execute commands as well as run as an interactive shell. Read its manual page and/or use the "help" command for more info. Some basic commands are:

{{Cmd|<nowiki>virsh help
virsh list --all
virsh start $domain
virsh shutdown $domain</nowiki>
}}

The libvirt project provides a GUI for managing hosts, called virt-manager. It handles local systems as well as remote ones via SSH.
{{Cmd|<nowiki># apk add dbus polkit virt-manager font-terminus
# rc-update add dbus</nowiki>}}

In order to use libvirtd to remotely control KVM over ssh PolicyKit needs a .pkla informing it that this is allowed.
Write the following file to /etc/polkit-1/localauthority/50-local.d/50-libvirt-ssh-remote-access-policy.pkla
{{Cmd|<nowiki>[Remote libvirt SSH access]
Identity=unix-group:libvirt
Action=org.libvirt.unix.manage
ResultAny=yes
ResultInactive=yes
ResultActive=yes</nowiki>
}}

== Provision an Alpine Linux vm with virt-install ==

You can use {{Cmd|virt-install}} to install Alpine in a VM. First create the {{ Path | meta-data}} and {{Path | user-data }} files.
<pre>
#alpine-config
ssh_authorized_keys:
- ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIOIiHcbg/7ytfLFHUNLRgEAubFz/13SwXBOM/05GNZe4 ncopa@ncopa-desktop
apk:
repositories:
- base_url: https://dl-cdn.alpinelinux.org/alpine
repos:
- main
- community
packages:
- tmux
- curl
runcmd:
- rm /etc/runlevels/*/tiny-cloud*
- lbu include /root/.ssh /home/alpine/.ssh
- ERASE_DISKS=/dev/vda setup-disk -m sys /dev/vda
- poweroff
</pre>

Then run:
{{Cmd | <nowiki>virt-install --name tmp-alp \
--disk size=4 \
--location $HOME/Downloads/alpine-virt-3.20.1-x86_64.iso,kernel=boot/vmlinuz-virt,initrd=boot/initramfs-virt \
--extra-args console=ttyS0 \
--osinfo alpinelinux3.19 \
--graphics none \
--console pty,target_type=serial \
--cloud-init meta-data=meta-data,user-data=user-data
</nowiki>}}
== Guest lifecycle management ==
The libvirt-guests service (available from Alpine 3.13.5) allows running guests to be automatically suspended or shut down when the host is shut down or rebooted.

The service is configured in /etc/conf.d/libvirt-guests. Enable the service with {{Cmd|# rc-update add libvirt-guests}}

== vfio ==

VFIO is more flexible way to do PCI passthrough. Let's suppose you want to use following ethernet card as PCI device in a VM.

# lspci | grep 02:00.0
02:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
# lspci -n -s 02:00.0
02:00.0 0200: 8086:10c9 (rev 01)

First, create ''/etc/mkinitfs/features.d/vfio.modules'' with the following content, so mkinitfs includes the VFIO modules in the initramfs.

kernel/drivers/vfio/vfio.ko.*
kernel/drivers/vfio/vfio_virqfd.ko.*
kernel/drivers/vfio/vfio_iommu_type1.ko.*
kernel/drivers/vfio/pci/vfio-pci.ko.*

Add ''vfio'' the the list of features in ''/etc/mkinitfs/mkinitfs.conf''.

Modify following file to instruct ''mkinitfs'' to load following module with the options and rebuild kernel ramdisk.

# cat /etc/modprobe.d/vfio.conf <<EOF
options vfio-pci ids=8086:10c9
options vfio_iommu_type1 allow_unsafe_interrupts=1
softdep igb pre: vfio-pci
EOF
# mkinitfs

Now we need to edit the "default_kernel_opts" and "modules" sections in the update-extlinux.conf file. Edit the "default_kernel_opts" to include ''intel_iommu=o iommu=pt'' for Intel platform (AMD uses ''amd_iommu=on''), and add the VFIO modules to the "modules" section.

# grep '^default_kernel_opts\|^modules' /etc/update-extlinux.conf
default_kernel_opts="quiet rootfstype=ext4 intel_iommu=on iommu=pt"
modules=sd-mod,usb-storage,ext4,raid1,vfio,vfio-pci,vfio_iommu_type1,vfio_virqfd

For syslinux/extlinux, run:

# update-extlinux

For GRUB (which [https://web.archive.org/web/20220821140615/https://git.alpinelinux.org/aports/tree/main/grub/alpine-mkconfig.patch#n9 now also uses] the update-extlinux.conf if present), run:

# grub-mkconfig -o /boot/grub/grub.cfg

Reboot and check dmesg.

# grep -i -e DMAR -e IOMMU /var/log/dmesg
[ 0.343795] DMAR: Host address width 36
[ 0.343797] DMAR: DRHD base: 0x000000fed90000 flags: 0x1
[ 0.343804] DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap c90780106f0462 ecap f020e3
[ 0.343806] DMAR: RMRR base: 0x000000000ed000 end: 0x000000000effff
[ 0.343807] DMAR: RMRR base: 0x000000bf7ed000 end: 0x000000bf7fffff
[ 0.553830] iommu: Default domain type: Passthrough (set via kernel command line)
[ 0.902477] DMAR: No ATSR found
[ 0.902563] DMAR: dmar0: Using Queued invalidation
...
[ 0.903256] pci 0000:02:00.0: Adding to iommu group 12
...
[ 0.903768] DMAR: Intel(R) Virtualization Technology for Directed I/O

If you do not run libvirt VMs under ''root'' (''egrep '^#*user' /etc/libvirt/qemu.conf''), then you must have correct permission on ''/dev/vfio/<iommu_group>'', eg. ''/dev/vfio/12''. You have to tune ''/etc/mdev.conf'' or [[udev]] rules. Also note that if there are multiple PCI devices in the same iommu group, you always have to add all of them to the VM otherwise you'll get an error message like "Please ensure all devices within the iommu_group are bound to their vfio bus driver"

# virsh dumpxml vm01 | xmllint --xpath '//*/hostdev' -
<hostdev mode="subsystem" type="pci" managed="yes">
<driver name="vfio"/>
<source>
<address domain="0x0000" bus="0x02" slot="0x00" function="0x0"/>
</source>
<alias name="hostdev0"/>
<address type="pci" domain="0x0000" bus="0x00" slot="0x06" function="0x0"/>
</hostdev>
<hostdev mode="subsystem" type="pci" managed="yes">
<driver name="vfio"/>
<source>
<address domain="0x0000" bus="0x02" slot="0x00" function="0x1"/>
</source>
<alias name="hostdev1"/>
<address type="pci" domain="0x0000" bus="0x00" slot="0x08" function="0x0"/>
</hostdev>

If you directly use QEMU without libvirt and are trying to pass a GPU to your VM, you may get a "VFIO_MAP_DMA failed: Out of memory" error, when starting the VM as a non-root user. One way to fix it is to install the ''shadow'' package, and increase the amount of memory the user can lock via the ''/etc/security/limits.conf'' file:
{{Cmd|<nowiki># apk add shadow
# echo "youruser soft memlock RAMamount \
youruser hard memlock RAMamount" >> /etc/security/limits.conf
# reboot</nowiki>}}

Replace "youruser" with the user you wish to run the VM as, and "RAMamount" with how much RAM your VM will need (in KB). The exact amount may throw the same error in the end, so you probably want to increase this value by a few dozen MB (typically +40).

A lot of info on the [https://wiki.archlinux.org/index.php/PCI_passthrough_via_OVMF Archwiki article for PCI passthrough via OVMF].

[[Category:Virtualization]]

Template:AlpineLatest

2024-06-18T19:14:52Z

Ncopa:

<noinclude>{{Template}}
</noinclude>3.20.1

Release Notes for Alpine 3.20.0

2024-05-22T10:24:11Z

Ncopa: add kde 6

== Base System ==

=== grub 2.12 ===

When upgrading existing installations using grub on UEFI systems, make sure to update the installed bootloader before rebooting otherwise your machine might not boot.

The problem is that grub added a new configuration that executes <code>fwsetup --is-supported</code>, but grub 2.06 does not support the <code>--is-supported</code> argument yet, causing grub to try to reboot into firmware unconditionally.

Here is an example assuming the default setup. Don't blindly copy this example, but verify what's applicable to your system.

==== EFI ====

{{Cmd|
# grub-install --target{{=}}<var>$target</var> --efi-directory{{=}}<var>$efi_directory</var> \
--bootloader-id{{=}}alpine --boot-directory{{=}}/boot --no-nvram
# install -D <var>$efi_directory</var>/EFI/alpine/grub<var>$fwa</var>.efi <var>$efi_directory</var>/EFI/boot/boot<var>$fwa</var>.efi

}}

; target : The relevant [https://gitlab.alpinelinux.org/alpine/alpine-conf/-/blob/master/setup-disk.in#L320-324 target] for your system
; efi_directory : Either {{Path|/boot/efi}} or {{Path|/boot}}. Run <code>awk '$2 ~ /boot/ && $3 ~ /fat|msdos/ { print $2 }' /proc/mounts</code> to confirm.
; fwa : The respective [https://gitlab.alpinelinux.org/alpine/alpine-conf/-/blob/master/setup-disk.in#L320-324 firmware architecture] for your system

==== Short-term workaround ====

A short-term workaround to get the system bootable again is to restore the backup configuration:

{{Cmd|cp /boot/grub/grub.cfg.backup /boot/grub.cfg }}

This should allow you to boot the system again in order to fix it permanently. This will be reverted when either grub or the kernel is updated again.

This will only work if <code>update-grub</code> has not been executed any more since the upgrade to grub 2.12.

== Others ==

=== Redis ===
Due to [https://github.com/redis/redis/pull/13157 the relicensing of Redis] to [https://redis.io/legal/rsalv2-agreement/ RSALv2]+[https://redis.io/legal/server-side-public-license-sspl/ SSPLv1], a non-free license model, the [https://spdx.org/licenses/BSD-3-Clause.html BSD-3-Clause] licensed fork [https://valkey.io/ Valkey] has replaced Redis in the main package repository.

A {{#ifexpr: {{AlpineLatest}} >= 3.20 |{{pkg|valkey-compat|branch=v3.20|arch=}}|{{pkg|valkey-compat|branch=edge|arch=}}}} package is provided with symlinks and group for easy Redis replacement.

The {{#ifexpr: {{AlpineLatest}} >= 3.20 |{{pkg|redis|branch=v3.20|arch=}}|{{pkg|redis|branch=edge|arch=}}}} aport has been moved to the community repository, with a shorter support cycle, and will not be upgraded past 7.2.x due to the license change.

Another replacement alternative, the [https://spdx.org/licenses/LGPL-3.0-only.html LGPL-3.0-only] licensed fork [https://redict.io/ Redict] is also available in the community repository.

=== yq ===
yq was renamed to yq-go. [https://gitlab.alpinelinux.org/alpine/aports/-/issues/16052 #16052]

=== aws-cli ===
Due to incompatibility issues with Python 3.12, aws-cli has been temporarily disabled until the issue is resolved by upstream. See the corresponding problem upstream: [https://github.com/aws/aws-cli/issues/8342 #8342]

=== GNOME 46 ===

New upstream release of GNOME.

Depending on how you installed GNOME, you may have to manually add <code>gcr-ssh-agent</code> after upgrading to retain GNOME Keyring ssh integration.

=== KDE 6 ===

KDE Plasma has been upgraded to Plasma 6, bringing the major update to Qt6 with it. This also includes applications from KDE Gear although some individual applications remain on Qt5 for now. The update makes the Wayland session the default and this Alpine release is the last one to support the X11 session.

=== podman [https://github.com/containers/podman/releases/tag/v5.0.0 5.x] ===

The default tool for rootless networking has been swapped from <code>slirp4netns</code> to
<code>pasta</code> (<code>passt</code>) for improved performance. As a result, networks named pasta are
no longer supported.

== Upgrades ==

* Crystal 1.12
* LLVM 18
* nginx 1.26
* .NET 8
* Nim 2.0
* OpenJDK 22
* Python 3.12
* Racket 8.13
* Ruby 3.3
* Rust 1.78
* R 4.4
* Sway 1.9

Release Notes for Alpine 3.20.0

2024-05-07T19:23:51Z

Ncopa:

== Base System ==

=== grub 2.12 ===

When upgrading existing installations using grub on UEFI systems, make sure to update the installed bootloader before rebooting, otherwise your machine might not boot.

The problem is that grub added new configuration that executes <code>fwsetup --is-supported</code>. The problem is that grub 2.06 does not supported the <code>--is-supported</code> argument yet, causing grub to unconditionally try to reboot into firmware.

Here is an example assuming the default setup. Don't blindly copy this examples but verify what's applicable to your system.

==== EFI ====

{{Cmd|
# grub-install --target{{=}}<var>$target</var> --efi-directory{{=}}<var>$efi_directory</var> \
--bootloader-id{{=}}alpine --boot-directory{{=}}/boot --no-nvram
# install -D <var>$efi_directory</var>/EFI/alpine/grub<var>$fwa</var>.efi <var>$efi_directory</var>/EFI/boot/boot<var>$fwa</var>.efi

}}

; target : The relevant [https://gitlab.alpinelinux.org/alpine/alpine-conf/-/blob/master/setup-disk.in#L320-324 target] for your system
; efi_directory : Either {{Path|/boot/efi}} or {{Path|/boot}}. Run <code>awk '$2 ~ /boot/ && $3 ~ /fat|msdos/ { print $2 }' /proc/mounts</code> to confirm.
; fwa : The respective [https://gitlab.alpinelinux.org/alpine/alpine-conf/-/blob/master/setup-disk.in#L320-324 firmware architecture] for your system

==== Short-term work-around ====

A short-term work-around to get the system bootable again is to restore the backup configuration:

{{Cmd|cp /boot/grub/grub.cfg.back /boot/grub.cfg }}

This should allow you to boot the system again to fix it permanently. This will be reverted again when either grub or the kernel is updated again.

This will only work if <code>update-grub</code> has not been executed any more since the upgrade to grub 2.12.

== Others ==

=== Redis ===
Due to [https://github.com/redis/redis/pull/13157 the relicensing of Redis] to [https://redis.io/legal/rsalv2-agreement/ RSALv2]+[https://redis.io/legal/server-side-public-license-sspl/ SSPLv1], a non-free license model, the [https://spdx.org/licenses/BSD-3-Clause.html BSD-3-Clause] licensed fork [https://valkey.io/ Valkey] has replaced Redis in the main package repository.

A [https://pkgs.alpinelinux.org/packages?name=valkey-compat valkey-compat] package is provided with symlinks and group for easy Redis replcament.

The [https://pkgs.alpinelinux.org/packages?name=redis redis aport] has been moved to the community repository, with a shorter support cycle, and will not be upgraded past 7.2.x due to the license change.

Another replacement alternative, the [https://spdx.org/licenses/LGPL-3.0-only.html LGPL-3.0-only] licensed fork [https://redict.io/ Redict] is also avalable in the community repository.

=== yq ===
yq was renamed to yq-go. https://gitlab.alpinelinux.org/alpine/aports/-/issues/16052

Template:AlpineLatest

2024-01-26T20:08:39Z

Ncopa: bump 3.19.1

<noinclude>{{Template}}
</noinclude>3.19.1

Release Notes for Alpine 1.7.13

2024-01-19T10:14:58Z

Ncopa: /* 2/3 of the packages tested */ remove link to the obsolete package test suite

{{Historical|Alpine 1.7.13 is an ancient release. URLs on this page no longer function.}}

This is a development release.

As always, the latest iso image can be downloaded from <nowiki>http://dev.alpinelinux.org/alpine/v1.7/iso</nowiki> and usbdrive tarballs from <nowiki>http://dev.alpinelinux.org/alpine/v1.7/usbdrive</nowiki>

Some news:
== Updated kernels ==
Due to the recent local root exploit both generic and vserver kernel are updated. To prevent similar future bugs be exploitable I have enabled UDEREF in kernels. This is a good protection but it does have some serious performance issues when running on virtual machines without hardware support.

== New version of busybox ==
Upgraded to busybox-1.9.x series. This adds some new features while still reduce the overall size. You gotta love busybox! Look out for bugs.

== 2/3 of the packages tested ==
The Alpine Package Testing Suite has now tests for over 2/3 of the packages. It means that most packages are confirmed working. Lots of bugs were found and fixed during the creation of those scripts.

<pre>
Removed packages:
barnyard-postgres-0.2.0-r1
dspam-postgres-3.8.0-r6
gnats-minimal-4.1.0
hotplug-20040923-r2
hotplug-base-20040401
isdn4k-utils-3.9_pre20060124
libevent-1.3a
libnfsidmap-0.19
lua-sqlite3-0.4.1
pmacct-postgres-0.11.3
snort-postgres-2.6.1.3-r1
ulogd-postgres-1.23-r1

New pacakges:
acf-dansguardian-0.1
acf-squid-0.2
bitlib-23_p2
dante-1.1.19-r1
diffstat-1.45
distcc-client-2.18.3-r10
distcc-server-2.18.3-r10
luatdb-doc-20080214

Upgraded/downgraded packages (from version):
acf-alpine-baselayout-0.2 (0.1)
acf-alpine-conf-0.2 (0.1)
acf-core-0.2 (0.1)
acf-devtools-0.2 (0.1)
acf-dhcp-0.2 (0.1)
acf-openntpd-0.2 (0.1)
acf-openvpn-0.2 (0.1)
acf-shorewall-0.2 (0.1)
acf-snort-0.2 (0.1)
apk-tools-0.13.1 (0.13)
busybox-1.9.1 (1.8.2-r1)
chrony-1.23 (1.21-r1)
clamav-0.92.1 (0.91.2-r1)
com_err-1.40.4 (1.40.3)
cracklib-2.8.12 (2.8.10)
cracklib-words-1.2 (1.1)
curl-7.17.1 (7.16.4)
dosfstools-2.11-r3 (2.11-r1)
dpkg-1.14.12 (1.13.25)
e2fsprogs-1.40.4 (1.40.3)
file-4.23 (4.21-r1)
findutils-4.3.11 (4.3.8-r1)
haserl-0.9.22 (0.9.21)
iptables-1.3.8-r3 (1.3.8-r2)
less-418 (416)
libao-0.8.8 (0.8.6-r3)
libcap-1.10-r11 (1.10-r9)
libpaper-1.1.23 (1.1.21)
libpcre-7.6-r1 (7.4)
libtasn1-1.2 (0.3.5)
libtool-1.5.26 (1.5.24)
libuuid1-1.40.4 (1.40.3)
lilo-22.8-r2 (22.7.3-r1)
lua-5.1.2-r2 (5.1.1-r2)
luaposix-5.1.2 (5.1-r2)
luatdb-20080214 (20070618)
man-1.6f (1.6e-r3)
mediawiki-1.11.1 (1.8.5)
mpd-0.13.1 (0.13.0)
mpg123-1.2.0 (0.67)
nano-2.0.7 (2.0.6)
ntfs3g-1.2216 (1.810)
ntfsprogs-2.0.0 (1.13.1-r1)
olsrd-0.5.5 (0.5.4)
openssh-4.7_p1-r3 (4.7_p1-r1)
openssh-client-4.7_p1-r3 (4.7_p1-r1)
openssh-kerberos-4.7_p1-r3 (4.7_p1-r1)
openssh-server-4.7_p1-r3 (4.7_p1-r1)
openvpn-2.0.7-r2 (2.0.6)
openvpn-doc-2.0.7-r2 (2.0.6)
pciutils-2.2.9 (2.2.8)
postfix-2.4.6-r2 (2.4.5)
psmisc-22.6 (22.5-r2)
readline-5.2_p12-r1 (5.2_p7)
slmodem-2.9.11_pre20080126-r1 (2.9.11_pre20070813)
snarf-7.0-r3 (7.0-r2)
ss-1.40.4 (1.40.3)
subversion-1.4.6 (1.4.5)
sysstat-8.0.4-r1 (8.0.3)
tcl-8.4.18 (8.4.15)
testdisk-6.8-r1 (6.5)
tinyproxy-1.6.3-r1 (1.6.3)
vpnc-0.5.1-r1 (0.5.1)

</pre>

[[Category:News]]

Release Notes for Alpine 1.7.8

2024-01-19T10:14:10Z

Ncopa: /* Alpine Package Testing Suite */ remove link to the obsolete package testing suite

The 1.7.8 release focus on bugfixing. While I believe this is a fairly stable release, there are reports on some bugs in PaX these days. So do some testing before you put this kernel on production machines. This kernel is based on hardened-sources-2.6.22-r8, marked as stable in Gentoo.

==iSCSI support==
This release includes support for both [[ISCSI_Target_and_Initiator_Configuration#iSCSI_Target|target]] (iscsitarget) and [[ISCSI_Target_and_Initiator_Configuration#iSCSI_Initiator|initiator]] (open-iscsi).

==Alpine Package Testing Suite==
Most important news this release is the use of the Alpine Package Testing Suite, which means packages are verified before a release. This will improve the quality of alpine as new tests are added.

Once there is a test script for every package, alpine-1.8, stable, will be released, so if you are interested in getting 1.8 out, you can do alot by helping writing test scripts.

<pre>
Removed packages:
apcupsd-3.10.18-r1
drbd-8.0.6-r1

New pacakges:
cracklib-words-1.1
json4lua-0.9.20
open-iscsi-2.0.865.15

Upgraded/downgraded packages (from version):
alpine-baselayout-1.6.2 (1.6.1)
alpine-conf-1.2 (1.1)
arpwatch-2.1.15-r5 (2.1.15-r4)
attr-2.4.39 (2.4.38)
baselayout-2.0.0_rc6 (2.0.0_rc5)
binutils-dev-2.18-r1 (2.17-r1)
busybox-1.7.3 (1.7.2)
bzip2-1.0.4-r1 (1.0.4)
cpio-2.9-r1 (2.9)
db-4.3.29-r2 (4.5.20_p2)
debootstrap-1.0.6 (1.0.3)
device-mapper-1.02.22-r5 (1.02.19-r1)
dovecot-1.0.5 (1.0.3)
dspam-3.8.0-r7 (3.8.0-r6)
ebtables-2.0.8.2 (2.0.8.1)
haproxy-1.3.13 (1.3.12)
iptraf-3.0.0-r4 (3.0.0-r3)
iscsitarget-0.4.15-r1 (0.4.15)
libgcrypt-1.2.4 (1.2.2-r1)
libmcrypt-2.5.8 (2.5.7)
libpcap-0.9.8 (0.9.7)
libpng-1.2.22 (1.2.21-r3)
lm_sensors-2.10.4 (2.10.1)
lsof-4.78-r1 (4.78)
lvm2-2.02.28-r2 (2.02.10)
mhash-0.9.9-r1 (0.9.9)
net-snmp-5.4.1-r1 (5.4)
openct-0.6.14 (0.6.11-r1)
openssl-0.9.8g (0.9.8f)
pciutils-2.2.7-r1 (2.2.4-r3)
php-5.2.5 (5.2.4_p20070914-r2)
python-2.4.4-r6 (2.4.4-r5)
slmodem-2.9.11_pre20070813 (2.9.11_pre20070505)
strace-4.5.16 (4.5.15)
tcpdump-3.9.8 (3.9.7-r1)
</pre>

[[Category:News]]

Release Notes for Alpine 3.19.0

2023-12-04T10:59:43Z

Ncopa:

== Base System ==

=== iptables-nft ===

The <code>/sbin/iptables{,-save,-restore}</code> symlinks now point to xtables-nft-multi instead of xtables-legacy-multi. This means they use the nftables kernel backend instead of the legacy iptables one.

Since the new iptables- binaries also don't use the iptables backend, to work with any existing rules and save them, you need to install {{pkg|iptables-legacy}} and use <code>iptables-legacy-save</code>.

Because mixing backends is not supported, you should reboot your system if you have to use the iptables commands after upgrading.

=== netns ===

The OpenRC package contains a patch to make it possible to start most services in netns namespaces. See also [[Netns|netns]].

== Others ==

=== HashiCorp packages ===

Due to [https://www.hashicorp.com/blog/hashicorp-adopts-business-source-license the relicensing of HashiCorp software] to [https://spdx.org/licenses/BUSL-1.1.html BUSL-1.1], a non-Open-Source license, the following software have been removed from Alpine:

* Consul
* Nomad
* Packer
* Terraform
* Vault

Our discussion on the topic can be found [https://gitlab.alpinelinux.org/alpine/aports/-/issues/15193 here].

{{pkg|opentofu}}, a fork of Terraform, is available in our testing repository for users of our rolling release, edge.

=== Java 21 ===

The latest LTS java release, openjdk21, is now available in the community repository.

=== KDE ===

KDE Applications have been upgraded from 23.04.x to 23.08.x. KDE Frameworks have been upgraded from 5.105.0 to 5.112.0.
Note that the KDE Frameworks packages have been renamed to add a 5 suffix in preparation for the upcoming KDE 6 release in the next Alpine release. Everything should automatically be upgraded properly but if problems occur make sure to check if the right renamed packages are installed.

=== Yggdrasil v0.5 ===

{{pkg|yggdrasil}} was upgraded to 0.5.x and the new routing scheme is incompatible with previous versions. "Nodes running this new version '''will not''' be able to peer with earlier versions of Yggdrasil" ([https://github.com/yggdrasil-network/yggdrasil-go/releases/tag/v0.5.0 v0.5.0 release notes], [https://yggdrasil-network.github.io/2023/10/22/upcoming-v05-release.html v0.5 blog post]).

== Upgrades ==

* GCC 13
* LLVM 17
* Kea 2.4
* Xen 4.18
* Git 2.43
* Perl 5.38
* PHP 8.3
* PostgreSQL 16
* SQLite 3.44
* Redis 7.2
* Node.js (lts) 20.10
* Node.js (current) 21.3
* QEMU 8.1
* Ceph 18.2
* GNOME 45
* LXQt 1.4
* wlroots 0.17
* Go 1.21
* Rust 1.72
* Crystal 1.10
* Racket 8.11
* ECL 23.9.9
* Erlang 26
* zlib 1.3
* libsodium 1.0.19
* ICU 74.1
* Protobuf 24.4
* fmt 10
* PipeWire 1.0.0

== Raspberry pi ==

The {{pkg|linux-rpi}} has been simplified. There is now a single kernel flavor for each architecture. This means that the kernels {{pkg|linux-rpi2}} and {{pkg|linux-rpi4}} are replaced with {{pkg|linux-rpi}}. The {{Path|config.txt}} is now generated by {{pkg|raspberrypi-bootloader}}.

[[Category:News]]

Release Notes for Alpine 3.19.0

2023-12-04T10:59:06Z

Ncopa: Mention linux-rpi changes

== Base System ==

=== iptables-nft ===

The <code>/sbin/iptables{,-save,-restore}</code> symlinks now point to xtables-nft-multi instead of xtables-legacy-multi. This means they use the nftables kernel backend instead of the legacy iptables one.

Since the new iptables- binaries also don't use the iptables backend, to work with any existing rules and save them, you need to install {{pkg|iptables-legacy}} and use <code>iptables-legacy-save</code>.

Because mixing backends is not supported, you should reboot your system if you have to use the iptables commands after upgrading.

=== netns ===

The OpenRC package contains a patch to make it possible to start most services in netns namespaces. See also [[Netns|netns]].

== Others ==

=== HashiCorp packages ===

Due to [https://www.hashicorp.com/blog/hashicorp-adopts-business-source-license the relicensing of HashiCorp software] to [https://spdx.org/licenses/BUSL-1.1.html BUSL-1.1], a non-Open-Source license, the following software have been removed from Alpine:

* Consul
* Nomad
* Packer
* Terraform
* Vault

Our discussion on the topic can be found [https://gitlab.alpinelinux.org/alpine/aports/-/issues/15193 here].

{{pkg|opentofu}}, a fork of Terraform, is available in our testing repository for users of our rolling release, edge.

=== Java 21 ===

The latest LTS java release, openjdk21, is now available in the community repository.

=== KDE ===

KDE Applications have been upgraded from 23.04.x to 23.08.x. KDE Frameworks have been upgraded from 5.105.0 to 5.112.0.
Note that the KDE Frameworks packages have been renamed to add a 5 suffix in preparation for the upcoming KDE 6 release in the next Alpine release. Everything should automatically be upgraded properly but if problems occur make sure to check if the right renamed packages are installed.

=== Yggdrasil v0.5 ===

{{pkg|yggdrasil}} was upgraded to 0.5.x and the new routing scheme is incompatible with previous versions. "Nodes running this new version '''will not''' be able to peer with earlier versions of Yggdrasil" ([https://github.com/yggdrasil-network/yggdrasil-go/releases/tag/v0.5.0 v0.5.0 release notes], [https://yggdrasil-network.github.io/2023/10/22/upcoming-v05-release.html v0.5 blog post]).

== Upgrades ==

* GCC 13
* LLVM 17
* Kea 2.4
* Xen 4.18
* Git 2.43
* Perl 5.38
* PHP 8.3
* PostgreSQL 16
* SQLite 3.44
* Redis 7.2
* Node.js (lts) 20.10
* Node.js (current) 21.3
* QEMU 8.1
* Ceph 18.2
* GNOME 45
* LXQt 1.4
* wlroots 0.17
* Go 1.21
* Rust 1.72
* Crystal 1.10
* Racket 8.11
* ECL 23.9.9
* Erlang 26
* zlib 1.3
* libsodium 1.0.19
* ICU 74.1
* Protobuf 24.4
* fmt 10
* PipeWire 1.0.0

== Raspberry pi ==

The {{pkg|linux-rpi kernels}} has been simplified. There is now a single kernel flavor for each architecture. This means that the kernels {{pkg|linux-rpi2}} and {{pkg|linux-rpi4}} are replaced with {{pkg|linux-rpi}}. The {{Path|config.txt}} is now generated by {{pkg|raspberrypi-bootloader}}.

[[Category:News]]

Template:AlpineLatest

2023-11-30T12:15:51Z

Ncopa: bump to 3.18.5

<noinclude>{{Template}}
</noinclude>3.18.5

Create Alpine Linux PV DomU

2023-08-18T15:03:53Z

Ncopa: /* Adjust the domU config file to boot from fresh install */ fix pvgrub2 loader path and install grub-xenhost

== Obtain a copy of Alpine Linux ==

To create an Alpine Linux paravirtualized (PV) DomU you'll need an Alpine Linux iso.

Download the latest alpine-virt iso from https://alpinelinux.org/downloads/

In this example we'll use {{path|/data/}} for the download and disk images.

==Mount the ISO image ==

Next, mount the iso so you can read the kernel and initramfs:

{{cmd | mount -t iso9660 -o loop /data/alpine-virt-{{AlpineLatest}}-x86_64.iso /media/cdrom }}

Now you have the kernel in {{path|/media/cdrom/boot/vmlinuz-virt}} and initramfs in {{path|/media/cdrom/boot/initramfs-virt}}.

Alternatively you can use {{path|uniso}} or {{path|p7zip}} to extract the content to a temporary area.

== Create the disk image ==
Now you need to create an empty file to be used as the hard drive of the DomU (in this example we are using a 3GB disk):

{{cmd | <nowiki>dd if=/dev/zero of=/data/a1.img bs=1M count=3000</nowiki>}}

Alternatively, if an LVM volume group (e.g. vg1) with free space is available on dom0, create a logical volume for Alpine:

{{cmd | <nowiki>sudo lvcreate -n alpine -L 10g vg1</nowiki>}}

== Create a DomU config file that boots the ISO image ==
Next, create a basic DomU configuration file, so you can launch the pv guest iso (save it where you like, although the most common place is {{path|/etc/xen/}}).

{{cat | /etc/xen/a1.cfg | <nowiki># Alpine Linux PV DomU

# Kernel paths for install
kernel = "/media/cdrom/boot/vmlinuz-virt"
ramdisk = "/media/cdrom/boot/initramfs-virt"
extra="modules=loop,squashfs console=hvc0"

# Path to HDD and iso file
disk = [
'format=raw, vdev=xvda, access=w, target=/data/a1.img',
'format=raw, vdev=xvdc, access=r, devtype=cdrom, target=/data/alpine-virt-</nowiki>{{AlpineLatest}}<nowiki>-x86_64.iso'
]

# Network configuration
vif = ['bridge=br0']

# DomU settings
memory = 512
name = "alpine-a1"
vcpus = 1
maxvcpus = 1
</nowiki>}}

If using LVM, replace {{path|/data/a1.img}} with {{path|/dev/vg1/alpine}} in the disk specification.

== Install the guest ==
Now that you have the necessary files, you can start the DomU to proceed with the install:

{{cmd|xl create -f /etc/xen/a1.cfg -c}}

Log into the system with user "root" and no password.

After configuring the basic system, you will be asked where would you like to install Alpine. Choose xvda and sys.

That will create three partitions on your disk. xvda1 for /boot, xvda2 for swap and xvda3 for /

<pre>
Available disks are:
xvda (3.1 GB )
Which disk(s) would you like to use? (or '?' for help or 'none') [none] xvda
The following disk is selected:
xvda (3.1 GB )
How would you like to use it? ('sys', 'data' or '?' for help) [?] sys
WARNING: The following disk(s) will be erased:
xvda (3.1 GB )
WARNING: Erase the above disk(s) and continue? [y/N]: y
Initializing partitions on /dev/xvda...
Creating file systems...
Installing system on /dev/xvda3:

Installation is complete. Please reboot.

#
</pre>

When you reboot, the pv bootloader pvgrub, will look to /boot/grub/grub.cfg for its menu, so create that file first.

Mount the boot partition and create a {{path|grub/grub.cfg}} file for pvgrub. (Note that grub.cfg is for pvgrub2 which replaced pvgrub1 and its menu.lst beginning in 2013.)

{{cmd |<nowiki>mount /dev/xvda1 /mnt
mkdir /mnt/grub</nowiki>}}

Install a basic text editor like nano or vim: 
{{cmd | apk add nano}}

If using nano, enter: 
{{cmd | nano /mnt/grub/grub.cfg}}

Then add the following to create a basic grub2 configuration file:
{{cat | /mnt/grub/grub.cfg |<nowiki>menuentry 'alpine-xen' {
set root=(xen/xvda,msdos1)
linux /boot/vmlinuz-virt root=/dev/xvda3 modules=ext4 console=hvc0
initrd /boot/initramfs
}</nowiki>}}

Finally, Ctrl-S to save, Ctrl-X to exit nano.

Unmount and power off.
{{cmd |umount /mnt
poweroff}}

== Adjust the domU config file to boot from fresh install ==

In your Dom0, edit your DomU config file to boot with pvgrub.

{{cat | /etc/xen/a1.cfg |<nowiki># Alpine Linux PV DomU

kernel = "/usr/lib/grub-xen/grub-x86_64-xen.bin"

# Path to HDD and iso file
disk = [
'format=raw, vdev=xvda, access=w, target=/data/a1.img'
]

# Network configuration
vif = ['bridge=br0']

# DomU settings
memory = 512
name = "alpine-a1"
vcpus = 1
maxvcpus = 1
</nowiki>}}

Make sure that grub-xenhost is installed.
{{cmd | apk add grub-xenhost}}

Remember to unmount the loopback iso image.
{{cmd | umount /media/cdrom}}

The next time you boot, you'll be presented with the grub boot menu, and your VM will boot.

== Using Legacy pvgrub ==

To use Legacy pvgrub you need to use a {{path|/boot/grub/menu.lst}} instead of {{path|/boot/grub/grub.cfg}}.

{{cat | /etc/xen/a1.cfg |<nowiki>default 0
timeout 2
title alpine-xen-pv
root (hd0,0)
kernel /boot/vmlinuz-virt root=/dev/xvda3 modules=ext4 console=hvc0
initrd /boot/initramfs-virt
</nowiki>}}

And in {{path|/etc/xen/a1.cfg}} you need to change the 'kernel' loader to
{{cat | /etc/xen/a1.cfg |<nowiki>...
kernel = "/usr/lib/xen/boot/pv-grub-x86_64.gz"
...
</nowiki>}}

== See also ==
* [https://www.linkedin.com/pulse/setting-up-alpine-linux-370-domu-vm-xenserver-72-ali-poursamadi Setting up Alpine Linux 3.7.0 as a domU VM on XenServer 7.2]

[[Category:Virtualization]]

Create Alpine Linux PV DomU

2023-08-18T14:59:49Z

Ncopa: /* Adjust the domU config file to boot from fresh install */ add instructions for legacy pvgrub

== Obtain a copy of Alpine Linux ==

To create an Alpine Linux paravirtualized (PV) DomU you'll need an Alpine Linux iso.

Download the latest alpine-virt iso from https://alpinelinux.org/downloads/

In this example we'll use {{path|/data/}} for the download and disk images.

==Mount the ISO image ==

Next, mount the iso so you can read the kernel and initramfs:

{{cmd | mount -t iso9660 -o loop /data/alpine-virt-{{AlpineLatest}}-x86_64.iso /media/cdrom }}

Now you have the kernel in {{path|/media/cdrom/boot/vmlinuz-virt}} and initramfs in {{path|/media/cdrom/boot/initramfs-virt}}.

Alternatively you can use {{path|uniso}} or {{path|p7zip}} to extract the content to a temporary area.

== Create the disk image ==
Now you need to create an empty file to be used as the hard drive of the DomU (in this example we are using a 3GB disk):

{{cmd | <nowiki>dd if=/dev/zero of=/data/a1.img bs=1M count=3000</nowiki>}}

Alternatively, if an LVM volume group (e.g. vg1) with free space is available on dom0, create a logical volume for Alpine:

{{cmd | <nowiki>sudo lvcreate -n alpine -L 10g vg1</nowiki>}}

== Create a DomU config file that boots the ISO image ==
Next, create a basic DomU configuration file, so you can launch the pv guest iso (save it where you like, although the most common place is {{path|/etc/xen/}}).

{{cat | /etc/xen/a1.cfg | <nowiki># Alpine Linux PV DomU

# Kernel paths for install
kernel = "/media/cdrom/boot/vmlinuz-virt"
ramdisk = "/media/cdrom/boot/initramfs-virt"
extra="modules=loop,squashfs console=hvc0"

# Path to HDD and iso file
disk = [
'format=raw, vdev=xvda, access=w, target=/data/a1.img',
'format=raw, vdev=xvdc, access=r, devtype=cdrom, target=/data/alpine-virt-</nowiki>{{AlpineLatest}}<nowiki>-x86_64.iso'
]

# Network configuration
vif = ['bridge=br0']

# DomU settings
memory = 512
name = "alpine-a1"
vcpus = 1
maxvcpus = 1
</nowiki>}}

If using LVM, replace {{path|/data/a1.img}} with {{path|/dev/vg1/alpine}} in the disk specification.

== Install the guest ==
Now that you have the necessary files, you can start the DomU to proceed with the install:

{{cmd|xl create -f /etc/xen/a1.cfg -c}}

Log into the system with user "root" and no password.

After configuring the basic system, you will be asked where would you like to install Alpine. Choose xvda and sys.

That will create three partitions on your disk. xvda1 for /boot, xvda2 for swap and xvda3 for /

<pre>
Available disks are:
xvda (3.1 GB )
Which disk(s) would you like to use? (or '?' for help or 'none') [none] xvda
The following disk is selected:
xvda (3.1 GB )
How would you like to use it? ('sys', 'data' or '?' for help) [?] sys
WARNING: The following disk(s) will be erased:
xvda (3.1 GB )
WARNING: Erase the above disk(s) and continue? [y/N]: y
Initializing partitions on /dev/xvda...
Creating file systems...
Installing system on /dev/xvda3:

Installation is complete. Please reboot.

#
</pre>

When you reboot, the pv bootloader pvgrub, will look to /boot/grub/grub.cfg for its menu, so create that file first.

Mount the boot partition and create a {{path|grub/grub.cfg}} file for pvgrub. (Note that grub.cfg is for pvgrub2 which replaced pvgrub1 and its menu.lst beginning in 2013.)

{{cmd |<nowiki>mount /dev/xvda1 /mnt
mkdir /mnt/grub</nowiki>}}

Install a basic text editor like nano or vim: 
{{cmd | apk add nano}}

If using nano, enter: 
{{cmd | nano /mnt/grub/grub.cfg}}

Then add the following to create a basic grub2 configuration file:
{{cat | /mnt/grub/grub.cfg |<nowiki>menuentry 'alpine-xen' {
set root=(xen/xvda,msdos1)
linux /boot/vmlinuz-virt root=/dev/xvda3 modules=ext4 console=hvc0
initrd /boot/initramfs
}</nowiki>}}

Finally, Ctrl-S to save, Ctrl-X to exit nano.

Unmount and power off.
{{cmd |umount /mnt
poweroff}}

== Adjust the domU config file to boot from fresh install ==

In your Dom0, edit your DomU config file to boot with pvgrub.

{{cat | /etc/xen/a1.cfg |<nowiki># Alpine Linux PV DomU

kernel = "/usr/lib/xen/boot/pv-grub-x86_64.gz"

# Path to HDD and iso file
disk = [
'format=raw, vdev=xvda, access=w, target=/data/a1.img'
]

# Network configuration
vif = ['bridge=br0']

# DomU settings
memory = 512
name = "alpine-a1"
vcpus = 1
maxvcpus = 1
</nowiki>}}

The name and location of pvgrub in Dom0 is distribution-specific, so you may need to change the "kernel=" line, above.

For example, in Debian 10, it's {{path|'/usr/lib/grub-xen/grub-x86_64-xen.bin'}}

Remember to unmount the loopback iso image.
{{cmd | umount /media/cdrom}}

The next time you boot, you'll be presented with the grub boot menu, and your VM will boot.

== Using Legacy pvgrub ==

To use Legacy pvgrub you need to use a {{path|/boot/grub/menu.lst}} instead of {{path|/boot/grub/grub.cfg}}.

{{cat | /etc/xen/a1.cfg |<nowiki>default 0
timeout 2
title alpine-xen-pv
root (hd0,0)
kernel /boot/vmlinuz-virt root=/dev/xvda3 modules=ext4 console=hvc0
initrd /boot/initramfs-virt
</nowiki>}}

And in {{path|/etc/xen/a1.cfg}} you need to change the 'kernel' loader to
{{cat | /etc/xen/a1.cfg |<nowiki>...
kernel = "/usr/lib/xen/boot/pv-grub-x86_64.gz"
...
</nowiki>}}

== See also ==
* [https://www.linkedin.com/pulse/setting-up-alpine-linux-370-domu-vm-xenserver-72-ali-poursamadi Setting up Alpine Linux 3.7.0 as a domU VM on XenServer 7.2]

[[Category:Virtualization]]

Create Alpine Linux PV DomU

2023-08-18T14:53:11Z

Ncopa: /* Install the guest */ add console=hvc0 as boot option

== Obtain a copy of Alpine Linux ==

To create an Alpine Linux paravirtualized (PV) DomU you'll need an Alpine Linux iso.

Download the latest alpine-virt iso from https://alpinelinux.org/downloads/

In this example we'll use {{path|/data/}} for the download and disk images.

==Mount the ISO image ==

Next, mount the iso so you can read the kernel and initramfs:

{{cmd | mount -t iso9660 -o loop /data/alpine-virt-{{AlpineLatest}}-x86_64.iso /media/cdrom }}

Now you have the kernel in {{path|/media/cdrom/boot/vmlinuz-virt}} and initramfs in {{path|/media/cdrom/boot/initramfs-virt}}.

Alternatively you can use {{path|uniso}} or {{path|p7zip}} to extract the content to a temporary area.

== Create the disk image ==
Now you need to create an empty file to be used as the hard drive of the DomU (in this example we are using a 3GB disk):

{{cmd | <nowiki>dd if=/dev/zero of=/data/a1.img bs=1M count=3000</nowiki>}}

Alternatively, if an LVM volume group (e.g. vg1) with free space is available on dom0, create a logical volume for Alpine:

{{cmd | <nowiki>sudo lvcreate -n alpine -L 10g vg1</nowiki>}}

== Create a DomU config file that boots the ISO image ==
Next, create a basic DomU configuration file, so you can launch the pv guest iso (save it where you like, although the most common place is {{path|/etc/xen/}}).

{{cat | /etc/xen/a1.cfg | <nowiki># Alpine Linux PV DomU

# Kernel paths for install
kernel = "/media/cdrom/boot/vmlinuz-virt"
ramdisk = "/media/cdrom/boot/initramfs-virt"
extra="modules=loop,squashfs console=hvc0"

# Path to HDD and iso file
disk = [
'format=raw, vdev=xvda, access=w, target=/data/a1.img',
'format=raw, vdev=xvdc, access=r, devtype=cdrom, target=/data/alpine-virt-</nowiki>{{AlpineLatest}}<nowiki>-x86_64.iso'
]

# Network configuration
vif = ['bridge=br0']

# DomU settings
memory = 512
name = "alpine-a1"
vcpus = 1
maxvcpus = 1
</nowiki>}}

If using LVM, replace {{path|/data/a1.img}} with {{path|/dev/vg1/alpine}} in the disk specification.

== Install the guest ==
Now that you have the necessary files, you can start the DomU to proceed with the install:

{{cmd|xl create -f /etc/xen/a1.cfg -c}}

Log into the system with user "root" and no password.

After configuring the basic system, you will be asked where would you like to install Alpine. Choose xvda and sys.

That will create three partitions on your disk. xvda1 for /boot, xvda2 for swap and xvda3 for /

<pre>
Available disks are:
xvda (3.1 GB )
Which disk(s) would you like to use? (or '?' for help or 'none') [none] xvda
The following disk is selected:
xvda (3.1 GB )
How would you like to use it? ('sys', 'data' or '?' for help) [?] sys
WARNING: The following disk(s) will be erased:
xvda (3.1 GB )
WARNING: Erase the above disk(s) and continue? [y/N]: y
Initializing partitions on /dev/xvda...
Creating file systems...
Installing system on /dev/xvda3:

Installation is complete. Please reboot.

#
</pre>

When you reboot, the pv bootloader pvgrub, will look to /boot/grub/grub.cfg for its menu, so create that file first.

Mount the boot partition and create a {{path|grub/grub.cfg}} file for pvgrub. (Note that grub.cfg is for pvgrub2 which replaced pvgrub1 and its menu.lst beginning in 2013.)

{{cmd |<nowiki>mount /dev/xvda1 /mnt
mkdir /mnt/grub</nowiki>}}

Install a basic text editor like nano or vim: 
{{cmd | apk add nano}}

If using nano, enter: 
{{cmd | nano /mnt/grub/grub.cfg}}

Then add the following to create a basic grub2 configuration file:
{{cat | /mnt/grub/grub.cfg |<nowiki>menuentry 'alpine-xen' {
set root=(xen/xvda,msdos1)
linux /boot/vmlinuz-virt root=/dev/xvda3 modules=ext4 console=hvc0
initrd /boot/initramfs
}</nowiki>}}

Finally, Ctrl-S to save, Ctrl-X to exit nano.

Unmount and power off.
{{cmd |umount /mnt
poweroff}}

== Adjust the domU config file to boot from fresh install ==

In your Dom0, edit your DomU config file to boot with pvgrub.

{{cat | /etc/xen/a1.cfg |<nowiki># Alpine Linux PV DomU

kernel = "/usr/lib/xen/boot/pv-grub-x86_64.gz"

# Path to HDD and iso file
disk = [
'format=raw, vdev=xvda, access=w, target=/data/a1.img'
]

# Network configuration
vif = ['bridge=br0']

# DomU settings
memory = 512
name = "alpine-a1"
vcpus = 1
maxvcpus = 1
</nowiki>}}

The name and location of pvgrub in Dom0 is distribution-specific, so you may need to change the "kernel=" line, above.

For example, in Debian 10, it's {{path|'/usr/lib/grub-xen/grub-x86_64-xen.bin'}}

Remember to unmount the loopback iso image.
{{cmd | umount /media/cdrom}}

The next time you boot, you'll be presented with the grub boot menu, and your VM will boot.

== See also ==
* [https://www.linkedin.com/pulse/setting-up-alpine-linux-370-domu-vm-xenserver-72-ali-poursamadi Setting up Alpine Linux 3.7.0 as a domU VM on XenServer 7.2]

[[Category:Virtualization]]

Template:AlpineLatest

2023-08-07T17:31:21Z

Ncopa:

<noinclude>{{Template}}
</noinclude>3.18.3

Template:Issue

2023-07-31T06:12:48Z

Ncopa: fix url to issues

<noinclude>{{Template}}
== Template Documentation ==
Link to [http://bugs.alpinelinux.org/ Alpine Issues].

== Example ==
<pre>{{Issue|279}}</pre>

will produce:
{{Issue|279}}

The issue's description can be included as an optional second argument.

</noinclude><includeonly>[https://gitlab.alpinelinux.org/alpine/aports/-/issues/{{{1}}} #{{{1}}}{{Ifn|{{{2|}}}|. {{{2}}}}}]</includeonly>

Release Notes for Alpine 3.18.0

2023-05-09T19:03:38Z

Ncopa: /* GNOME */

== Base System ==

=== Linux Kernel ===

{{pkg|linux-lts}} was updated from 5.15 to 6.1. [https://lkml.org/lkml/2022/12/11/206 release notes]

Kernel modules are now signed.

''Note: {{pkg|akms}} (Alpine Kernel Module Support) doesn't support modules signing yet, it will be implemented later.''

=== musl 1.2.4 ===

Support for DNS lookups over TCP. [https://www.openwall.com/lists/musl/2023/05/02/1 release notes]

=== DT_RELR ===

on x86, x86_64, and ppc64le, <code>-Wl,-z,pack-relative-relocs</code> is now added to the base LDFLAGS. this reduces elf (executable/shared-library) size by 10% on average.

however, these binaries are now not portable to other musl-based systems that have a musl older than 1.2.4, because older versions are incapable of loading these binaries.

=== OpenSSL 3.1 ===

[https://www.openssl.org/news/openssl-3.1-notes.html release notes]

=== Experimental headless installer ===

Support for head-less installs with [https://gitlab.alpinelinux.org/alpine/cloud/tiny-cloud tiny-cloud] was added. This is done via a volume with label <code>cidata</code>, similar to cloud-init's [https://cloudinit.readthedocs.io/en/latest/reference/datasources/nocloud.html NoCloud] provider. If this volume is found during boot, the network will be auto configured and provided, a default user named <code>alpine</code> will be created and ssh keys provided in meta-data will be added. This is experimental and may change without prior notice.

=== e2fsprogs 1.47.0 ===

The {{pkg|e2fsprogs}} package shipped with Alpine 3.18 changed the behaviour of <code>mke2fs</code> so that newly created filesystems have two additional features enabled.

From [https://e2fsprogs.sourceforge.net/e2fsprogs-release.html#1.47.0 release notes]:

<blockquote>The mke2fs program (via the mke2fs.conf file) now enables the metadata_csum_seed and orphan_file features by default.</blockquote>

However, whilst the <code>metadata_csum_seed</code> feature is known about by older versions of e2fsck the <code>orphan_file</code> feature was both added to e2fsprogs 1.47.0 '''and''' enabled at the same time. Therefore older versions of e2fsck are unable to fsck a filesystem created by mke2fs 1.47.0.

== Compilers and Runtimes ==


=== LLVM 16 ===

{{pkg|llvm16}} was added. [https://releases.llvm.org/16.0.0/docs/ReleaseNotes.html release notes]

=== Lua ===

{{pkg|luarocks}}, the package manager for Lua, was updated from 2.x to 3x. [https://github.com/luarocks/luarocks/blob/master/CHANGELOG.md#whats-new-in-luarocks-300 release notes]

=== Python ===

{{pkg|python3}} was updated from 3.10 to 3.11. [https://docs.python.org/3/whatsnew/3.11.html release notes]

==== splitting of python pycache .pyc files ====

Most python modules split their <code>__pycache__</code> to a <code>-pyc</code> subpackage, pulled by default. To save space and not pull it (incurring python interpreter startup costs, as it generates it each run), run <code>apk add !python3-pyc</code>

=== Ruby 3.2 ===

{{pkg|ruby}} was updated from 3.1 to 3.2. [https://www.ruby-lang.org/en/news/2022/12/25/ruby-3-2-0-released/ release notes]



=== Crystal 1.8 ===

{{pkg|crystal}} was updated from 1.6 to 1.8. [https://crystal-lang.org/2023/01/09/1.7.0-released/ release notes for 1.7], [https://crystal-lang.org/2023/04/14/1.8.0-released/ release notes for 1.8]

=== Go 1.20 ===

{{pkg|go}} [https://go.dev/blog/go1.20 release notes]

=== PHP 8.2 ===

Added 8.2 packages with a subset of the most common extensions. Version 8.1 still remains the primary provider priority, but some web applications started to use 8.2.

=== R 4.3 ===

{{pkg|R}} was updated from 4.2 to 4.3. [https://www.r-bloggers.com/2023/04/whats-new-in-r-4-3-0/ release notes]

=== Rust 1.69 ===

{{pkg|rust}} was updated from 1.64 to 1.69.

== Desktop ==

=== gdk-pixbuf-loaders ===

A few gdk-pixbuf loaders were added, and they were all added to an <code>install_if</code> metapackage rule. Run <code>apk add gdk-pixbuf-loaders</code> to enable the loaders for the corresponding image libraries you have installed.

=== GNOME 44 ===

[https://release.gnome.org/44/ release notes]

The {{pkg|gnome}} metapackage was reworked and the packages {{pkg|gnome-apps-extra}} and {{pkg|gnome-games-collection}} were removed to avoid opinionated lists in metapackages. It is advised to remove those from <code>/etc/apk/world</code> before performing the upgrade. Additionally, the new subpackage {{pkg|gnome-dev-tools}} was added following the upstream's recommendations.

On related news, to make use of GNOME Software, it is necessary to enable the <code>apk-polkit-server</code> openrc service. More info in the [https://wiki.alpinelinux.org/wiki/Gnome#Enabling_GNOME_Software wiki]

=== Plasma 5.27 ===

{{pkg|plasma}} was updated from 5.26 to 5.27. This includes some new packages like {{pkg|plasma-welcome}} (a welcoming application that shows up on the first boot to configure some initial settings) and {{pkg|flatpak-kcm}} (a configuration page for the system settings to control Flatpak permissions, much like GNOME's Flatseal).
This Plasma release is the last one that will be built on Qt5 and will probably remain in use for Alpine 3.19 as well.

=== Sway 1.8 ===

{{pkg|sway}} was updated from 1.7 to 1.8. [https://github.com/swaywm/sway/releases/tag/1.8 release notes]

== Others ==

=== dbus ===

dbus-activation has been removed from packages {{pkg|openrc-settingsd}} and {{pkg|apk-polkit-rs}}. To make use of their services, make sure to start and enable the <code>openrc-settingsd</code> and <code>apk-polkit-server</code> services, respectively.

=== nginx 1.24 ===

{{pkg|nginx}} was updated to the new stable branch 1.24.x. [https://nginx.org/en/CHANGES-1.24 release notes]

=== Removal of pipewire-media-session ===

{{pkg|pipewire-media-session}} was removed, as upstream explicitly recommends not to use it, and it's completely superceded by wireplumber.
if you used it, make sure you don't have {{pkg|pipewire-media-session}} in <code>/etc/apk/world</code>, and configure any scripts you might've had to launch <code>wireplumber</code> instead.

=== QEMU 8 ===

QEMU was updated from 7.1 to 8.0. [https://www.qemu.org/2023/04/20/qemu-8-0-0/ release notes]

=== Docker 23 ===

The {{pkg|docker}} package shipped with Alpine 3.18 has a dependency on {{pkg|docker-cli-buildx}}, as Docker 23 now uses it for builds.

Also, Docker 23 no longer enables the <code>overlay</code> storage driver, as it has been deprecated for a long time and is nearing removal. if your deployment is still configured to use it, <code>dockerd</code> will fail to start. To fix this, either...

* migrate to <code>overlay2</code> in <code>/etc/docker/daemon.json</code>
* hardcode it to <code>overlay</code> in the same file (instead of blank), though this will eventually break in a future upgrade

For more detailed information about Docker 23, please refer to the [https://docs.docker.com/engine/release-notes/23.0/ release notes].

Release Notes for Alpine 3.18.0

2023-05-09T19:02:53Z

Ncopa: /* Plasma 5.27.4 */

== Base System ==

=== Linux Kernel ===

{{pkg|linux-lts}} was updated from 5.15 to 6.1. [https://lkml.org/lkml/2022/12/11/206 release notes]

Kernel modules are now signed.

''Note: {{pkg|akms}} (Alpine Kernel Module Support) doesn't support modules signing yet, it will be implemented later.''

=== musl 1.2.4 ===

Support for DNS lookups over TCP. [https://www.openwall.com/lists/musl/2023/05/02/1 release notes]

=== DT_RELR ===

on x86, x86_64, and ppc64le, <code>-Wl,-z,pack-relative-relocs</code> is now added to the base LDFLAGS. this reduces elf (executable/shared-library) size by 10% on average.

however, these binaries are now not portable to other musl-based systems that have a musl older than 1.2.4, because older versions are incapable of loading these binaries.

=== OpenSSL 3.1 ===

[https://www.openssl.org/news/openssl-3.1-notes.html release notes]

=== Experimental headless installer ===

Support for head-less installs with [https://gitlab.alpinelinux.org/alpine/cloud/tiny-cloud tiny-cloud] was added. This is done via a volume with label <code>cidata</code>, similar to cloud-init's [https://cloudinit.readthedocs.io/en/latest/reference/datasources/nocloud.html NoCloud] provider. If this volume is found during boot, the network will be auto configured and provided, a default user named <code>alpine</code> will be created and ssh keys provided in meta-data will be added. This is experimental and may change without prior notice.

=== e2fsprogs 1.47.0 ===

The {{pkg|e2fsprogs}} package shipped with Alpine 3.18 changed the behaviour of <code>mke2fs</code> so that newly created filesystems have two additional features enabled.

From [https://e2fsprogs.sourceforge.net/e2fsprogs-release.html#1.47.0 release notes]:

<blockquote>The mke2fs program (via the mke2fs.conf file) now enables the metadata_csum_seed and orphan_file features by default.</blockquote>

However, whilst the <code>metadata_csum_seed</code> feature is known about by older versions of e2fsck the <code>orphan_file</code> feature was both added to e2fsprogs 1.47.0 '''and''' enabled at the same time. Therefore older versions of e2fsck are unable to fsck a filesystem created by mke2fs 1.47.0.

== Compilers and Runtimes ==


=== LLVM 16 ===

{{pkg|llvm16}} was added. [https://releases.llvm.org/16.0.0/docs/ReleaseNotes.html release notes]

=== Lua ===

{{pkg|luarocks}}, the package manager for Lua, was updated from 2.x to 3x. [https://github.com/luarocks/luarocks/blob/master/CHANGELOG.md#whats-new-in-luarocks-300 release notes]

=== Python ===

{{pkg|python3}} was updated from 3.10 to 3.11. [https://docs.python.org/3/whatsnew/3.11.html release notes]

==== splitting of python pycache .pyc files ====

Most python modules split their <code>__pycache__</code> to a <code>-pyc</code> subpackage, pulled by default. To save space and not pull it (incurring python interpreter startup costs, as it generates it each run), run <code>apk add !python3-pyc</code>

=== Ruby 3.2 ===

{{pkg|ruby}} was updated from 3.1 to 3.2. [https://www.ruby-lang.org/en/news/2022/12/25/ruby-3-2-0-released/ release notes]



=== Crystal 1.8 ===

{{pkg|crystal}} was updated from 1.6 to 1.8. [https://crystal-lang.org/2023/01/09/1.7.0-released/ release notes for 1.7], [https://crystal-lang.org/2023/04/14/1.8.0-released/ release notes for 1.8]

=== Go 1.20 ===

{{pkg|go}} [https://go.dev/blog/go1.20 release notes]

=== PHP 8.2 ===

Added 8.2 packages with a subset of the most common extensions. Version 8.1 still remains the primary provider priority, but some web applications started to use 8.2.

=== R 4.3 ===

{{pkg|R}} was updated from 4.2 to 4.3. [https://www.r-bloggers.com/2023/04/whats-new-in-r-4-3-0/ release notes]

=== Rust 1.69 ===

{{pkg|rust}} was updated from 1.64 to 1.69.

== Desktop ==

=== gdk-pixbuf-loaders ===

A few gdk-pixbuf loaders were added, and they were all added to an <code>install_if</code> metapackage rule. Run <code>apk add gdk-pixbuf-loaders</code> to enable the loaders for the corresponding image libraries you have installed.

=== GNOME ===

The {{pkg|gnome}} metapackage was reworked and the packages {{pkg|gnome-apps-extra}} and {{pkg|gnome-games-collection}} were removed to avoid opinionated lists in metapackages. It is advised to remove those from <code>/etc/apk/world</code> before performing the upgrade. Additionally, the new subpackage {{pkg|gnome-dev-tools}} was added following the upstream's recommendations.

On related news, to make use of GNOME Software, it is necessary to enable the <code>apk-polkit-server</code> openrc service. More info in the [https://wiki.alpinelinux.org/wiki/Gnome#Enabling_GNOME_Software wiki]

=== Plasma 5.27 ===

{{pkg|plasma}} was updated from 5.26 to 5.27. This includes some new packages like {{pkg|plasma-welcome}} (a welcoming application that shows up on the first boot to configure some initial settings) and {{pkg|flatpak-kcm}} (a configuration page for the system settings to control Flatpak permissions, much like GNOME's Flatseal).
This Plasma release is the last one that will be built on Qt5 and will probably remain in use for Alpine 3.19 as well.

=== Sway 1.8 ===

{{pkg|sway}} was updated from 1.7 to 1.8. [https://github.com/swaywm/sway/releases/tag/1.8 release notes]

== Others ==

=== dbus ===

dbus-activation has been removed from packages {{pkg|openrc-settingsd}} and {{pkg|apk-polkit-rs}}. To make use of their services, make sure to start and enable the <code>openrc-settingsd</code> and <code>apk-polkit-server</code> services, respectively.

=== nginx 1.24 ===

{{pkg|nginx}} was updated to the new stable branch 1.24.x. [https://nginx.org/en/CHANGES-1.24 release notes]

=== Removal of pipewire-media-session ===

{{pkg|pipewire-media-session}} was removed, as upstream explicitly recommends not to use it, and it's completely superceded by wireplumber.
if you used it, make sure you don't have {{pkg|pipewire-media-session}} in <code>/etc/apk/world</code>, and configure any scripts you might've had to launch <code>wireplumber</code> instead.

=== QEMU 8 ===

QEMU was updated from 7.1 to 8.0. [https://www.qemu.org/2023/04/20/qemu-8-0-0/ release notes]

=== Docker 23 ===

The {{pkg|docker}} package shipped with Alpine 3.18 has a dependency on {{pkg|docker-cli-buildx}}, as Docker 23 now uses it for builds.

Also, Docker 23 no longer enables the <code>overlay</code> storage driver, as it has been deprecated for a long time and is nearing removal. if your deployment is still configured to use it, <code>dockerd</code> will fail to start. To fix this, either...

* migrate to <code>overlay2</code> in <code>/etc/docker/daemon.json</code>
* hardcode it to <code>overlay</code> in the same file (instead of blank), though this will eventually break in a future upgrade

For more detailed information about Docker 23, please refer to the [https://docs.docker.com/engine/release-notes/23.0/ release notes].

Release Notes for Alpine 3.18.0

2023-05-09T19:00:40Z

Ncopa: /* Compilers and Runtimes */ add g0 1.20

== Base System ==

=== Linux Kernel ===

{{pkg|linux-lts}} was updated from 5.15 to 6.1. [https://lkml.org/lkml/2022/12/11/206 release notes]

Kernel modules are now signed.

''Note: {{pkg|akms}} (Alpine Kernel Module Support) doesn't support modules signing yet, it will be implemented later.''

=== musl 1.2.4 ===

Support for DNS lookups over TCP. [https://www.openwall.com/lists/musl/2023/05/02/1 release notes]

=== DT_RELR ===

on x86, x86_64, and ppc64le, <code>-Wl,-z,pack-relative-relocs</code> is now added to the base LDFLAGS. this reduces elf (executable/shared-library) size by 10% on average.

however, these binaries are now not portable to other musl-based systems that have a musl older than 1.2.4, because older versions are incapable of loading these binaries.

=== OpenSSL 3.1 ===

[https://www.openssl.org/news/openssl-3.1-notes.html release notes]

=== Experimental headless installer ===

Support for head-less installs with [https://gitlab.alpinelinux.org/alpine/cloud/tiny-cloud tiny-cloud] was added. This is done via a volume with label <code>cidata</code>, similar to cloud-init's [https://cloudinit.readthedocs.io/en/latest/reference/datasources/nocloud.html NoCloud] provider. If this volume is found during boot, the network will be auto configured and provided, a default user named <code>alpine</code> will be created and ssh keys provided in meta-data will be added. This is experimental and may change without prior notice.

=== e2fsprogs 1.47.0 ===

The {{pkg|e2fsprogs}} package shipped with Alpine 3.18 changed the behaviour of <code>mke2fs</code> so that newly created filesystems have two additional features enabled.

From [https://e2fsprogs.sourceforge.net/e2fsprogs-release.html#1.47.0 release notes]:

<blockquote>The mke2fs program (via the mke2fs.conf file) now enables the metadata_csum_seed and orphan_file features by default.</blockquote>

However, whilst the <code>metadata_csum_seed</code> feature is known about by older versions of e2fsck the <code>orphan_file</code> feature was both added to e2fsprogs 1.47.0 '''and''' enabled at the same time. Therefore older versions of e2fsck are unable to fsck a filesystem created by mke2fs 1.47.0.

== Compilers and Runtimes ==


=== LLVM 16 ===

{{pkg|llvm16}} was added. [https://releases.llvm.org/16.0.0/docs/ReleaseNotes.html release notes]

=== Lua ===

{{pkg|luarocks}}, the package manager for Lua, was updated from 2.x to 3x. [https://github.com/luarocks/luarocks/blob/master/CHANGELOG.md#whats-new-in-luarocks-300 release notes]

=== Python ===

{{pkg|python3}} was updated from 3.10 to 3.11. [https://docs.python.org/3/whatsnew/3.11.html release notes]

==== splitting of python pycache .pyc files ====

Most python modules split their <code>__pycache__</code> to a <code>-pyc</code> subpackage, pulled by default. To save space and not pull it (incurring python interpreter startup costs, as it generates it each run), run <code>apk add !python3-pyc</code>

=== Ruby 3.2 ===

{{pkg|ruby}} was updated from 3.1 to 3.2. [https://www.ruby-lang.org/en/news/2022/12/25/ruby-3-2-0-released/ release notes]



=== Crystal 1.8 ===

{{pkg|crystal}} was updated from 1.6 to 1.8. [https://crystal-lang.org/2023/01/09/1.7.0-released/ release notes for 1.7], [https://crystal-lang.org/2023/04/14/1.8.0-released/ release notes for 1.8]

=== Go 1.20 ===

{{pkg|go}} [https://go.dev/blog/go1.20 release notes]

=== PHP 8.2 ===

Added 8.2 packages with a subset of the most common extensions. Version 8.1 still remains the primary provider priority, but some web applications started to use 8.2.

=== R 4.3 ===

{{pkg|R}} was updated from 4.2 to 4.3. [https://www.r-bloggers.com/2023/04/whats-new-in-r-4-3-0/ release notes]

=== Rust 1.69 ===

{{pkg|rust}} was updated from 1.64 to 1.69.

== Desktop ==

=== gdk-pixbuf-loaders ===

A few gdk-pixbuf loaders were added, and they were all added to an <code>install_if</code> metapackage rule. Run <code>apk add gdk-pixbuf-loaders</code> to enable the loaders for the corresponding image libraries you have installed.

=== GNOME ===

The {{pkg|gnome}} metapackage was reworked and the packages {{pkg|gnome-apps-extra}} and {{pkg|gnome-games-collection}} were removed to avoid opinionated lists in metapackages. It is advised to remove those from <code>/etc/apk/world</code> before performing the upgrade. Additionally, the new subpackage {{pkg|gnome-dev-tools}} was added following the upstream's recommendations.

On related news, to make use of GNOME Software, it is necessary to enable the <code>apk-polkit-server</code> openrc service. More info in the [https://wiki.alpinelinux.org/wiki/Gnome#Enabling_GNOME_Software wiki]

=== Plasma 5.27.4 ===

{{pkg|plasma}} was updated from 5.26.5 to 5.27.4. This includes some new packages like {{pkg|plasma-welcome}} (a welcoming application that shows up on the first boot to configure some initial settings) and {{pkg|flatpak-kcm}} (a configuration page for the system settings to control Flatpak permissions, much like GNOME's Flatseal).
This Plasma release is the last one that will be built on Qt5 and will probably remain in use for Alpine 3.19 as well.

=== Sway 1.8 ===

{{pkg|sway}} was updated from 1.7 to 1.8. [https://github.com/swaywm/sway/releases/tag/1.8 release notes]

== Others ==

=== dbus ===

dbus-activation has been removed from packages {{pkg|openrc-settingsd}} and {{pkg|apk-polkit-rs}}. To make use of their services, make sure to start and enable the <code>openrc-settingsd</code> and <code>apk-polkit-server</code> services, respectively.

=== nginx 1.24 ===

{{pkg|nginx}} was updated to the new stable branch 1.24.x. [https://nginx.org/en/CHANGES-1.24 release notes]

=== Removal of pipewire-media-session ===

{{pkg|pipewire-media-session}} was removed, as upstream explicitly recommends not to use it, and it's completely superceded by wireplumber.
if you used it, make sure you don't have {{pkg|pipewire-media-session}} in <code>/etc/apk/world</code>, and configure any scripts you might've had to launch <code>wireplumber</code> instead.

=== QEMU 8 ===

QEMU was updated from 7.1 to 8.0. [https://www.qemu.org/2023/04/20/qemu-8-0-0/ release notes]

=== Docker 23 ===

The {{pkg|docker}} package shipped with Alpine 3.18 has a dependency on {{pkg|docker-cli-buildx}}, as Docker 23 now uses it for builds.

Also, Docker 23 no longer enables the <code>overlay</code> storage driver, as it has been deprecated for a long time and is nearing removal. if your deployment is still configured to use it, <code>dockerd</code> will fail to start. To fix this, either...

* migrate to <code>overlay2</code> in <code>/etc/docker/daemon.json</code>
* hardcode it to <code>overlay</code> in the same file (instead of blank), though this will eventually break in a future upgrade

For more detailed information about Docker 23, please refer to the [https://docs.docker.com/engine/release-notes/23.0/ release notes].

Release Notes for Alpine 3.18.0

2023-05-09T18:53:45Z

Ncopa: add openssl 3.1

== Base System ==

=== Linux Kernel ===

{{pkg|linux-lts}} was updated from 5.15 to 6.1. [https://lkml.org/lkml/2022/12/11/206 release notes]

Kernel modules are now signed.

''Note: {{pkg|akms}} (Alpine Kernel Module Support) doesn't support modules signing yet, it will be implemented later.''

=== musl 1.2.4 ===

Support for DNS lookups over TCP. [https://www.openwall.com/lists/musl/2023/05/02/1 release notes]

=== DT_RELR ===

on x86, x86_64, and ppc64le, <code>-Wl,-z,pack-relative-relocs</code> is now added to the base LDFLAGS. this reduces elf (executable/shared-library) size by 10% on average.

however, these binaries are now not portable to other musl-based systems that have a musl older than 1.2.4, because older versions are incapable of loading these binaries.

=== OpenSSL 3.1 ===

[https://www.openssl.org/news/openssl-3.1-notes.html release notes]

=== Experimental headless installer ===

Support for head-less installs with [https://gitlab.alpinelinux.org/alpine/cloud/tiny-cloud tiny-cloud] was added. This is done via a volume with label <code>cidata</code>, similar to cloud-init's [https://cloudinit.readthedocs.io/en/latest/reference/datasources/nocloud.html NoCloud] provider. If this volume is found during boot, the network will be auto configured and provided, a default user named <code>alpine</code> will be created and ssh keys provided in meta-data will be added. This is experimental and may change without prior notice.

=== e2fsprogs 1.47.0 ===

The {{pkg|e2fsprogs}} package shipped with Alpine 3.18 changed the behaviour of <code>mke2fs</code> so that newly created filesystems have two additional features enabled.

From [https://e2fsprogs.sourceforge.net/e2fsprogs-release.html#1.47.0 release notes]:

<blockquote>The mke2fs program (via the mke2fs.conf file) now enables the metadata_csum_seed and orphan_file features by default.</blockquote>

However, whilst the <code>metadata_csum_seed</code> feature is known about by older versions of e2fsck the <code>orphan_file</code> feature was both added to e2fsprogs 1.47.0 '''and''' enabled at the same time. Therefore older versions of e2fsck are unable to fsck a filesystem created by mke2fs 1.47.0.

== Compilers and Runtimes ==


=== LLVM 16 ===

{{pkg|llvm16}} was added. [https://releases.llvm.org/16.0.0/docs/ReleaseNotes.html release notes]

=== Lua ===

{{pkg|luarocks}}, the package manager for Lua, was updated from 2.x to 3x. [https://github.com/luarocks/luarocks/blob/master/CHANGELOG.md#whats-new-in-luarocks-300 release notes]

=== Python ===

{{pkg|python3}} was updated from 3.10 to 3.11. [https://docs.python.org/3/whatsnew/3.11.html release notes]

==== splitting of python pycache .pyc files ====

Most python modules split their <code>__pycache__</code> to a <code>-pyc</code> subpackage, pulled by default. To save space and not pull it (incurring python interpreter startup costs, as it generates it each run), run <code>apk add !python3-pyc</code>

=== Ruby 3.2 ===

{{pkg|ruby}} was updated from 3.1 to 3.2. [https://www.ruby-lang.org/en/news/2022/12/25/ruby-3-2-0-released/ release notes]



=== Crystal 1.8 ===

{{pkg|crystal}} was updated from 1.6 to 1.8. [https://crystal-lang.org/2023/01/09/1.7.0-released/ release notes for 1.7], [https://crystal-lang.org/2023/04/14/1.8.0-released/ release notes for 1.8]

=== PHP 8.2 ===

Added 8.2 packages with a subset of the most common extensions. Version 8.1 still remains the primary provider priority, but some web applications started to use 8.2.

=== R 4.3 ===

{{pkg|R}} was updated from 4.2 to 4.3. [https://www.r-bloggers.com/2023/04/whats-new-in-r-4-3-0/ release notes]

=== Rust 1.69 ===

{{pkg|rust}} was updated from 1.64 to 1.69.

== Desktop ==

=== gdk-pixbuf-loaders ===

A few gdk-pixbuf loaders were added, and they were all added to an <code>install_if</code> metapackage rule. Run <code>apk add gdk-pixbuf-loaders</code> to enable the loaders for the corresponding image libraries you have installed.

=== GNOME ===

The {{pkg|gnome}} metapackage was reworked and the packages {{pkg|gnome-apps-extra}} and {{pkg|gnome-games-collection}} were removed to avoid opinionated lists in metapackages. It is advised to remove those from <code>/etc/apk/world</code> before performing the upgrade. Additionally, the new subpackage {{pkg|gnome-dev-tools}} was added following the upstream's recommendations.

On related news, to make use of GNOME Software, it is necessary to enable the <code>apk-polkit-server</code> openrc service. More info in the [https://wiki.alpinelinux.org/wiki/Gnome#Enabling_GNOME_Software wiki]

=== Plasma 5.27.4 ===

{{pkg|plasma}} was updated from 5.26.5 to 5.27.4. This includes some new packages like {{pkg|plasma-welcome}} (a welcoming application that shows up on the first boot to configure some initial settings) and {{pkg|flatpak-kcm}} (a configuration page for the system settings to control Flatpak permissions, much like GNOME's Flatseal).
This Plasma release is the last one that will be built on Qt5 and will probably remain in use for Alpine 3.19 as well.

=== Sway 1.8 ===

{{pkg|sway}} was updated from 1.7 to 1.8. [https://github.com/swaywm/sway/releases/tag/1.8 release notes]

== Others ==

=== dbus ===

dbus-activation has been removed from packages {{pkg|openrc-settingsd}} and {{pkg|apk-polkit-rs}}. To make use of their services, make sure to start and enable the <code>openrc-settingsd</code> and <code>apk-polkit-server</code> services, respectively.

=== nginx 1.24 ===

{{pkg|nginx}} was updated to the new stable branch 1.24.x. [https://nginx.org/en/CHANGES-1.24 release notes]

=== Removal of pipewire-media-session ===

{{pkg|pipewire-media-session}} was removed, as upstream explicitly recommends not to use it, and it's completely superceded by wireplumber.
if you used it, make sure you don't have {{pkg|pipewire-media-session}} in <code>/etc/apk/world</code>, and configure any scripts you might've had to launch <code>wireplumber</code> instead.

=== QEMU 8 ===

QEMU was updated from 7.1 to 8.0. [https://www.qemu.org/2023/04/20/qemu-8-0-0/ release notes]

=== Docker 23 ===

The {{pkg|docker}} package shipped with Alpine 3.18 has a dependency on {{pkg|docker-cli-buildx}}, as Docker 23 now uses it for builds.

Also, Docker 23 no longer enables the <code>overlay</code> storage driver, as it has been deprecated for a long time and is nearing removal. if your deployment is still configured to use it, <code>dockerd</code> will fail to start. To fix this, either...

* migrate to <code>overlay2</code> in <code>/etc/docker/daemon.json</code>
* hardcode it to <code>overlay</code> in the same file (instead of blank), though this will eventually break in a future upgrade

For more detailed information about Docker 23, please refer to the [https://docs.docker.com/engine/release-notes/23.0/ release notes].

Release Notes for Alpine 3.18.0

2023-05-09T15:03:35Z

Ncopa: /* Base System */ mention head-less install with tiny-cloud

== Base System ==

=== Linux Kernel ===

{{pkg|linux-lts}} was updated from 5.15 to 6.1. [https://lkml.org/lkml/2022/12/11/206 release notes]

Kernel modules are now signed.

''Note: {{pkg|akms}} (Alpine Kernel Module Support) doesn't support modules signing yet, it will be implemented later.''

=== musl 1.2.4 ===

Support for DNS lookups over TCP. [https://www.openwall.com/lists/musl/2023/05/02/1 release notes]

=== DT_RELR ===

on x86, x86_64, and ppc64le, <code>-Wl,-z,pack-relative-relocs</code> is now added to the base LDFLAGS. this reduces elf (executable/shared-library) size by 10% on average.

however, these binaries are now not portable to other musl-based systems that have a musl older than 1.2.4, because older versions are incapable of loading these binaries.

=== Experimental headless installer ===

Support for head-less installs with [https://gitlab.alpinelinux.org/alpine/cloud/tiny-cloud tiny-cloud] was added. This is done via a volume with label <code>cidata</code>, similar to cloud-init's [https://cloudinit.readthedocs.io/en/latest/reference/datasources/nocloud.html NoCloud] provider. If this volume is found during boot, the network will be auto configured and provided, a default user named <code>alpine</code> will be created and ssh keys provided in meta-data will be added. This is experimental and may change without prior notice.

=== e2fsprogs 1.47.0 ===

The {{pkg|e2fsprogs}} package shipped with Alpine 3.18 changed the behaviour of <code>mke2fs</code> so that newly created filesystems have two additional features enabled.

From [https://e2fsprogs.sourceforge.net/e2fsprogs-release.html#1.47.0 release notes]:

<blockquote>The mke2fs program (via the mke2fs.conf file) now enables the metadata_csum_seed and orphan_file features by default.</blockquote>

However, whilst the <code>metadata_csum_seed</code> feature is known about by older versions of e2fsck the <code>orphan_file</code> feature was both added to e2fsprogs 1.47.0 '''and''' enabled at the same time. Therefore older versions of e2fsck are unable to fsck a filesystem created by mke2fs 1.47.0.

== Compilers and Runtimes ==


=== LLVM 16 ===

{{pkg|llvm16}} was added. [https://releases.llvm.org/16.0.0/docs/ReleaseNotes.html release notes]

=== Lua ===

{{pkg|luarocks}}, the package manager for Lua, was updated from 2.x to 3x. [https://github.com/luarocks/luarocks/blob/master/CHANGELOG.md#whats-new-in-luarocks-300 release notes]

=== Python ===

{{pkg|python3}} was updated from 3.10 to 3.11. [https://docs.python.org/3/whatsnew/3.11.html release notes]

==== splitting of python pycache .pyc files ====

Most python modules split their <code>__pycache__</code> to a <code>-pyc</code> subpackage, pulled by default. To save space and not pull it (incurring python interpreter startup costs, as it generates it each run), run <code>apk add !python3-pyc</code>

=== Ruby 3.2 ===

{{pkg|ruby}} was updated from 3.1 to 3.2. [https://www.ruby-lang.org/en/news/2022/12/25/ruby-3-2-0-released/ release notes]



=== Crystal 1.8 ===

{{pkg|crystal}} was updated from 1.6 to 1.8. [https://crystal-lang.org/2023/01/09/1.7.0-released/ release notes for 1.7], [https://crystal-lang.org/2023/04/14/1.8.0-released/ release notes for 1.8]

=== PHP 8.2 ===

Added 8.2 packages with a subset of the most common extensions. Version 8.1 still remains the primary provider priority, but some web applications started to use 8.2.

=== R 4.3 ===

{{pkg|R}} was updated from 4.2 to 4.3. [https://www.r-bloggers.com/2023/04/whats-new-in-r-4-3-0/ release notes]

=== Rust 1.69 ===

{{pkg|rust}} was updated from 1.64 to 1.69.

== Desktop ==

=== gdk-pixbuf-loaders ===

A few gdk-pixbuf loaders were added, and they were all added to an <code>install_if</code> metapackage rule. Run <code>apk add gdk-pixbuf-loaders</code> to enable the loaders for the corresponding image libraries you have installed.

=== GNOME ===

The {{pkg|gnome}} metapackage was reworked and the packages {{pkg|gnome-apps-extra}} and {{pkg|gnome-games-collection}} were removed to avoid opinionated lists in metapackages. It is advised to remove those from <code>/etc/apk/world</code> before performing the upgrade. Additionally, the new subpackage {{pkg|gnome-dev-tools}} was added following the upstream's recommendations.

On related news, to make use of GNOME Software, it is necessary to enable the <code>apk-polkit-server</code> openrc service. More info in the [https://wiki.alpinelinux.org/wiki/Gnome#Enabling_GNOME_Software wiki]

=== Plasma 5.27.4 ===

{{pkg|plasma}} was updated from 5.26.5 to 5.27.4. This includes some new packages like {{pkg|plasma-welcome}} (a welcoming application that shows up on the first boot to configure some initial settings) and {{pkg|flatpak-kcm}} (a configuration page for the system settings to control Flatpak permissions, much like GNOME's Flatseal).
This Plasma release is the last one that will be built on Qt5 and will probably remain in use for Alpine 3.19 as well.

=== Sway 1.8 ===

{{pkg|sway}} was updated from 1.7 to 1.8. [https://github.com/swaywm/sway/releases/tag/1.8 release notes]

== Others ==

=== dbus ===

dbus-activation has been removed from packages {{pkg|openrc-settingsd}} and {{pkg|apk-polkit-rs}}. To make use of their services, make sure to start and enable the <code>openrc-settingsd</code> and <code>apk-polkit-server</code> services, respectively.

=== nginx 1.24 ===

{{pkg|nginx}} was updated to the new stable branch 1.24.x. [https://nginx.org/en/CHANGES-1.24 release notes]

=== Removal of pipewire-media-session ===

{{pkg|pipewire-media-session}} was removed, as upstream explicitly recommends not to use it, and it's completely superceded by wireplumber.
if you used it, make sure you don't have {{pkg|pipewire-media-session}} in <code>/etc/apk/world</code>, and configure any scripts you might've had to launch <code>wireplumber</code> instead.

=== QEMU 8 ===

QEMU was updated from 7.1 to 8.0. [https://www.qemu.org/2023/04/20/qemu-8-0-0/ release notes]

=== Docker 23 ===

The {{pkg|docker}} package shipped with Alpine 3.18 has a dependency on {{pkg|docker-cli-buildx}}, as Docker 23 now uses it for builds.

Also, Docker 23 no longer enables the <code>overlay</code> storage driver, as it has been deprecated for a long time and is nearing removal. if your deployment is still configured to use it, <code>dockerd</code> will fail to start. To fix this, either...

* migrate to <code>overlay2</code> in <code>/etc/docker/daemon.json</code>
* hardcode it to <code>overlay</code> in the same file (instead of blank), though this will eventually break in a future upgrade

For more detailed information about Docker 23, please refer to the [https://docs.docker.com/engine/release-notes/23.0/ release notes].

Release Notes for Alpine 3.18.0

2023-05-09T14:49:47Z

Ncopa: /* Others */ move stuff in main to the top

== Base System ==

=== Linux Kernel ===

{{pkg|linux-lts}} was updated from 5.15 to 6.1. [https://lkml.org/lkml/2022/12/11/206 release notes]

Kernel modules are now signed.

''Note: {{pkg|akms}} (Alpine Kernel Module Support) doesn't support modules signing yet, it will be implemented later.''

=== musl 1.2.4 ===

Support for DNS lookups over TCP. [https://www.openwall.com/lists/musl/2023/05/02/1 release notes]

=== DT_RELR ===

on x86, x86_64, and ppc64le, <code>-Wl,-z,pack-relative-relocs</code> is now added to the base LDFLAGS. this reduces elf (executable/shared-library) size by 10% on average.

however, these binaries are now not portable to other musl-based systems that have a musl older than 1.2.4, because older versions are incapable of loading these binaries.

=== e2fsprogs 1.47.0 ===

The {{pkg|e2fsprogs}} package shipped with Alpine 3.18 changed the behaviour of <code>mke2fs</code> so that newly created filesystems have two additional features enabled.

From [https://e2fsprogs.sourceforge.net/e2fsprogs-release.html#1.47.0 release notes]:

<blockquote>The mke2fs program (via the mke2fs.conf file) now enables the metadata_csum_seed and orphan_file features by default.</blockquote>

However, whilst the <code>metadata_csum_seed</code> feature is known about by older versions of e2fsck the <code>orphan_file</code> feature was both added to e2fsprogs 1.47.0 '''and''' enabled at the same time. Therefore older versions of e2fsck are unable to fsck a filesystem created by mke2fs 1.47.0.

== Compilers and Runtimes ==


=== LLVM 16 ===

{{pkg|llvm16}} was added. [https://releases.llvm.org/16.0.0/docs/ReleaseNotes.html release notes]

=== Lua ===

{{pkg|luarocks}}, the package manager for Lua, was updated from 2.x to 3x. [https://github.com/luarocks/luarocks/blob/master/CHANGELOG.md#whats-new-in-luarocks-300 release notes]

=== Python ===

{{pkg|python3}} was updated from 3.10 to 3.11. [https://docs.python.org/3/whatsnew/3.11.html release notes]

==== splitting of python pycache .pyc files ====

Most python modules split their <code>__pycache__</code> to a <code>-pyc</code> subpackage, pulled by default. To save space and not pull it (incurring python interpreter startup costs, as it generates it each run), run <code>apk add !python3-pyc</code>

=== Ruby 3.2 ===

{{pkg|ruby}} was updated from 3.1 to 3.2. [https://www.ruby-lang.org/en/news/2022/12/25/ruby-3-2-0-released/ release notes]



=== Crystal 1.8 ===

{{pkg|crystal}} was updated from 1.6 to 1.8. [https://crystal-lang.org/2023/01/09/1.7.0-released/ release notes for 1.7], [https://crystal-lang.org/2023/04/14/1.8.0-released/ release notes for 1.8]

=== PHP 8.2 ===

Added 8.2 packages with a subset of the most common extensions. Version 8.1 still remains the primary provider priority, but some web applications started to use 8.2.

=== R 4.3 ===

{{pkg|R}} was updated from 4.2 to 4.3. [https://www.r-bloggers.com/2023/04/whats-new-in-r-4-3-0/ release notes]

=== Rust 1.69 ===

{{pkg|rust}} was updated from 1.64 to 1.69.

== Desktop ==

=== gdk-pixbuf-loaders ===

A few gdk-pixbuf loaders were added, and they were all added to an <code>install_if</code> metapackage rule. Run <code>apk add gdk-pixbuf-loaders</code> to enable the loaders for the corresponding image libraries you have installed.

=== GNOME ===

The {{pkg|gnome}} metapackage was reworked and the packages {{pkg|gnome-apps-extra}} and {{pkg|gnome-games-collection}} were removed to avoid opinionated lists in metapackages. It is advised to remove those from <code>/etc/apk/world</code> before performing the upgrade. Additionally, the new subpackage {{pkg|gnome-dev-tools}} was added following the upstream's recommendations.

On related news, to make use of GNOME Software, it is necessary to enable the <code>apk-polkit-server</code> openrc service. More info in the [https://wiki.alpinelinux.org/wiki/Gnome#Enabling_GNOME_Software wiki]

=== Plasma 5.27.4 ===

{{pkg|plasma}} was updated from 5.26.5 to 5.27.4. This includes some new packages like {{pkg|plasma-welcome}} (a welcoming application that shows up on the first boot to configure some initial settings) and {{pkg|flatpak-kcm}} (a configuration page for the system settings to control Flatpak permissions, much like GNOME's Flatseal).
This Plasma release is the last one that will be built on Qt5 and will probably remain in use for Alpine 3.19 as well.

=== Sway 1.8 ===

{{pkg|sway}} was updated from 1.7 to 1.8. [https://github.com/swaywm/sway/releases/tag/1.8 release notes]

== Others ==

=== dbus ===

dbus-activation has been removed from packages {{pkg|openrc-settingsd}} and {{pkg|apk-polkit-rs}}. To make use of their services, make sure to start and enable the <code>openrc-settingsd</code> and <code>apk-polkit-server</code> services, respectively.

=== nginx 1.24 ===

{{pkg|nginx}} was updated to the new stable branch 1.24.x. [https://nginx.org/en/CHANGES-1.24 release notes]

=== Removal of pipewire-media-session ===

{{pkg|pipewire-media-session}} was removed, as upstream explicitly recommends not to use it, and it's completely superceded by wireplumber.
if you used it, make sure you don't have {{pkg|pipewire-media-session}} in <code>/etc/apk/world</code>, and configure any scripts you might've had to launch <code>wireplumber</code> instead.

=== QEMU 8 ===

QEMU was updated from 7.1 to 8.0. [https://www.qemu.org/2023/04/20/qemu-8-0-0/ release notes]

=== Docker 23 ===

The {{pkg|docker}} package shipped with Alpine 3.18 has a dependency on {{pkg|docker-cli-buildx}}, as Docker 23 now uses it for builds.

Also, Docker 23 no longer enables the <code>overlay</code> storage driver, as it has been deprecated for a long time and is nearing removal. if your deployment is still configured to use it, <code>dockerd</code> will fail to start. To fix this, either...

* migrate to <code>overlay2</code> in <code>/etc/docker/daemon.json</code>
* hardcode it to <code>overlay</code> in the same file (instead of blank), though this will eventually break in a future upgrade

For more detailed information about Docker 23, please refer to the [https://docs.docker.com/engine/release-notes/23.0/ release notes].

Release Notes for Alpine 3.18.0

2023-05-09T14:48:22Z

Ncopa: /* Desktop */ move stuff in main to the top

== Base System ==

=== Linux Kernel ===

{{pkg|linux-lts}} was updated from 5.15 to 6.1. [https://lkml.org/lkml/2022/12/11/206 release notes]

Kernel modules are now signed.

''Note: {{pkg|akms}} (Alpine Kernel Module Support) doesn't support modules signing yet, it will be implemented later.''

=== musl 1.2.4 ===

Support for DNS lookups over TCP. [https://www.openwall.com/lists/musl/2023/05/02/1 release notes]

=== DT_RELR ===

on x86, x86_64, and ppc64le, <code>-Wl,-z,pack-relative-relocs</code> is now added to the base LDFLAGS. this reduces elf (executable/shared-library) size by 10% on average.

however, these binaries are now not portable to other musl-based systems that have a musl older than 1.2.4, because older versions are incapable of loading these binaries.

=== e2fsprogs 1.47.0 ===

The {{pkg|e2fsprogs}} package shipped with Alpine 3.18 changed the behaviour of <code>mke2fs</code> so that newly created filesystems have two additional features enabled.

From [https://e2fsprogs.sourceforge.net/e2fsprogs-release.html#1.47.0 release notes]:

<blockquote>The mke2fs program (via the mke2fs.conf file) now enables the metadata_csum_seed and orphan_file features by default.</blockquote>

However, whilst the <code>metadata_csum_seed</code> feature is known about by older versions of e2fsck the <code>orphan_file</code> feature was both added to e2fsprogs 1.47.0 '''and''' enabled at the same time. Therefore older versions of e2fsck are unable to fsck a filesystem created by mke2fs 1.47.0.

== Compilers and Runtimes ==


=== LLVM 16 ===

{{pkg|llvm16}} was added. [https://releases.llvm.org/16.0.0/docs/ReleaseNotes.html release notes]

=== Lua ===

{{pkg|luarocks}}, the package manager for Lua, was updated from 2.x to 3x. [https://github.com/luarocks/luarocks/blob/master/CHANGELOG.md#whats-new-in-luarocks-300 release notes]

=== Python ===

{{pkg|python3}} was updated from 3.10 to 3.11. [https://docs.python.org/3/whatsnew/3.11.html release notes]

==== splitting of python pycache .pyc files ====

Most python modules split their <code>__pycache__</code> to a <code>-pyc</code> subpackage, pulled by default. To save space and not pull it (incurring python interpreter startup costs, as it generates it each run), run <code>apk add !python3-pyc</code>

=== Ruby 3.2 ===

{{pkg|ruby}} was updated from 3.1 to 3.2. [https://www.ruby-lang.org/en/news/2022/12/25/ruby-3-2-0-released/ release notes]



=== Crystal 1.8 ===

{{pkg|crystal}} was updated from 1.6 to 1.8. [https://crystal-lang.org/2023/01/09/1.7.0-released/ release notes for 1.7], [https://crystal-lang.org/2023/04/14/1.8.0-released/ release notes for 1.8]

=== PHP 8.2 ===

Added 8.2 packages with a subset of the most common extensions. Version 8.1 still remains the primary provider priority, but some web applications started to use 8.2.

=== R 4.3 ===

{{pkg|R}} was updated from 4.2 to 4.3. [https://www.r-bloggers.com/2023/04/whats-new-in-r-4-3-0/ release notes]

=== Rust 1.69 ===

{{pkg|rust}} was updated from 1.64 to 1.69.

== Desktop ==

=== gdk-pixbuf-loaders ===

A few gdk-pixbuf loaders were added, and they were all added to an <code>install_if</code> metapackage rule. Run <code>apk add gdk-pixbuf-loaders</code> to enable the loaders for the corresponding image libraries you have installed.

=== GNOME ===

The {{pkg|gnome}} metapackage was reworked and the packages {{pkg|gnome-apps-extra}} and {{pkg|gnome-games-collection}} were removed to avoid opinionated lists in metapackages. It is advised to remove those from <code>/etc/apk/world</code> before performing the upgrade. Additionally, the new subpackage {{pkg|gnome-dev-tools}} was added following the upstream's recommendations.

On related news, to make use of GNOME Software, it is necessary to enable the <code>apk-polkit-server</code> openrc service. More info in the [https://wiki.alpinelinux.org/wiki/Gnome#Enabling_GNOME_Software wiki]

=== Plasma 5.27.4 ===

{{pkg|plasma}} was updated from 5.26.5 to 5.27.4. This includes some new packages like {{pkg|plasma-welcome}} (a welcoming application that shows up on the first boot to configure some initial settings) and {{pkg|flatpak-kcm}} (a configuration page for the system settings to control Flatpak permissions, much like GNOME's Flatseal).
This Plasma release is the last one that will be built on Qt5 and will probably remain in use for Alpine 3.19 as well.

=== Sway 1.8 ===

{{pkg|sway}} was updated from 1.7 to 1.8. [https://github.com/swaywm/sway/releases/tag/1.8 release notes]

== Others ==

=== Removal of pipewire-media-session ===

{{pkg|pipewire-media-session}} was removed, as upstream explicitly recommends not to use it, and it's completely superceded by wireplumber.
if you used it, make sure you don't have {{pkg|pipewire-media-session}} in <code>/etc/apk/world</code>, and configure any scripts you might've had to launch <code>wireplumber</code> instead.

=== dbus ===

dbus-activation has been removed from packages {{pkg|openrc-settingsd}} and {{pkg|apk-polkit-rs}}. To make use of their services, make sure to start and enable the <code>openrc-settingsd</code> and <code>apk-polkit-server</code> services, respectively.

=== QEMU 8 ===

QEMU was updated from 7.1 to 8.0. [https://www.qemu.org/2023/04/20/qemu-8-0-0/ release notes]

=== Docker 23 ===

The {{pkg|docker}} package shipped with Alpine 3.18 has a dependency on {{pkg|docker-cli-buildx}}, as Docker 23 now uses it for builds.

Also, Docker 23 no longer enables the <code>overlay</code> storage driver, as it has been deprecated for a long time and is nearing removal. if your deployment is still configured to use it, <code>dockerd</code> will fail to start. To fix this, either...

* migrate to <code>overlay2</code> in <code>/etc/docker/daemon.json</code>
* hardcode it to <code>overlay</code> in the same file (instead of blank), though this will eventually break in a future upgrade

For more detailed information about Docker 23, please refer to the [https://docs.docker.com/engine/release-notes/23.0/ release notes].

=== nginx 1.24 ===

{{pkg|nginx}} was updated to the new stable branch 1.24.x. [https://nginx.org/en/CHANGES-1.24 release notes]

Release Notes for Alpine 3.18.0

2023-05-09T14:47:16Z

Ncopa: /* Compilers and Runtimes */ sort by repo,alphabeitcally (eg main before community, then sort alphabetic)

== Base System ==

=== Linux Kernel ===

{{pkg|linux-lts}} was updated from 5.15 to 6.1. [https://lkml.org/lkml/2022/12/11/206 release notes]

Kernel modules are now signed.

''Note: {{pkg|akms}} (Alpine Kernel Module Support) doesn't support modules signing yet, it will be implemented later.''

=== musl 1.2.4 ===

Support for DNS lookups over TCP. [https://www.openwall.com/lists/musl/2023/05/02/1 release notes]

=== DT_RELR ===

on x86, x86_64, and ppc64le, <code>-Wl,-z,pack-relative-relocs</code> is now added to the base LDFLAGS. this reduces elf (executable/shared-library) size by 10% on average.

however, these binaries are now not portable to other musl-based systems that have a musl older than 1.2.4, because older versions are incapable of loading these binaries.

=== e2fsprogs 1.47.0 ===

The {{pkg|e2fsprogs}} package shipped with Alpine 3.18 changed the behaviour of <code>mke2fs</code> so that newly created filesystems have two additional features enabled.

From [https://e2fsprogs.sourceforge.net/e2fsprogs-release.html#1.47.0 release notes]:

<blockquote>The mke2fs program (via the mke2fs.conf file) now enables the metadata_csum_seed and orphan_file features by default.</blockquote>

However, whilst the <code>metadata_csum_seed</code> feature is known about by older versions of e2fsck the <code>orphan_file</code> feature was both added to e2fsprogs 1.47.0 '''and''' enabled at the same time. Therefore older versions of e2fsck are unable to fsck a filesystem created by mke2fs 1.47.0.

== Compilers and Runtimes ==


=== LLVM 16 ===

{{pkg|llvm16}} was added. [https://releases.llvm.org/16.0.0/docs/ReleaseNotes.html release notes]

=== Lua ===

{{pkg|luarocks}}, the package manager for Lua, was updated from 2.x to 3x. [https://github.com/luarocks/luarocks/blob/master/CHANGELOG.md#whats-new-in-luarocks-300 release notes]

=== Python ===

{{pkg|python3}} was updated from 3.10 to 3.11. [https://docs.python.org/3/whatsnew/3.11.html release notes]

==== splitting of python pycache .pyc files ====

Most python modules split their <code>__pycache__</code> to a <code>-pyc</code> subpackage, pulled by default. To save space and not pull it (incurring python interpreter startup costs, as it generates it each run), run <code>apk add !python3-pyc</code>

=== Ruby 3.2 ===

{{pkg|ruby}} was updated from 3.1 to 3.2. [https://www.ruby-lang.org/en/news/2022/12/25/ruby-3-2-0-released/ release notes]



=== Crystal 1.8 ===

{{pkg|crystal}} was updated from 1.6 to 1.8. [https://crystal-lang.org/2023/01/09/1.7.0-released/ release notes for 1.7], [https://crystal-lang.org/2023/04/14/1.8.0-released/ release notes for 1.8]

=== PHP 8.2 ===

Added 8.2 packages with a subset of the most common extensions. Version 8.1 still remains the primary provider priority, but some web applications started to use 8.2.

=== R 4.3 ===

{{pkg|R}} was updated from 4.2 to 4.3. [https://www.r-bloggers.com/2023/04/whats-new-in-r-4-3-0/ release notes]

=== Rust 1.69 ===

{{pkg|rust}} was updated from 1.64 to 1.69.

== Desktop ==

=== GNOME ===

The {{pkg|gnome}} metapackage was reworked and the packages {{pkg|gnome-apps-extra}} and {{pkg|gnome-games-collection}} were removed to avoid opinionated lists in metapackages. It is advised to remove those from <code>/etc/apk/world</code> before performing the upgrade. Additionally, the new subpackage {{pkg|gnome-dev-tools}} was added following the upstream's recommendations.

On related news, to make use of GNOME Software, it is necessary to enable the <code>apk-polkit-server</code> openrc service. More info in the [https://wiki.alpinelinux.org/wiki/Gnome#Enabling_GNOME_Software wiki]

=== Plasma 5.27.4 ===

{{pkg|plasma}} was updated from 5.26.5 to 5.27.4. This includes some new packages like {{pkg|plasma-welcome}} (a welcoming application that shows up on the first boot to configure some initial settings) and {{pkg|flatpak-kcm}} (a configuration page for the system settings to control Flatpak permissions, much like GNOME's Flatseal).
This Plasma release is the last one that will be built on Qt5 and will probably remain in use for Alpine 3.19 as well.

=== Sway 1.8 ===

{{pkg|sway}} was updated from 1.7 to 1.8. [https://github.com/swaywm/sway/releases/tag/1.8 release notes]

=== gdk-pixbuf-loaders ===

A few gdk-pixbuf loaders were added, and they were all added to an <code>install_if</code> metapackage rule. Run <code>apk add gdk-pixbuf-loaders</code> to enable the loaders for the corresponding image libraries you have installed.

== Others ==

=== Removal of pipewire-media-session ===

{{pkg|pipewire-media-session}} was removed, as upstream explicitly recommends not to use it, and it's completely superceded by wireplumber.
if you used it, make sure you don't have {{pkg|pipewire-media-session}} in <code>/etc/apk/world</code>, and configure any scripts you might've had to launch <code>wireplumber</code> instead.

=== dbus ===

dbus-activation has been removed from packages {{pkg|openrc-settingsd}} and {{pkg|apk-polkit-rs}}. To make use of their services, make sure to start and enable the <code>openrc-settingsd</code> and <code>apk-polkit-server</code> services, respectively.

=== QEMU 8 ===

QEMU was updated from 7.1 to 8.0. [https://www.qemu.org/2023/04/20/qemu-8-0-0/ release notes]

=== Docker 23 ===

The {{pkg|docker}} package shipped with Alpine 3.18 has a dependency on {{pkg|docker-cli-buildx}}, as Docker 23 now uses it for builds.

Also, Docker 23 no longer enables the <code>overlay</code> storage driver, as it has been deprecated for a long time and is nearing removal. if your deployment is still configured to use it, <code>dockerd</code> will fail to start. To fix this, either...

* migrate to <code>overlay2</code> in <code>/etc/docker/daemon.json</code>
* hardcode it to <code>overlay</code> in the same file (instead of blank), though this will eventually break in a future upgrade

For more detailed information about Docker 23, please refer to the [https://docs.docker.com/engine/release-notes/23.0/ release notes].

=== nginx 1.24 ===

{{pkg|nginx}} was updated to the new stable branch 1.24.x. [https://nginx.org/en/CHANGES-1.24 release notes]

Talk:Release Notes for Alpine 3.18.0

2023-05-09T14:42:10Z

Ncopa: Created page with "I think it makes sense to try keep everything in `main` at the top and `community` below. Just ingeneral."

I think it makes sense to try keep everything in `main` at the top and `community` below. Just ingeneral.

Release Notes for Alpine 3.18.0

2023-05-08T06:13:03Z

Ncopa:

=== Linux Kernel ===

linux-lts 6.1 https://lkml.org/lkml/2022/12/11/206

Kernel modules are now signed.

=== musl 1.2.4 ===

Support for DNS lookups over TCP.

https://www.openwall.com/lists/musl/2023/05/02/1

=== DT_RELR ===

on x86, x86_64, and ppc64le, <code>-Wl,-z,pack-relative-relocs</code> is now added to the base LDFLAGS. this reduces elf (executable/shared-library) size by 10% on average.

however, these binaries are now not portable to other musl-based systems that have a musl older than 1.2.4, because older versions are incapable of loading these binaries.

=== GNOME ===

The gnome metapackage was reworked and the packages gnome-apps-extra and gnome-games-collection were removed to avoid opinionated lists in metapackages. It is advised to remove those from /etc/apk/world before performing the upgrade. Additionally, the new subpackage gnome-dev-tools was added following upstream's recommendations.

=== dbus ===

dbus-activation has been removed from packages <code>openrc-settingsd</code> and <code>apk-polkit-rs</code>. To make use of their services, make sure to start and enable the <code>openrc-settingsd</code> and <code>apk-polkit-server</code> services, respectively.

=== removal of pipewire-media-session ===

pipewire-media-session was removed, as upstream explicitly recommends to not use it, and it's completely superceded by wireplumber.
if you used it, make sure you don't have pipewire-media-session in /etc/apk/world, and configure any scripts you might've had to launch wireplumber instead.

=== Python ===

python 3.11 https://docs.python.org/3/whatsnew/3.11.html

=== splitting of python pycache .pyc files ===

most python modules split their __pycache__ to a -pyc subpackage, pulled by default. to save space and not pull it (incurring python interpreter startup costs, as it generates it each run), run <code>apk add !python3-pyc</code>

=== PHP 8.2 ===

Added 8.2 packages with subset of the most common extensions. Version 8.1 still remains primary provider priority but some web applications started to use 8.2.

=== Ruby 3.2 ===

Ruby was updated to 3.2. https://www.ruby-lang.org/en/news/2022/12/25/ruby-3-2-0-released/

=== gdk-pixbuf-loaders ===

a few gdk-pixbuf loaders were added, and they were all added to an install_if metapackage rule- <code>apk add gdk-pixbuf-loaders</code> to enable the loaders for corresponding image libraries you have installed.

=== Docker 23 ===

The <code>docker</code> package shipped with Alpine 3.18 has a dependency on <code>docker-cli-buildx</code>, as Docker 23 now uses it for builds.

Also, Docker 23 no longer enables the <code>overlay</code> storage driver, as it has been deprecated for a long time and is nearing removal. if your deployment is still configured to use it, <code>dockerd</code> will fail to start. To fix this, either...

* migrate to <code>overlay2</code> in <code>/etc/docker/daemon.json</code>
* hardcode it to <code>overlay</code> in the same file (instead of blank), though this will eventually break in a future upgrade

For more detailed information about Docker 23, please refer to https://docs.docker.com/engine/release-notes/23.0/

Release Notes for Alpine 3.18.0

2023-05-08T06:07:22Z

Ncopa:

=== Linux Kernel ===

linux-lts 6.1 https://lkml.org/lkml/2022/12/11/206

Kernel modules are now signed.

=== Python ===

python 3.11 https://docs.python.org/3/whatsnew/3.11.html

python packages have the precompiled pyc files split into a subpackage. Use `apk add !pyc` to avoid having those installed and save some space.

=== GNOME ===

The gnome metapackage was reworked and the packages gnome-apps-extra and gnome-games-collection were removed to avoid opinionated lists in metapackages. It is advised to remove those from /etc/apk/world before performing the upgrade. Additionally, the new subpackage gnome-dev-tools was added following upstream's recommendations.

=== dbus ===

dbus-activation has been removed from packages <code>openrc-settingsd</code> and <code>apk-polkit-rs</code>. To make use of their services, make sure to start and enable the <code>openrc-settingsd</code> and <code>apk-polkit-server</code> services, respectively.

=== musl 1.2.4 ===

Support for DNS lookups over TCP.

https://www.openwall.com/lists/musl/2023/05/02/1

=== DT_RELR ===

on x86, x86_64, and ppc64le, <code>-Wl,-z,pack-relative-relocs</code> is now added to the base LDFLAGS. this reduces elf (executable/shared-library) size by 10% on average.

however, these binaries are now not portable to other musl-based systems that have a musl older than 1.2.4, because older versions are incapable of loading these binaries.

=== removal of pipewire-media-session ===

pipewire-media-session was removed, as upstream explicitly recommends to not use it, and it's completely superceded by wireplumber.
if you used it, make sure you don't have pipewire-media-session in /etc/apk/world, and configure any scripts you might've had to launch wireplumber instead.

=== splitting of python pycache .pyc files ===

most python modules split their __pycache__ to a -pyc subpackage, pulled by default. to save space and not pull it (incurring python interpreter startup costs, as it generates it each run), run <code>apk add !python3-pyc</code>

=== PHP 8.2 ===

Added 8.2 packages with subset of the most common extensions. Version 8.1 still remains primary provider priority but some web applications started to use 8.2.

=== Ruby 3.2 ===

Ruby was updated to 3.2. https://www.ruby-lang.org/en/news/2022/12/25/ruby-3-2-0-released/

=== gdk-pixbuf-loaders ===

a few gdk-pixbuf loaders were added, and they were all added to an install_if metapackage rule- <code>apk add gdk-pixbuf-loaders</code> to enable the loaders for corresponding image libraries you have installed.

=== Docker 23 ===

The <code>docker</code> package shipped with Alpine 3.18 has a dependency on <code>docker-cli-buildx</code>, as Docker 23 now uses it for builds.

Also, Docker 23 no longer enables the <code>overlay</code> storage driver, as it has been deprecated for a long time and is nearing removal. if your deployment is still configured to use it, <code>dockerd</code> will fail to start. To fix this, either...

* migrate to <code>overlay2</code> in <code>/etc/docker/daemon.json</code>
* hardcode it to <code>overlay</code> in the same file (instead of blank), though this will eventually break in a future upgrade

For more detailed information about Docker 23, please refer to https://docs.docker.com/engine/release-notes/23.0/