Alpine Linux - User contributions [en]

ZFS

2026-04-12T05:26:38Z

Apropos: fix: replace markdown code syntax with mediawiki syntax

[https://openzfs.org/wiki/Main_Page ZFS] or OpenZFS is an open-source storage platform. It includes the functionality of both traditional file systems and volume manager.

This page has instructions for creating and auto-mounting an encrypted ZFS drive or partition on an existing encrypted alpine linux system, using ZFS's own encryption capabilities. To do fresh install of Alpine Linux with root partition on ZFS, see [[Root on ZFS with native encryption]].

== Installation ==

Install the necessary packages and utilities by using the command:{{Cmd|# apk add zfs}}
Ensure that the kernel modules are loaded and verify that the device nodes are present:{{Cmd|<nowiki># modprobe zfs
# mdev -s </nowiki> }}
If your use of ZFS depends on volumes appearing in {{Path|/dev/zvol/$ZPOOL/$ZVOL}}, you will also need to [[Eudev|setup eudev]] and:{{Cmd|# apk add zfs-udev}}

== Configuration ==

The system will be encrypted when powered off but will not require you to type an extra password at boot, since it uses a key stored on the encrypted root partition. Alternative options are also given, such as prompting for a password at boot rather than storing the key on the root drive. The example in this guide is modeled around creating a ZFS filesystem to be used as a user's home directory, but it can be trivially modified to create a filesystem for other purposes.

=== Create an encryption key ===

This section can be skipped if you intend to unlock the drive by typing a password rather than unlocking automatically. You should use a password instead if your root partition is not encrypted. The location of the file {{Path|/etc/home.key}} can be anything. {{Cmd|<nowiki># dd if=/dev/random of=/etc/home.key bs=32 count=1
# chmod 600 /etc/home.key</nowiki>}}

IMPORTANT: Make sure you don't lose this key by overwriting your root filesystem or anything like that. You might want to store a copy of it on an encrypted USB drive, for instance.

=== Create the zpool ===

Replace <code>/dev/sd...</code> with the name of the disk or partition where you would like to make the zfs filesystem, such as <code>/dev/nvme0n1</code> or <code>/dev/sda1</code>. If you would like to be prompted for a password at boot rather than using the key as generated above, then replace <code>-O keylocation=file:///etc/home.key -O keyformat=raw</code> with <code>-O keylocation=prompt -O keyformat=passphrase</code>. The name "homepool" can be anything.{{Cmd|<nowiki># zpool create -o ashift=12 -O acltype=posixacl -O compression=lz4 \
-O dnodesize=auto -O normalization=formD -O relatime=on -O xattr=sa \
-O encryption=aes-256-gcm -O keylocation=file:///etc/home.key -O keyformat=raw \
-O mountpoint=none homepool /dev/sd...</nowiki>}}

After completing this, verifying that the pool has been created should return something like::{{Cmd|<nowiki># zpool status
pool: homepool
state: ONLINE
config:

NAME STATE READ WRITE CKSUM
homepool ONLINE 0 0 0
sd... ONLINE 0 0 0

errors: No known data errors</nowiki>}}

To create and mount the filesystem issue the command {{Cmd|<nowiki># zfs create -o mountpoint=/home/username homepool/username
# chown username:username /home/username </nowiki>}}

The last command i.e ''chown'' is likely unnecessary if not creating a homedir.

=== Service configuration ===

Setup the following services to auto-mount the new filesystem using [[OpenRC]]
To import existing zpools:{{Cmd|# rc-update add zfs-import}}
To load the encryption keys:{{Cmd|# rc-update add zfs-load-key}}
Finally to mount the filesystems:{{Cmd|# rc-update add zfs-mount}}

Reboot the system, so that the encrypted ZFS drive is automounted and becomes available for use.

== Maintenance ==

On alpine Linux, there in no cron/script provided to scrub (and eventually trim) your pool(s) on a regular basis, like in other Linux distributions.

=== Scrub ===

Scrubbing (and eventually trim) your pool(s) on a [https://blogs.oracle.com/oracle-systems/post/disk-scrub-why-and-when Oracle regular basis] is essential. The scrub examines all data in the specified pools to verify that it checksums correctly. For replicated (mirror, raidz, or draid) devices, ZFS automatically repairs any damage discovered during the scrub

When scrubbing a pool with encrypted filesystems the keys do not need to be loaded. However, if the keys are not loaded and an unrepairable checksum error is detected the file name cannot be included in the zpool status -v verbose error report.

A scrub is split into two parts: metadata scanning and block scrubbing. The metadata scanning sorts blocks into large sequential ranges which can then be read much more efficiently from disk when issuing the scrub I/O.

This script is taken from debian zfs scripts. It is used to list the pools, make sure they are online, and no scrub is being done at the time. The contents of the script placed at {{path|/usr/libexec/zfs/scrub}} is as follows:{{cat|/usr/libexec/zfs/scrub|<nowiki>#!/bin/sh -eu

# directly exit successfully when zfs module is not loaded
if ! [ -d /sys/module/zfs ]; then
exit 0
fi

# [auto] / enable / disable
PROPERTY_NAME="org.alpine:periodic-scrub"

get_property () {
# Detect the ${PROPERTY_NAME} property on a given pool.
# We are abusing user-defined properties on the root dataset,
# since they're not available on pools https://github.com/openzfs/zfs/pull/11680
# TODO: use zpool user-defined property when such feature is available.
pool="$1"
zfs get -H -o value "${PROPERTY_NAME}" "${pool}" 2>/dev/null || return 1
}

scrub_if_not_scrub_in_progress () {
pool="$1"
if ! zpool status "${pool}" | grep -q "scrub in progress"; then
# Ignore errors and continue with scrubbing other pools.
zpool scrub "${pool}" || true
fi
}

# Scrub all healthy pools that are not already scrubbing as per their configs.
zpool list -H -o health,name 2>&1 | \
awk -F'\t' '$1 == "ONLINE" {print $2}' | \
while read pool
do
# read user-defined config
ret=$(get_property "${pool}")
if [ $? -ne 0 ] || [ "disable" = "${ret}" ]; then
:
elif [ "-" = "${ret}" ] || [ "auto" = "${ret}" ] || [ "enable" = "${ret}" ]; then
scrub_if_not_scrub_in_progress "${pool}"
else
cat > /dev/stderr <<EOF
$0: [WARNING] illegal value "${ret}" for property "${PROPERTY_NAME}" of ZFS dataset "${pool}".
$0: Acceptable choices for this property are: auto, enable, disable. The default is auto.
EOF
fi
done
</nowiki>}}

Make the script executable: {{cmd|# chmod +x /usr/libexec/zfs/scrub}}

It is recommended to scrub regularly to assure your pool(s) and datas are in good shape. So the scrub script will be launched once a month, on the 2nd sunday of the month using [[cron]]

Edit your crontabs using the command: {{cmd|# crontab -e}}

and add these 2 lines
<pre>
# zfs scrub the second sunday of every month
24 0 8-14 * * if [ $(date +\%w) -eq 0 ] && [ -x /usr/libexec/zfs/scrub ]; then /usr/libexec/zfs/scrub; fi
</pre>

=== Trim ===

The command {{ic|zpool trim}} initiates an immediate on-demand TRIM operation for all of the free space in a pool. This operation informs the underlying storage devices of all blocks in the pool which are no longer allocated and allows thinly provisioned devices to reclaim the space.

A manual on-demand TRIM operation can be initiated irrespective of the [https://openzfs.github.io/openzfs-docs/man/v2.2/7/zpoolprops.7.html#autotrim autotrim] pool property setting. The link shows the types of vdev devices which can be trimmed.

This script is taken from debian zfs scripts. It is used to list the pools, make sure they are online, build only with NVME ssd drive(s) and no trim is being done at the time. The contents of the script placed at {{path|/usr/libexec/zfs/trim}} is as follows:{{cat|/usr/libexec/zfs/trim|<nowiki>#!/bin/sh -eu

# directly exit successfully when zfs module is not loaded
if ! [ -d /sys/module/zfs ]; then
exit 0
fi

# [auto] / enable / disable
PROPERTY_NAME="org.alpine:periodic-trim"

get_property () {
# Detect the ${PROPERTY_NAME} property on a given pool.
# We are abusing user-defined properties on the root dataset,
# since they're not available on pools https://github.com/openzfs/zfs/pull/11680
# TODO: use zpool user-defined property when such feature is available.
pool="$1"
zfs get -H -o value "${PROPERTY_NAME}" "${pool}" 2>/dev/null || return 1
}

trim_if_not_already_trimming () {
pool="$1"
if ! zpool status "${pool}" | grep -q "trimming"; then
# Ignore errors (i.e. HDD pools),
# and continue with trimming other pools.
zpool trim "${pool}" || true
fi
}

zpool_is_nvme_only () {
zpool=$1
# get a list of devices attached to the specified zpool
zpool list -vHPL "${zpool}" |
awk -F'\t' '$2 ~ /^\/dev\// {
if($2 !~ /^\/dev\/nvme/)
exit 1
}'
}

# TRIM all healthy pools that are not already trimming as per their configs.
zpool list -H -o health,name 2>&1 | \
awk -F'\t' '$1 == "ONLINE" {print $2}' | \
while read pool
do
# read user-defined config
ret=$(get_property "${pool}")
if [ $? -ne 0 ] || [ "disable" = "${ret}" ]; then
:
elif [ "enable" = "${ret}" ]; then
trim_if_not_already_trimming "${pool}"
elif [ "-" = "${ret}" ] || [ "auto" = "${ret}" ]; then
if zpool_is_nvme_only "${pool}"; then
trim_if_not_already_trimming "${pool}"
fi
else
cat > /dev/stderr <<EOF
$0: [WARNING] illegal value "${ret}" for property "${PROPERTY_NAME}" of ZFS dataset "${pool}".
$0: Acceptable choices for this property are: auto, enable, disable. The default is auto.
EOF
fi
done
</nowiki>
}}

Make the script executable: {{cmd|# chmod +x /usr/libexec/zfs/trim}}

It is recommended to trim regularly to assure your pool(s) and datas are in good shape. So the trim script will be launched once a month, on the 1st sunday of the month using [[cron]]

Edit your crontabs using the command: {{cmd|# crontab -e}}
and add these 2 lines
<pre>
# zfs trim the first sunday of every month
24 0 1-7 * * if [ $(date +\%w) -eq 0 ] && [ -x /usr/libexec/zfs/trim ]; then /usr/libexec/zfs/trim; fi
</pre>

== See also ==

* [https://openzfs.org/wiki/System_Administration ZFS System Administration]
* [https://openzfs.github.io/openzfs-docs/Getting%20Started/Alpine%20Linux/Root%20on%20ZFS.html OpenZFS Guide for Alpine Linux]
* [[Root on ZFS with native encryption]]
* [[Setting up ZFS on LUKS]]
[[Category:Filesystems]]
[[Category:Storage]]
[[Category:Installation]]
[[Category:Security]]

Configure Networking

2026-04-12T03:38:37Z

Apropos: Fix minor grammatical errors / tweak some wording throughout, and make clear that NetworkManager and iwd are both fully supported

This page documents the steps to configure the network in Alpine Linux using either [[#Network setup-scripts|network setup-scripts]] or manually and to [[#Connectivity testing|test your Internet access]]. Alpine Linux uses [[ifupdown-ng]] for managing its network configuration by default. For additional functionality and graphical or terminal UIs, [[NetworkManager]] or [[iwd]] can be used.

For wireless capability, [[Wi-Fi|wpa_supplicant]] and [[iwd]] are both available and fully supported in Alpine Linux.

{{Tip|To setup basic networking quickly, use the [[#setup-interfaces|setup-interfaces]] script.}}

== Network setup-scripts ==

A number of network related scripts are available from the {{pkg|alpine-conf}} package as part of [[Alpine setup scripts]]. These scripts can quickly configure various networking related options in Alpine Linux and satisfy most trivial configurations.

When [[Installation|installing]] Alpine Linux, the <code>setup-alpine</code> script interactively calls the scripts to setup networking.

* <code>[[Alpine_setup_scripts#setup-hostname|setup-hostname]]</code>
* <code>[[#setup-interfaces|setup-interfaces]]</code>
* <code>[[Alpine_setup_scripts#setup-dns|setup-dns]]</code>
* <code>[[Alpine_setup_scripts#setup-proxy|setup-proxy]]</code>
* <code>[[Alpine_setup_scripts#setup-ntp|setup-ntp]]</code>

=== setup-interfaces ===

This script can be used to configure Ethernet, [[Wi-Fi|wireless]], bridge, bond and vlan interfaces and will satisfy most trivial configurations. Start the script by running the command: {{Cmd|# setup-interfaces}}
Available interfaces are: eth0 wlan0.
Enter '?' for help on bridges, bonding and vlans.
Which one do you want to initialize? (or '?' or 'done') [eth0]

choose <code>eth0</code> for Ethernet or <code>wlan0</code> for wireless device, as appropriate.

if asked:
Ip address for eth0? (or 'dhcp', 'none', '?') [dhcp]

choose <code>dhcp</code>, if you are using dhcp.

Now it will ask <code>Do you to do any manual network configuration? (y/n) [n]</code>

In most cases, you can accept the default option '''n''' . Choosing '''y''' will open the {{Path|/etc/network/interfaces}} file for editing in [[BusyBox#vi| '''vi''' editor]] to proceed with manual network configuration.

The above script configures [[Configure_Networking#Networking_service|Networking service]], starts the service and adds it to the boot run level.

If your networking needs are more advanced, refer to the following detailed guide for manual network configuration.

== Setting hostname ==

To set the system hostname:{{Cmd|# echo "shortname" > /etc/hostname}}

Then, to activate the change: {{Cmd|# hostname -F /etc/hostname}}

If you're using IPv6, you should also add the following special IPv6 addresses to your {{path|/etc/hosts}} file:{{cat|/etc/hosts|...
::1 localhost ipv6-localhost ipv6-loopback
fe00::0 ipv6-localnet
ff00::0 ipv6-mcastprefix
ff02::1 ipv6-allnodes
ff02::2 ipv6-allrouters
ff02::3 ipv6-allhosts
}}

{{Tip|If you're going to use automatic IP configuration, such as IPv4 DHCP or IPv6 Stateless Autoconfiguration, you can skip ahead to [[#Configuring_DNS|Configuring DNS]]. Otherwise, if you're going to use a static IPv4 or IPv6 address, continue below.}}

For a static IP configuration, it's common to also add the machine's hostname you just set (above) to the {{path|/etc/hosts}} file.

Here's an IPv4 example:{{cat|/etc/hosts|...
192.168.1.150 shortname.domain.com
...
}}

And here's an IPv6 example:{{cat|/etc/hosts|...
2001:470:ffff:ff::2 shortname.domain.com
...
}}

== Configuring DNS ==

{{Tip|'''For users of IPv4 DHCP:''' Please note that {{path|/etc/resolv.conf}} will be completely overwritten with any nameservers provided by DHCP.
If DHCP does not provide any nameservers, then {{path|/etc/resolv.conf}} will still be overwritten, but will not contain any nameservers!}}

For a static IP address and static nameservers, use one of the following examples.

For IPv4 nameservers, edit your {{path|/etc/resolv.conf}} file to look like this: 
The following example uses [https://en.wikipedia.org/wiki/Google_Public_DNS Google's Public DNS servers].
{{cat|/etc/resolv.conf|nameserver 8.8.8.8
nameserver 8.8.4.4
}}

For IPv6 nameservers, edit your {{path|/etc/resolv.conf}} file to look like this: 
The following example uses [https://www.he.net/ Hurricane Electric's] public DNS server.
{{cat|/etc/resolv.conf|nameserver 2001:470:20::2}}
You can also use Hurricane Electric's public IPv4 DNS server:
{{cat|/etc/resolv.conf|nameserver 74.82.42.42}}

{{Tip|If you decide to use Hurricane Electric's nameserver, be aware that it is 'Google-whitelisted'. What does this mean? It allows you access to many of Google's services via IPv6. (Just don't add other, non-whitelisted, nameservers to {{path|/etc/resolv.conf}} — ironically, such as Google's Public DNS Servers.) Read [https://www.google.com/intl/en/ipv6/ here] for more information.}}

== Interface configuration ==
{{Seealso|Wi-Fi}}
Manual interface configuration is explained in the following sections to meet non-trivial networking requirements. In the following configuration examples, the device name used is <code>eth0</code>. It can be substituted by appropriate device names like <code>wlan0</code> for wireless etc..

=== Loopback configuration ===

To configure loopback, add the following to the file {{path|/etc/network/interfaces}}: {{cat|/etc/network/interfaces|auto lo
iface lo inet loopback}}

The above works to set up the IPv4 loopback address (127.0.0.1), and the IPv6 loopback address (<code>::1</code>) — if you enabled IPv6.

{{Note| For [[#Busybox ifupdown|Busybox ifupdown]], loopback configuration must appear first in {{path|/etc/network/interfaces}} file to prevent networking issues.}}

=== DHCP configuration ===

A basic configuration for a desktop computer appears as follows:{{cat|/etc/network/interfaces|...
auto eth0
iface eth0
use dhcp}}

Refer busybox DHCP client [[udhcpc]] page for additional configuration options. If {{pkg|dhcpcd}} is installed, with [[ifupdown-ng]], DHCPv6 will also be used as dhcpcd interacts with both DHCPv4 and DHCPv6 from the same process.

==== IPv6 stateless autoconfiguration ====

With IPv6, stateless auto-configuration is typically used to configure network interfaces. If you are not interested in using IPv4 at all, you can simply use the ipv6-ra executor to ensure that an interface is configured to accept IPv6 RA advertisements:{{cat|/etc/network/interfaces|...
auto eth0
iface eth0
use ipv6-ra}}

=== Static address configuration ===

Add the following to the file {{path|/etc/network/interfaces}}: {{cat|/etc/network/interfaces|...
auto eth0
iface eth0
address 203.0.113.2/24
gateway 203.0.113.1}}

==== Multiple address ====

{{cat|/etc/network/interfaces|...
auto eth0
iface eth0
address 203.0.113.2/24
address 203.0.113.3/24
address 203.0.113.4/24
gateway 203.0.113.1}}

==== Dual-stack configuration ====

This example shows a dual-stack configuration. {{cat|/etc/network/interfaces|...
auto eth0
iface eth0
address 203.0.113.2/24
address 203.0.113.3/24
address 203.0.113.4/24
gateway 203.0.113.1

address 2001:db8:1000:2::2/64
address 2001:db8:1000:2::3/64
address 2001:db8:1000:2::4/64
gateway 2001:db8:1000:2::1}}

== Networking service ==
{{Tip|If [[Wi-Fi]] is used, follow the instructions mentioned on those pages.}}
Changes made to {{path|/etc/network/interfaces}} related to ethernet can be activated by running: {{Cmd|# rc-service networking restart}}
To '''start''' (or '''restart''') the networking service: {{Cmd|# rc-service networking --quiet start &}}
To add networking service so that it starts on boot: {{Cmd|# rc-update add networking boot}}

== Advanced network configuration ==

=== Busybox ifupdown ===

If the default [[ifupdown-ng]] is uninstalled, the [[Busybox]] ifupdown gets used. Busybox ifupdown syntax is slightly different from ifupdown-ng, but [[ifupdown-ng]] fully supports Busybox ifupdown syntax.

The CIDR notation '''203.0.113.2/24 ''' is not supported by BusyBox ifupdown, so for IP address use subnet mask notation i.e '''203.0.113.2/255.255.255.0'''.

The interface configuration file {{Path|/etc/network/interfaces}} for DHCP with Busybox ifupdown syntax appears as follows:
{{cat|/etc/network/interfaces|...
auto eth0
iface eth0 inet dhcp}}
For static IP address, use the word {{ic|static}} instead of {{ic|dhcp}} and provide ip address as shown:
{{cat|/etc/network/interfaces|...
auto eth0
iface eth0 inet static
address 203.0.113.2
netmask 255.255.255.0}}

=== Change network interface name ===

To change interface names from default <code>eth0</code> or <code>wlan0</code>, refer appropriate device manager pages i.e [[Eudev#Predictable_network_interface_names|eudev]] or [[Mdev#Custom_network_interface_name|mdev]].

Alternately, if [[ifupdown-ng]] is used, to set network interface name as {{ic|dmz}} for a MAC address {{ic|00:11:22:33:44:55}} add the following {{ic|pre-up}} command to your file {{Path|/etc/network/interfaces}} as follows:
{{Cat|/etc/network/interfaces|...
<nowiki>auto dmz
iface dmz inet dhcp
pre-up nameif -s dmz 00:11:22:33:44:55
</nowiki>}}

=== Change MAC or hw address ===

If [[ifupdown-ng]] is used, to set the MAC or hw address as {{ic|de:ad:be:ef:ca:fe}} for {{ic|wlan0}} interface, add the following {{ic|pre-up}} command to the relevant interface configuration stanza in the file {{Path|/etc/network/interfaces}} as follows:
{{Cat|/etc/network/interfaces|...
<nowiki>auto wlan0
iface wlan0 inet dhcp
pre-up ip link set $IFACE addr de:ad:be:ef:ca:fe
</nowiki>}}

== Troubleshooting ==

=== Connectivity testing ===

Test if networking is configured properly by attempting to ping out:
{{Cmd|<nowiki>$ ping www.google.com
PING www.l.google.com (74.125.47.103) 56(84) bytes of data.
64 bytes from yw-in-f103.1e100.net (74.125.47.103): icmp_seq=1 ttl=48 time=58.5 ms
64 bytes from yw-in-f103.1e100.net (74.125.47.103): icmp_seq=2 ttl=48 time=56.4 ms
64 bytes from yw-in-f103.1e100.net (74.125.47.103): icmp_seq=3 ttl=48 time=57.0 ms
64 bytes from yw-in-f103.1e100.net (74.125.47.103): icmp_seq=4 ttl=48 time=60.2 ms
^C
--- www.l.google.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3007ms
rtt min/avg/max/mdev = 56.411/58.069/60.256/1.501 ms
</nowiki>}}

For an IPv6 traceroute run <code>traceroute6</code>:
{{Cmd|$ traceroute6 ipv6.google.com
traceroute to ipv6.l.google.com (2001:4860:8009::67) from 2001:470:ffff:ff::2, 30 hops max, 16 byte packets
1 2001:470:ffff:ff::1 (2001:470:ffff:ff::1) 3.49 ms 0.62 ms 0.607 ms
2 * * *
3 * * *
4 pr61.iad07.net.google.com (2001:504:0:2:0:1:5169:1) 134.313 ms 95.342 ms 88.425 ms
5 2001:4860::1:0:9ff (2001:4860::1:0:9ff) 100.759 ms 100.537 ms 89.907 ms
6 2001:4860::1:0:5db (2001:4860::1:0:5db) 115.563 ms 102.946 ms 106.191 ms
7 2001:4860::2:0:a7 (2001:4860::2:0:a7) 101.754 ms 100.475 ms 100.512 ms
8 2001:4860:0:1::c3 (2001:4860:0:1::c3) 99.272 ms 111.989 ms 99.835 ms
9 yw-in-x67.1e100.net (2001:4860:8009::67) 101.545 ms 109.675 ms 99.431 ms
}}

=== iproute2 ===

Install the {{pkg|iproute2}} package which provides the 'ss' command which is an alternate to netstat.: {{Cmd|# apk add iproute2}}

Show listening tcp ports:{{Cmd|$ ss -tl}}
Show listening tcp ports and associated processes:{{Cmd|$ ss -ptl}}
Show listening and established tcp connections:{{Cmd|$ ss -ta}}
Show socket usage summary:{{Cmd|$ ss -s}}
Show more options:{{Cmd|$ ss -h}}

=== drill ===

Install {{pkg|drill}} (it will also install the 'ldns' package) which is a superior replacement for nslookup and dig etc: {{Cmd|# apk add drill}}

Then use it as you would for dig: {{Cmd|$ drill alpinelinux.org @8.8.8.8}}
To perform a reverse lookup (get a name from an IP) use the following syntax: {{Cmd|$ drill -x 8.8.8.8 @208.67.222.222}}

=== Missing interface ===

To list your available network interfaces use the commands {{ic|ip link}} or {{ic|ip a}}. Refer to [[Wi-Fi#Troubleshooting|Wifi troubleshooting]] page for issues related to wireless interfaces. If nothing works, you may have to use an alternate interface (e.g. a usb to ethernet adapter).

=== Connectivity failing / "ping: bad address" ===

If pings fail, a possible reason may have been improper permissions or ownership of {{Path|/etc/resolv.conf}}, perhaps due to a backup being restored without these being set correctly.
Test for these:
<pre>
$ ls /etc/resolv.conf
-rw-r--r-- 1 root root 845 Oct 24 23:58 /etc/resolv.conf
</pre>

The above output is appropriate: {{ic|-rw-r--r--}} permissions, with {{ic|root:root}} ownership. Otherwise, one would need to reset whatever is required:
<pre>
doas chmod 644 /etc/resolv.conf
doas chown root:root /etc/resolv.conf
</pre>

Although in many cases {{ic|-rw----r--}} may appear to work ({{ic|chmod 604}}), having 'group read denied' for this file could be insufficient in some environments e.g. for Docker, Nomad and container environments, etc.

The file may have been made immutable/unwritable, in which case its immutability will have to be temporarily suspended in order to correct the permissions and/or ownership settings. To test for immutability:
<pre>
$ lsattr /etc/resolv.conf
----i--------e- /etc/resolv.conf
</pre>
The output in such an installation demonstrates an 'i', which confirms immutability. In such cases:
# Remove immutability temporarily with {{ic|doas chattr -i /etc/resolv.conf}}
# Reset permissions and/or ownership, as per the above
# Restore immutability: {{ic|doas chattr +i /etc/resolv.conf}}
Regarding immutability, the aforementioned [[udhcpc]] page delves deeper on the matter of overwriting {{Path|resolv.conf}}.

== See also ==

You may also wish to review the following network related articles:
* [[Ifupdown-ng|Ifupdown-ng]] Basic networking Device Manager in Alpine Linux
* [[NetworkManager]] - Alternate Front-end to Networking
* [[VLAN]]
* [https://github.com/ifupdown-ng/ifupdown-ng/blob/main/doc/interfaces-vxlan.scd vxlan]
* [[Bonding|Bonding setup]]
* [[Bridge|Network bridge setup]]
* [[udhcpc|udhcpc configuration]]
* [[Wifi#wpa_supplicant|wpa_supplicant]] - Default wifi daemon
* [[Iwd|iwd]] - An alternate wifi daemon
* [[Tutorials and Howtos#Firewall|List of Firewall software]]

[[Category:Networking]]

How to get regular stuff working

2026-04-12T03:27:14Z

Apropos: /* Filesystem support */ link directly to overview

Alpine Linux is built around [[Musl| musl libc]] and [[BusyBox]] and software packages are thinned out and split into [[#Subpackages and missing functionality|subpackages]]. This makes it small and very resource efficient. The [[BusyBox#BusyBox applets|utilities in BusyBox]] tend to only implement standard options and lack GNU-specific extensions. This page explains how to get the utilities typically found in GNU/Linux distributions.

Many utilities on this page are provided either by a package containing multiple collected utilities, or through a meta package. The [[Alpine Package Keeper|apk info]] command and its various flags (<code>--provides</code>, <code>--depends</code>, <code>--who-owns</code>, etc) is useful for determining exactly what is provided by what.

== Core utilities ==
{{Main|GNU core utilities}}

Most of the basic file, shell and text manipulation utilities commonly grouped under [https://en.wikipedia.org/wiki/List_of_GNU_Core_Utilities_commands core utilities] are provided by [[BusyBox]]. To replace it with GNU {{pkg|coreutils}} package:{{Cmd|# apk add {{pkg|coreutils}}}}

== Linux utilities ==

A set of approximately 100 basic Linux system utilities not included in the GNU core utilities, such as <code>mount</code>, <code>cfdisk</code>, <code>more</code>, <code>lsblk</code> and <code>kill</code> are maintained under [https://en.wikipedia.org/wiki/Util-linux util-linux]. The {{pkg|util-linux}} package is split into multiple subpackages (see below), so it is possible to install only some of them individually. To have the complete {{pkg|util-linux}} package:{{Cmd|# apk add {{pkg|util-linux}}}}

The standard file pager <code>less</code> is not actually provided by {{pkg|coreutils}} or {{pkg|util-linux}}, but rather by the standalone package {{pkg|less}}.

== Subpackages and missing functionality ==

When a package is installed in Alpine Linux, no assumption is made as to what features the user wants, so [[Alpine_Package_Keeper#Subpackages|subpackages]] are not installed by default. As such, the user might get a false impression of missing functionality.

For example, the {{pkg|networkmanager}} package for [[NetworkManager]] has 20+ subpackages based on features. If the user installs the {{pkg|networkmanager}} package, ''only'' the NetworkManager utility will get installed. To manage Wi-Fi networks, use commands like <code>nmcli</code> and <code>nmtui</code>, or launch the GTK applet, the user is expected to add the required subpackages {{pkg|networkmanager-wifi}}, {{pkg|networkmanager-cli}}, {{pkg|networkmanager-tui}}, and {{pkg|network-manager-applet}} respectively.

This is in contrast to many other Linux distributions, where when NetworkManager is installed all the above functionality plus that of {{pkg|networkmanager-bluetooth}}, {{pkg|networkmanager-adsl}}, {{pkg|networkmanager-wwan}}, {{pkg|networkmanager-openvpn}}, {{pkg|networkmanager-l2tp}}, {{pkg|networkmanager-ppp}}, and the like are automatically installed, along with their dependencies.

== Search utilities ==

The standard search tools <code>find</code> and <code>xargs</code> are provided by the {{pkg|findutils}} package:{{Cmd|# apk add {{pkg|findutils}}}}

GNU Grep is available as the {{pkg|grep}} package. The {{pkg|ripgrep}} package is also available and provides <code>rg</code>.

== Shell management ==
{{Main|Shell management}}
The default shell used by Alpine Linux is the Busybox variant of the [[Shell_management#Ash_shell|ash shell]]. This is a POSIX compliant shell. All popular shells are available in Alpine Linux and the [[Shell_management#Change_default_shell|default shell can be changed]], if desired.

== Hardware management ==

Install {{pkg|pciutils}} and {{pkg|usbutils}} for identifying and configuring PCI and USB hardware using the full featured version of <code>lspci</code> and <code>lsusb</code> commands respectively. {{Cmd|# apk add {{pkg|pciutils}} {{pkg|usbutils}}}}

The packages {{pkg|hwdata-pci}} and {{pkg|hwdata-usb}} are dependencies for the above utilities and they are installed automatically. These packages can be removed once the hardware configuration has been completed.

== Filesystem support ==
{{Main|Filesystems}}

Alpine supports [[Filesystems#Overview|a variety of filesystems]]. Support (and tooling) for them may be had through their various packages: {{pkg|dosfstools}}, {{pkg|exfatprogs}}, {{pkg|zfs}}, etc...

== Disk management ==
{{Main|File management}}

[[File management#Udisks|udisks]] and [[File management#GVfs|GVfs]] make managing (removable) disks much easier.
{{cmd|# apk add {{pkg|udisks2}} {{pkg|gvfs-fuse}}}}

== Network management ==
{{Main|Configure Networking}}
For network, you may want to install {{pkg|iproute2}}. {{Cmd|# apk add {{pkg|iproute2}}}}

== Locale and key management ==
* [[Locale|Locales]], including keyboards, languages and date and time formats are typically configured with the [[Alpine_configuration_management_scripts#setup-alpine|setup-alpine]] and like scripts, and within desktop environment settings.

* Consult the [[Compose_key|Compose Key]] wikipage to create foreign currency symbols, accents and diacritics, endashes (–) and emdashes (—), etc.

== Development environment ==
{{Main|Developer Documentation}}
Compiling codebases in Alpine Linux may be more challenging because it uses [[Musl|musl instead of glibc]]. The {{pkg|build-base}} meta package provides regular compiler stuff such as {{pkg|binutils}} (providing <code>ld</code>, <code>objdump</code>, <code>readelf</code>, etc...), {{pkg|gcc}}, {{pkg|g++}}, {{pkg|make}}, etc...

{{Cmd|# apk add {{pkg|build-base}}}}

The {{pkg|alpine-sdk}} meta package is provided to build packages for Alpine Linux. It includes {{pkg|abuild}}, {{pkg|build-base}}, and {{pkg|git}}.

{{Cmd|# apk add {{pkg|alpine-sdk}}}}

{{pkg|cmake}} may be desirable to have installed.

{{Cmd|# apk add {{pkg|cmake}} {{pkg|extra-cmake-modules}}}}

{{pkg|ccache}} and a lot other tools are also available in Alpine Linux.

[[Category:Installation]]
[[Category:System Administration]]

How to get regular stuff working

2026-04-12T03:26:37Z

Apropos: Add section on filesystem support

Alpine Linux is built around [[Musl| musl libc]] and [[BusyBox]] and software packages are thinned out and split into [[#Subpackages and missing functionality|subpackages]]. This makes it small and very resource efficient. The [[BusyBox#BusyBox applets|utilities in BusyBox]] tend to only implement standard options and lack GNU-specific extensions. This page explains how to get the utilities typically found in GNU/Linux distributions.

Many utilities on this page are provided either by a package containing multiple collected utilities, or through a meta package. The [[Alpine Package Keeper|apk info]] command and its various flags (<code>--provides</code>, <code>--depends</code>, <code>--who-owns</code>, etc) is useful for determining exactly what is provided by what.

== Core utilities ==
{{Main|GNU core utilities}}

Most of the basic file, shell and text manipulation utilities commonly grouped under [https://en.wikipedia.org/wiki/List_of_GNU_Core_Utilities_commands core utilities] are provided by [[BusyBox]]. To replace it with GNU {{pkg|coreutils}} package:{{Cmd|# apk add {{pkg|coreutils}}}}

== Linux utilities ==

A set of approximately 100 basic Linux system utilities not included in the GNU core utilities, such as <code>mount</code>, <code>cfdisk</code>, <code>more</code>, <code>lsblk</code> and <code>kill</code> are maintained under [https://en.wikipedia.org/wiki/Util-linux util-linux]. The {{pkg|util-linux}} package is split into multiple subpackages (see below), so it is possible to install only some of them individually. To have the complete {{pkg|util-linux}} package:{{Cmd|# apk add {{pkg|util-linux}}}}

The standard file pager <code>less</code> is not actually provided by {{pkg|coreutils}} or {{pkg|util-linux}}, but rather by the standalone package {{pkg|less}}.

== Subpackages and missing functionality ==

When a package is installed in Alpine Linux, no assumption is made as to what features the user wants, so [[Alpine_Package_Keeper#Subpackages|subpackages]] are not installed by default. As such, the user might get a false impression of missing functionality.

For example, the {{pkg|networkmanager}} package for [[NetworkManager]] has 20+ subpackages based on features. If the user installs the {{pkg|networkmanager}} package, ''only'' the NetworkManager utility will get installed. To manage Wi-Fi networks, use commands like <code>nmcli</code> and <code>nmtui</code>, or launch the GTK applet, the user is expected to add the required subpackages {{pkg|networkmanager-wifi}}, {{pkg|networkmanager-cli}}, {{pkg|networkmanager-tui}}, and {{pkg|network-manager-applet}} respectively.

This is in contrast to many other Linux distributions, where when NetworkManager is installed all the above functionality plus that of {{pkg|networkmanager-bluetooth}}, {{pkg|networkmanager-adsl}}, {{pkg|networkmanager-wwan}}, {{pkg|networkmanager-openvpn}}, {{pkg|networkmanager-l2tp}}, {{pkg|networkmanager-ppp}}, and the like are automatically installed, along with their dependencies.

== Search utilities ==

The standard search tools <code>find</code> and <code>xargs</code> are provided by the {{pkg|findutils}} package:{{Cmd|# apk add {{pkg|findutils}}}}

GNU Grep is available as the {{pkg|grep}} package. The {{pkg|ripgrep}} package is also available and provides <code>rg</code>.

== Shell management ==
{{Main|Shell management}}
The default shell used by Alpine Linux is the Busybox variant of the [[Shell_management#Ash_shell|ash shell]]. This is a POSIX compliant shell. All popular shells are available in Alpine Linux and the [[Shell_management#Change_default_shell|default shell can be changed]], if desired.

== Hardware management ==

Install {{pkg|pciutils}} and {{pkg|usbutils}} for identifying and configuring PCI and USB hardware using the full featured version of <code>lspci</code> and <code>lsusb</code> commands respectively. {{Cmd|# apk add {{pkg|pciutils}} {{pkg|usbutils}}}}

The packages {{pkg|hwdata-pci}} and {{pkg|hwdata-usb}} are dependencies for the above utilities and they are installed automatically. These packages can be removed once the hardware configuration has been completed.

== Filesystem support ==
{{Main|Filesystems}}

Alpine supports [[Filesystems|a variety of filesystems]]. Support (and tooling) for them may be had through their various packages: {{pkg|dosfstools}}, {{pkg|exfatprogs}}, {{pkg|zfs}}, etc...

== Disk management ==
{{Main|File management}}

[[File management#Udisks|udisks]] and [[File management#GVfs|GVfs]] make managing (removable) disks much easier.
{{cmd|# apk add {{pkg|udisks2}} {{pkg|gvfs-fuse}}}}

== Network management ==
{{Main|Configure Networking}}
For network, you may want to install {{pkg|iproute2}}. {{Cmd|# apk add {{pkg|iproute2}}}}

== Locale and key management ==
* [[Locale|Locales]], including keyboards, languages and date and time formats are typically configured with the [[Alpine_configuration_management_scripts#setup-alpine|setup-alpine]] and like scripts, and within desktop environment settings.

* Consult the [[Compose_key|Compose Key]] wikipage to create foreign currency symbols, accents and diacritics, endashes (–) and emdashes (—), etc.

== Development environment ==
{{Main|Developer Documentation}}
Compiling codebases in Alpine Linux may be more challenging because it uses [[Musl|musl instead of glibc]]. The {{pkg|build-base}} meta package provides regular compiler stuff such as {{pkg|binutils}} (providing <code>ld</code>, <code>objdump</code>, <code>readelf</code>, etc...), {{pkg|gcc}}, {{pkg|g++}}, {{pkg|make}}, etc...

{{Cmd|# apk add {{pkg|build-base}}}}

The {{pkg|alpine-sdk}} meta package is provided to build packages for Alpine Linux. It includes {{pkg|abuild}}, {{pkg|build-base}}, and {{pkg|git}}.

{{Cmd|# apk add {{pkg|alpine-sdk}}}}

{{pkg|cmake}} may be desirable to have installed.

{{Cmd|# apk add {{pkg|cmake}} {{pkg|extra-cmake-modules}}}}

{{pkg|ccache}} and a lot other tools are also available in Alpine Linux.

[[Category:Installation]]
[[Category:System Administration]]

How to get regular stuff working

2026-04-12T03:25:26Z

Apropos: /* Disk management */ cleanup and mention gvfs

Alpine Linux is built around [[Musl| musl libc]] and [[BusyBox]] and software packages are thinned out and split into [[#Subpackages and missing functionality|subpackages]]. This makes it small and very resource efficient. The [[BusyBox#BusyBox applets|utilities in BusyBox]] tend to only implement standard options and lack GNU-specific extensions. This page explains how to get the utilities typically found in GNU/Linux distributions.

Many utilities on this page are provided either by a package containing multiple collected utilities, or through a meta package. The [[Alpine Package Keeper|apk info]] command and its various flags (<code>--provides</code>, <code>--depends</code>, <code>--who-owns</code>, etc) is useful for determining exactly what is provided by what.

== Core utilities ==
{{Main|GNU core utilities}}

Most of the basic file, shell and text manipulation utilities commonly grouped under [https://en.wikipedia.org/wiki/List_of_GNU_Core_Utilities_commands core utilities] are provided by [[BusyBox]]. To replace it with GNU {{pkg|coreutils}} package:{{Cmd|# apk add {{pkg|coreutils}}}}

== Linux utilities ==

A set of approximately 100 basic Linux system utilities not included in the GNU core utilities, such as <code>mount</code>, <code>cfdisk</code>, <code>more</code>, <code>lsblk</code> and <code>kill</code> are maintained under [https://en.wikipedia.org/wiki/Util-linux util-linux]. The {{pkg|util-linux}} package is split into multiple subpackages (see below), so it is possible to install only some of them individually. To have the complete {{pkg|util-linux}} package:{{Cmd|# apk add {{pkg|util-linux}}}}

The standard file pager <code>less</code> is not actually provided by {{pkg|coreutils}} or {{pkg|util-linux}}, but rather by the standalone package {{pkg|less}}.

== Subpackages and missing functionality ==

When a package is installed in Alpine Linux, no assumption is made as to what features the user wants, so [[Alpine_Package_Keeper#Subpackages|subpackages]] are not installed by default. As such, the user might get a false impression of missing functionality.

For example, the {{pkg|networkmanager}} package for [[NetworkManager]] has 20+ subpackages based on features. If the user installs the {{pkg|networkmanager}} package, ''only'' the NetworkManager utility will get installed. To manage Wi-Fi networks, use commands like <code>nmcli</code> and <code>nmtui</code>, or launch the GTK applet, the user is expected to add the required subpackages {{pkg|networkmanager-wifi}}, {{pkg|networkmanager-cli}}, {{pkg|networkmanager-tui}}, and {{pkg|network-manager-applet}} respectively.

This is in contrast to many other Linux distributions, where when NetworkManager is installed all the above functionality plus that of {{pkg|networkmanager-bluetooth}}, {{pkg|networkmanager-adsl}}, {{pkg|networkmanager-wwan}}, {{pkg|networkmanager-openvpn}}, {{pkg|networkmanager-l2tp}}, {{pkg|networkmanager-ppp}}, and the like are automatically installed, along with their dependencies.

== Search utilities ==

The standard search tools <code>find</code> and <code>xargs</code> are provided by the {{pkg|findutils}} package:{{Cmd|# apk add {{pkg|findutils}}}}

GNU Grep is available as the {{pkg|grep}} package. The {{pkg|ripgrep}} package is also available and provides <code>rg</code>.

== Shell management ==
{{Main|Shell management}}
The default shell used by Alpine Linux is the Busybox variant of the [[Shell_management#Ash_shell|ash shell]]. This is a POSIX compliant shell. All popular shells are available in Alpine Linux and the [[Shell_management#Change_default_shell|default shell can be changed]], if desired.

== Hardware management ==

Install {{pkg|pciutils}} and {{pkg|usbutils}} for identifying and configuring PCI and USB hardware using the full featured version of <code>lspci</code> and <code>lsusb</code> commands respectively. {{Cmd|# apk add {{pkg|pciutils}} {{pkg|usbutils}}}}

The packages {{pkg|hwdata-pci}} and {{pkg|hwdata-usb}} are dependencies for the above utilities and they are installed automatically. These packages can be removed once the hardware configuration has been completed.

== Disk management ==
{{Main|File management}}

[[File management#Udisks|udisks]] and [[File management#GVfs|GVfs]] make managing (removable) disks much easier.
{{cmd|# apk add {{pkg|udisks2}} {{pkg|gvfs-fuse}}}}

== Network management ==
{{Main|Configure Networking}}
For network, you may want to install {{pkg|iproute2}}. {{Cmd|# apk add {{pkg|iproute2}}}}

== Locale and key management ==
* [[Locale|Locales]], including keyboards, languages and date and time formats are typically configured with the [[Alpine_configuration_management_scripts#setup-alpine|setup-alpine]] and like scripts, and within desktop environment settings.

* Consult the [[Compose_key|Compose Key]] wikipage to create foreign currency symbols, accents and diacritics, endashes (–) and emdashes (—), etc.

== Development environment ==
{{Main|Developer Documentation}}
Compiling codebases in Alpine Linux may be more challenging because it uses [[Musl|musl instead of glibc]]. The {{pkg|build-base}} meta package provides regular compiler stuff such as {{pkg|binutils}} (providing <code>ld</code>, <code>objdump</code>, <code>readelf</code>, etc...), {{pkg|gcc}}, {{pkg|g++}}, {{pkg|make}}, etc...

{{Cmd|# apk add {{pkg|build-base}}}}

The {{pkg|alpine-sdk}} meta package is provided to build packages for Alpine Linux. It includes {{pkg|abuild}}, {{pkg|build-base}}, and {{pkg|git}}.

{{Cmd|# apk add {{pkg|alpine-sdk}}}}

{{pkg|cmake}} may be desirable to have installed.

{{Cmd|# apk add {{pkg|cmake}} {{pkg|extra-cmake-modules}}}}

{{pkg|ccache}} and a lot other tools are also available in Alpine Linux.

[[Category:Installation]]
[[Category:System Administration]]

Filesystems

2026-04-12T03:17:46Z

Apropos: /* Overview */ Add mention of ZFS

This page documents the Alpine Linux supported filesystems needed for various storage media.

== Overview ==

The following table lists the packages and tools related to various filesystems available along with the '''command''' to format.
<onlyinclude>
{| class="wikitable" align="center" style="width:100%; border:1px #0771a6 solid; background:#f9f9f9; text-align:left; border-collapse:collapse;"
|-style="background:#333333; color:#ffffff; font-size: 1.2em; text-align:center;"
|width="18%" | Tool
|width="18%"| Filesystem
|width="15%"|Formatting command
|Brief Notes
|-
|{{Pkg|btrfs-progs}}||[[Btrfs]]||mkfs.btrfs||Combines copy-on-write and volume management, similar to ZFS.
|-
|{{Pkg|dosfstools}} ||FAT12/FAT16/FAT32||mkfs.vfat||Widely-used DOS filesystems. Also used for [[UEFI|EFI]] partitions.
|-
|{{Pkg|e2fsprogs}} ||ext2/ext3/ext4||mkfs.ext4||Journaling filesystems. ext4 is the current default on Linux.
|-
|{{Pkg|exfatprogs}} ||exfat||mkfs.exfat||Commonly used on USB flash drives and SD cards.
|-
|{{Pkg|f2fs-tools}} ||[[F2FS]]||mkfs.f2fs||
|-
|{{Pkg|hfsprogs}} ||HFS/HFS+||mkfs.hfsplus||Used in older Apple/Mac products before APFS.
|-
|{{Pkg|jfsutils}} ||JFS||mkfs.jfs||
|-
|{{Pkg|ntfs-3g-progs}} ||NTFS ||mkfs.ntfs||Full-featured, Microsoft/Windows FUSE driver.
|-
|{{Pkg|squashfs-tools}} ||[[SquashFS]]||mksquashfs||Compressed read-only file system.
|-
|{{Pkg|xfsprogs}} ||XFS||mkfs.xfs||
|}</onlyinclude>

Additionally, Alpine has [[ZFS|excellent support]] for [https://en.wikipedia.org/wiki/ZFS ZFS], a highly robust copy-on-write filesystem / volume manager.

== Filesystem labels ==

Most of the commonly used filesystems store the '''volume label''' or '''filesystem label''' in their metadata/superblock.

Labels can be set during filesystem creation or at a later time. The below table lists the commands for both. The commands are non-destructive as long as the filesystem is '''Unmounted''', except for [[btrfs]].

{| class="wikitable" align="center" style="width:100%; border:1px #0771a6 solid; background:#f9f9f9; text-align:left; border-collapse:collapse;"
|-style="background:#333333; color:#ffffff; font-size: 1.2em; text-align:center;"
|width="8%" | Filesystem
|width="18%"| Tool
|width="25%"| Filesystem creation
|width="35%"| Existing filesystem
|Mounted/Unmounted
|-
|[[btrfs]]||{{Pkg|btrfs-progs}}||mkfs.btrfs -L "label" /dev/sdXY||btrfs filesystem label /mount/point "newlabel"||Mounted
|-
|FAT32||{{Pkg|dosfstools}} ||mkfs.fat -n "LABEL" /dev/sdXY ||fatlabel /dev/sdXY "NEWLABEL"||Unmounted
|-
|ext4||{{Pkg|e2fsprogs-extra}} ||mkfs.ext4 -L "label" /dev/sdXY||tune2fs -L "newlabel" /dev/sdXY||Unmounted
|-
|NTFS ||{{Pkg|ntfs-3g-progs}} ||mkfs.ntfs -L "label" /dev/sdXY||ntfslabel /dev/sdXY "newlabel"||Unmounted
|-
|XFS||{{Pkg|xfsprogs}} ||mkfs.xfs -L "label" /dev/sdXY||xfs_admin -L "newlabel" /dev/sdXY||Unmounted
|}

== See also ==

* [[Setting_up_disks_manually#Manual_partitioning|Manual partitioning]]
* [https://www.nico.schottelius.org/blog/2024-10-10-how-to-enable-encrypted-swap-in-alpine-linux/ How to enable encrypted swap in Alpine Linux]

[[Category:Storage]]
[[Category:Installation]]
[[Category:Filesystems]]

Filesystems

2026-04-12T03:08:46Z

Apropos: Remove empty Filesystem tools section and add information to filesystem tools table

This page documents the Alpine Linux supported filesystems needed for various storage media.

== Overview ==

The following table lists the packages and tools related to various filesystems available along with the '''command''' to format.
<onlyinclude>
{| class="wikitable" align="center" style="width:100%; border:1px #0771a6 solid; background:#f9f9f9; text-align:left; border-collapse:collapse;"
|-style="background:#333333; color:#ffffff; font-size: 1.2em; text-align:center;"
|width="18%" | Tool
|width="18%"| Filesystem
|width="15%"|Formatting command
|Brief Notes
|-
|{{Pkg|btrfs-progs}}||[[Btrfs]]||mkfs.btrfs||Combines copy-on-write and volume management, similar to ZFS.
|-
|{{Pkg|dosfstools}} ||FAT12/FAT16/FAT32||mkfs.vfat||Widely-used DOS filesystems. Also used for [[UEFI|EFI]] partitions.
|-
|{{Pkg|e2fsprogs}} ||ext2/ext3/ext4||mkfs.ext4||Journaling filesystems. ext4 is the current default on Linux.
|-
|{{Pkg|exfatprogs}} ||exfat||mkfs.exfat||Commonly used on USB flash drives and SD cards.
|-
|{{Pkg|f2fs-tools}} ||[[F2FS]]||mkfs.f2fs||
|-
|{{Pkg|hfsprogs}} ||HFS/HFS+||mkfs.hfsplus||Used in older Apple/Mac products before APFS.
|-
|{{Pkg|jfsutils}} ||JFS||mkfs.jfs||
|-
|{{Pkg|ntfs-3g-progs}} ||NTFS ||mkfs.ntfs||Full-featured, Microsoft/Windows FUSE driver.
|-
|{{Pkg|squashfs-tools}} ||[[SquashFS]]||mksquashfs||Compressed read-only file system.
|-
|{{Pkg|xfsprogs}} ||XFS||mkfs.xfs||
|}</onlyinclude>

== Filesystem labels ==

Most of the commonly used filesystems store the '''volume label''' or '''filesystem label''' in their metadata/superblock.

Labels can be set during filesystem creation or at a later time. The below table lists the commands for both. The commands are non-destructive as long as the filesystem is '''Unmounted''', except for [[btrfs]].

{| class="wikitable" align="center" style="width:100%; border:1px #0771a6 solid; background:#f9f9f9; text-align:left; border-collapse:collapse;"
|-style="background:#333333; color:#ffffff; font-size: 1.2em; text-align:center;"
|width="8%" | Filesystem
|width="18%"| Tool
|width="25%"| Filesystem creation
|width="35%"| Existing filesystem
|Mounted/Unmounted
|-
|[[btrfs]]||{{Pkg|btrfs-progs}}||mkfs.btrfs -L "label" /dev/sdXY||btrfs filesystem label /mount/point "newlabel"||Mounted
|-
|FAT32||{{Pkg|dosfstools}} ||mkfs.fat -n "LABEL" /dev/sdXY ||fatlabel /dev/sdXY "NEWLABEL"||Unmounted
|-
|ext4||{{Pkg|e2fsprogs-extra}} ||mkfs.ext4 -L "label" /dev/sdXY||tune2fs -L "newlabel" /dev/sdXY||Unmounted
|-
|NTFS ||{{Pkg|ntfs-3g-progs}} ||mkfs.ntfs -L "label" /dev/sdXY||ntfslabel /dev/sdXY "newlabel"||Unmounted
|-
|XFS||{{Pkg|xfsprogs}} ||mkfs.xfs -L "label" /dev/sdXY||xfs_admin -L "newlabel" /dev/sdXY||Unmounted
|}

== See also ==

* [[Setting_up_disks_manually#Manual_partitioning|Manual partitioning]]
* [https://www.nico.schottelius.org/blog/2024-10-10-how-to-enable-encrypted-swap-in-alpine-linux/ How to enable encrypted swap in Alpine Linux]

[[Category:Storage]]
[[Category:Installation]]
[[Category:Filesystems]]

How to get regular stuff working

2026-04-12T02:45:28Z

Apropos: /* Development environment */ Note some examples of what binutils provides

Alpine Linux is built around [[Musl| musl libc]] and [[BusyBox]] and software packages are thinned out and split into [[#Subpackages and missing functionality|subpackages]]. This makes it small and very resource efficient. The [[BusyBox#BusyBox applets|utilities in BusyBox]] tend to only implement standard options and lack GNU-specific extensions. This page explains how to get the utilities typically found in GNU/Linux distributions.

Many utilities on this page are provided either by a package containing multiple collected utilities, or through a meta package. The [[Alpine Package Keeper|apk info]] command and its various flags (<code>--provides</code>, <code>--depends</code>, <code>--who-owns</code>, etc) is useful for determining exactly what is provided by what.

== Core utilities ==
{{Main|GNU core utilities}}

Most of the basic file, shell and text manipulation utilities commonly grouped under [https://en.wikipedia.org/wiki/List_of_GNU_Core_Utilities_commands core utilities] are provided by [[BusyBox]]. To replace it with GNU {{pkg|coreutils}} package:{{Cmd|# apk add {{pkg|coreutils}}}}

== Linux utilities ==

A set of approximately 100 basic Linux system utilities not included in the GNU core utilities, such as <code>mount</code>, <code>cfdisk</code>, <code>more</code>, <code>lsblk</code> and <code>kill</code> are maintained under [https://en.wikipedia.org/wiki/Util-linux util-linux]. The {{pkg|util-linux}} package is split into multiple subpackages (see below), so it is possible to install only some of them individually. To have the complete {{pkg|util-linux}} package:{{Cmd|# apk add {{pkg|util-linux}}}}

The standard file pager <code>less</code> is not actually provided by {{pkg|coreutils}} or {{pkg|util-linux}}, but rather by the standalone package {{pkg|less}}.

== Subpackages and missing functionality ==

When a package is installed in Alpine Linux, no assumption is made as to what features the user wants, so [[Alpine_Package_Keeper#Subpackages|subpackages]] are not installed by default. As such, the user might get a false impression of missing functionality.

For example, the {{pkg|networkmanager}} package for [[NetworkManager]] has 20+ subpackages based on features. If the user installs the {{pkg|networkmanager}} package, ''only'' the NetworkManager utility will get installed. To manage Wi-Fi networks, use commands like <code>nmcli</code> and <code>nmtui</code>, or launch the GTK applet, the user is expected to add the required subpackages {{pkg|networkmanager-wifi}}, {{pkg|networkmanager-cli}}, {{pkg|networkmanager-tui}}, and {{pkg|network-manager-applet}} respectively.

This is in contrast to many other Linux distributions, where when NetworkManager is installed all the above functionality plus that of {{pkg|networkmanager-bluetooth}}, {{pkg|networkmanager-adsl}}, {{pkg|networkmanager-wwan}}, {{pkg|networkmanager-openvpn}}, {{pkg|networkmanager-l2tp}}, {{pkg|networkmanager-ppp}}, and the like are automatically installed, along with their dependencies.

== Search utilities ==

The standard search tools <code>find</code> and <code>xargs</code> are provided by the {{pkg|findutils}} package:{{Cmd|# apk add {{pkg|findutils}}}}

GNU Grep is available as the {{pkg|grep}} package. The {{pkg|ripgrep}} package is also available and provides <code>rg</code>.

== Shell management ==
{{Main|Shell management}}
The default shell used by Alpine Linux is the Busybox variant of the [[Shell_management#Ash_shell|ash shell]]. This is a POSIX compliant shell. All popular shells are available in Alpine Linux and the [[Shell_management#Change_default_shell|default shell can be changed]], if desired.

== Hardware management ==

Install {{pkg|pciutils}} and {{pkg|usbutils}} for identifying and configuring PCI and USB hardware using the full featured version of <code>lspci</code> and <code>lsusb</code> commands respectively. {{Cmd|# apk add {{pkg|pciutils}} {{pkg|usbutils}}}}

The packages {{pkg|hwdata-pci}} and {{pkg|hwdata-usb}} are dependencies for the above utilities and they are installed automatically. These packages can be removed once the hardware configuration has been completed.

== Disk management ==
{{Main|File management}}
Managing disks including removable disks is much easier with udisks.{{Cmd|# apk add {{pkg|udisks2}}}} To see the mounted disks:{{Cmd|# udisksctl status}}

== Network management ==
{{Main|Configure Networking}}
For network, you may want to install {{pkg|iproute2}}. {{Cmd|# apk add {{pkg|iproute2}}}}

== Locale and key management ==
* [[Locale|Locales]], including keyboards, languages and date and time formats are typically configured with the [[Alpine_configuration_management_scripts#setup-alpine|setup-alpine]] and like scripts, and within desktop environment settings.

* Consult the [[Compose_key|Compose Key]] wikipage to create foreign currency symbols, accents and diacritics, endashes (–) and emdashes (—), etc.

== Development environment ==
{{Main|Developer Documentation}}
Compiling codebases in Alpine Linux may be more challenging because it uses [[Musl|musl instead of glibc]]. The {{pkg|build-base}} meta package provides regular compiler stuff such as {{pkg|binutils}} (providing <code>ld</code>, <code>objdump</code>, <code>readelf</code>, etc...), {{pkg|gcc}}, {{pkg|g++}}, {{pkg|make}}, etc...

{{Cmd|# apk add {{pkg|build-base}}}}

The {{pkg|alpine-sdk}} meta package is provided to build packages for Alpine Linux. It includes {{pkg|abuild}}, {{pkg|build-base}}, and {{pkg|git}}.

{{Cmd|# apk add {{pkg|alpine-sdk}}}}

{{pkg|cmake}} may be desirable to have installed.

{{Cmd|# apk add {{pkg|cmake}} {{pkg|extra-cmake-modules}}}}

{{pkg|ccache}} and a lot other tools are also available in Alpine Linux.

[[Category:Installation]]
[[Category:System Administration]]

How to get regular stuff working

2026-04-12T02:36:41Z

Apropos: Stick Subpackages section below the Linux utilities section (which references it) + minor wording changes

Alpine Linux is built around [[Musl| musl libc]] and [[BusyBox]] and software packages are thinned out and split into [[#Subpackages and missing functionality|subpackages]]. This makes it small and very resource efficient. The [[BusyBox#BusyBox applets|utilities in BusyBox]] tend to only implement standard options and lack GNU-specific extensions. This page explains how to get the utilities typically found in GNU/Linux distributions.

Many utilities on this page are provided either by a package containing multiple collected utilities, or through a meta package. The [[Alpine Package Keeper|apk info]] command and its various flags (<code>--provides</code>, <code>--depends</code>, <code>--who-owns</code>, etc) is useful for determining exactly what is provided by what.

== Core utilities ==
{{Main|GNU core utilities}}

Most of the basic file, shell and text manipulation utilities commonly grouped under [https://en.wikipedia.org/wiki/List_of_GNU_Core_Utilities_commands core utilities] are provided by [[BusyBox]]. To replace it with GNU {{pkg|coreutils}} package:{{Cmd|# apk add {{pkg|coreutils}}}}

== Linux utilities ==

A set of approximately 100 basic Linux system utilities not included in the GNU core utilities, such as <code>mount</code>, <code>cfdisk</code>, <code>more</code>, <code>lsblk</code> and <code>kill</code> are maintained under [https://en.wikipedia.org/wiki/Util-linux util-linux]. The {{pkg|util-linux}} package is split into multiple subpackages (see below), so it is possible to install only some of them individually. To have the complete {{pkg|util-linux}} package:{{Cmd|# apk add {{pkg|util-linux}}}}

The standard file pager <code>less</code> is not actually provided by {{pkg|coreutils}} or {{pkg|util-linux}}, but rather by the standalone package {{pkg|less}}.

== Subpackages and missing functionality ==

When a package is installed in Alpine Linux, no assumption is made as to what features the user wants, so [[Alpine_Package_Keeper#Subpackages|subpackages]] are not installed by default. As such, the user might get a false impression of missing functionality.

For example, the {{pkg|networkmanager}} package for [[NetworkManager]] has 20+ subpackages based on features. If the user installs the {{pkg|networkmanager}} package, ''only'' the NetworkManager utility will get installed. To manage Wi-Fi networks, use commands like <code>nmcli</code> and <code>nmtui</code>, or launch the GTK applet, the user is expected to add the required subpackages {{pkg|networkmanager-wifi}}, {{pkg|networkmanager-cli}}, {{pkg|networkmanager-tui}}, and {{pkg|network-manager-applet}} respectively.

This is in contrast to many other Linux distributions, where when NetworkManager is installed all the above functionality plus that of {{pkg|networkmanager-bluetooth}}, {{pkg|networkmanager-adsl}}, {{pkg|networkmanager-wwan}}, {{pkg|networkmanager-openvpn}}, {{pkg|networkmanager-l2tp}}, {{pkg|networkmanager-ppp}}, and the like are automatically installed, along with their dependencies.

== Search utilities ==

The standard search tools <code>find</code> and <code>xargs</code> are provided by the {{pkg|findutils}} package:{{Cmd|# apk add {{pkg|findutils}}}}

GNU Grep is available as the {{pkg|grep}} package. The {{pkg|ripgrep}} package is also available and provides <code>rg</code>.

== Shell management ==
{{Main|Shell management}}
The default shell used by Alpine Linux is the Busybox variant of the [[Shell_management#Ash_shell|ash shell]]. This is a POSIX compliant shell. All popular shells are available in Alpine Linux and the [[Shell_management#Change_default_shell|default shell can be changed]], if desired.

== Hardware management ==

Install {{pkg|pciutils}} and {{pkg|usbutils}} for identifying and configuring PCI and USB hardware using the full featured version of <code>lspci</code> and <code>lsusb</code> commands respectively. {{Cmd|# apk add {{pkg|pciutils}} {{pkg|usbutils}}}}

The packages {{pkg|hwdata-pci}} and {{pkg|hwdata-usb}} are dependencies for the above utilities and they are installed automatically. These packages can be removed once the hardware configuration has been completed.

== Disk management ==
{{Main|File management}}
Managing disks including removable disks is much easier with udisks.{{Cmd|# apk add {{pkg|udisks2}}}} To see the mounted disks:{{Cmd|# udisksctl status}}

== Network management ==
{{Main|Configure Networking}}
For network, you may want to install {{pkg|iproute2}}. {{Cmd|# apk add {{pkg|iproute2}}}}

== Locale and key management ==
* [[Locale|Locales]], including keyboards, languages and date and time formats are typically configured with the [[Alpine_configuration_management_scripts#setup-alpine|setup-alpine]] and like scripts, and within desktop environment settings.

* Consult the [[Compose_key|Compose Key]] wikipage to create foreign currency symbols, accents and diacritics, endashes (–) and emdashes (—), etc.

== Development environment ==
{{Main|Developer Documentation}}
Compiling in Alpine Linux may be more challenging because it uses [[Musl|musl instead of glibc]]. The {{pkg|build-base}} meta package provides regular compiler stuff such as {{pkg|binutils}}, {{pkg|gcc}}, {{pkg|g++}}, {{pkg|make}} etc..

{{Cmd|# apk add {{pkg|build-base}}}}

The {{pkg|alpine-sdk}} meta package is provided to build packages for Alpine Linux. It includes {{pkg|abuild}}, {{pkg|build-base}}, and {{pkg|git}}.

{{Cmd|# apk add {{pkg|alpine-sdk}}}}

To install CMake:

{{Cmd|# apk add {{pkg|cmake}} {{pkg|extra-cmake-modules}}}}

{{pkg|ccache}} and a lot other tools are also available in Alpine Linux.

[[Category:Installation]]
[[Category:System Administration]]

Wi-Fi

2026-04-12T02:21:08Z

Apropos: link to nonexistent header for aesthetics

Alpine Linux has two wireless daemons ([[#wpa_supplicant|wpa_supplicant]] and [[iwd]]) and both are fully supported. This page describes how to set up a wireless network connection using the default daemon, {{Pkg|wpa_supplicant}}. {{Note|Do not use both wireless daemons ([[#wpa_supplicant|wpa_supplicant]] and [[iwd]]) simultaneously, as it leads to conflicts.}}

== Prerequisites ==

A working wireless [[#Device driver|device driver]]. Use the commands {{ic|ip link}} or {{ic|ip a}} to list your available network interfaces {{Path|wlan0}}, if you don't see any, refer to [[#Troubleshooting|Troubleshooting]] section.

== Setup-interfaces ==

The [[Configure_Networking#setup-interfaces|setup-interfaces]] script automates the installation and configuration of
<code>wpa_supplicant</code> daemon to use Wi-Fi. [[NetworkManager]] can then be used to manage your Wi-Fi using various gui/tui tools.

== Manual configuration ==

To get started install {{Pkg|wpa_supplicant}} package: {{Cmd|# apk add wpa_supplicant}}

Use this command to add your Wi-Fi network to wpa_supplicant: {{Cmd|# wpa_passphrase 'ExampleWifiSSID' 'ExampleWifiPassword' > /etc/wpa_supplicant/wpa_supplicant.conf}}
''(Access point not broadcasting its SSID requires additional line <code>scan_ssid=1</code> in the file {{Path|/etc/wpa_supplicant/wpa_supplicant.conf}})''

{{Note|the Wi-Fi SSID and password are case sensitive and the single quote before and after the SSID and password need to be there}}

Start wpa_supplicant in the foreground to check if wireless connection succeeds.{{Cmd|# wpa_supplicant -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf}}

'''Optional security precaution:'''

By default {{Pkg|wpa_supplicant}} will store your Wi-Fi password in plain text:{{Cat|/etc/wpa_supplicant/wpa_supplicant.conf|<nowiki>network={
ssid="<YourSSIDShouldBeHere>"
#psk="<YourPasswordShouldBeHereInPlainText>"
psk=<RandomLettersAndNumbersShouldBeHere>
}</nowiki>}}
If you don't want your password stored in plain text, delete the line with <code>#psk="<YourPasswordShouldBeHereInPlainText>"</code> on it.

If all is well, run it as a daemon in the background by setting the {{Path|-B}} option. {{Cmd|# wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf}}

Configure the interface with an IP address.{{Cmd|# udhcpc -i wlan0}}

Sanity check: the interface should have a {{Path|inet}} address. {{Cmd|$ ip addr show wlan0}}

Add a entry for the desired interface (e.g. <code>wlan0</code>) in the file as follows:{{Cat|/etc/network/interfaces|auto lo
auto wlan0
iface wlan0 inet dhcp}}

{{Warning|Don't remove or comment out the '''auto lo''' entry}}

Sanity check: Make sure {{Path|/etc/wpa_supplicant/wpa_supplicant.conf}} is the correct configuration for the wireless access point you want to connect to.

Bring the interface down. {{Cmd|# ip link set wlan0 down}}

Manually restart (or '''start''') '''networking'''.{{Cmd|# rc-service networking --quiet restart &}}

Perform [[Configure_Networking#Connectivity_testing|sanity checks]]. For issues related to name resolution, refer [[Configure_Networking#Configuring_DNS|Networking]] section.

=== Service configuration ===
{{Seealso|NetworkManager}}

Proceed to configure wpa_supplicant service to start automatically on boot, if networking works properly: {{Cmd|# rc-update add wpa_supplicant boot}}
Also ensure that '''networking''' is set to automatically start on boot: {{Cmd|# rc-update add networking boot}}

Manage wpa_supplicant service using the standard '''start''', '''stop''' and '''restart''' options. For eg: to start wpa_supplicant service: {{Cmd|# rc-service wpa_supplicant start}}

=== Launching udhcpc through wpa_cli actions ===

With the above configuration, udhcpc will only run once at boot. If the Wifi isn't available then, or the network changes after booting, udhcpc needs to be notified. You can automatically notify udhcpc of network changes by using a wpa_cli action file, such as the one installed by default at {{Path|/etc/wpa_supplicant/wpa_cli.sh}}.

To manually start a wpa_cli daemon with an action file, use the `-a` option: {{Cmd|# wpa_cli -a /etc/wpa_supplicant/wpa_cli.sh}}

To do this automatically, use the `wpa_cli` service included in {{Pkg|wpa_supplicant-openrc}}: {{Cat|/etc/conf.d/wpa_cli|<nowiki>WPACLI_OPTS="-a /etc/wpa_supplicant/wpa_cli.sh"</nowiki>}}
Add the service to start at boot: {{Cmd|# rc-update add wpa_cli boot}}

== Device driver ==

Wireless networking devices require device drivers and some chipsets also require firmware, in addition to a corresponding driver. In most cases the packaged [[Kernels#Firmware|firmware]] should get you the required drivers. The following section provides more information for various chipsets like [[#Broadcom_Wi-Fi_Chipset_Users|'''Broadcom''']] and some of these out-of-tree kernel drivers use [[Alpine kernel module support]].

=== Intel wireless devices ===

Intel wireless users seeking a minimal set of firmware packages need to ensure that the following firmware packages are installed: the {{Pkg|linux-firmware-none}} meta package and {{Pkg|linux-firmware-other}}. Additionally, the {{ic|iwlwifi}} command is provided by a further package beginning from Alpine Linux v3.23 and Edge: such installations will [https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/65712 also require] {{Pkg|linux-firmware-intel}}, which now supplies {{Path|iwlwifi*.ucode.zst}}. Earlier supported versions of Alpine Linux had the {{ic|iwlwifi}} command bundled in {{Pkg|linux-firmware-other}}.{{Pill||text=v3.23.x}}

=== Broadcom Wi-Fi Chipset ===

The Broadcom chipset is quite popular among older computers. The b43 driver is included in the default kernel packages. However, you might need to compile the firmware manually for this chipset as it is not included in {{pkg|linux-firmware}} for some cards. To check what broadcom chip you have using lspci: {{Cmd|$ lspci -nn -d 14e4:}}

Check what driver you need on the [https://wireless.docs.kernel.org/en/latest/en/users/drivers/b43.html#list-of-hardware b43 compatibility page].

====B43====

Download firmware cutter. {{Cmd|$ apk add b43-fwcutter}}

Now we have everything to download the proprietary driver and extract the firmware from it: {{Cmd|<nowiki># export FIRMWARE_INSTALL_DIR="/lib/firmware"
$ wget https://mirror2.openwrt.org/sources/broadcom-wl-5.100.138.tar.bz2
$ tar xjf broadcom-wl-5.100.138.tar.bz2
$ b43-fwcutter -w "$FIRMWARE_INSTALL_DIR" broadcom-wl-5.100.138/linux/wl_apsta.o</nowiki>}}

More information can be found [https://linuxwireless.sipsolutions.net/en/users/Drivers/b43/#Other_distributions_not_mentioned_above here].

Now you need to use modprobe so the device will show up: {{Cmd|# modprobe b43}}

Reboot and you have a working b43 driver. Now continue with the normal instructions.

==== wl ====

For '''wl''' chipset, you can download the APKBUILD from [https://codeberg.org/NeYurii/broadcom-wl here]. The site has necessary instructions and the it uses [[Alpine kernel module support]] for automatic building and updating driver for new kernel versions.

Commonly when building the APK with these instructions, you will get a "Permission denied" error for a specific line in the APKBUILD.

To fix this, edit the APKBUILD by changing the line: {{Cmd|ln -s /sys/kernel/btf/vmlinux /usr/src/linux-headers-"$(uname -r)"/}}

to: {{Cmd|doas ln -s /sys/kernel/btf/vmlinux /usr/src/linux-headers-"$(uname -r)"/}}

After that, it should build with no problems.

Alternately, install the software to build a driver: {{Cmd|apk add git alpine-sdk linux-headers linux-lts-dev}}

Then install the driver build repo (this is archived, however it's legacy so that doesn't matter): {{Cmd|git clone https://github.com/antoineco/broadcom-wl
cd broadcom-wl
}}

Then follow the build instructions listed in the git repo: {{Cmd|make
doas make install
doas depmod -A
doas modprobe wl
}}

Reboot and you have a working wl driver. Now continue with the normal instructions.

=== Realtek wireless devices ===

A number of out-of-tree kernel drivers for '''Realtek chipset''' are packaged and found here '''{{pkg|rtl*src*}}'''. These drivers can be installed using [[Alpine kernel module support]].

== Troubleshooting ==

In most cases the packaged [[Kernels#Firmware|firmware]] should get you the required drivers. To list your available network interfaces use the commands: {{Cmd|$ ip link}} or {{Cmd|$ ip a}}

If the above command shows {{Path|wlan0}} interface, proceed to bring it up using the command: {{Codeline|# ip link set wlan0 up}}. '''If no network interface is displayed, you probably need to load and/or install a [[#Device driver|device driver]]'''.

=== checking network cards ===

{{Cmd|$ cat /proc/net/dev }} lists the network interfaces that are detected. If the expected interfaces are not available, check what network hardware chip you have using builtin {{ic|lsusb}} command. If the output lacks sufficient information, install additional packages referred in [[How to get regular stuff working#Hardware_Management| hardware management]] to use below commands:
{{Cmd|$ lspci -nn }}
{{Cmd|$ lsusb}}

Check what [[#Device driver|device driver]] the card uses and modprobe it. Check that the card is in master mode.

=== Check dmesg ===

Run dmesg and check for errors related to the wireless interface. Usually, dmesg gives maximum information related to network and all other hardware.
{{Cmd|# dmesg}}

=== Rfkill ===

An error message <code>ioctl 0x8914 failed: No error information</code>, is the <code>busybox ip</code>'s way of saying your wireless radio is rfkilled, which means the wireless card is blocked by kernel. This can be changed using rfkill. To show the current status of your Wi-Fi:
~'''$''' rfkill list
0: phy0: wlan
Soft blocked: no
Hard blocked: no


If the card is hard-blocked, use the hardware button or switch to unblock it. If the card is not hard-blocked but soft-blocked, use the following command: {{Cmd|# rfkill unblock wifi}}

== See also ==

* [[Configure_Networking| Networking in Alpine Linux]]
* [[Iwd|iwd]] - An alternate to wpa_supplicant
* [[NetworkManager]] - Front-end to Networking
* [https://wiki.postmarketos.org/wiki/WiFi PostmarketOS Wiki]
* [https://wiki.archlinux.org/title/Network_configuration/Wireless Archwiki]
* [https://wiki.gentoo.org/wiki/Wi-Fi Gentoo Wiki]
* [[Alpine kernel module support]] - A fully automated solution for building kernel modules
* [https://unix.stackexchange.com/questions/606073/how-to-build-kernel-modules-in-alpine-3-12 Build kernel modules manually]

[[Category:Networking]]

Wi-Fi

2026-04-12T02:18:25Z

Apropos: minor grammar tweaks, some rewording

Alpine Linux has two wireless daemons ([[Wi-Fi|wpa_supplicant]] and [[iwd]]) and both are fully supported. This page describes how to set up a wireless network connection using the default daemon, {{Pkg|wpa_supplicant}}. {{Note|Do not use both wireless daemons ([[Wi-Fi|wpa_supplicant]] and [[iwd]]) simultaneously, as it leads to conflicts.}}

== Prerequisites ==

A working wireless [[#Device driver|device driver]]. Use the commands {{ic|ip link}} or {{ic|ip a}} to list your available network interfaces {{Path|wlan0}}, if you don't see any, refer to [[#Troubleshooting|Troubleshooting]] section.

== Setup-interfaces ==

The [[Configure_Networking#setup-interfaces|setup-interfaces]] script automates the installation and configuration of
<code>wpa_supplicant</code> daemon to use Wi-Fi. [[NetworkManager]] can then be used to manage your Wi-Fi using various gui/tui tools.

== Manual configuration ==

To get started install {{Pkg|wpa_supplicant}} package: {{Cmd|# apk add wpa_supplicant}}

Use this command to add your Wi-Fi network to wpa_supplicant: {{Cmd|# wpa_passphrase 'ExampleWifiSSID' 'ExampleWifiPassword' > /etc/wpa_supplicant/wpa_supplicant.conf}}
''(Access point not broadcasting its SSID requires additional line <code>scan_ssid=1</code> in the file {{Path|/etc/wpa_supplicant/wpa_supplicant.conf}})''

{{Note|the Wi-Fi SSID and password are case sensitive and the single quote before and after the SSID and password need to be there}}

Start wpa_supplicant in the foreground to check if wireless connection succeeds.{{Cmd|# wpa_supplicant -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf}}

'''Optional security precaution:'''

By default {{Pkg|wpa_supplicant}} will store your Wi-Fi password in plain text:{{Cat|/etc/wpa_supplicant/wpa_supplicant.conf|<nowiki>network={
ssid="<YourSSIDShouldBeHere>"
#psk="<YourPasswordShouldBeHereInPlainText>"
psk=<RandomLettersAndNumbersShouldBeHere>
}</nowiki>}}
If you don't want your password stored in plain text, delete the line with <code>#psk="<YourPasswordShouldBeHereInPlainText>"</code> on it.

If all is well, run it as a daemon in the background by setting the {{Path|-B}} option. {{Cmd|# wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf}}

Configure the interface with an IP address.{{Cmd|# udhcpc -i wlan0}}

Sanity check: the interface should have a {{Path|inet}} address. {{Cmd|$ ip addr show wlan0}}

Add a entry for the desired interface (e.g. <code>wlan0</code>) in the file as follows:{{Cat|/etc/network/interfaces|auto lo
auto wlan0
iface wlan0 inet dhcp}}

{{Warning|Don't remove or comment out the '''auto lo''' entry}}

Sanity check: Make sure {{Path|/etc/wpa_supplicant/wpa_supplicant.conf}} is the correct configuration for the wireless access point you want to connect to.

Bring the interface down. {{Cmd|# ip link set wlan0 down}}

Manually restart (or '''start''') '''networking'''.{{Cmd|# rc-service networking --quiet restart &}}

Perform [[Configure_Networking#Connectivity_testing|sanity checks]]. For issues related to name resolution, refer [[Configure_Networking#Configuring_DNS|Networking]] section.

=== Service configuration ===
{{Seealso|NetworkManager}}

Proceed to configure wpa_supplicant service to start automatically on boot, if networking works properly: {{Cmd|# rc-update add wpa_supplicant boot}}
Also ensure that '''networking''' is set to automatically start on boot: {{Cmd|# rc-update add networking boot}}

Manage wpa_supplicant service using the standard '''start''', '''stop''' and '''restart''' options. For eg: to start wpa_supplicant service: {{Cmd|# rc-service wpa_supplicant start}}

=== Launching udhcpc through wpa_cli actions ===

With the above configuration, udhcpc will only run once at boot. If the Wifi isn't available then, or the network changes after booting, udhcpc needs to be notified. You can automatically notify udhcpc of network changes by using a wpa_cli action file, such as the one installed by default at {{Path|/etc/wpa_supplicant/wpa_cli.sh}}.

To manually start a wpa_cli daemon with an action file, use the `-a` option: {{Cmd|# wpa_cli -a /etc/wpa_supplicant/wpa_cli.sh}}

To do this automatically, use the `wpa_cli` service included in {{Pkg|wpa_supplicant-openrc}}: {{Cat|/etc/conf.d/wpa_cli|<nowiki>WPACLI_OPTS="-a /etc/wpa_supplicant/wpa_cli.sh"</nowiki>}}
Add the service to start at boot: {{Cmd|# rc-update add wpa_cli boot}}

== Device driver ==

Wireless networking devices require device drivers and some chipsets also require firmware, in addition to a corresponding driver. In most cases the packaged [[Kernels#Firmware|firmware]] should get you the required drivers. The following section provides more information for various chipsets like [[#Broadcom_Wi-Fi_Chipset_Users|'''Broadcom''']] and some of these out-of-tree kernel drivers use [[Alpine kernel module support]].

=== Intel wireless devices ===

Intel wireless users seeking a minimal set of firmware packages need to ensure that the following firmware packages are installed: the {{Pkg|linux-firmware-none}} meta package and {{Pkg|linux-firmware-other}}. Additionally, the {{ic|iwlwifi}} command is provided by a further package beginning from Alpine Linux v3.23 and Edge: such installations will [https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/65712 also require] {{Pkg|linux-firmware-intel}}, which now supplies {{Path|iwlwifi*.ucode.zst}}. Earlier supported versions of Alpine Linux had the {{ic|iwlwifi}} command bundled in {{Pkg|linux-firmware-other}}.{{Pill||text=v3.23.x}}

=== Broadcom Wi-Fi Chipset ===

The Broadcom chipset is quite popular among older computers. The b43 driver is included in the default kernel packages. However, you might need to compile the firmware manually for this chipset as it is not included in {{pkg|linux-firmware}} for some cards. To check what broadcom chip you have using lspci: {{Cmd|$ lspci -nn -d 14e4:}}

Check what driver you need on the [https://wireless.docs.kernel.org/en/latest/en/users/drivers/b43.html#list-of-hardware b43 compatibility page].

====B43====

Download firmware cutter. {{Cmd|$ apk add b43-fwcutter}}

Now we have everything to download the proprietary driver and extract the firmware from it: {{Cmd|<nowiki># export FIRMWARE_INSTALL_DIR="/lib/firmware"
$ wget https://mirror2.openwrt.org/sources/broadcom-wl-5.100.138.tar.bz2
$ tar xjf broadcom-wl-5.100.138.tar.bz2
$ b43-fwcutter -w "$FIRMWARE_INSTALL_DIR" broadcom-wl-5.100.138/linux/wl_apsta.o</nowiki>}}

More information can be found [https://linuxwireless.sipsolutions.net/en/users/Drivers/b43/#Other_distributions_not_mentioned_above here].

Now you need to use modprobe so the device will show up: {{Cmd|# modprobe b43}}

Reboot and you have a working b43 driver. Now continue with the normal instructions.

==== wl ====

For '''wl''' chipset, you can download the APKBUILD from [https://codeberg.org/NeYurii/broadcom-wl here]. The site has necessary instructions and the it uses [[Alpine kernel module support]] for automatic building and updating driver for new kernel versions.

Commonly when building the APK with these instructions, you will get a "Permission denied" error for a specific line in the APKBUILD.

To fix this, edit the APKBUILD by changing the line: {{Cmd|ln -s /sys/kernel/btf/vmlinux /usr/src/linux-headers-"$(uname -r)"/}}

to: {{Cmd|doas ln -s /sys/kernel/btf/vmlinux /usr/src/linux-headers-"$(uname -r)"/}}

After that, it should build with no problems.

Alternately, install the software to build a driver: {{Cmd|apk add git alpine-sdk linux-headers linux-lts-dev}}

Then install the driver build repo (this is archived, however it's legacy so that doesn't matter): {{Cmd|git clone https://github.com/antoineco/broadcom-wl
cd broadcom-wl
}}

Then follow the build instructions listed in the git repo: {{Cmd|make
doas make install
doas depmod -A
doas modprobe wl
}}

Reboot and you have a working wl driver. Now continue with the normal instructions.

=== Realtek wireless devices ===

A number of out-of-tree kernel drivers for '''Realtek chipset''' are packaged and found here '''{{pkg|rtl*src*}}'''. These drivers can be installed using [[Alpine kernel module support]].

== Troubleshooting ==

In most cases the packaged [[Kernels#Firmware|firmware]] should get you the required drivers. To list your available network interfaces use the commands: {{Cmd|$ ip link}} or {{Cmd|$ ip a}}

If the above command shows {{Path|wlan0}} interface, proceed to bring it up using the command: {{Codeline|# ip link set wlan0 up}}. '''If no network interface is displayed, you probably need to load and/or install a [[#Device driver|device driver]]'''.

=== checking network cards ===

{{Cmd|$ cat /proc/net/dev }} lists the network interfaces that are detected. If the expected interfaces are not available, check what network hardware chip you have using builtin {{ic|lsusb}} command. If the output lacks sufficient information, install additional packages referred in [[How to get regular stuff working#Hardware_Management| hardware management]] to use below commands:
{{Cmd|$ lspci -nn }}
{{Cmd|$ lsusb}}

Check what [[#Device driver|device driver]] the card uses and modprobe it. Check that the card is in master mode.

=== Check dmesg ===

Run dmesg and check for errors related to the wireless interface. Usually, dmesg gives maximum information related to network and all other hardware.
{{Cmd|# dmesg}}

=== Rfkill ===

An error message <code>ioctl 0x8914 failed: No error information</code>, is the <code>busybox ip</code>'s way of saying your wireless radio is rfkilled, which means the wireless card is blocked by kernel. This can be changed using rfkill. To show the current status of your Wi-Fi:
~'''$''' rfkill list
0: phy0: wlan
Soft blocked: no
Hard blocked: no


If the card is hard-blocked, use the hardware button or switch to unblock it. If the card is not hard-blocked but soft-blocked, use the following command: {{Cmd|# rfkill unblock wifi}}

== See also ==

* [[Configure_Networking| Networking in Alpine Linux]]
* [[Iwd|iwd]] - An alternate to wpa_supplicant
* [[NetworkManager]] - Front-end to Networking
* [https://wiki.postmarketos.org/wiki/WiFi PostmarketOS Wiki]
* [https://wiki.archlinux.org/title/Network_configuration/Wireless Archwiki]
* [https://wiki.gentoo.org/wiki/Wi-Fi Gentoo Wiki]
* [[Alpine kernel module support]] - A fully automated solution for building kernel modules
* [https://unix.stackexchange.com/questions/606073/how-to-build-kernel-modules-in-alpine-3-12 Build kernel modules manually]

[[Category:Networking]]

How to get regular stuff working

2026-04-12T02:05:45Z

Apropos: /* Search utilities */ clean up wording and mention ripgrep. deciding not to mention fd (find alternative) as ripgrep is much more widely used

Alpine Linux is built around [[Musl| musl libc]] and [[BusyBox]] and software packages are thinned out and split into [[#Subpackages and missing functionality|subpackages]]. This makes it small and very resource efficient. The [[BusyBox#BusyBox applets|utilities in BusyBox]] tend to only implement standard options and lack GNU-specific extensions. This page explains how to get the utilities typically found in GNU/Linux distributions.

Many utilities on this page are provided either by a package containing multiple collected utilities, or through a meta package. The [[Alpine Package Keeper|apk info]] command and its various flags (<code>--provides</code>, <code>--depends</code>, <code>--who-owns</code>, etc) is useful for determining exactly what is provided by what.

== Core utilities ==
{{Main|GNU core utilities}}

Most of the basic file, shell and text manipulation utilities commonly grouped under [https://en.wikipedia.org/wiki/List_of_GNU_Core_Utilities_commands Core Utilities] are provided by [[BusyBox]]. To replace it with GNU {{pkg|coreutils}} package:{{Cmd|# apk add {{pkg|coreutils}}}}

== Linux utilities ==

A set of approximately 100 basic Linux system utilities not included in GNU Core Utilities, such as <code>mount</code>, <code>cfdisk</code>, <code>more</code>, <code>lsblk</code> and <code>kill</code> are maintained under [https://en.wikipedia.org/wiki/Util-linux util-linux]. The {{pkg|util-linux}} package is split into multiple subpackages, so it is possible to install only some of them individually. To have the complete {{pkg|util-linux}} package:{{Cmd|# apk add {{pkg|util-linux}}}}

The full featured file pager utility <code>less</code> can be installed from the {{pkg|less}} package.

== Search utilities ==

The standard search tools <code>find</code> and <code>xargs</code> are provided by the {{pkg|findutils}} package:{{Cmd|# apk add {{pkg|findutils}}}}

GNU Grep is available as the {{pkg|grep}} package. The {{pkg|ripgrep}} package is also available and provides <code>rg</code>.

== Shell management ==
{{Main|Shell management}}
The default shell used by Alpine Linux is the Busybox variant of the [[Shell_management#Ash_shell|ash shell]]. This is a POSIX compliant shell. All popular shells are available in Alpine Linux and the [[Shell_management#Change_default_shell|default shell can be changed]], if desired.

== Hardware management ==

Install {{pkg|pciutils}} and {{pkg|usbutils}} for identifying and configuring PCI and USB hardware using the full featured version of <code>lspci</code> and <code>lsusb</code> commands respectively. {{Cmd|# apk add {{pkg|pciutils}} {{pkg|usbutils}}}}

The packages {{pkg|hwdata-pci}} and {{pkg|hwdata-usb}} are dependencies for the above utilities and they are installed automatically. These packages can be removed once the hardware configuration has been completed.

== Disk management ==
{{Main|File management}}
Managing disks including removable disks is much easier with udisks.{{Cmd|# apk add {{pkg|udisks2}}}} To see the mounted disks:{{Cmd|# udisksctl status}}

== Network management ==
{{Main|Configure Networking}}
For network, you may want to install {{pkg|iproute2}}. {{Cmd|# apk add {{pkg|iproute2}}}}

== Locale and key management ==
* [[Locale|Locales]], including keyboards, languages and date and time formats are typically configured with the [[Alpine_configuration_management_scripts#setup-alpine|setup-alpine]] and like scripts, and within desktop environment settings.

* Consult the [[Compose_key|Compose Key]] wikipage to create foreign currency symbols, accents and diacritics, endashes (–) and emdashes (—), etc.

== Subpackages and missing functionality ==

When a package is installed in Alpine Linux, no assumption is made as to what features the user wants, so [[Alpine_Package_Keeper#Subpackages|subpackages]] are not installed by default. As such, the user might get a false impression of missing functionality.

For example, the {{pkg|networkmanager}} package for [[NetworkManager]] has 20+ subpackages based on features. If the user installs the {{pkg|networkmanager}} package, ''only'' the NetworkManager utility will get installed. To manage Wi-Fi networks, use commands like <code>nmcli</code> and <code>nmtui</code>, or launch the GTK applet, the user is expected to add the required subpackages {{pkg|networkmanager-wifi}}, {{pkg|networkmanager-cli}}, {{pkg|networkmanager-tui}}, and {{pkg|network-manager-applet}} respectively.

This is in contrast to many other Linux distributions, where when NetworkManager is installed all the above functionality plus that of {{pkg|networkmanager-bluetooth}}, {{pkg|networkmanager-adsl}}, {{pkg|networkmanager-wwan}}, {{pkg|networkmanager-openvpn}}, {{pkg|networkmanager-l2tp}}, {{pkg|networkmanager-ppp}}, and the like are automatically installed, along with their dependencies.

== Development environment ==
{{Main|Developer Documentation}}
Compiling in Alpine Linux may be more challenging because it uses [[Musl|musl instead of glibc]]. The {{pkg|build-base}} meta package provides regular compiler stuff such as {{pkg|binutils}}, {{pkg|gcc}}, {{pkg|g++}}, {{pkg|make}} etc..

{{Cmd|# apk add {{pkg|build-base}}}}

The {{pkg|alpine-sdk}} meta package is provided to build packages for Alpine Linux. It includes {{pkg|abuild}}, {{pkg|build-base}}, and {{pkg|git}}.

{{Cmd|# apk add {{pkg|alpine-sdk}}}}

To install CMake:

{{Cmd|# apk add {{pkg|cmake}} {{pkg|extra-cmake-modules}}}}

{{pkg|ccache}} and a lot other tools are also available in Alpine Linux.

[[Category:Installation]]
[[category: System Administration]]

How to get regular stuff working

2026-04-12T00:28:11Z

Apropos: Note the usefulness of apk info when dealing with utilities packages / meta packages

Alpine Linux is built around [[Musl| musl libc]] and [[BusyBox]] and software packages are thinned out and split into [[#Subpackages and missing functionality|subpackages]]. This makes it small and very resource efficient. The [[BusyBox#BusyBox applets|utilities in BusyBox]] tend to only implement standard options and lack GNU-specific extensions. This page explains how to get the utilities typically found in GNU/Linux distributions.

Many utilities on this page are provided either by a package containing multiple collected utilities, or through a meta package. The [[Alpine Package Keeper|apk info]] command and its various flags (<code>--provides</code>, <code>--depends</code>, <code>--who-owns</code>, etc) is useful for determining exactly what is provided by what.

== Core utilities ==
{{Main|GNU core utilities}}

Most of the basic file, shell and text manipulation utilities commonly grouped under [https://en.wikipedia.org/wiki/List_of_GNU_Core_Utilities_commands Core Utilities] are provided by [[BusyBox]]. To replace it with GNU {{pkg|coreutils}} package:{{Cmd|# apk add {{pkg|coreutils}}}}

== Linux utilities ==

A set of approximately 100 basic Linux system utilities not included in GNU Core Utilities, such as <code>mount</code>, <code>cfdisk</code>, <code>more</code>, <code>lsblk</code> and <code>kill</code> are maintained under [https://en.wikipedia.org/wiki/Util-linux util-linux]. The {{pkg|util-linux}} package is split into multiple subpackages, so it is possible to install only some of them individually. To have the complete {{pkg|util-linux}} package:{{Cmd|# apk add {{pkg|util-linux}}}}

The full featured file pager utility <code>less</code> can be installed from the {{pkg|less}} package.

== Search utilities ==

Standard search tools <code>xargs</code> and <code>find</code> can be installed by via the {{pkg|findutils}} package as follows:{{Cmd|# apk add {{pkg|findutils}} }}

GNU Grep is also available as the {{pkg|grep}} package.

== Shell management ==
{{Main|Shell management}}
The default shell used by Alpine Linux is the Busybox variant of the [[Shell_management#Ash_shell|ash shell]]. This is a POSIX compliant shell. All popular shells are available in Alpine Linux and the [[Shell_management#Change_default_shell|default shell can be changed]], if desired.

== Hardware management ==

Install {{pkg|pciutils}} and {{pkg|usbutils}} for identifying and configuring PCI and USB hardware using the full featured version of <code>lspci</code> and <code>lsusb</code> commands respectively. {{Cmd|# apk add {{pkg|pciutils}} {{pkg|usbutils}}}}

The packages {{pkg|hwdata-pci}} and {{pkg|hwdata-usb}} are dependencies for the above utilities and they are installed automatically. These packages can be removed once the hardware configuration has been completed.

== Disk management ==
{{Main|File management}}
Managing disks including removable disks is much easier with udisks.{{Cmd|# apk add {{pkg|udisks2}}}} To see the mounted disks:{{Cmd|# udisksctl status}}

== Network management ==
{{Main|Configure Networking}}
For network, you may want to install {{pkg|iproute2}}. {{Cmd|# apk add {{pkg|iproute2}}}}

== Locale and key management ==
* [[Locale|Locales]], including keyboards, languages and date and time formats are typically configured with the [[Alpine_configuration_management_scripts#setup-alpine|setup-alpine]] and like scripts, and within desktop environment settings.

* Consult the [[Compose_key|Compose Key]] wikipage to create foreign currency symbols, accents and diacritics, endashes (–) and emdashes (—), etc.

== Subpackages and missing functionality ==

When a package is installed in Alpine Linux, no assumption is made as to what features the user wants, so [[Alpine_Package_Keeper#Subpackages|subpackages]] are not installed by default. As such, the user might get a false impression of missing functionality.

For example, the {{pkg|networkmanager}} package for [[NetworkManager]] has 20+ subpackages based on features. If the user installs the {{pkg|networkmanager}} package, ''only'' the NetworkManager utility will get installed. To manage Wi-Fi networks, use commands like <code>nmcli</code> and <code>nmtui</code>, or launch the GTK applet, the user is expected to add the required subpackages {{pkg|networkmanager-wifi}}, {{pkg|networkmanager-cli}}, {{pkg|networkmanager-tui}}, and {{pkg|network-manager-applet}} respectively.

This is in contrast to many other Linux distributions, where when NetworkManager is installed all the above functionality plus that of {{pkg|networkmanager-bluetooth}}, {{pkg|networkmanager-adsl}}, {{pkg|networkmanager-wwan}}, {{pkg|networkmanager-openvpn}}, {{pkg|networkmanager-l2tp}}, {{pkg|networkmanager-ppp}}, and the like are automatically installed, along with their dependencies.

== Development environment ==
{{Main|Developer Documentation}}
Compiling in Alpine Linux may be more challenging because it uses [[Musl|musl instead of glibc]]. The {{pkg|build-base}} meta package provides regular compiler stuff such as {{pkg|binutils}}, {{pkg|gcc}}, {{pkg|g++}}, {{pkg|make}} etc..

{{Cmd|# apk add {{pkg|build-base}}}}

The {{pkg|alpine-sdk}} meta package is provided to build packages for Alpine Linux. It includes {{pkg|abuild}}, {{pkg|build-base}}, and {{pkg|git}}.

{{Cmd|# apk add {{pkg|alpine-sdk}}}}

To install CMake:

{{Cmd|# apk add {{pkg|cmake}} {{pkg|extra-cmake-modules}}}}

{{pkg|ccache}} and a lot other tools are also available in Alpine Linux.

[[Category:Installation]]
[[category: System Administration]]

How to get regular stuff working

2026-04-11T23:55:56Z

Apropos: Rename "Util-linux" section to "Linux utilities"

Alpine Linux is built around [[Musl| musl libc]] and [[BusyBox]] and software packages are thinned out and split into [[#Subpackages and missing functionality|subpackages]]. This makes it small and very resource efficient. The [[BusyBox#BusyBox applets|utilities in BusyBox]] tend to only implement standard options and lack GNU-specific extensions. This page explains how to get the utilities typically found in GNU/Linux distributions.

== Core utilities ==
{{Main|GNU core utilities}}

Most of the basic file, shell and text manipulation utilities commonly grouped under [https://en.wikipedia.org/wiki/List_of_GNU_Core_Utilities_commands Core Utilities] are provided by [[BusyBox]]. To replace it with GNU {{pkg|coreutils}} package:{{Cmd|# apk add {{pkg|coreutils}}}}

== Linux utilities ==

A set of approximately 100 basic Linux system utilities not included in GNU Core Utilities, such as <code>mount</code>, <code>cfdisk</code>, <code>more</code>, <code>lsblk</code> and <code>kill</code> are maintained under [https://en.wikipedia.org/wiki/Util-linux util-linux]. The {{pkg|util-linux}} package is split into multiple subpackages, so it is possible to install only some of them individually. To have the complete {{pkg|util-linux}} package:{{Cmd|# apk add {{pkg|util-linux}}}}

The full featured file pager utility <code>less</code> can be installed from the {{pkg|less}} package.

== Search utilities ==

Standard search tools <code>xargs</code> and <code>find</code> can be installed by via the {{pkg|findutils}} package as follows:{{Cmd|# apk add {{pkg|findutils}} }}

GNU Grep is also available as the {{pkg|grep}} package.

== Shell management ==
{{Main|Shell management}}
The default shell used by Alpine Linux is the Busybox variant of the [[Shell_management#Ash_shell|ash shell]]. This is a POSIX compliant shell. All popular shells are available in Alpine Linux and the [[Shell_management#Change_default_shell|default shell can be changed]], if desired.

== Hardware management ==

Install {{pkg|pciutils}} and {{pkg|usbutils}} for identifying and configuring PCI and USB hardware using the full featured version of <code>lspci</code> and <code>lsusb</code> commands respectively. {{Cmd|# apk add {{pkg|pciutils}} {{pkg|usbutils}}}}

The packages {{pkg|hwdata-pci}} and {{pkg|hwdata-usb}} are dependencies for the above utilities and they are installed automatically. These packages can be removed once the hardware configuration has been completed.

== Disk management ==
{{Main|File management}}
Managing disks including removable disks is much easier with udisks.{{Cmd|# apk add {{pkg|udisks2}}}} To see the mounted disks:{{Cmd|# udisksctl status}}

== Network management ==
{{Main|Configure Networking}}
For network, you may want to install {{pkg|iproute2}}. {{Cmd|# apk add {{pkg|iproute2}}}}

== Locale and key management ==
* [[Locale|Locales]], including keyboards, languages and date and time formats are typically configured with the [[Alpine_configuration_management_scripts#setup-alpine|setup-alpine]] and like scripts, and within desktop environment settings.

* Consult the [[Compose_key|Compose Key]] wikipage to create foreign currency symbols, accents and diacritics, endashes (–) and emdashes (—), etc.

== Subpackages and missing functionality ==

When a package is installed in Alpine Linux, no assumption is made as to what features the user wants, so [[Alpine_Package_Keeper#Subpackages|subpackages]] are not installed by default. As such, the user might get a false impression of missing functionality.

For example, the {{pkg|networkmanager}} package for [[NetworkManager]] has 20+ subpackages based on features. If the user installs the {{pkg|networkmanager}} package, ''only'' the NetworkManager utility will get installed. To manage Wi-Fi networks, use commands like <code>nmcli</code> and <code>nmtui</code>, or launch the GTK applet, the user is expected to add the required subpackages {{pkg|networkmanager-wifi}}, {{pkg|networkmanager-cli}}, {{pkg|networkmanager-tui}}, and {{pkg|network-manager-applet}} respectively.

This is in contrast to many other Linux distributions, where when NetworkManager is installed all the above functionality plus that of {{pkg|networkmanager-bluetooth}}, {{pkg|networkmanager-adsl}}, {{pkg|networkmanager-wwan}}, {{pkg|networkmanager-openvpn}}, {{pkg|networkmanager-l2tp}}, {{pkg|networkmanager-ppp}}, and the like are automatically installed, along with their dependencies.

== Development environment ==
{{Main|Developer Documentation}}
Compiling in Alpine Linux may be more challenging because it uses [[Musl|musl instead of glibc]]. The {{pkg|build-base}} meta package provides regular compiler stuff such as {{pkg|binutils}}, {{pkg|gcc}}, {{pkg|g++}}, {{pkg|make}} etc..

{{Cmd|# apk add {{pkg|build-base}}}}

The {{pkg|alpine-sdk}} meta package is provided to build packages for Alpine Linux. It includes {{pkg|abuild}}, {{pkg|build-base}}, and {{pkg|git}}.

{{Cmd|# apk add {{pkg|alpine-sdk}}}}

To install CMake:

{{Cmd|# apk add {{pkg|cmake}} {{pkg|extra-cmake-modules}}}}

{{pkg|ccache}} and a lot other tools are also available in Alpine Linux.

[[Category:Installation]]
[[category: System Administration]]

How to get regular stuff working

2026-04-11T23:54:35Z

Apropos: Rewrite prose in Subpackages and missing functionality

Alpine Linux is built around [[Musl| musl libc]] and [[BusyBox]] and software packages are thinned out and split into [[#Subpackages and missing functionality|subpackages]]. This makes it small and very resource efficient. The [[BusyBox#BusyBox applets|utilities in BusyBox]] tend to only implement standard options and lack GNU-specific extensions. This page explains how to get the utilities typically found in GNU/Linux distributions.

== Core utilities ==
{{Main|GNU core utilities}}

Most of the basic file, shell and text manipulation utilities commonly grouped under [https://en.wikipedia.org/wiki/List_of_GNU_Core_Utilities_commands Core Utilities] are provided by [[BusyBox]]. To replace it with GNU {{pkg|coreutils}} package:{{Cmd|# apk add {{pkg|coreutils}}}}

== Util-linux ==

A set of approximately 100 basic Linux system utilities not included in GNU Core Utilities, such as <code>mount</code>, <code>cfdisk</code>, <code>more</code>, <code>lsblk</code> and <code>kill</code> are maintained under [https://en.wikipedia.org/wiki/Util-linux Util-linux]. The {{pkg|util-linux}} package is split into multiple subpackages, so it is possible to install only some of them individually. To have the complete {{pkg|util-linux}} package:{{Cmd|# apk add {{pkg|util-linux}}}}

The full featured file pager utility <code>less</code> can be installed from the {{pkg|less}} package.

== Search utilities ==

Standard search tools <code>xargs</code> and <code>find</code> can be installed by via the {{pkg|findutils}} package as follows:{{Cmd|# apk add {{pkg|findutils}} }}

GNU Grep is also available as the {{pkg|grep}} package.

== Shell management ==
{{Main|Shell management}}
The default shell used by Alpine Linux is the Busybox variant of the [[Shell_management#Ash_shell|ash shell]]. This is a POSIX compliant shell. All popular shells are available in Alpine Linux and the [[Shell_management#Change_default_shell|default shell can be changed]], if desired.

== Hardware management ==

Install {{pkg|pciutils}} and {{pkg|usbutils}} for identifying and configuring PCI and USB hardware using the full featured version of <code>lspci</code> and <code>lsusb</code> commands respectively. {{Cmd|# apk add {{pkg|pciutils}} {{pkg|usbutils}}}}

The packages {{pkg|hwdata-pci}} and {{pkg|hwdata-usb}} are dependencies for the above utilities and they are installed automatically. These packages can be removed once the hardware configuration has been completed.

== Disk management ==
{{Main|File management}}
Managing disks including removable disks is much easier with udisks.{{Cmd|# apk add {{pkg|udisks2}}}} To see the mounted disks:{{Cmd|# udisksctl status}}

== Network management ==
{{Main|Configure Networking}}
For network, you may want to install {{pkg|iproute2}}. {{Cmd|# apk add {{pkg|iproute2}}}}

== Locale and key management ==
* [[Locale|Locales]], including keyboards, languages and date and time formats are typically configured with the [[Alpine_configuration_management_scripts#setup-alpine|setup-alpine]] and like scripts, and within desktop environment settings.

* Consult the [[Compose_key|Compose Key]] wikipage to create foreign currency symbols, accents and diacritics, endashes (–) and emdashes (—), etc.

== Subpackages and missing functionality ==

When a package is installed in Alpine Linux, no assumption is made as to what features the user wants, so [[Alpine_Package_Keeper#Subpackages|subpackages]] are not installed by default. As such, the user might get a false impression of missing functionality.

For example, the {{pkg|networkmanager}} package for [[NetworkManager]] has 20+ subpackages based on features. If the user installs the {{pkg|networkmanager}} package, ''only'' the NetworkManager utility will get installed. To manage Wi-Fi networks, use commands like <code>nmcli</code> and <code>nmtui</code>, or launch the GTK applet, the user is expected to add the required subpackages {{pkg|networkmanager-wifi}}, {{pkg|networkmanager-cli}}, {{pkg|networkmanager-tui}}, and {{pkg|network-manager-applet}} respectively.

This is in contrast to many other Linux distributions, where when NetworkManager is installed all the above functionality plus that of {{pkg|networkmanager-bluetooth}}, {{pkg|networkmanager-adsl}}, {{pkg|networkmanager-wwan}}, {{pkg|networkmanager-openvpn}}, {{pkg|networkmanager-l2tp}}, {{pkg|networkmanager-ppp}}, and the like are automatically installed, along with their dependencies.

== Development environment ==
{{Main|Developer Documentation}}
Compiling in Alpine Linux may be more challenging because it uses [[Musl|musl instead of glibc]]. The {{pkg|build-base}} meta package provides regular compiler stuff such as {{pkg|binutils}}, {{pkg|gcc}}, {{pkg|g++}}, {{pkg|make}} etc..

{{Cmd|# apk add {{pkg|build-base}}}}

The {{pkg|alpine-sdk}} meta package is provided to build packages for Alpine Linux. It includes {{pkg|abuild}}, {{pkg|build-base}}, and {{pkg|git}}.

{{Cmd|# apk add {{pkg|alpine-sdk}}}}

To install CMake:

{{Cmd|# apk add {{pkg|cmake}} {{pkg|extra-cmake-modules}}}}

{{pkg|ccache}} and a lot other tools are also available in Alpine Linux.

[[Category:Installation]]
[[category: System Administration]]

How to get regular stuff working

2026-04-11T22:32:21Z

Apropos: tweak appearance of link to musl libc page

Alpine Linux is built around [[Musl| musl libc]] and [[BusyBox]] and software packages are thinned out and split into [[#Subpackages and missing functionality|subpackages]]. This makes it small and very resource efficient. The [[BusyBox#BusyBox applets|utilities in BusyBox]] tend to only implement standard options and lack GNU-specific extensions. This page explains how to get the utilities typically found in GNU/Linux distributions.

== Core utilities ==
{{Main|GNU core utilities}}

Most of the basic file, shell and text manipulation utilities commonly grouped under [https://en.wikipedia.org/wiki/List_of_GNU_Core_Utilities_commands Core Utilities] are provided by [[BusyBox]]. To replace it with GNU {{pkg|coreutils}} package:{{Cmd|# apk add {{pkg|coreutils}}}}

== Util-linux ==

A set of approximately 100 basic Linux system utilities not included in GNU Core Utilities, such as <code>mount</code>, <code>cfdisk</code>, <code>more</code>, <code>lsblk</code> and <code>kill</code> are maintained under [https://en.wikipedia.org/wiki/Util-linux Util-linux]. The {{pkg|util-linux}} package is split into multiple subpackages, so it is possible to install only some of them individually. To have the complete {{pkg|util-linux}} package:{{Cmd|# apk add {{pkg|util-linux}}}}

The full featured file pager utility <code>less</code> can be installed from the {{pkg|less}} package.

== Search utilities ==

Standard search tools <code>xargs</code> and <code>find</code> can be installed by via the {{pkg|findutils}} package as follows:{{Cmd|# apk add {{pkg|findutils}} }}

GNU Grep is also available as the {{pkg|grep}} package.

== Shell management ==
{{Main|Shell management}}
The default shell used by Alpine Linux is the Busybox variant of the [[Shell_management#Ash_shell|ash shell]]. This is a POSIX compliant shell. All popular shells are available in Alpine Linux and the [[Shell_management#Change_default_shell|default shell can be changed]], if desired.

== Hardware management ==

Install {{pkg|pciutils}} and {{pkg|usbutils}} for identifying and configuring PCI and USB hardware using the full featured version of <code>lspci</code> and <code>lsusb</code> commands respectively. {{Cmd|# apk add {{pkg|pciutils}} {{pkg|usbutils}}}}

The packages {{pkg|hwdata-pci}} and {{pkg|hwdata-usb}} are dependencies for the above utilities and they are installed automatically. These packages can be removed once the hardware configuration has been completed.

== Disk management ==
{{Main|File management}}
Managing disks including removable disks is much easier with udisks.{{Cmd|# apk add {{pkg|udisks2}}}} To see the mounted disks:{{Cmd|# udisksctl status}}

== Network management ==
{{Main|Configure Networking}}
For network, you may want to install {{pkg|iproute2}}. {{Cmd|# apk add {{pkg|iproute2}}}}

== Locale and key management ==
* [[Locale|Locales]], including keyboards, languages and date and time formats are typically configured with the [[Alpine_configuration_management_scripts#setup-alpine|setup-alpine]] and like scripts, and within desktop environment settings.

* Consult the [[Compose_key|Compose Key]] wikipage to create foreign currency symbols, accents and diacritics, endashes (–) and emdashes (—), etc.

== Subpackages and missing functionality ==

When a package is installed in Alpine Linux, no assumption is made on what features the user wants, so [[Alpine_Package_Keeper#Subpackages|subpackages]] are not installed by default. The user might get a false impression of missing functionality.

For eg: The {{pkg|networkmanager}} package for [[NetworkManager]], the standard network configuration tool has 20+ subpackages based on features. If the user installs {{pkg|networkmanager}} package or {{pkg|network-manager-applet}} only the NetworkManager utility and the applet will get installed. To manage Wifi networks or to use commands like <Code>nmcli</Code> and <Code>nmtui</Code> the user is expected to add the required subpackages {{pkg|networkmanager-wifi}}, {{pkg|networkmanager-cli}} and {{pkg|networkmanager-tui}} respectively.

In other Linux distributions when NetworkManager is installed, all the above features plus bluetooth, adsl, wwan, vpn, l2tp, ppp etc are automatically installed along with their dependencies.

== Development environment ==
{{Main|Developer_Documentation}}
Compiling in Alpine Linux may be more challenging because it uses [[Musl|musl instead of glibc]]. The {{pkg|build-base}} meta package provides regular compiler stuff such as {{pkg|binutils}}, {{pkg|gcc}}, {{pkg|g++}}, {{pkg|make}} etc..

{{Cmd|# apk add {{pkg|build-base}}}}

The {{pkg|alpine-sdk}} meta package is provided to build packages for Alpine Linux. It includes {{pkg|abuild}}, {{pkg|build-base}}, and {{pkg|git}}.

{{Cmd|# apk add {{pkg|alpine-sdk}}}}

To install CMake:

{{Cmd|# apk add {{pkg|cmake}} {{pkg|extra-cmake-modules}}}}

{{pkg|ccache}} and a lot other tools are also available in Alpine Linux.

[[Category:Installation]]
[[category: System Administration]]

How to get regular stuff working

2026-04-11T22:29:54Z

Apropos: /* Development environment */ link to musl wiki page here instead

Alpine Linux is built around [[Musl]] libc and [[BusyBox]] and software packages are thinned out and split into [[#Subpackages and missing functionality|subpackages]]. This makes it small and very resource efficient. The [[BusyBox#BusyBox applets|utilities in BusyBox]] tend to only implement standard options and lack GNU-specific extensions. This page explains how to get the utilities typically found in GNU/Linux distributions.

== Core utilities ==
{{Main|GNU core utilities}}

Most of the basic file, shell and text manipulation utilities commonly grouped under [https://en.wikipedia.org/wiki/List_of_GNU_Core_Utilities_commands Core Utilities] are provided by [[BusyBox]]. To replace it with GNU {{pkg|coreutils}} package:{{Cmd|# apk add {{pkg|coreutils}}}}

== Util-linux ==

A set of approximately 100 basic Linux system utilities not included in GNU Core Utilities, such as <code>mount</code>, <code>cfdisk</code>, <code>more</code>, <code>lsblk</code> and <code>kill</code> are maintained under [https://en.wikipedia.org/wiki/Util-linux Util-linux]. The {{pkg|util-linux}} package is split into multiple subpackages, so it is possible to install only some of them individually. To have the complete {{pkg|util-linux}} package:{{Cmd|# apk add {{pkg|util-linux}}}}

The full featured file pager utility <code>less</code> can be installed from the {{pkg|less}} package.

== Search utilities ==

Standard search tools <code>xargs</code> and <code>find</code> can be installed by via the {{pkg|findutils}} package as follows:{{Cmd|# apk add {{pkg|findutils}} }}

GNU Grep is also available as the {{pkg|grep}} package.

== Shell management ==
{{Main|Shell management}}
The default shell used by Alpine Linux is the Busybox variant of the [[Shell_management#Ash_shell|ash shell]]. This is a POSIX compliant shell. All popular shells are available in Alpine Linux and the [[Shell_management#Change_default_shell|default shell can be changed]], if desired.

== Hardware management ==

Install {{pkg|pciutils}} and {{pkg|usbutils}} for identifying and configuring PCI and USB hardware using the full featured version of <code>lspci</code> and <code>lsusb</code> commands respectively. {{Cmd|# apk add {{pkg|pciutils}} {{pkg|usbutils}}}}

The packages {{pkg|hwdata-pci}} and {{pkg|hwdata-usb}} are dependencies for the above utilities and they are installed automatically. These packages can be removed once the hardware configuration has been completed.

== Disk management ==
{{Main|File management}}
Managing disks including removable disks is much easier with udisks.{{Cmd|# apk add {{pkg|udisks2}}}} To see the mounted disks:{{Cmd|# udisksctl status}}

== Network management ==
{{Main|Configure Networking}}
For network, you may want to install {{pkg|iproute2}}. {{Cmd|# apk add {{pkg|iproute2}}}}

== Locale and key management ==
* [[Locale|Locales]], including keyboards, languages and date and time formats are typically configured with the [[Alpine_configuration_management_scripts#setup-alpine|setup-alpine]] and like scripts, and within desktop environment settings.

* Consult the [[Compose_key|Compose Key]] wikipage to create foreign currency symbols, accents and diacritics, endashes (–) and emdashes (—), etc.

== Subpackages and missing functionality ==

When a package is installed in Alpine Linux, no assumption is made on what features the user wants, so [[Alpine_Package_Keeper#Subpackages|subpackages]] are not installed by default. The user might get a false impression of missing functionality.

For eg: The {{pkg|networkmanager}} package for [[NetworkManager]], the standard network configuration tool has 20+ subpackages based on features. If the user installs {{pkg|networkmanager}} package or {{pkg|network-manager-applet}} only the NetworkManager utility and the applet will get installed. To manage Wifi networks or to use commands like <Code>nmcli</Code> and <Code>nmtui</Code> the user is expected to add the required subpackages {{pkg|networkmanager-wifi}}, {{pkg|networkmanager-cli}} and {{pkg|networkmanager-tui}} respectively.

In other Linux distributions when NetworkManager is installed, all the above features plus bluetooth, adsl, wwan, vpn, l2tp, ppp etc are automatically installed along with their dependencies.

== Development environment ==
{{Main|Developer_Documentation}}
Compiling in Alpine Linux may be more challenging because it uses [[Musl|musl instead of glibc]]. The {{pkg|build-base}} meta package provides regular compiler stuff such as {{pkg|binutils}}, {{pkg|gcc}}, {{pkg|g++}}, {{pkg|make}} etc..

{{Cmd|# apk add {{pkg|build-base}}}}

The {{pkg|alpine-sdk}} meta package is provided to build packages for Alpine Linux. It includes {{pkg|abuild}}, {{pkg|build-base}}, and {{pkg|git}}.

{{Cmd|# apk add {{pkg|alpine-sdk}}}}

To install CMake:

{{Cmd|# apk add {{pkg|cmake}} {{pkg|extra-cmake-modules}}}}

{{pkg|ccache}} and a lot other tools are also available in Alpine Linux.

[[Category:Installation]]
[[category: System Administration]]

How to get regular stuff working

2026-04-11T22:28:37Z

Apropos: /* Development environment */ oops

Alpine Linux is built around [[Musl]] libc and [[BusyBox]] and software packages are thinned out and split into [[#Subpackages and missing functionality|subpackages]]. This makes it small and very resource efficient. The [[BusyBox#BusyBox applets|utilities in BusyBox]] tend to only implement standard options and lack GNU-specific extensions. This page explains how to get the utilities typically found in GNU/Linux distributions.

== Core utilities ==
{{Main|GNU core utilities}}

Most of the basic file, shell and text manipulation utilities commonly grouped under [https://en.wikipedia.org/wiki/List_of_GNU_Core_Utilities_commands Core Utilities] are provided by [[BusyBox]]. To replace it with GNU {{pkg|coreutils}} package:{{Cmd|# apk add {{pkg|coreutils}}}}

== Util-linux ==

A set of approximately 100 basic Linux system utilities not included in GNU Core Utilities, such as <code>mount</code>, <code>cfdisk</code>, <code>more</code>, <code>lsblk</code> and <code>kill</code> are maintained under [https://en.wikipedia.org/wiki/Util-linux Util-linux]. The {{pkg|util-linux}} package is split into multiple subpackages, so it is possible to install only some of them individually. To have the complete {{pkg|util-linux}} package:{{Cmd|# apk add {{pkg|util-linux}}}}

The full featured file pager utility <code>less</code> can be installed from the {{pkg|less}} package.

== Search utilities ==

Standard search tools <code>xargs</code> and <code>find</code> can be installed by via the {{pkg|findutils}} package as follows:{{Cmd|# apk add {{pkg|findutils}} }}

GNU Grep is also available as the {{pkg|grep}} package.

== Shell management ==
{{Main|Shell management}}
The default shell used by Alpine Linux is the Busybox variant of the [[Shell_management#Ash_shell|ash shell]]. This is a POSIX compliant shell. All popular shells are available in Alpine Linux and the [[Shell_management#Change_default_shell|default shell can be changed]], if desired.

== Hardware management ==

Install {{pkg|pciutils}} and {{pkg|usbutils}} for identifying and configuring PCI and USB hardware using the full featured version of <code>lspci</code> and <code>lsusb</code> commands respectively. {{Cmd|# apk add {{pkg|pciutils}} {{pkg|usbutils}}}}

The packages {{pkg|hwdata-pci}} and {{pkg|hwdata-usb}} are dependencies for the above utilities and they are installed automatically. These packages can be removed once the hardware configuration has been completed.

== Disk management ==
{{Main|File management}}
Managing disks including removable disks is much easier with udisks.{{Cmd|# apk add {{pkg|udisks2}}}} To see the mounted disks:{{Cmd|# udisksctl status}}

== Network management ==
{{Main|Configure Networking}}
For network, you may want to install {{pkg|iproute2}}. {{Cmd|# apk add {{pkg|iproute2}}}}

== Locale and key management ==
* [[Locale|Locales]], including keyboards, languages and date and time formats are typically configured with the [[Alpine_configuration_management_scripts#setup-alpine|setup-alpine]] and like scripts, and within desktop environment settings.

* Consult the [[Compose_key|Compose Key]] wikipage to create foreign currency symbols, accents and diacritics, endashes (–) and emdashes (—), etc.

== Subpackages and missing functionality ==

When a package is installed in Alpine Linux, no assumption is made on what features the user wants, so [[Alpine_Package_Keeper#Subpackages|subpackages]] are not installed by default. The user might get a false impression of missing functionality.

For eg: The {{pkg|networkmanager}} package for [[NetworkManager]], the standard network configuration tool has 20+ subpackages based on features. If the user installs {{pkg|networkmanager}} package or {{pkg|network-manager-applet}} only the NetworkManager utility and the applet will get installed. To manage Wifi networks or to use commands like <Code>nmcli</Code> and <Code>nmtui</Code> the user is expected to add the required subpackages {{pkg|networkmanager-wifi}}, {{pkg|networkmanager-cli}} and {{pkg|networkmanager-tui}} respectively.

In other Linux distributions when NetworkManager is installed, all the above features plus bluetooth, adsl, wwan, vpn, l2tp, ppp etc are automatically installed along with their dependencies.

== Development environment ==
{{Main|Developer_Documentation}}
Compiling in Alpine Linux may be more challenging because it uses [https://musl.libc.org/ musl] instead of glibc. The {{pkg|build-base}} meta package provides regular compiler stuff such as {{pkg|binutils}}, {{pkg|gcc}}, {{pkg|g++}}, {{pkg|make}} etc..

{{Cmd|# apk add {{pkg|build-base}}}}

The {{pkg|alpine-sdk}} meta package is provided to build packages for Alpine Linux. It includes {{pkg|abuild}}, {{pkg|build-base}}, and {{pkg|git}}.

{{Cmd|# apk add {{pkg|alpine-sdk}}}}

To install CMake:

{{Cmd|# apk add {{pkg|cmake}} {{pkg|extra-cmake-modules}}}}

{{pkg|ccache}} and a lot other tools are also available in Alpine Linux.

[[Category:Installation]]
[[category: System Administration]]

How to get regular stuff working

2026-04-11T22:27:39Z

Apropos: /* Development environment */ fix link to musl

Alpine Linux is built around [[Musl]] libc and [[BusyBox]] and software packages are thinned out and split into [[#Subpackages and missing functionality|subpackages]]. This makes it small and very resource efficient. The [[BusyBox#BusyBox applets|utilities in BusyBox]] tend to only implement standard options and lack GNU-specific extensions. This page explains how to get the utilities typically found in GNU/Linux distributions.

== Core utilities ==
{{Main|GNU core utilities}}

Most of the basic file, shell and text manipulation utilities commonly grouped under [https://en.wikipedia.org/wiki/List_of_GNU_Core_Utilities_commands Core Utilities] are provided by [[BusyBox]]. To replace it with GNU {{pkg|coreutils}} package:{{Cmd|# apk add {{pkg|coreutils}}}}

== Util-linux ==

A set of approximately 100 basic Linux system utilities not included in GNU Core Utilities, such as <code>mount</code>, <code>cfdisk</code>, <code>more</code>, <code>lsblk</code> and <code>kill</code> are maintained under [https://en.wikipedia.org/wiki/Util-linux Util-linux]. The {{pkg|util-linux}} package is split into multiple subpackages, so it is possible to install only some of them individually. To have the complete {{pkg|util-linux}} package:{{Cmd|# apk add {{pkg|util-linux}}}}

The full featured file pager utility <code>less</code> can be installed from the {{pkg|less}} package.

== Search utilities ==

Standard search tools <code>xargs</code> and <code>find</code> can be installed by via the {{pkg|findutils}} package as follows:{{Cmd|# apk add {{pkg|findutils}} }}

GNU Grep is also available as the {{pkg|grep}} package.

== Shell management ==
{{Main|Shell management}}
The default shell used by Alpine Linux is the Busybox variant of the [[Shell_management#Ash_shell|ash shell]]. This is a POSIX compliant shell. All popular shells are available in Alpine Linux and the [[Shell_management#Change_default_shell|default shell can be changed]], if desired.

== Hardware management ==

Install {{pkg|pciutils}} and {{pkg|usbutils}} for identifying and configuring PCI and USB hardware using the full featured version of <code>lspci</code> and <code>lsusb</code> commands respectively. {{Cmd|# apk add {{pkg|pciutils}} {{pkg|usbutils}}}}

The packages {{pkg|hwdata-pci}} and {{pkg|hwdata-usb}} are dependencies for the above utilities and they are installed automatically. These packages can be removed once the hardware configuration has been completed.

== Disk management ==
{{Main|File management}}
Managing disks including removable disks is much easier with udisks.{{Cmd|# apk add {{pkg|udisks2}}}} To see the mounted disks:{{Cmd|# udisksctl status}}

== Network management ==
{{Main|Configure Networking}}
For network, you may want to install {{pkg|iproute2}}. {{Cmd|# apk add {{pkg|iproute2}}}}

== Locale and key management ==
* [[Locale|Locales]], including keyboards, languages and date and time formats are typically configured with the [[Alpine_configuration_management_scripts#setup-alpine|setup-alpine]] and like scripts, and within desktop environment settings.

* Consult the [[Compose_key|Compose Key]] wikipage to create foreign currency symbols, accents and diacritics, endashes (–) and emdashes (—), etc.

== Subpackages and missing functionality ==

When a package is installed in Alpine Linux, no assumption is made on what features the user wants, so [[Alpine_Package_Keeper#Subpackages|subpackages]] are not installed by default. The user might get a false impression of missing functionality.

For eg: The {{pkg|networkmanager}} package for [[NetworkManager]], the standard network configuration tool has 20+ subpackages based on features. If the user installs {{pkg|networkmanager}} package or {{pkg|network-manager-applet}} only the NetworkManager utility and the applet will get installed. To manage Wifi networks or to use commands like <Code>nmcli</Code> and <Code>nmtui</Code> the user is expected to add the required subpackages {{pkg|networkmanager-wifi}}, {{pkg|networkmanager-cli}} and {{pkg|networkmanager-tui}} respectively.

In other Linux distributions when NetworkManager is installed, all the above features plus bluetooth, adsl, wwan, vpn, l2tp, ppp etc are automatically installed along with their dependencies.

== Development environment ==
{{Main|Developer_Documentation}}
Compiling in Alpine Linux may be more challenging because it uses [https://musl.libc.org/ musl] instead of glibc. The {{pkg|build-base}} meta package provides regular compiler stuff such as {{pkg|binutils}}, {{pkg|gcc}}, {{pkg|g++}}, {{pkg|make}} etc..

{{Cmd|# apk add {{pkg|build-base}}}

The {{pkg|alpine-sdk}} meta package is provided to build packages for Alpine Linux. It includes {{pkg|abuild}}, {{pkg|build-base}}, and {{pkg|git}}.

{{Cmd|# apk add {{pkg|alpine-sdk}}}}

To install CMake:

{{Cmd|# apk add {{pkg|cmake}} {{pkg|extra-cmake-modules}}}}

{{pkg|ccache}} and a lot other tools are also available in Alpine Linux.

[[Category:Installation]]
[[category: System Administration]]

User:Apropos

2026-03-22T23:32:55Z

Apropos: Created page with "Hello, I'm ~apropos on the internet. I've got Alpine Linux running on a little Thinkpad X61 (dual-booting w/ 9front thru Grub atm, and planning on adding FreeBSD once I get around to it). I really like it! I love that Alpine is small enough to understand in most all its entirety. I've made this account here to contribute little fixes and notes and things from my messing around with Alpine."

Hello, I'm ~apropos on the internet. I've got Alpine Linux running on a little Thinkpad X61 (dual-booting w/ 9front thru Grub atm, and planning on adding FreeBSD once I get around to it). I really like it! I love that Alpine is small enough to understand in most all its entirety. I've made this account here to contribute little fixes and notes and things from my messing around with Alpine.

Alpine Package Keeper

2026-03-22T03:22:28Z

Apropos: /* World */ fix relative link

{{TOC right}}
This page documents the Alpine Package Keeper(APK), the package manager in Alpine Linux. Refer to the excellent guide [https://docs.alpinelinux.org/user-handbook/0.1a/Working/apk.html Working with APK] from Alpine Linux documentation project to learn the basics quickly.

[[Software management#Graphical software manager|Graphical software managers]] can be used for certain basic package management tasks like adding/removing and upgrading packages.

Package management in RAM-based installs like [[Installation#Diskless_Mode|Diskless]] mode and [[Data Disk Mode|Data disk]] mode require [[#Package management in Diskless mode|additional step using lbu]].

== apk v3 ==


{{Pill_clickable||v3 only|green|palegreen|right|Release Notes for Alpine 3.23.0#apk-tools_v3}}
With the release of Alpine Linux [[Release Notes for Alpine 3.23.0|v3.23]], the Alpine package manager has transitioned to [https://gitlab.alpinelinux.org/alpine/apk-tools/-/releases/v3.0.0 apk-tools v3], but the index and package formats are still at v2. apk v3 targets backwards compatibility and new features are flagged on the relevant sections of this page as seen on the right side. The diff output of the documentation between V2 and V3 is [[Apk/apkv3 doc diff|available here]] for reference.

== Overview ==

The {{pkg|apk-tools}} provides '''apk''' and it supports the following operations:
{| class="wikitable" align="center" style="width:100%; border:1px #0771a6 solid; background:#f9f9f9; text-align:left; border-collapse:collapse;"
|-
|style="background:black; color:white" colspan=2 align=center |Package installation and removal
|-
|[[#Add a Package|add]] || Add or modify constraints in [[#World|WORLD]] and commit changes
|-
|[[#Remove a Package|del]] || Remove constraints from [[#World|WORLD]] and commit changes
|-
|style="background:black; color:white" colspan=2 align=center |System maintenance
|-
|[[#apk fix|fix ]] || Fix, reinstall or upgrade packages without modifying [[#World|WORLD]]
|-
|[[#Update Package list|update]]|| Update repository indexes
|-
|[[#Upgrade a Running System|upgrade]]|| Install upgrades available from repositories
|-
|[[#Local Cache|cache]] || Manage the local package cache
|-
|style="background:black; color:white" colspan=2 align=center |Querying package information
|-
|[[#apk query|query]] || Query information about packages by various criteria
|-
|[[#Listing installed packages|list]] || List packages matching a pattern or other criteria
|-
|[[#apk dot|dot]] || Render dependencies as [https://graphviz.org/ graphviz] graphs
|-
|[[#apk policy|policy]]|| Show repository policy for packages
|-
|[[#Search for Packages|search]] || Search for packages by name or description
|-
|[[#Information on Packages|info]] || Give detailed information about packages or repositories
|-
|-
|style="background:black; color:white" colspan=2 align=center |Repository and package maintenance
|-
|mkndx || Create repository index (v3) file from packages
|-
|mkpkg || Create package (v3)
|-
|index || Create repository index (v2) file from packages
|-
|fetch || Download packages from repositories to a local directory
|-
|manifest|| Show checksums of package contents
|-
|extract || Extract package file contents
|-
|verify || Verify package integrity and signature
|-
|adbsign || Sign, resign or recompress v3 packages and indexes
|-
|style="background:black; color:white" colspan=2 align=center |Miscellaneous
|-
|[[#apk audit|audit]]|| Audit system for changes
|-
|stats || Show statistics about repositories and installations
|-
|version|| Compare package versions or perform tests on version strings
|-
|adbdump|| Dump v3 files in textual representation
|-
|adbgen || Generate v3 files from text representation
|-
|convdb || Convert v2 installed database to v3 format
|-
|convndx || Convert v2 indexes to v3 format
|-
|}

== Packages and Repositories ==
{{Main|Repositories}}
Official software packages for Alpine Linux have the extension <code>.apk</code>, and are often called "a-packs". Packages in Alpine Linux are organized into [[Repositories|'''repositories''']] and are defined in the {{Path|/etc/apk/repositories}} file. [[Apk spec#Package Format V2|apk v2]] packages are digitally signed tar.gz archives containing programs, configuration files, and dependency metadata.

=== Subpackages ===

In Alpine Linux, software packages are thinned out and split into subpackages to give more control over what features are installed and keeps the installation as small and efficient as possible.

Subpackages related to service files, documentation and shell completions are installed automatically by the package manager using '''auto-install''' rule based on [[APKBUILD_Reference#install_if|install_if]] directive. For example, if {{pkg|zsh}} is already installed, on installing any package with {{pkg|*zsh-completion*}} subpackage, apk automatically installs the associated subpackage. The {{pkg|docs}} meta package for pulling in [[Alpine_Linux:FAQ#Why_don't_I_have_man_pages_or_where_is_the_'man'_command?|all documentation]] works the same way.

Alpine Linux [https://pkgs.alpinelinux.org package database] page shows the list of available subpackages for any package.

== World ==

At {{Path|/etc/apk/world}}, apk maintains the world, that is, a list of constraints the package selection needs to fulfill. World describes the desired system state. {{Path|/etc/apk/world}} is a plaintext file with one constraint using dependency notation per line. Each line has the format: 
<code>[!]NAME{@tag}{[<>~=]version}</code>.

There can be only one line with a given package NAME in the file and except the package NAME, all the other options are optional.

* '''!''' is used for [[#Package masking|masking a specific package]]
* '''@tag''' allows apk to use the [[Repositories#Tagged_repository|tagged repository]] for the named package
* '''[<>~=]version''' are used for [[#Package pinning|package pinning]].

The commands {{ic|apk add foo}} and {{ic|apk del bar}} manipulate the desired state by adding or removing packages <code>foo</code>, <code>bar</code> respectively as a dependency constraint in {{Path|/etc/apk/world}}. If the {{Path|/etc/apk/world}} is edited manually, run the command [[#apk fix|apk fix]] to apply the changes.

{{Warning|When manually editing world file, do not remove the meta package entry '''alpine-base''' or other important entries like '''linux-*''' etc. Doing so may render the system unbootable.}}

Every constraint listed in {{Path|/etc/apk/world}} must be solvable in order for the system to be considered correct, and no transaction may be committed that is incorrect. If apk cannot verify the correctness of the requested change, it will back out adding the constraint before attempting to change what packages are actually installed on the system. Thus apk will never [[#ERROR:_unsatisfiable_constraints|commit]] a change to the system that leaves it unbootable.

{{Warning|The option {{ic|force-broken-world}}, will delete world constraints until a solution without conflicts is found to boot. This does not allow installation of packages with unjustifiable dependencies. Using this will likely result in unexpected removal of some packages.}}

== Update Package list ==

Alpine Linux [[Repositories|'''repositories''']] change as packages are added and upgraded. To get the latest list of available packages, use the ''update'' command. This command downloads the {{Path|APKINDEX.tar.gz}} from each repository and stores it in the local cache, typically {{Path|/var/cache/apk/}}, {{Path|/var/lib/apk/}} or {{Path|/etc/apk/cache/}}. {{Cmd|# apk update}}

Adding the <code>--update-cache</code>, or for short <code>-U</code> switch to another apk command, as in <code>apk --update-cache upgrade</code> or <code>apk -U add ...</code>, the command has the same effect as first running <code>apk update</code> before the other apk command.

It is a good idea to always do an '''update''' right '''before''' doing an '''upgrade or add''' command. That way the command will install the latest available packages from the repositories.

== Add a Package ==

Use '''add''' to install packages from a [[Repositories|'''repository''']]. Any necessary dependencies are also installed. If you have multiple repositories, the '''add''' command installs the newest package. {{Cmd|<nowiki># apk add openssh
# apk add openssh openntp vim </nowiki>}}

Packages from a [[Repositories#Tagged repository|tagged repository]] can be installed by adding tags to them:{{cmd|# apk add wireguard-go@testing}}

A specific package can also be [[#Package pinning|held back or pinned]] at a specific level or version.

=== Add a local Package ===

To install a locally available apk package, for example if this device has no internet access but you can upload apk packages directly to it, use the '''--allow-untrusted''' flag: {{cmd|# apk add --allow-untrusted /path/to/file.apk}}

Note that multiple packages can be given. When installing a local package, all dependencies should also be specified. For example:

{{cmd|# apk add --allow-untrusted /var/tig-2.2-r0.apk /var/git-2.11.1-20.apk}}

When a non-repository package is added, a version constraint is added with the package identity hash in the World file.

{{Note|If {{ic|'''--available'''}} option is used with [[#Upgrade a Running System|apk upgrade]] command, local packages are upgraded or downgraded back to a repository version.}}

== Remove a Package ==

Use '''del''' to remove a package along with dependencies that are no longer needed.{{cmd|<nowiki># apk del openssh
# apk del openssh openntp vim</nowiki>}}

== Upgrade a Running System ==
{{Seealso|Upgrading Alpine Linux to a new release branch}}
To get the latest security upgrades and bugfixes available for all the installed packages from the [[Repositories#Release_Branches|current release branch]] of a running system, always [[#Update Package list| update the packages list]] before issuing the '''upgrade''' command as shown below:{{cmd|<nowiki># apk update
# apk upgrade </nowiki>}}

Or, combining the same into one single command:{{cmd|# apk -U upgrade}}

To upgrade only ''specific'' packages, use the '''upgrade''' command and specify them: {{cmd|<nowiki># apk update
# apk upgrade busybox</nowiki>}}

When upgrading packages, the package manager may create <var>apk-new</var> files to avoid overwriting configuration files. Once the packages are updated, remember to [[#Handling apk-new files|handle such <var>apk-new<var>]] files.

Here is an example, showing the procedure on a system that has [[Repositories#Using testing repository|testing repository tagged]]:
<Pre>
# apk update
fetch <nowiki>https://dl-3.alpinelinux.org/alpine/v3.6/main/x86_64/APKINDEX.tar.gz</nowiki>
fetch <nowiki>https://dl-3.alpinelinux.org/alpine/v3.6/community/x86_64/APKINDEX.tar.gz</nowiki>
fetch <nowiki>https://dl-3.alpinelinux.org/alpine/edge/testing/x86_64/APKINDEX.tar.gz</nowiki>
v3.6.2-191-gf98d79930f <nowiki>[https://dl-3.alpinelinux.org/alpine/v3.6/main]</nowiki>
v3.6.2-190-ga5d68c47df <nowiki>[https://dl-3.alpinelinux.org/alpine/v3.6/community]</nowiki>
v3.6.0-4624-g11f1b9c8ab <nowiki>[https://dl-3.alpinelinux.org/alpine/edge/testing]</nowiki>
OK: 20118 distinct packages available

# apk upgrade
(1/2) Upgrading extra-cmake-modules@testing (5.38.0-r0 -> 5.39.0-r0)
(2/2) Upgrading extra-cmake-modules-doc@testing (5.38.0-r0 -> 5.39.0-r0)
Executing mdocml-apropos-1.14.1-r0.trigger
OK: 2635 MiB in 803 packages
</Pre>

=== Upgrading "diskless" and "data" disk mode installs ===

When upgrading packages, the kernel and firmware packages are '''not''' upgraded. Upgrading them requires [[Diskless Mode#update-kernel script|'''update-kernel''']] script.

=== Handling apk-new files ===

apk avoids overwriting configuration files in the {{path|/etc}} directory. Whenever apk installs a file there, but realizes a potentially edited one is already present, it will write its file to that filename with {{path|.apk-new}} appended. When upgrading, you see a message like below: {{Cmd|# apk upgrade
(1/2) Upgrading openrc-user-pam (0.62.2-r2 -> 0.62.2-r3)
(2/2) Upgrading openrc (0.62.2-r2 -> 0.62.2-r3)
openrc-0.62.2-r3: installing file to etc/rc.conf.apk-new
openrc-0.62.2-r3.post-upgrade: Executing script}}

You may handle these by hand, or use the [[Alpine configuration management scripts#update-conf|update-conf]] utility:-

* To list files where changes to configurations from the new packages exist: {{Cmd|# update-conf -l}}
:Paths appear to locations, possibly using double-slash (''"//"'') unix notation, where both the old file and the new file with the {{Path|.apk-new}} extension exist.
* Simply invoking {{ic|update-conf}} will present you with the difference between the two files and offer various choices for dealing with the conflicts.{{Cmd|# update-conf}}
:'''Be very careful''' not to choose ''"u"'' to ''use'' the new file versions for files such as {{Path|passwd}}, {{Path|doas.conf}}, {{Path|shadow}}, {{Path|hosts}}, etc., because otherwise the existing password hashes, user doas settings, etc. '''''would be wiped, and lockouts would occur!''''' Instead, one could choose to compare the new lines (shown with a ''"+"'') with the lines that would be removed (''"-"'') and edit (''"e"'') the files if so wished, or zap (''"z"'') the new version – i.e. delete the new version – if no essential changes are required.
:Therefore, '''update-conf''' does not currently have a merge function set up by default to preserve essential data unlike, say, Debian's '''update-passwd'''.


=== Autoupdate tool for apk ===

Alpine Linux [https://github.com/jirutka/apk-autoupdate tool for automatic updates] is available as {{pkg|apk-autoupdate}} package. It can be used with [[Cron]] to enable unattended, automatic upgrades of packages.

== Package management in Diskless mode ==

Besides using [[#Local Cache|Local Cache]], all package management tasks in [[Diskless Mode|diskless]] and [[Data Disk Mode|Data disk]] mode systems like adding, removing and [[#Upgrading "diskless" and "data" disk mode installs|upgrading]] packages requires running the command: {{Cmd|'''# [[Alpine_local_backup#Committing changes|lbu commit]]'''}}

Only when the above command is run, the changes will take effect on next reboot.

== apk audit ==

The audit applet examines the system or specified directories for changes compared to the package database. The purpose of audit is to detect unauthorized modifications or to identify files/paths to [[Alpine_local_backup#Include_special_files/folders_to_the_apkovl|include them in apkovl]].

These flags determine the '''scope''' of the audit i.e which files are examined:
--backup (Default): Files flagged as configuration/protected
--system: Files provided by packages but ignores new/untracked files and configuration files.
--full: All package tracked files and all newly added files/directories.

When the audit exits with code 99 but produces no output, change the scope and re-run the audit with option --full --details to reveal the output.

The following flags modify the output and provide additional information:
--details: Shows the exact metadata differences using + and - symbols.
--check-permissions: Includes UID, GID, and Mode in the comparison.
--packages: Prints only the packages with changed files.

The packages flag is useful to repair all packages with modified files, by using the command:{{Cmd|<nowiki># apk audit --packages -q | xargs apk fix</nowiki>}}

By default, the output format is one file per line, for each modified file. A character is printed indicating the line type, followed by a space, then either the affected path or the metadata details. The metadata details appear above the relevant file/path.

An optional <path> can be added to limit the audit to a specific directory. The example output below illustrates most of the options explained above.

<pre>
# chmod 777 /etc/init.d/networking
# apk audit --check-permissions --details /etc/init.d/networking
# echo $?
99
# apk audit --check-permissions --details --full |grep -C 3 networking
- mode=755 uid=0 gid=0 hash=9fe622bd6d06ed19eb53c1a665343b98f864c5cd
+ mode=777 uid=0 gid=0 hash=9fe622bd6d06ed19eb53c1a665343b98f864c5cd
M etc/init.d/networking
# apk fix openrc
# apk audit --check-permissions --details --full |grep -C 3 networking
# echo $?
1
</pre>

The following table summarizes the changes detected and displayed by the audit command.

{| class="wikitable" align="center" style="width:100%; border:1px #0771a6 solid; background:#f9f9f9; text-align:left; border-collapse:collapse;"
|-
|style="background:black; color:white" colspan=2 align=center |Audit command output
|-
| - || Details as per Database record (shown only with --details flag)
|-
| + || Details as per On-disk record (shown only with --details flag)
|-
| A || File added
|-
| d || Directory added
|-
| D || Directory added (with non-listed files/subdirs)
|-
| e || error occured during audit (e.g. no permissions to read file)
|-
| M || File metadata changed (uid, gid, or mode)
|-
| m || Directory metadata changed
|-
| U || File contents modified
|-
| X || File deleted
|-
| x || xattrs changed
|-
|}

== apk query ==
{{Pill_clickable||v3 only|green|palegreen|right|Alpine Package Keeper#apk_v3}}
The query applet is a superset of [[#Information on Packages|info]], [[#Listing installed packages|list]] and [[#Search for Packages|search]] commands to interrogate the installed database and indexes for information related to packages. The command outputs human readable format in addition to json and yaml output.

== Search for Packages ==

{{Tip|Alpine Linux provides a specialized [https://pkgs.alpinelinux.org web interface] dedicated to looking through various available packages.}}

The '''search''' command searches the repository Index files for installable packages.

The return format is '''Package'''-'''Version'''. Omit '''Version''' for ''apk add '''Package'''''

Examples:
* To list all packages available, along with their descriptions: {{cmd|$ apk search -v}}
* To list all packages are part of the ACF system: {{cmd|$ apk search -v 'acf*' }}
* To list all packages that list NTP as part of their description, use the ''-d'' or ''--description'' option: {{cmd|$ apk search -v --description 'NTP' }}
* To list all packages that provide the <code>git</code> command: {{cmd|$ apk search -v 'cmd:git'}}

== Information on Packages ==

The '''info''' command provides information on the contents of packages, their dependencies, and which files belong to a package.

For a given package, each element can be chosen (for example, ''-w'' to show just the webpage information), or all information displayed with the ''-a'' command.

Example: {{cmd|$ apk info -a zlib}}

'''zlib-1.2.5-r1 description:'''
A compression/decompression Library

'''zlib-1.2.5-r1 webpage:'''
<nowiki>https://zlib.net</nowiki>

'''zlib-1.2.5-r1 installed size:'''
94208

'''zlib-1.2.5-r1 depends on:'''
libc0.9.32

'''zlib-1.2.5-r1 is required by:'''
libcrypto1.0-1.0.0-r0
apk-tools-2.0.2-r4
openssh-client-5.4_p1-r2
openssh-5.4_p1-r2
libssl1.0-1.0.0-r0
freeswitch-1.0.6-r6
atop-1.25-r0

'''zlib-1.2.5-r1 contains:'''
lib/libz.so.1.2.5
lib/libz.so.1
lib/libz.so

'''zlib-1.2.5-r1 triggers:'''

As shown in the example you can determine
* The '''description''' of the package (''-d'' or ''--description'')
* The '''webpage''' where the application is hosted (''-w'' or ''--webpage'')
* The '''size''' the package will require once installed (in bytes) (''-s'' or ''--size'')
* What packages are required to use this one ('''depends''') (''-R'' or ''--depends'')
* What packages require this one to be installed ('''required by''') (''-r'' or ''--rdepends'')
* The '''contents''' of the package, that is, which files it installs (''-L'' or ''--contents'')
* Any '''triggers''' this package sets. (''-t'' or ''--triggers'') Listed here are directories that are watched; if a change happens to the directory, then the trigger script is run at the end of the apk add/delete. For example, doing a depmod once after installing all packages that add kernel modules.

=== Check file ownership ===

The '''info''' command is also useful to determine which package a file belongs to when used with the {{ic|--who-owns}} option, or simply {{ic|-W}}. For example: {{cmd|$ apk info --who-owns /sbin/lbu}}
will display
<pre>
/sbin/lbu is owned by alpine-conf-x.x-rx
</pre>

=== Check Dependencies ===

The '''info''' command specific to check package dependency and reverse dependency is explained below:

The option '''-R''' or '''--depends''' lists the dependencies of the package: {{Cmd|$ apk info --depends pipewire}}
<pre>
pipewire-1.0.6-r1 depends on:
/bin/sh
so:libc.musl-x86_64.so.1
so:libpipewire-0.3.so.0
</pre>

The option '''-r''' or '''--rdepends''' lists the reverse dependencies of the package (all other packages which depend on the package). {{Cmd|$ apk info --rdepends pipewire}}
<pre>
pipewire-1.0.6-r1 is required by:
xdg-desktop-portal-wlr-0.7.1-r0
pipewire-pulse-1.0.6-r1
</pre>

=== Listing installed packages ===

To list all installed packages, use: {{Cmd|$ apk info}}

To list all installed packages in alphabetical order, with a description of each, do:{{Cmd|$ apk -vv info|sort}}

To list packages locally installed that are not longer available in repositories, use {{Cmd|$ apk list --orphaned}}

To browse details of installed package in a "TUI" with:{{Cmd|<nowiki>$ apk list --installed -q | fzf --preview 'apk query {1}'</nowiki>}}

To list subpackages for a package, for e.g {{pkg|util-linux}}:{{Cmd|$ apk list --quiet --origin util-linux}}

The apk tool does not have a subcommand to list manually-installed packages that do not have reverse dependencies. To get this information on a traditional system that is not using [[Alpine local backup|lbu]], try this script. Note that this approach will also list core packages like alpine-base that should not be removed.

<pre>
#!/bin/sh
apk info | grep -ve '-doc$' | sort | while read pkg
do
rdep=`apk info -qr "$pkg"`
[ -z "$rdep" ] && echo $pkg
done
</pre>

=== List packages by installed size ===
{{Pill_clickable||v3 only|green|palegreen|right|Alpine Package Keeper#apk query}}
The below command lists all installed packages by installed size. It requires {{pkg|jq}} package and uses [[#apk query|query]] option. Use the below command with <Code>less</Code> or <Code>head</Code> command:
{{Cmd|<nowiki>$ apk --installed query --format json --fields name,installed-size '*'|jq -r '.[] | [."installed-size", ."name"] | @tsv' | sort -nr</nowiki>}}

== Local Cache ==
{{Seealso|Local APK cache}}
APK can keep a cache of installed packages on a local disk. HDD or [[Installation#System_Disk_Mode|sys mode]] installs don't need an apk cache, it still allows to serve packages over the network, though, e.g. to get installed by other local machines.

{{Note|For [[Diskless Mode|diskless]] installations, [[Local APK cache|local package cache]] is needed to automatically (re-)install packages when booting.}}

When newer packages are added to the cache over time, the older versions of the packages default to remain in the cache directory. The older versions of packages can be removed with the '''clean''' command. {{cmd|# apk cache clean}} Or to see what is deleted include the verbose switch: {{cmd|# apk -v cache clean}}

If packages got deleted accidentally from the cache directory, then use the '''download''' command, {{cmd|# apk cache download}}

The above two steps can be combined into one with the '''sync''' command - this cleans out old packages and downloads missing packages. {{cmd|# apk cache -v sync}}

== apk dot ==

The dot option renders package dependencies as {{pkg|graphviz}} graphs.[[File:Seatd dependencies.png|800px|center|alt=Seatd dependencies|Seatd dependencies]] Steps to use the dot option is documented below:
# Save the output of apk dot option to a dot file.{{Cmd|$ apk dot seatd > seatd_dependencies.dot}}
# Use <code>dot</code> utility from {{pkg|graphviz}} package to convert the {{Path|seatd_dependencies.dot}} file into a graphical format such as PNG, PDF, or SVG. {{Cmd|$ dot -Tpng seatd_dependencies.dot -o seatd_dependencies.png}}

== apk fix ==

If a package is specified, the '''fix''' subcommand applies repair strategies to correct errors in the installation of the specified packages. If no packages are specified, this command synchronizes all the installed packages with the [[#World|desired system state]].

However, if the currently installed '''''version''''' of the package (say, <var>foo</var> version <var>1.2.3-r4</var>) is no longer available in the operating system's repositories (i.e. the repos specified in {{Path|/etc/apk/repositories}}) following the latest system update, then '''apk fix''' will not fix the package and will report ''"[APK unavailable, skipped]"'' instead:

{{Cmd|$ doas apk fix <var>foo</var>
(1/1) [APK unavailable, skipped] Reinstalling foo (1.2.3-r4)}}

This outcome applies both with '''apk v3''' and '''v2''', and includes cases where either a higher or lower version of the package is found in the employed repos. In such cases where a different version exists, consider replacing the package using the [[Alpine_Package_Keeper#Add_a_local_Package|{{ic|apk upgrade --available}}]] command, which will either upgrade or downgrade ''all packages'' to the versions currently offered.

== apk policy ==

To display the repository a package was installed from and will be updated from, plus any [[#Repository_pinning|tagged]] or enabled repositories where it is also offered, if any, for this architecture - its '''policy''': {{Cmd|$ apk policy ''package''}}

For example:
<pre>
$ apk policy vlc
vlc policy:
2.2.6-r1:
lib/apk/db/installed
https://dl-3.alpinelinux.org/alpine/v3.7/community
3.0.0_rc2-r1:
@edgecommunity https://dl-3.alpinelinux.org/alpine/edge/community
</pre>

== Configuration file ==
{{Pill_clickable||v3 only|green|palegreen|right|Alpine Package Keeper#apk_v3}}
Support for config file for setting default global options has been enabled. The user defined config file {{path|/etc/config/apk}}, if present overrides the {{path|/lib/apk/config}}, intended for distribution default options. To override the default config file name, the environment variable {{ic|APK_CONFIG}} can be used.

The configuration file contains one long option per line as shown here for reference:{{Cat|/etc/config/apk|no-cache
timeout 120}}

The following aliases are available: {{ic|cache}} equals {{ic|cache yes}} and {{ic|no-cache}} equals {{ic|cache no}}.

== Transaction logs ==
{{Pill_clickable||v3 only|green|palegreen|right|Alpine Package Keeper#apk_v3}}
All apk commands which modify the database i.e write transactions are logged to {{Path|/var/log/apk.log}}. To disable the writing of the log file, the configuration option {{ic|logfile}} in the [[#Configuration file|configuration file]] must be set as follows:{{Cat|/etc/config/apk|logfile no}}

== Advanced APK Usage ==

=== Commandline repository options ===

By default, the '''apk''' utility will use the system repositories for all operations. This behavior can be overridden by the following options:
{|
| --repositories-file REPOFILE
| Override the system repositories by specifying a repositories file.
|-
| <nowiki>-X|--repository REPO</nowiki>
| Specify a supplemental repository that will be used in addition to the system repositories. This option can be provided multiple times.
|}

{{cmd|# apk add cherokee --update-cache --repository https://dl-cdn.alpinelinux.org/alpine/edge/testing/ --allow-untrusted}}

=== apk Command Line Parsing ===

==== Use of Single Quotes ====
Advanced use of '''apk''' could require the use of single quotes around its argument (e.g. {{ic|apk <var>add</var> '<var>argument</var>'}}) when certain characters are being employed, since Unix shells – including the default '''sh''' ('''ash'''/'''busybox''') shell, '''bash''' or '''zsh'''/'''fish''' – will attempt to interpret the argument if it is not enveloped in single quotes:-
* {{ic|<}} in an argument would be unintendedly interpreted as "input redirection"; {{ic|asterisk<1.6.1}} without quotes would prompt the shell to attempt to read from an {{Path|asterisk}} file; similarly, {{ic|>}} would be interpreted unintendedly as "output redirection"
* {{ic|~}} would attempt to expand the argument to include the user’s home directory path
* {{ic|*}}, {{ic|?}}, {{ic|[0-9]}} without single quotes around the argument could cause globbing, meaning that the shell would try to expand the package name using the meaning of those characters ({{ic|*}} meaning any string of alphanumeric characters, for example) and then try to apply '''apk''' to any ''file'' fitting that name in the current working directory as an unintended interpretation
* {{ic|!}} in a '''bash''' or '''zsh''' shell without using quotes would be interpreted as "history expansion" as opposed to [[#Package_masking|"negate installation"]], as intended. Note that, if using '''ash''' (Alpine Linux’s default), the lack of single quotes is not problematic there as that shell does not support history expansion. History expansion is ''disabled by default'' in '''fish'''.
Therefore, the use of single quotes is typically required in various shells to enclose the package name/version, with or with any '!' symbol, to be handed directly to the '''apk''' tool so that it is not attempted to be interpreted by the shell.

=== Package pinning ===
{{Seealso|Repositories#Tagged repository}}

In certain cases, you may want to upgrade a system, but keep a specific package at a specific level or version by pinning a Package. It is possible to add "sticky" or versioned dependencies.

{{Warning| If you desire deterministic, repeatable package installation (such as with containerized environments) via package pinning, it is important to understand your package repo's version retention rules. Always pin to a package version that is intended for your [[Repositories#Release_Branches|release branch]]. Pinning to a version on the [[Repositories#Edge|edge]] branch may stop working after the package version is revoked from the repo.}}

For instance, to hold the ''asterisk'' package to the 1.6.2 level or lower:{{cmd|<nowiki># apk add asterisk=1.6.0.21-r0</nowiki>}}
or – note the need for [[#Use_of_Single_Quotes|single quotes]]:{{cmd|# apk add 'asterisk<1.6.1'}}

To upgrade the entire system, keeping the asterisk package at the 1.6.0 or lower level:{{cmd|# apk upgrade}}

To later upgrade to the current version, and ensure that 1.6.1 is the minimum version used. {{cmd|# apk add 'asterisk>1.6.1'}}

You can also use "fuzzy" version matching to pin the version to a major/minor release. To match any version of asterisk that starts with 1.6 (such as 1.6.0.21-r0 or 1.6.9.31-r9) use the command: {{cmd|<nowiki># apk add 'asterisk=~1.6'</nowiki>}}

==== Holding a specific package back ====
See [[#Package pinning|Package pinning]]

=== Package masking ===

In case a package is pulled in yet is superfluous or unwanted, or if it were to be installed and conflict with another, one could ''mask'' it i.e. ''exclude it'' from being installed unless '''apk''' is later instructed ''explicitly'' to add it. To mask/exclude an unwanted package hypothetically called ''foo'':
{{Cmd|# apk add '!foo'}}
Beforehand, ensure that the '''''package is not installed'''''. If so, ''uninstall it first'', as otherwise, it would become an ''"orphaned package"'': installed, yet not being managed by the '''apk''' package keeper, which could cause an obfuscated problem(s) if it or its dependencies linger and later conflict with another package; it could be harder to trace the issue(s) then.

The exclamation mark (!) is often used in logic and IT to express negation.

As [[#Use_of_Single_Quotes|detailed above]], be sure to employ the single quotes (') if using certain shells ''other than'' the unaffected '''ash''' shell so as to avoid an unintended interpretation by the shell interpreter.

The package then appears negated in ''world'':
{{Cat|/etc/apk/world|fon
!foo
fop}}

==== Unmasking a specific package ====

Simply install it ''explicitly'' using '''apk'''. Say:
{{Cmd|# apk add foo}}
Uninstall it afterwards, if not required.
Alternatively, delete the line in {{Path|/etc/apk/world}} where the package is negated. Be sure not to leave any spurious character.

=== Commit hooks ===

If you'd like to trigger an action or run a certain script on every commit made by apk, there's a built-in method for that. On every commit apk looks for executables located in the "/etc/apk/commit_hooks.d/" directory, and executes them both before and after the commit. To provide some way to selectively run hooks either before or after a change is commited by apk, the scripts are called with "pre-commit" or "post-commit" as argument 1.
This is an example of a hook to do different things before and after commit:

{{cmd|1=#!/bin/sh

if [ "$1" = "pre-commit" ]; then
do_something

elif [ "$1" = "post-commit" ]; then
do_something_else
fi}}

Commit hooks are $PATH-aware, so for the sake of security it's recommended to specify absolute paths to executables.

== Rosetta Stone ==

[[Comparison with other distros#Comparison chart/Rosetta Stone|Rosetta Stone]] or a Comparison chart shows how standard things related to package management are done in Alpine Linux compared to other popular distributions.

== Troubleshooting ==

=== ERROR: unable to select packages ===

This error typically indicates that the package manager cannot find a suitable package to install. On issuing a command to add a package for eg: {{ic|# apk add labwc}}, you may receive below error message:
<Pre>
ERROR: unable to select packages:
labwc (no such package):
required by: world[labwc]
</Pre>

The above error indicates {{pkg|labwc}} does not exist in the [[Repositories|repositories]] currently configured in {{Path|/etc/apk/repositories}}. Ensure that <code>community</code> repository is [[Repositories#Managing_repositories|enabled]], as by default only <code>main</code> repository is enabled. You may also want to check [https://pkgs.alpinelinux.org/packages packages database] to identify the correct package name and the [[Repositories|repository]] in which the package is available.

<Pre>
ERROR: unable to select packages:
so:libxml2.so.2 (no such package):
required by: llvm19-libs-19.1.7-r1[so:libxml2.so.2]
</Pre>

The above error message may occur in [[Edge|Edge]] branch in certain other situations, even if all the necessary [[Repositories|repositories]] are enabled. Temporary non-availability of the packages from the repositories can occur, when software packages are [https://build.alpinelinux.org/ rebuilt]. You may want to wait for some time to try again.

=== ERROR: unsatisfiable constraints ===

This error signifies a dependency conflict. It means that the package you're trying to install has dependencies that cannot be simultaneously satisfied within the current package repository.

You may want to check [https://pkgs.alpinelinux.org/packages packages database] to identify the correct package name and version and the [[Repositories|repository]] in which the package is available.

=== WARNING: This apk-tools is OLD! ===

'''apk update''', '''apk upgrade''' or '''apk add''' may report the following:
WARNING: This apk-tools is OLD! Some packages might not function properly

This may happen if you are running Alpine Linux stable version with a [[Repositories#Edge|Edge]] package(s) also installed. One resolution is to consider upgrading {{pkg|apk-tools}}. If edge/main is already [[Repositories#Tagged repository|tagged]] as ''@edgemain'' in your {{Path|/etc/apk/repositories}} file, then try: {{Cmd|# apk add --upgrade apk-tools@edgemain}}

=== ERROR: UNTRUSTED signature ===

This happens when the release version changes. You need to update the local apk keys.

If you have already updated your repositories, allow them to update without the trusted key:
{{Cmd|# apk update --allow-untrusted}}

Then install the keys upgrade:
{{Cmd|# apk fix --upgrade --allow-untrusted alpine-keys}}

Now updates and upgrades should proceed normally.

Alternative, the updated alpine-keys package may be obtained, verified, installed directly, as covered earlier, prior to a repository update.

=== ERROR: unable to select packages: breaks: world ===

{{Cmd|<nowiki># apk add vim
ERROR: unable to select packages:
vim-common-9.1.1566-r0:
breaks: world[!vim-common]
satisfies: vim-9.1.1566-r0[vim-common=9.1.1566-r0]</nowiki>}}

When issuing package management commands, the above error will arise, if the command cannot be solved without breaking the [[#World|World]]. 

=== World updated but the following packages are not removed ===

On issuing a command to remove a package for eg: {{ic|# apk del btrfs-progs}}, you may receive below error message:
<Pre>
World updated, but the following packages are not removed due to:
btrfs-progs: btrbk
</Pre>

Here, the removal of package {{Pkg|btrfs-progs}} affects another package {{Pkg|btrbk}} in the constraints file [[#World|/etc/apk/world]]. So the package {{Pkg|btrfs-progs}} will be removed from the constraints file, but not removed from the system. The {{Pkg|btrfs-progs}} will remain in the system, until the constraint i.e {{Pkg|btrbk}} which depends on {{Pkg|btrfs-progs}} is removed.

If {{ic|apk del btrbk}} is issued, the package {{Pkg|btrfs-progs}} will be automatically removed from system as the constraint {{Pkg|btrfs-progs}} does not exist in {{Path|/etc/apk/world}}.

=== Huh? Error reporter did not find the broken constraints===

<Pre>
ERROR: unable to select packages:
Huh? Error reporter did not find the broken constraints.
</Pre>

The above message can be due to version conflicts caused by a software package present in the [[#World|world]] file and appears when [[Upgrading Alpine Linux to a new release branch]]. When apk-tools solver returns above message, that is always a bug. Please file a bug report [https://gitlab.alpinelinux.org/alpine/apk-tools/-/issues here].

To identify the offending software package, take a backup of the world file, then take stuff out of world until the upgrade works. Or alternatively, begin with a minimal version of world file and add things until it breaks again.

Once the upgrade is done, you may be able to add back the offending software package, if supported in the newer version.

Check the [https://irclogs.alpinelinux.org/%23alpine-linux-2026-02.log IRC logs] dated 2026-02-18 for an example on how this error was temporarily resolved.

=== Issues due to /usr merge ===

Further to the [https://alpinelinux.org/posts/2025-10-01-usr-merge.html /usr merge] announcement, for users who have migrated to the [[Repositories#Message_on_/usr_merge|merged /usr]], there are certain known issues like {{Issue|17624|apk audit does not work}}.


==== ERROR:Could not find owner package ====

The {{ic|apk info --who-owns}} command is currently subject to requiring the declaration of a file's path to be updated in the case where '''[[Repositories#Message_on_/usr_merge|/usr merge]]''' had been previously applied and where, additionally, the file was originally assigned to paths under {{Path|/lib}}, {{Path|/bin}} or {{Path|/sbin}}. Otherwise, an error is returned, seeing how these are now soft-linked into {{Path|/usr}}:

<pre>
$ apk info --who-owns /sbin/lbu
ERROR: /sbin/lbu: Could not find owner package
</pre>

In order for this facility to function in such cases, {{Path|/usr}} currently needs to be prepended to the declaration of the path for all such files, seeing how those files are now soft-linked to {{Path|/usr/lib}}, {{Path|/usr/bin}} or {{Path|/usr/sbin}}: {{cmd|$ apk info --who-owns /usr/sbin/lbu}}

== See also ==

* [https://git.alpinelinux.org/apk-tools/tree/doc/apk.8.scd Manual for apk(8)]
* [https://git.alpinelinux.org/apk-tools/tree/doc/apk-world.5.scd Manual for apk-world(5)]
* [https://pkgs.alpinelinux.org Official web interface for packages]
* [[Software management]]
* [https://ariadne.space/2021/04/24/why-apktools-is-different-than.html Why apk-tools is different than other package managers]
* [https://ariadne.space/2021/10/30/spelunking-through-the-apktools-dependency.html spelunking through the apk-tools dependency solver]
* [https://whynothugo.nl/journal/2023/02/18/in-praise-of-alpine-and-apk/ In praise of alpine and apk]
* [https://www.cyberciti.biz/faq/10-alpine-linux-apk-command-examples/ 10 Alpine Linux apk Command Examples]
[[Category:Package Manager]]
[[Category:System_Administration]]

Alpine Linux:FAQ

2026-03-22T03:18:05Z

Apropos: /* Why don't I have man pages or where is the 'man' command? */ Note interaction of MANPATH environment variable with man page lookup

[[Image:filetypes.svg|64px|left|link=]]

Alpine Linux is an independent, non-commercial, general purpose Linux distribution designed for power users who appreciate security, simplicity and resource efficiency.

This is a list of '''frequently asked questions''' about Alpine Linux. If your question is not answered on this page, check the available [[Alpine Linux:Support|support]] options.

== General ==
=== Where to start? ===

The [[Installation]] page and the [[Installation#Post-Installation|Post Installation]] section on that page, provide a basic orientation.

A broader overview may be found on the official [https://alpinelinux.org/about About] page and at the [[Alpine Linux:Overview|wiki overview]].

Please note that testing is safer on your own virtual machine.

=== I have found a bug, where can I report it? ===
You can report it on the [https://gitlab.alpinelinux.org/groups/alpine/-/issues bugtracker], but search it first to see if the issue has already been reported.

=== Are there any details about the releases available? ===
Please check the [https://alpinelinux.org/releases/ Release Branches] page for more information.

=== What is the difference between edge and stable release branch? ===

[[Repositories#Edge|'''Edge''']] is the name given to the current [[Aports tree|development tree]] of Alpine Linux. ''edge'' can be considered as '''rolling release version''' of Alpine Linux. This version contains the latest build of all available Alpine Linux packages. Those packages are updated on a regular basis.

[[Repositories#Release Branches|Stable release branches]] are just what they sound like: initially a point-in-time snapshot of the package archives, but then maintained with bugfixes only in order to keep a stable environment. Occasionally, snapshot ISO images of the then-current state of edge are made and are available for download. Typically these are made when there are major kernel upgrades or package upgrades that require initramfs rebuilds.

=== What architectures does Alpine Linux support? ===
The table below lists the architectures that are officially supported.
{{:Include:Architecture support matrix}}
Please check [https://alpinelinux.org/downloads Downloads] page for media availability on each one.


=== How can I contribute? ===
You can contribute by:
* Using the software and giving [https://gitlab.alpinelinux.org/groups/alpine/-/issues feedback].
* Documenting your [https://www.alpinelinux.org Alpine Linux] experiences on this [[Main_Page|wiki]].
* Flag packages as outdated in the [https://pkgs.alpinelinux.org/packages package database], or even better enable release monitoring in [https://release-monitoring.org/ Anitya] for them.
* In many other ways.
Please visit the [[Contribute|Contribute page]] to read more about this topic.

=== Why don't I have man pages or where is the 'man' command? ===

The <code>man</code> command, the {{pkg|man-pages}} and the system's ''core'' manual pages are not installed by default. Since binary packages are thinned out and split, documentation sub-packages in the format '''packagename-doc''' are not installed by default.
The core utilities provided by [[BusyBox]] – e.g. {{ic|ls}}, {{ic|traceroute}} and {{ic|poweroff}} – do not have individual man pages in keeping with BusyBox's minimalist design. Instead, the man page package for BusyBox, {{pkg|busybox-doc}}, supplies a single '''busybox''' man page that lists all the available switches for those utility applets; once '''busybox-doc''' is installed, the switches for each utility can be listed using the {{ic|--help}} option – e.g. {{ic|ls --help}} – or by scrolling through {{ic|$ man busybox}}.

Install the ''man pages reader'' called {{pkg|mandoc}}. It is the default reader since Alpine Linux v3.12, preferred over {{pkg|man-db}} or {{pkg|man-pages}}, as it supplies a smaller, faster, and more secure <code>man</code> command:
{{cmd|# apk add {{pkg|mandoc}}}}

Once {{pkg|mandoc}} is installed, add documentation for the package where you need it. For example, say you installed '''nftables''', and you now require its man page:
{{cmd|# apk add {{pkg|nftables-doc}}}}

Alternatively, the {{pkg|docs}} meta package will immediately install the documentation sub-package for all of the currently installed packages (plus the {{pkg|mandoc}} reader, if not installed). {{pkg|docs}} additionally ensures that documentation sub-packages are installed/removed automatically for any packages that one may add/remove in the future.

{{cmd|# apk add docs}}

Optionally, to be able to search all ''installed'' man pages for a given command, say, {{ic|<var>password</var>}}, install {{pkg|mandoc-apropos}}, which supplies the <code>apropos</code> instruction.

{{cmd|# apk add {{pkg|mandoc-apropos}}}}

Then, search installed man pages for the command:

$ apropos <var>password</var>
chage(1) - change user password expiry information
expiry(1) - check and enforce password expiration policy
git-credential-cache(1) - Helper to temporarily store passwords in memory
keepassxc(1) - a modern open-source password manager
[...]

Keep in mind that not all packages have a corresponding documentation package, and even when it has one, it may not be in the form of man pages. Also ensure that the <code>MANPATH</code> environment variable, if set, includes <code>/usr/share/man</code> and <code>/usr/local/share/man</code>. If not set, <code>man</code> will fall back on default man page paths, so there is no need to set it explicitly, unless other <code>man</code> page locations are added.

==Setup==

=== What is the difference between ''sys'', ''data'', and ''diskless'' when running <code>setup-alpine</code> or <code>setup-disk</code>? ===

[[System Disk Mode|'''sys''' or '''system''' disk]] mode is the traditional hard disk installation. The following partitions will be created on the disk: ''/boot/'', ''/'' (filesystem root) and ''swap'', if <code>setup-alpine</code> is used, or use <code>setup-disk</code> script for custom partitioning. This mode may be used for development boxes, desktops, virtual servers, etc.

In [[Data Disk Mode|'''data''' disk]] mode, disk(s) are used for data storage, not for the operating system. Runs from the media and only a ''/var/'' is created on disk. The system itself will run from a ''tmpfs'' (RAM). Use this mode if you only want to use the disk(s) for data, like ''mailspool'', ''databases'', ''logs'', etc.

In [[Diskless Mode|'''diskless''']] mode, no disks are to be used. Here the entire system run from a ''tmpfs'' (RAM). [[Alpine local backup]] may still be used in this mode.

=== How do I upgrade Alpine? ===

To upgrade to a new stable release or edge refer to [[Upgrading Alpine Linux to a new release branch]].

=== Why don't my cron jobs run? ===
{{Main|Cron}}
Start service ''crond'' and add it to the default runlevel:{{cmd|rc-service crond start && rc-update add crond}}

After that the cron daemon is started automatically on system boot and executes the scripts placed in the folders under ''/etc/periodic/'' - there are folders for ''15min'', ''hourly'', ''daily'', ''weekly'' and ''monthly'' scripts.

To check whether your scripts are likely to run, use the ''run-parts'' command, for example:{{cmd|run-parts --test /etc/periodic/15min}}

This command will tell you what should run but will not actually execute the scripts.

If the results of the test are not as expected, check the following:

* Make sure the script is executable - if unsure, issue the command {{cmd|chmod +x /etc/periodic/[path/scriptname]}}
* Make sure the first line of your script is <code>#!/bin/sh</code>
* Do not use periods on your script file names - this stops them from working; for example: {{Path|/etc/periodic/daily/myscript}} will run, but {{Path|/etc/periodic/daily/myscript.sh}} won't.

== Time and timezones ==

=== How do I set the local timezone? ===

If you wish to edit the ''timezone'' (TZ) after installation, run the [[Alpine_setup_scripts#setup-timezone|setup-timezone]] script.

== Packages ==

=== Can you build an APK package for ...? ===
Please create an [https://gitlab.alpinelinux.org/alpine/aports/issues/new issue] in the [https://gitlab.alpinelinux.org bugtracker]. Prefix it with "package request:" in the title and include a short description (one-line), a URL for the home page, why you need it, and a URL for the source package.

=== How can I build my own package? ===
Please see the [[Creating an Alpine package]] page.

=== What does "required by: world[$pkgname]" mean? ===

It means that the package you tried to install does not exist in the [[Alpine Package Keeper#Packages and Repositories|repositories]] you have configured.

Ensure that the [[Repositories#Managing_repositories|community repository is enabled]] in the {{path|/etc/apk/repositories}} file.

Or is the package in a [[Repositories#Tagged_repository|tagged repository]] and you forgot to suffix the package with the repo tag? Example:{{cmd|# apk add experimental-package@testing}}

=== How can I find out if a certain package exists in Alpine? ===

If you want to only search repositories you have configured in /etc/apk/repositories, then <code>apk search $pkgname</code> should get you sorted. If you want to search all repositories have a look at the [https://pkgs.alpinelinux.org/ online pkg oracle]

=== WARNING: Ignoring APKINDEX.xxxx.tar.gz ===
If you get <code>WARNING: Ignoring APKINDEX.xxxx.tar.gz: No such file or directory</code> while running [[Alpine_Linux_package_management|package related tools]], check your {{Path|/etc/apk/repositories}} file.

To check the content of the repositories file
{{Cmd|cat /etc/apk/repositories}}

or
{{Cmd|setup-apkrepos}}

== Dynamic DNS ==
=== How do I schedule a regular dynamic DNS update? ===
You'll want to install the {{pkg|ez-ipupdate}} package:
{{cmd|apk add ez-ipupdate}}

After that, create a new file at {{path|/etc/ez-ipupdate.conf}} with contents similar to:
service-type=dyndns
user=myusername:mypassword
interface=eth1
host=myhostname.dyndns.org

Make the new ip cache directory:
{{cmd|mkdir /var/cache/ez-ipupdate
lbu add /var/cache/ez-ipupdate}}

Then schedule a new cron job with this command:
{{cmd|echo >> /var/log/ez-ipupdate && \ /bin/date >> /var/log/ez-ipupdate && \ ez-ipupdate --config-file /etc/ez-ipupdate.conf -f -F /var/run/ez-ipupdate.pid \ --cache-file /var/cache/ez-ipupdate/ipcache --quiet >> /var/log/ez-ipupdate 2>&1}}

Don't forget to backup your settings!
{{cmd|lbu ci}}

== Terminal ==

=== How to enable/fix colors for git? ===

The problem is not in git itself or terminal, but in the <tt>less</tt> command.
Busybox’s <tt>less</tt> doesn’t support <tt>-r</tt> (<tt>--raw-control-chars</tt>) and <tt>-R</tt> (<tt>--RAW-CONTROL-CHARS</tt>) options.

The simplest (yet not ideal) solution is to install GNU less:

{{cmd|apk add less}}

Additionally, for colorized diff while using verbose commit (<tt>git commit -v</tt>), add this to shell init scripts (e.g.: {{Path|~/.profile}}):

{{Cat|~/.profile|<nowiki>export GIT_EDITOR=vim</nowiki>}}

=== Fix lacking lsusb / lspci output ===
{{Main|How to get regular stuff working}}
If you launch {{ic|lsusb}} or {{ic|lspci}} on a default installation, there's no device descriptions, and the latter doesn't exist.

This can be fixed by installing the '''{{pkg|usbutils}}''' and '''{{pkg|hwdata}}''' tables.

== Old questions, no longer frequently asked ==

=== Alpine freezes during boot from Compact Flash, how can I fix? ===
Most Compact Flash card readers do not support proper DMA. 
You should append '''nodma''' to the ''append'' line in {{path|syslinux.cfg}}.

=== How do I remove the CD-ROM? ===
Since the modloop loopback device is on CD-ROM you cannot just run <code>eject</code>. You need to unmount the modloop first. 
Unmounting both the modloop and the CDROM in one step can be done by executing:
{{Cmd|/etc/init.d/modloop stop}}

Then it's possible to eject the CD-ROM:
{{Cmd|eject}}

=== How can I install custom firmware in a diskless system? ===

The modules and firmware are both special images which are mounted as read-only. 
To fix this issue you can copy the firmware directory to your writeable media (cf/usb) and copy your custom firmware to it. 
After reboot Alpine should automatically use the directory on your local storage instead of the loopback device.

=== OpenNTPD reports an error with "adjtime" ===
Your log contains something like:
reply from 85.214.86.126: offset 865033148.784255 delay 0.055466, next query 32s
reply from 202.150.212.24: offset 865033148.779314 delay 0.400771, next query 3s
adjusting local clock by 865033148.779835s
adjtime failed: Invalid argument

{{pkg|openntpd}} is supposed to make small adjustments in the time without causing time jumps. 
If the adjustment is too big then something is clearly wrong and ntpd gives up. (its actually adjtime(3) that has a limit on how big adjustments are allowed)

You can make ntpd set the time at startup by adding ''-s'' option to ntpd. This is done by setting '''NTPD_OPTS="-s"''' in {{path|/etc/conf.d/ntpd}}.

=== Using a cron job to keep the time in sync ===
The [[Cron#Basic_example|cron]] page explains how to run the command {{ic|ntpd -d -q -n -p uk.pool.ntp.orgA}} as a cron job.

=== Windows clients reports an error when trying to sync ===
{{pkg|openntpd}} needs to run for a while before it is satisfied it is in sync.
Until then it will set a flag "clock not synchronized" and Windows will report an error while trying to sync with your openntpd server.

Only thing to do is wait, do something else for 15-20mins and then check.