Alpine Linux - User contributions [en]

Release Notes for Alpine 3.19.0

2023-12-06T18:35:51Z

HRio: /* Upgrades */ add linux

== 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.

=== GNOME ===

GNOME packages have been updated to 45. As part of that release, Cheese has been replaced by Snapshot, and Eye of GNOME by Loupe as the default apps for taking and seeing pictures, respectively. In additions, GNOME Photos was dropped as being mostly unmaintained.

=== 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 ==

* Linux 6.6
* 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.4
* 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 [https://pkgs.alpinelinux.org/packages?name=linux-rpi&branch=edge linux-rpi] has been simplified. There is now a single kernel flavor for each architecture. This means that the kernels [https://pkgs.alpinelinux.org/packages?name=linux-rpi2&branch=v3.18 linux-rpi2] and [https://pkgs.alpinelinux.org/packages?name=linux-rpi4&branch=v3.18 linux-rpi4] are replaced with [https://pkgs.alpinelinux.org/packages?name=linux-rpi&branch=edge linux-rpi]. The {{Path|config.txt}} is now generated by [https://pkgs.alpinelinux.org/packages?name=raspberrypi-bootloader-common&branch=edge raspberrypi-bootloader-common].

[[Category:News]]

Release Notes for Alpine 3.16.0

2022-05-23T08:24:44Z

HRio: mention Xen

== Important changes ==

=== /tmp mounted as tmpfs ===

Previously <code>/tmp</code> was just part of the root filesystem and was cleaned on boot via the bootmisc openrc service script. In v3.16, on new installation, <code>/tmp</code> will be mounted as tmpfs.

=== ICU data split ===

TODO(jirutka): Describe this change.

* {{pkg|icu-data-en}} (2.6 MiB) - Stripped down ICU data with only en_US/GB locale and no legacy charset converters (installed by default with {{pkg|icu-libs}}).
* {{pkg|icu-data-full}} (29 MiB) - Full ICU data.

{{pkg|nodejs}} is now compiled with system ICU.

=== NetworkManager plugins ===

NetworkManager plugins (e.g. WiFi or ADSL support) have been moved into subpackages and are not installed by default. If you use some of them, install the corresponding packages:

* WiFi: {{pkg|networkmanager-wifi}}
* ADSL: {{pkg|networkmanager-adsl}}
* Mobile broardband: {{pkg|networkmanager-wwan}}
* BlueTooth: {{pkg|networkmanager-bluetooth}}
* PPP: {{pkg|networkmanager-ppp}}
* Open vSwitch: {{pkg|networkmanager-ovs}}

== New features and noteworthy new packages ==

=== Fixed not showing boot output using consoles with drivers compiled as modules ===

Fixed OpenRC output not being shown on VirtIO consoles.

=== SDL 1.2 migrated to SDL 1.2 compat ===

The old sdl package (SDL 1.2) was moved from community to testing and as such won't be part of Alpine 3.16. Applications that use sdl instead use sdl12-compat, which is based on the much more well-maintained sdl2 (SDL 2.0). This results in various improvements such as support for Wayland, PipeWire, and more gamepads.

=== utmp ===

TODO(jirutka): Write something…

https://skarnet.org/software/utmps/

The following packages are built with utmps:

* busybox
* dropbear
* mingetty
* openssh
* util-linux

=== login-utils ===

Allow users to choose between login utils from util-linux ({{pkg|util-linux-login}}) and shadow ({{pkg|shadow-login}}).

See ce0392393120a7077e99d50dec6f8574efe7f09a

TODO(jirutka): Polish it.

=== Zsh - modular zshrc and plugins support ===

TODO(jirutka): Write description.

=== doas-sudo-shim ===

If you are hesitant to switch to {{pkg|doas}} because you have <code>sudo</code> too deep in your muscle memory, hesitant no more! Just install {{pkg|doas-sudo-shim}} and you can continue to use the <code>sudo</code> command, but without its security issues and bloat.

== Significant updates ==

* LLVM 13
* Python 3.10
* QEMU 7
* Ruby 3.1
* Rust 1.60
* R 4.2
* Sway 1.7
* Xen 4.16.1

=== KDE ===

Plasma has been upgraded from 5.23 to 5.24.

KDE applications (the release service) have been upgraded from 21.08 to 22.04 and KDE Frameworks have been upgraded from 5.88 to 5.93.

Plasma Mobile Gear have been upgraded from 21.12 to 22.04.

=== GNOME 42 ===

Most GNOME packages have been upgraded to version 42.

=== Python upgraded to 3.10 ===

Python has been upgraded to version 3.10, and all python modules have been rebuilt against python 3.10. Make sure that all custom python3 modules are built against python3.10

VRF

2020-11-06T14:06:56Z

HRio: add #

[[VRF]] or Virtual Routing and Forwarding (or perhaps Virtual Routing Functions) provide virtualization of the routing table. They are useful for isolating services and entire networks from each other while avoiding the complexity of network namespaces.

== Prerequisites ==

To make use of VRFs, you will need `iproute2` and a kernel that is capable of using eBPF installed. Kernel 5.4.19-r1 and later are capable of using eBPF.

== VRF creation ==

The easiest way to define VRFs is to add them to /etc/network/interfaces:

<pre>
auto vrf-mgmt
iface vrf-mgmt inet manual
pre-up ip link add $IFACE type vrf table 42
up ip link set dev $IFACE up
</pre>

You can then associate specific interfaces with VRFs using pre-up commands:

<pre>
auto eth0
iface eth0 inet static
address 1.2.3.4
netmask 255.255.255.0
pre-up ip link set $IFACE master vrf-mgmt
up ip route add default table 42 via 1.2.3.1
</pre>

== VRF-based Service Isolation ==

Services can be isolated to specific VRFs when running OpenRC 0.42.1-r4 or newer. You can set the <code>$vrf</code> variable in an <code>/etc/conf.d</code> file for a service to isolate it in most cases.

For example, with sshd:

<pre>
# echo 'vrf="vrf-mgmt"' >> /etc/conf.d/sshd
# rc-service sshd restart
</pre>

== Name route tables ==

Routing tables can be named i.e. 42 can be named mgmt be editing /etc/iproute2/rt_tables or creating and separate config (e.g. /etc/iproute2/rt_tables.d/vrf.conf)

Example vrf.conf
<pre>
42 mgmt
43 int
44 ext
</pre>

Then instead of having to remember that 42 is is used for mgmt it can be used directly with ip route, example
<pre>
# ip route add default table mgmt via 1.2.3.1
</pre>

== Running network clients in a specific VRF ==

For ping is a simple as specifying a local interface that is already bound to a specific vrf

Example
<pre>
# ping -I eth0 <ip to ping>
</pre>

For other process like apk we use the ip vrf command
<pre>
# ip vrf exec vrf-mgmt apk update
</pre>

VRF

2020-11-06T14:06:19Z

HRio: /* Running netowork clients in a specific VRF */

VRF

2020-11-06T14:06:11Z

HRio: running interactive commands

[[VRF]] or Virtual Routing and Forwarding (or perhaps Virtual Routing Functions) provide virtualization of the routing table. They are useful for isolating services and entire networks from each other while avoiding the complexity of network namespaces.

== Prerequisites ==

To make use of VRFs, you will need `iproute2` and a kernel that is capable of using eBPF installed. Kernel 5.4.19-r1 and later are capable of using eBPF.

== VRF creation ==

The easiest way to define VRFs is to add them to /etc/network/interfaces:

<pre>
auto vrf-mgmt
iface vrf-mgmt inet manual
pre-up ip link add $IFACE type vrf table 42
up ip link set dev $IFACE up
</pre>

You can then associate specific interfaces with VRFs using pre-up commands:

<pre>
auto eth0
iface eth0 inet static
address 1.2.3.4
netmask 255.255.255.0
pre-up ip link set $IFACE master vrf-mgmt
up ip route add default table 42 via 1.2.3.1
</pre>

== VRF-based Service Isolation ==

Services can be isolated to specific VRFs when running OpenRC 0.42.1-r4 or newer. You can set the <code>$vrf</code> variable in an <code>/etc/conf.d</code> file for a service to isolate it in most cases.

For example, with sshd:

<pre>
# echo 'vrf="vrf-mgmt"' >> /etc/conf.d/sshd
# rc-service sshd restart
</pre>

== Name route tables ==

Routing tables can be named i.e. 42 can be named mgmt be editing /etc/iproute2/rt_tables or creating and separate config (e.g. /etc/iproute2/rt_tables.d/vrf.conf)

Example vrf.conf
<pre>
42 mgmt
43 int
44 ext
</pre>

Then instead of having to remember that 42 is is used for mgmt it can be used directly with ip route, example
<pre>
# ip route add default table mgmt via 1.2.3.1
</pre>

== Running netowork clients in a specific VRF ==

For ping is a simple as specifying a local interface that is already bound to a specific vrf

Example
<pre>
# ping -I eth0 <ip to ping>
</pre>

For other process like apk we use the ip vrf command
<pre>
ip vrf exec vrf-mgmt apk update
</pre>

VRF

2020-11-06T13:38:05Z

HRio: again

VRF

2020-11-06T13:37:48Z

HRio: markdown to wiki :-)

[[VRF]] or Virtual Routing and Forwarding (or perhaps Virtual Routing Functions) provide virtualization of the routing table. They are useful for isolating services and entire networks from each other while avoiding the complexity of network namespaces.

== Prerequisites ==

To make use of VRFs, you will need `iproute2` and a kernel that is capable of using eBPF installed. Kernel 5.4.19-r1 and later are capable of using eBPF.

== VRF creation ==

The easiest way to define VRFs is to add them to /etc/network/interfaces:

<pre>
auto vrf-mgmt
iface vrf-mgmt inet manual
pre-up ip link add $IFACE type vrf table 42
up ip link set dev $IFACE up
</pre>

You can then associate specific interfaces with VRFs using pre-up commands:

<pre>
auto eth0
iface eth0 inet static
address 1.2.3.4
netmask 255.255.255.0
pre-up ip link set $IFACE master vrf-mgmt
up ip route add default table 42 via 1.2.3.1
</pre>

== VRF-based Service Isolation ==

Services can be isolated to specific VRFs when running OpenRC 0.42.1-r4 or newer. You can set the <code>$vrf</code> variable in an <code>/etc/conf.d</code> file for a service to isolate it in most cases.

For example, with sshd:

<pre>
# echo 'vrf="vrf-mgmt"' >> /etc/conf.d/sshd
# rc-service sshd restart
</pre>

== Name route tables ==

Routing tables can be named i.e. 42 can be named mgmt be editing /etc/iproute2/rt_tables or creating and separate config (e.g. /etc/iproute2/rt_tables.d/vrf.conf)

Example vrf.conf
<pre>
42 mgmt
43 int
44 ext
</pre>

Then instead of having to remember that 42 is is used for mgmt it can be used directly with ip route, example
```
# ip route add default table mgmt via 1.2.3.1
```

VRF

2020-11-06T13:37:19Z

HRio: about routing table names

[[VRF]] or Virtual Routing and Forwarding (or perhaps Virtual Routing Functions) provide virtualization of the routing table. They are useful for isolating services and entire networks from each other while avoiding the complexity of network namespaces.

== Prerequisites ==

To make use of VRFs, you will need `iproute2` and a kernel that is capable of using eBPF installed. Kernel 5.4.19-r1 and later are capable of using eBPF.

== VRF creation ==

The easiest way to define VRFs is to add them to /etc/network/interfaces:

<pre>
auto vrf-mgmt
iface vrf-mgmt inet manual
pre-up ip link add $IFACE type vrf table 42
up ip link set dev $IFACE up
</pre>

You can then associate specific interfaces with VRFs using pre-up commands:

<pre>
auto eth0
iface eth0 inet static
address 1.2.3.4
netmask 255.255.255.0
pre-up ip link set $IFACE master vrf-mgmt
up ip route add default table 42 via 1.2.3.1
</pre>

== VRF-based Service Isolation ==

Services can be isolated to specific VRFs when running OpenRC 0.42.1-r4 or newer. You can set the <code>$vrf</code> variable in an <code>/etc/conf.d</code> file for a service to isolate it in most cases.

For example, with sshd:

<pre>
# echo 'vrf="vrf-mgmt"' >> /etc/conf.d/sshd
# rc-service sshd restart
</pre>

== Name route tables ==

Routing tables can be named i.e. 42 can be named mgmt be editing /etc/iproute2/rt_tables or creating and separate config (e.g. /etc/iproute2/rt_tables.d/vrf.conf)

Example vrf.conf
```
42 mgmt
43 int
44 ext
```

Then instead of having to remember that 42 is is used for mgmt it can be used directly with ip route, example
```
# ip route add default table mgmt via 1.2.3.1
```

VRF

2020-11-06T13:33:19Z

HRio: fix route, gateway can not be used as the route ends up in the wrong table

VRF

2020-11-06T12:44:59Z

HRio: fix vrf-mgmt still in state down and swtich to $IFACE

User talk:HRio

2020-11-06T10:03:24Z

HRio: Blanked the page

Talk:VRF

2020-11-06T10:02:58Z

HRio: vrf-mgmt not UP

Seems that vrf-mgmt is not end up in state UP. Needed to do like follows

<pre>
auto vrf-mgmt
iface vrf-mgmt inet manual
pre-up ip link add $IFACE type vrf table 42
up ip link set dev $IFACE up
</pre>

<pre>
auto eth0
iface eth0 inet static
address 1.2.3.4
netmask 255.255.255.0
gateway 1.2.3.1
pre-up ip link set $IFACE master vrf-mgmt
</pre>

User talk:HRio

2020-11-06T10:01:33Z

HRio: vrf-mgmt not UP

Talk:Release Notes for Alpine 3.12.0

2020-07-03T13:33:52Z

HRio:

Should we not mention that the python package needs to be removed (apk del python) and python2 and/or python3 must be installed? if the python package is still installed the latest update to python3 (3.8.3) will never be installed with apk upgrade.

Talk:Release Notes for Alpine 3.12.0

2020-07-03T13:33:29Z

HRio: apt del python ?

Should we not mention that the python package needs to be removed (apk del python) and python2 and/or python3 must be installed? if the python package is not installed the latest update to python3 (3.8.3) will never be installed with apk upgrade.