Alpine Linux - User contributions [en]

Draft Release Notes for Alpine 3.24.0

2026-02-06T06:19:52Z

Lotheac: /* qemu-binfmt service deprecated */

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.

{{Note|Alpine 3.24 is WIP, see https://gitlab.alpinelinux.org/groups/alpine/-/milestones/27 for important changes. For the latest release 3.23, look at [[Release Notes for Alpine 3.23.0]].}}

== Important changes ==

=== /usr merge ===

New installations can opt-in to being /usr-merged, by setting the <code>BOOTSTRAP_USR_MERGED</code> environment variable to <code>1</code> before running <code>setup-disk</code>. Manual migration is also possible by installing the <code>merge-usr</code> package and running its binary as root. For more details see the [https://alpinelinux.org/posts/2025-10-01-usr-merge.html official announcement].

== Significant changes ==

=== GTK+ 3.0 moved to community ===

{{Note|TODO}}

=== gdk-pixbuf uses glycin/glycin loaders got split ===

{{Note|TODO}}

== Note-worthy updates ==

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

* BIRD TODO
* busybox TODO
* Deno TODO
* ffmpeg TODO
* GCC TODO
* GNOME TODO
* Go TODO
* ISC BIND TODO
* ISC Kea TODO
* KDE Plasma TODO
* Linux TODO
* LLVM TODO
* LXQt TODO
* .NET TODO
* nginx TODO
* NodeJS TODO (LTS)
* OpenJDK TODO
* PHP TODO
* Qt TODO
* Ruby TODO
* Rust TODO
* wlroots TODO
* zigbee2mqtt TODO

=== COSMIC 1 ===

This release makes the COSMIC desktop available in community as {{pkg|cosmic*}} including {{pkg|xdg-desktop-portal-cosmic*}}.

=== qemu-binfmt service deprecated ===

The <code>qemu-binfmt</code> service from the package <code>qemu-openrc</code> is deprecated, in favor of <code>binfmt.d</code> config files from user mode qemu packages (eg. <code>qemu-aarch64 qemu-x86_64</code>) combined with the <code>binfmt</code> service.

If you are using <code>qemu-binfmt</code>, run:
{{Cmd|# rc-update del qemu-binfmt && rc-update add binfmt}}

Contrary to the behavior of <code>qemu-binfmt</code>, the new default configuration prevents setuid programs from granting privileges. If you need to execute setuid programs via qemu:

* make sure you understand the implications: with this configuration, any user with execute access to any foreign-architecture setuid binary can execute arbitrary code with the privileges of that binary
* if you accept the risks, copy <code>/usr/lib/binfmt.d/qemu-*.conf</code> to <code>/etc/binfmt.d</code>, edit to add the <code>C</code> flag, and restart binfmt.

See [https://docs.kernel.org/admin-guide/binfmt-misc.html Kernel admin guide - binfmt] for more information about the <code>C</code> (<code>credentials</code>) flag.

== Significant removals ==



=== py3-six ===

{{Note|TODO https://gitlab.alpinelinux.org/alpine/aports/-/work_items/17822}}

=== More GTK 2 removals ===

{{Note|TODO}}

=== More Qt5 removals ===

{{Note|TODO}}

<hr><center>[[Release Notes for Alpine 3.23.0|← Previous page: Release Notes for Alpine 3.23.0]]</center>

[[Category:News]]

Draft Release Notes for Alpine 3.24.0

2026-02-06T05:52:30Z

Lotheac: /* qemu-binfmt service deprecated */

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.

{{Note|Alpine 3.24 is WIP, see https://gitlab.alpinelinux.org/groups/alpine/-/milestones/27 for important changes. For the latest release 3.23, look at [[Release Notes for Alpine 3.23.0]].}}

== Important changes ==

=== /usr merge ===

New installations can opt-in to being /usr-merged, by setting the <code>BOOTSTRAP_USR_MERGED</code> environment variable to <code>1</code> before running <code>setup-disk</code>. Manual migration is also possible by installing the <code>merge-usr</code> package and running its binary as root. For more details see the [https://alpinelinux.org/posts/2025-10-01-usr-merge.html official announcement].

== Significant changes ==

=== GTK+ 3.0 moved to community ===

{{Note|TODO}}

=== gdk-pixbuf uses glycin/glycin loaders got split ===

{{Note|TODO}}

== Note-worthy updates ==

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

* BIRD TODO
* busybox TODO
* Deno TODO
* ffmpeg TODO
* GCC TODO
* GNOME TODO
* Go TODO
* ISC BIND TODO
* ISC Kea TODO
* KDE Plasma TODO
* Linux TODO
* LLVM TODO
* LXQt TODO
* .NET TODO
* nginx TODO
* NodeJS TODO (LTS)
* OpenJDK TODO
* PHP TODO
* Qt TODO
* Ruby TODO
* Rust TODO
* wlroots TODO
* zigbee2mqtt TODO

=== COSMIC 1 ===

This release makes the COSMIC desktop available in community as {{pkg|cosmic*}} including {{pkg|xdg-desktop-portal-cosmic*}}.

=== qemu-binfmt service deprecated ===

The <code>qemu-binfmt</code> service from the package <code>qemu-openrc</code> is deprecated, in favor of <code>binfmt.d</code> config files from user mode qemu packages (eg. <code>qemu-aarch64 qemu-x86_64</code>) combined with the <code>binfmt</code> service.

If you are using <code>qemu-binfmt</code>, run:
{{Cmd|# rc-update del qemu-binfmt && rc-update add binfmt}}

Contrary to the behavior of <code>qemu-binfmt</code>, the default configuration for the new service prevents setuid programs from granting privileges. If you need to execute setuid programs via qemu:

* make sure you understand the implications: with this configuration, any user with execute access to any foreign-architecture setuid binary can execute arbitrary code with the privileges of that binary
* if you accept the risks, copy <code>/usr/lib/binfmt.d/qemu-*.conf</code> to <code>/etc/binfmt.d</code>, edit to add the <code>C</code> flag, and restart binfmt.

See [https://docs.kernel.org/admin-guide/binfmt-misc.html Kernel admin guide - binfmt] for more information about the <code>C</code> (<code>credentials</code>) flag.

== Significant removals ==



=== py3-six ===

{{Note|TODO https://gitlab.alpinelinux.org/alpine/aports/-/work_items/17822}}

=== More GTK 2 removals ===

{{Note|TODO}}

=== More Qt5 removals ===

{{Note|TODO}}

<hr><center>[[Release Notes for Alpine 3.23.0|← Previous page: Release Notes for Alpine 3.23.0]]</center>

[[Category:News]]

Draft Release Notes for Alpine 3.24.0

2026-02-04T13:13:56Z

Lotheac: add note about qemu-binfmt -> binfmt

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.

{{Note|Alpine 3.24 is WIP, see https://gitlab.alpinelinux.org/groups/alpine/-/milestones/27 for important changes. For the latest release 3.23, look at [[Release Notes for Alpine 3.23.0]].}}

== Important changes ==

=== /usr merge ===

New installations can opt-in to being /usr-merged, by setting the <code>BOOTSTRAP_USR_MERGED</code> environment variable to <code>1</code> before running <code>setup-disk</code>. Manual migration is also possible by installing the <code>merge-usr</code> package and running its binary as root. For more details see the [https://alpinelinux.org/posts/2025-10-01-usr-merge.html official announcement].

== Significant changes ==

=== GTK+ 3.0 moved to community ===

{{Note|TODO}}

=== gdk-pixbuf uses glycin/glycin loaders got split ===

{{Note|TODO}}

== Note-worthy updates ==

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

* BIRD TODO
* busybox TODO
* Deno TODO
* ffmpeg TODO
* GCC TODO
* GNOME TODO
* Go TODO
* ISC BIND TODO
* ISC Kea TODO
* KDE Plasma TODO
* Linux TODO
* LLVM TODO
* LXQt TODO
* .NET TODO
* nginx TODO
* NodeJS TODO (LTS)
* OpenJDK TODO
* PHP TODO
* Qt TODO
* Ruby TODO
* Rust TODO
* wlroots TODO
* zigbee2mqtt TODO

=== COSMIC 1 ===

This release makes the COSMIC desktop available in community as {{pkg|cosmic*}} including {{pkg|xdg-desktop-portal-cosmic*}}.

=== qemu-binfmt service deprecated ===

The <code>qemu-binfmt</code> service from the package <code>qemu-openrc</code> is deprecated, in favor of <code>binfmt.d</code> config files from user mode qemu packages (eg. <code>qemu-aarch64 qemu-x86_64</code>) combined with the <code>binfmt</code> service.

If you are using <code>qemu-binfmt</code>, run:
{{Cmd|# rc-update del qemu-binfmt && rc-update add binfmt}}

== Significant removals ==



=== py3-six ===

{{Note|TODO https://gitlab.alpinelinux.org/alpine/aports/-/work_items/17822}}

=== More GTK 2 removals ===

{{Note|TODO}}

=== More Qt5 removals ===

{{Note|TODO}}

<hr><center>[[Release Notes for Alpine 3.23.0|← Previous page: Release Notes for Alpine 3.23.0]]</center>

[[Category:News]]

How to make a cross architecture chroot

2026-02-04T13:07:54Z

Lotheac: /* Troubleshooting */

If you have an ARM computer, you will find that some software is only available for x86_64. One possible solution is to have a full x86_64 virtual machine, but that has quite a lot of overhead from having to emulate the entire system. Fortunately, there is [https://qemu-project.gitlab.io/qemu/user/main.html QEMU User space emulation] which still uses the host kernel, so there is less overhead. This guide will show you how to make a chroot and enable transparent x86_64 binary execution using qemu and binfmt_misc.

== Prerequisites ==

You should be familiar with the Linux command line.

This guide is written assuming you have Alpine as the main install as well as putting Alpine in the chroot.

Also, the commands shown assume you have '''root''' privileges. Either use <code>sudo/doas</code> as needed (or <code>su</code> first).

== Installing necessary software ==

'''[[Repositories#Managing_repositories| Enable the Community Repository]]''' and install the '''qemu''' user mode binaries for the architectures you want to use, in this case x86_64 and i386:

{{Cmd|# apk add {{Pkg|qemu-x86_64}} {{Pkg|qemu-i386}} {{Pkg|qemu-openrc}} {{Pkg|openrc}}}}

Please note there are the <code>qemu-system-*</code> packages, you don't want those since they are used for full virtual machine emulation.

== Enable the <code>binfmt</code> service and start it ==

{{Tip|This section applies to Alpine 3.24 and later. In earlier releases, enable <code>qemu-binfmt</code> instead of <code>binfmt</code>.}}

The binfmt service registers <code>binfmt_misc</code> handlers from configuration files in <code>binfmt.d</code> directories when it starts. The <code>qemu-*</code> user mode packages include the necessary configuration files, so it is sufficient to add the service to the default runlevel and start it:

{{Cmd|# rc-update add binfmt
# rc-service binfmt start}}

== Make the chroot folder ==

To keep it simple, we're just going to use the apk repositories specified on the host system. This guide assumes the <code>$CHROOT</code> environment variable holds the directory where you want to make the chroot. Make the chroot directory and the <code>etc/apk</code> subdirectory (which we'll copy the apk repositories file to):

{{Cmd|# mkdir -p $CHROOT/etc/apk/}}

Now copy the host's apk repositories into the chroot folder:

{{Cmd|# cp /etc/apk/repositories $CHROOT/etc/apk/}}

You'll also need to copy the <code>resolv.conf</code> file into the chroot so it can have internet access:

{{Cmd|# cp /etc/resolv.conf $CHROOT/etc/}}

== Install <code>alpine-base</code> into the chroot folder ==

The {{Pkg|alpine-base}} meta package is all that's needed to have a fully working alpine system. The apk invocation used here has a few more options than what you might be used to:

{{Cmd|# apk add -p $CHROOT --initdb -U --arch x86_64 --allow-untrusted alpine-base}}

Here's what all the options do:

*<code>-p $CHROOT</code>: Sets the root of the install to <code>$CHROOT</code> instead of <code>/</code>
*<code>--initdb</code>: Initialize a new package database.
*<code>-U</code>: Alias for <code>--cache-max-age 1</code>. Basically means don't install from cache.
*<code>--arch x86_64</code>: Install x86_64 packages instead of native packages. Replace this with whichever architecture you want to emulate instead (e.g. <code>--arch x86</code>).
*<code>--allow-untrusted</code>: Install packages with untrusted signature or no signature. (This is needed since the keys for different architectures are different than what will be on your host. If you have the correct keys, you can copy them into the <code>$CHROOT/etc/apk/keys/</code> directory and remove this flag).

== Mount the virtual file systems into the chroot ==

{{Cmd|# mount -t proc proc $CHROOT/proc/
# mount -t sysfs sys $CHROOT/sys/
# mount -o bind /dev/ $CHROOT/dev/
# mount -o bind /dev/pts/ $CHROOT/dev/pts/
# mount -o bind /run $CHROOT/run/}}

==The exciting part: Enter the chroot==

If you've followed all the steps, this part should be uneventful. The <code>chroot</code> invocation uses the special command of <code>sh -l</code> to run as a login shell and source <code>/etc/profile</code>:

{{Cmd|# chroot $CHROOT/ sh -l}}

==Troubleshooting==

If you get a <code>ERROR: ${package_name}.post-install: script exited with error 127</code> while trying to add the alpine-base, that normally means that qemu binfmt_misc hasn't been setup properly. Check if the <code>qemu-$arch</code> package has been installed and see if the binfmt service is running. Remember to restart the service after adding a new architecture.

{{Cmd|# rc-service binfmt restart}}

You can also see if there is a <code>qemu-$arch</code> entry in <code>/proc/sys/fs/binfmt_misc/</code>.

Programs that use [https://en.wikipedia.org/wiki/Netlink Netlink] (e.g. <code>ip addr</code>) don't seem to work properly since qemu doesn't emulate the Netlink protocol properly.

==References==

* [https://archive.is/ldO0C Transparently running binaries from any architecture in Linux with QEMU and binfmt_misc] (see the section titled <code>Emulating full ARM rootfs</code>)

[[Category:System Administration]]

How to make a cross architecture chroot

2026-02-04T13:05:16Z

Lotheac:

If you have an ARM computer, you will find that some software is only available for x86_64. One possible solution is to have a full x86_64 virtual machine, but that has quite a lot of overhead from having to emulate the entire system. Fortunately, there is [https://qemu-project.gitlab.io/qemu/user/main.html QEMU User space emulation] which still uses the host kernel, so there is less overhead. This guide will show you how to make a chroot and enable transparent x86_64 binary execution using qemu and binfmt_misc.

== Prerequisites ==

You should be familiar with the Linux command line.

This guide is written assuming you have Alpine as the main install as well as putting Alpine in the chroot.

Also, the commands shown assume you have '''root''' privileges. Either use <code>sudo/doas</code> as needed (or <code>su</code> first).

== Installing necessary software ==

'''[[Repositories#Managing_repositories| Enable the Community Repository]]''' and install the '''qemu''' user mode binaries for the architectures you want to use, in this case x86_64 and i386:

{{Cmd|# apk add {{Pkg|qemu-x86_64}} {{Pkg|qemu-i386}} {{Pkg|qemu-openrc}} {{Pkg|openrc}}}}

Please note there are the <code>qemu-system-*</code> packages, you don't want those since they are used for full virtual machine emulation.

== Enable the <code>binfmt</code> service and start it ==

{{Tip|This section applies to Alpine 3.24 and later. In earlier releases, enable <code>qemu-binfmt</code> instead of <code>binfmt</code>.}}

The binfmt service registers <code>binfmt_misc</code> handlers from configuration files in <code>binfmt.d</code> directories when it starts. The <code>qemu-*</code> user mode packages include the necessary configuration files, so it is sufficient to add the service to the default runlevel and start it:

{{Cmd|# rc-update add binfmt
# rc-service binfmt start}}

== Make the chroot folder ==

To keep it simple, we're just going to use the apk repositories specified on the host system. This guide assumes the <code>$CHROOT</code> environment variable holds the directory where you want to make the chroot. Make the chroot directory and the <code>etc/apk</code> subdirectory (which we'll copy the apk repositories file to):

{{Cmd|# mkdir -p $CHROOT/etc/apk/}}

Now copy the host's apk repositories into the chroot folder:

{{Cmd|# cp /etc/apk/repositories $CHROOT/etc/apk/}}

You'll also need to copy the <code>resolv.conf</code> file into the chroot so it can have internet access:

{{Cmd|# cp /etc/resolv.conf $CHROOT/etc/}}

== Install <code>alpine-base</code> into the chroot folder ==

The {{Pkg|alpine-base}} meta package is all that's needed to have a fully working alpine system. The apk invocation used here has a few more options than what you might be used to:

{{Cmd|# apk add -p $CHROOT --initdb -U --arch x86_64 --allow-untrusted alpine-base}}

Here's what all the options do:

*<code>-p $CHROOT</code>: Sets the root of the install to <code>$CHROOT</code> instead of <code>/</code>
*<code>--initdb</code>: Initialize a new package database.
*<code>-U</code>: Alias for <code>--cache-max-age 1</code>. Basically means don't install from cache.
*<code>--arch x86_64</code>: Install x86_64 packages instead of native packages. Replace this with whichever architecture you want to emulate instead (e.g. <code>--arch x86</code>).
*<code>--allow-untrusted</code>: Install packages with untrusted signature or no signature. (This is needed since the keys for different architectures are different than what will be on your host. If you have the correct keys, you can copy them into the <code>$CHROOT/etc/apk/keys/</code> directory and remove this flag).

== Mount the virtual file systems into the chroot ==

{{Cmd|# mount -t proc proc $CHROOT/proc/
# mount -t sysfs sys $CHROOT/sys/
# mount -o bind /dev/ $CHROOT/dev/
# mount -o bind /dev/pts/ $CHROOT/dev/pts/
# mount -o bind /run $CHROOT/run/}}

==The exciting part: Enter the chroot==

If you've followed all the steps, this part should be uneventful. The <code>chroot</code> invocation uses the special command of <code>sh -l</code> to run as a login shell and source <code>/etc/profile</code>:

{{Cmd|# chroot $CHROOT/ sh -l}}

==Troubleshooting==

If you get a <code>ERROR: ${package_name}.post-install: script exited with error 127</code> while trying to add the alpine-base, that normally means that qemu binfmt_misc hasn't been setup properly. Check if the <code>qemu-$arch</code> package has been installed and see if the binfmt_misc service is running. Remember to restart the service after adding a new architecture.

{{Cmd|# rc-service qemu-binfmt restart}}

You can also see if there is a <code>qemu-$arch</code> entry in <code>/proc/sys/fs/binfmt_misc/</code>.

Programs that use [https://en.wikipedia.org/wiki/Netlink Netlink] (e.g. <code>ip addr</code>) don't seem to work properly since qemu doesn't emulate the Netlink protocol properly.

==References==

* [https://archive.is/ldO0C Transparently running binaries from any architecture in Linux with QEMU and binfmt_misc] (see the section titled <code>Emulating full ARM rootfs</code>)

[[Category:System Administration]]

How to make a cross architecture chroot

2026-02-04T12:56:40Z

Lotheac: qemu-binfmt -> binfmt

If you have an ARM computer, you will find that some software is only available for x86_64. One possible solution is to have a full x86_64 virtual machine, but that has quite a lot of overhead from having to emulate the entire system. Fortunately, there is [https://qemu-project.gitlab.io/qemu/user/main.html QEMU User space emulation] which still uses the host kernel, so there is less overhead. This guide will show you how to make a chroot and enable transparent x86_64 binary execution using qemu and binfmt_misc.

== Prerequisites ==

You should be familiar with the Linux command line.

This guide is written assuming you have Alpine as the main install as well as putting Alpine in the chroot.

Also, the commands shown assume you have '''root''' privileges. Either use <code>sudo/doas</code> as needed (or <code>su</code> first).

== Installing necessary software ==

'''[[Repositories#Managing_repositories| Enable the Community Repository]]''' and install the '''qemu''' user mode binaries for the architectures you want to use, in this case x86_64 and i386:

{{Cmd|# apk add {{Pkg|qemu-x86_64}} {{Pkg|qemu-i386}} {{Pkg|qemu-openrc}} {{Pkg|openrc}}}}

Please note there are the <code>qemu-system-*</code> packages, you don't want those since they are used for full virtual machine emulation.

== Enable the <code>binfmt</code> service and start it ==

{{Tip|This section applies to Alpine 3.24 and later. In earlier releases, enable <code>qemu-binfmt</code> instead of <code>binfmt</code>.}}

The binfmt service registers binfmt_misc handlers from configuration files in binfmt.d directories when it starts. The qemu-* static packages include the necessary binfmt.d configuration files. Add the service to the default runlevel and start it:

{{Cmd|# rc-update add binfmt
# rc-service binfmt start}}

== Make the chroot folder ==

To keep it simple, we're just going to use the apk repositories specified on the host system. This guide assumes the <code>$CHROOT</code> environment variable holds the directory where you want to make the chroot. Make the chroot directory and the <code>etc/apk</code> subdirectory (which we'll copy the apk repositories file to):

{{Cmd|# mkdir -p $CHROOT/etc/apk/}}

Now copy the host's apk repositories into the chroot folder:

{{Cmd|# cp /etc/apk/repositories $CHROOT/etc/apk/}}

You'll also need to copy the <code>resolv.conf</code> file into the chroot so it can have internet access:

{{Cmd|# cp /etc/resolv.conf $CHROOT/etc/}}

== Install <code>alpine-base</code> into the chroot folder ==

The {{Pkg|alpine-base}} meta package is all that's needed to have a fully working alpine system. The apk invocation used here has a few more options than what you might be used to:

{{Cmd|# apk add -p $CHROOT --initdb -U --arch x86_64 --allow-untrusted alpine-base}}

Here's what all the options do:

*<code>-p $CHROOT</code>: Sets the root of the install to <code>$CHROOT</code> instead of <code>/</code>
*<code>--initdb</code>: Initialize a new package database.
*<code>-U</code>: Alias for <code>--cache-max-age 1</code>. Basically means don't install from cache.
*<code>--arch x86_64</code>: Install x86_64 packages instead of native packages. Replace this with whichever architecture you want to emulate instead (e.g. <code>--arch x86</code>).
*<code>--allow-untrusted</code>: Install packages with untrusted signature or no signature. (This is needed since the keys for different architectures are different than what will be on your host. If you have the correct keys, you can copy them into the <code>$CHROOT/etc/apk/keys/</code> directory and remove this flag).

== Mount the virtual file systems into the chroot ==

{{Cmd|# mount -t proc proc $CHROOT/proc/
# mount -t sysfs sys $CHROOT/sys/
# mount -o bind /dev/ $CHROOT/dev/
# mount -o bind /dev/pts/ $CHROOT/dev/pts/
# mount -o bind /run $CHROOT/run/}}

==The exciting part: Enter the chroot==

If you've followed all the steps, this part should be uneventful. The <code>chroot</code> invocation uses the special command of <code>sh -l</code> to run as a login shell and source <code>/etc/profile</code>:

{{Cmd|# chroot $CHROOT/ sh -l}}

==Troubleshooting==

If you get a <code>ERROR: ${package_name}.post-install: script exited with error 127</code> while trying to add the alpine-base, that normally means that qemu binfmt_misc hasn't been setup properly. Check if the <code>qemu-$arch</code> package has been installed and see if the binfmt_misc service is running. Remember to restart the service after adding a new architecture.

{{Cmd|# rc-service qemu-binfmt restart}}

You can also see if there is a <code>qemu-$arch</code> entry in <code>/proc/sys/fs/binfmt_misc/</code>.

Programs that use [https://en.wikipedia.org/wiki/Netlink Netlink] (e.g. <code>ip addr</code>) don't seem to work properly since qemu doesn't emulate the Netlink protocol properly.

==References==

* [https://archive.is/ldO0C Transparently running binaries from any architecture in Linux with QEMU and binfmt_misc] (see the section titled <code>Emulating full ARM rootfs</code>)

[[Category:System Administration]]