Alpine Linux:FAQ: Difference between revisions

From Alpine Linux
mNo edit summary
 
(54 intermediate revisions by 22 users not shown)
Line 1: Line 1:
[[Image:filetypes.svg|64px|left|link=]]
[[Image:filetypes.svg|64px|left|link=]]
This is a list of '''frequently asked questions''' about Alpine Linux.<br>
This is a list of '''frequently asked questions''' about Alpine Linux.<br />
If your question is not answered on this page, use the search box above to find work in progress pages not linked here, or in case of no answer, edit this page and write down your question.
If your question is not answered on this page, use the search box above to find work in progress pages not linked here, or in case of no answer, edit this page and write down your question.
{{Tip| Prepare your question. Think it through. Make it simple and understandable.}}  
{{Tip| Prepare your question. Think it through. Make it simple and understandable.}}  
Line 6: Line 6:
=General=
=General=


To get oriented and learn what makes our distribution distinctive, see the [http://alpinelinux.org/about About page] or [[Alpine Linux:Overview|our more detailed overview]].
Alpine Linux is used heavily in containers (e.g. Docker images) on servers, so many of its main packages are focused on server services.


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


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


If you don't have enough skills on Linux, use a virtual machine, possibly follow the [[Alpine_newbie#Install|Alpine_newbie Install section]] page wiki instructions.
A broader overview may be found on the official [https://alpinelinux.org/about About] page and at the [[Alpine Linux:Overview|wiki overview]].


If you are medium, have some kind of knowledge on Linux, please use the [[Newbie Alpine Ecosystem]] wiki page, and later after some test, take note that Alpine Linux is most used at containers and dockers. So that's why main package software are focused on services.
Please note that testing is safer on your own virtual machine.


== I have found a bug, where can I report it? ==
== I have found a bug, where can I report it? ==


You can report it on the '''https://gitlab.alpinelinux.org/groups/alpine/-/issues link of the bugtracker'''. But first search if was already reported.
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? ==
== Are there any details about the releases available? ==
Yes, please check the [[Alpine Linux:Releases|Releases]] page.
Yes, please check the [https://alpinelinux.org/releases/ releases] page.


== How can I contribute? ==
== How can I contribute? ==
You can contribute by:
You can contribute by:
* Using the software and giving feedback.
* Using the software and giving [https://gitlab.alpinelinux.org/groups/alpine/-/issues feedback].
* Documenting your [http://www.alpinelinux.org Alpine Linux] experiences on this [[Main_Page|wiki]].
* 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.
* In many other ways.
Please visit [[Contribute|Contribute page]] to read more about this topic.
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? ==
== Why don't I have man pages or where is the 'man' command? ==
The <code>man</code> command and man pages are not installed by default.
The <code>man</code> command and '''man pages''' are not installed by default.


* First, install the {{pkg|man}} package:
Install the <code>man</code> command:
<code>apk add man</code>
{{cmd|# apk add {{pkg|mandoc}}}}
* Once that's done, install the documentation for the packages that you require man pages for:
Install basic manual pages.  {{pkg|man-pages}} package provides the system's ''core'' manual pages:
<code>apk add ''package''-doc</code>
{{cmd|# apk add man-pages}}
 
Install the <code>apropos</code> command to search in '''man pages''':
For example, say you installed {{Pkg|iptables}} and you now require its man pages:
{{cmd|# apk add {{pkg|mandoc-apropos}}}}
<code>apk add iptables-doc</code> and then: <code>man iptables</code>. Keep in mind, not all packages will have a corresponding documentation package In our example above, we installed the man pages (and other documentation) for <code>iptables</code>
Once installed, add documentation for the package where you need it.  For example, say you installed {{pkg|nftables}} and you now require its '''man pages''':
{{cmd|# apk add {{pkg|nftables-doc}}}}
To always install the documentation companion package add the {{pkg|docs}} meta package. Keep in mind not all packages have a corresponding documentation package and even when it has one it may not include '''man pages''':
{{cmd|# apk add docs}}


== What is the difference between edge and stable releases? ==
== What is the difference between edge and stable releases? ==
Stable releases are just what they sound like: initially a point-in-time snapshot of the package archives, but then maintained with bug-fixes only in order to keep a stable environment.
Stable releases 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.


[[Edge]] is more of a rolling-release, with the latest and greatest packages available in the online repositories.<br>
[[Repositories#Edge|Edge]] is more of a rolling-release, with the latest and greatest packages available in the online repositories.<br />
Occasionally, snapshot ISO images of the then-current state of [[edge]] are made and are available for download.<br>
Occasionally, snapshot ISO images of the then-current state of edge are made and are available for download.<br />
Typically these are made when there are major kernel upgrades or package upgrades that require initramfs rebuilds.
Typically these are made when there are major kernel upgrades or package upgrades that require initramfs rebuilds.


== What architectures does Alpine support? ==
== What architectures does Alpine Linux support? ==
As Alpine uses the Linux kernel, it supports:
* '''aarch64''': 64-bit ARM processors (e.g. Raspberry Pi 4)
* '''x86_64''': The popular AMD64 compatible 64-bit x86 based machines, i386 is not recommended for newer/latest hardware.
* '''armhf''': 32-bit ARMv6 processors with a floating point unit (e.g. Raspberry Pi 1) (armv6hf)
* '''s390x''': For the Super powered IBM mainframes, especially IBM Z and IBM LinuxONE servers.
* '''armv7''': 32-bit ARMv7 processors with a floating point unit (armv7hf)
* '''ppc64le''': For the PowerPC devices with pure little-endian mode, mostly for POWER8 and POWER9
* '''s390x''': IBM mainframes using the z/Architecture (z196 minimum)
* '''x86''': (i386 pc 32bit) and x86_64 (i686 pc 64bit and amd64)
* '''ppc64le''': 64-bit little-endian POWER devices (e.g. Raptor Talos II) (POWER8 minimum)
* '''armhf''': The newer ARM hard-float for newer, more powerful 32-bit devices alongside 64-bit
* '''x86''': 32-bit Intel and AMD processors commonly found in older personal computers (e.g. Pentium M+). Can also run on x86_64 machines (not recommended). Requires SSE2 and CMOV.
* '''armv7''': The 32-bit ARM only execution state of the ARMv7 devices machines.
* '''x86_64''': 64-bit Intel and AMD processors commonly found in personal computers (e.g. Core i7, Ryzen 7)
* '''aarch64''': The 64-bit ARM only execution state of the ARMv8 device machines.
'''Please check [https://alpinelinux.org/downloads Download] page for media availability on each one''' and check [https://alpinelinux.org/releases/ Release Branches] page for latest.
* '''ppc64le''': for 64-bit big-endian PowerPC and Power ISA processors like some MAC computers.
* '''s390x''': for Server for IBM Z and LinuxONE mainframes.
'''Please check [https://alpinelinux.org/downloads Download] page for media availability on each one''' and check [[Alpine_Linux:Releases|Releases]] pages for latest.


== What kind of release of Alpine Linux are available? ==
== What kinds of release of Alpine Linux are available? ==
Please check the [[Alpine_Linux:Releases|Releases]] page for more information.
Please check the [https://alpinelinux.org/releases/ Release Branches] page for more information.


=Setup=
=Setup=


== What is the difference between 'sys', 'data', and 'diskless' when running 'setup-alpine' or 'setup-disk'? ==
== What is the difference between ''sys'', ''data'', and ''diskless'' when running <code>setup-alpine</code> or <code>setup-disk</code>? ==
'''sys:''' This mode is a traditional disk install. The following partitions will be created on the disk: <nowiki>/boot</nowiki>, <nowiki>/</nowiki> (filesystem root) and <nowiki>swap</nowiki>.<br>
 
'''sys:''' This mode is a traditional disk install. The following partitions will be created on the disk: ''/boot/'', ''/'' (filesystem root) and ''swap''.
This mode may be used for development boxes, desktops, virtual servers, etc.
This mode may be used for development boxes, desktops, virtual servers, etc.


'''data:''' This mode uses your disk(s) for data storage, not for the operating system. Runs from the media and only <nowiki>/var</nowiki> is created on disk.  The system itself will run from tmpfs (RAM).  Use this mode if you only want to use the disk(s) for a mailspool, databases, logs, etc.
'''data:''' This mode uses your disk(s) 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.


'''diskless:''' No disks are to be used. [[Alpine local backup]] may still be used in this mode.
'''diskless:''' No disks are to be used. [[Alpine local backup]] may still be used in this mode.


These modes are explained further [[Installation#Overview_of_run_modes_for_Alpine_system|on the '''Installation''' page]].
These modes are explained further on the [[Installation#Installation_Overview|'''Installation''']] page.


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


To upgrade to a new stable release or edge:
To upgrade to a new stable release or edge:
<code>apk upgrade --available</code>
{{ic|apk upgrade --available}}


==My cron jobs don't run?==
==Why don't my cron jobs run?==


Start service ''crond'' and add it to runlevel:
Start service ''crond'' and add it to the default runlevel:


: {{cmd|rc-service crond start && rc-update add crond}}
: {{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 {{path|/etc/periodic}} - there's a {{path|15min}} folder, plus ones for {{path|hourly}}, {{path|daily}}, {{path|weekly}} and {{path|monthly}} scripts.
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.


You can check whether your scripts are likely to run using the command:
To check whether your scripts are likely to run, use the ''run-parts'' command, for example:


: {{cmd|run-parts --test /etc/periodic/[foldername]}} - for example: ''run-parts --test /etc/periodic/15min''
: {{cmd|run-parts --test /etc/periodic/15min}}


This command will tell you what should run but will not actually execute the scripts.
This command will tell you what should run but will not actually execute the scripts.
Line 97: Line 99:
If the results of the test are not as expected, check the following:
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 a+x [scriptname]}}
* 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 :<pre>#!/bin/sh</pre>
* Make sure the first line of your script is <code>#!/bin/sh</code>
* Do not put file extensions on your script names - this stops them from working; for example: {{path|myscript}} will run, but {{path|myscript.sh}} won't
* 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 =
= Time and timezones =
Line 105: Line 107:
== How do I set the local timezone? ==
== How do I set the local timezone? ==


Starting in Alpine 2.2, setting the timezone can be done through the [[Setup-alpine|setup-alpine]] script, and no manual settings should be necessary.<br>
If you wish to edit the ''timezone'' (TZ) after installation, run the [[Alpine_setup_scripts#setup-timezone|setup-timezone]] script.
If you wish to edit the timezone after installation, run the [[Alpine_setup_scripts|setup-timezone]] script.


= Packages =
= Packages =


== Can you build an apk package for ...? ==
== Can you build an APK package for ...? ==
Yes, we probably can.<br>
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.
Please create an [https://gitlab.alpinelinux.org/alpine/aports/issues/new issue] in the [https://gitlab.alpinelinux.org bugtracker]. Prefix with "feat" in title and include a short description (one-line), an url for the home page, and an url for the source package.


== How can I build my own package? ==
== How can I build my own package? ==
Line 119: Line 119:
== What does "required by: world[$pkgname]" mean? ==
== What does "required by: world[$pkgname]" mean? ==


It means that the package you try to install does not exist in the repositories you have configured in <code>/etc/apk/repositories</code>. Maybe you forgot to add community, testing or unmaintained to /etc/apk/repositories?
It means that the package you tried to install does not exist in the repositories you have configured.  
 
Maybe you forgot to add community, testing or unmaintained to {{path|/etc/apk/repositories}}?
 
Or is the package in a [[Alpine Package Keeper#Repository pinning|pinned repository]] and you forgot to suffix the package with the repo tag? Example:


== How can i find out if a certain package exists in alpine? ==
{{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]
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 ==
== WARNING: Ignoring APKINDEX.xxxx.tar.gz ==
If you get <code>WARNING: Ignoring APKINDEX.xxxx.tar.gz: No such file or directory</code> while running package related tools, check your {{path|/etc/apk/repositories}} file if an entry points to {{path|.../v2.4/testing/}}. This directory is gone.
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
To check the content of the repositories file
Line 150: Line 156:


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


Don't forget to backup your settings!
Don't forget to backup your settings!
Line 166: Line 172:
{{cmd|apk add less}}
{{cmd|apk add less}}


= Old questions, no longer freqently asked =
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 ==
 
If you launch {{ic|lsusb}} or {{ic|lspci}} on a minimal installation, there's no device descriptions, and the latter doesn't exist.
This can be fixed by installing the hwdata tables, '''{{pkg|hwdata-usb}}''' or '''{{pkg|hwdata-pci}}''' respectively. For {{ic|lspci}}, add '''{{pkg|pciutils}}'''.
 
= Old questions, no longer frequently asked =


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


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


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


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


The modules and firmware are both special images which are mounted as read-only.<br>
The modules and firmware are both special images which are mounted as read-only.<br />
To fix this issue you can copy the firmware directory to your writeable media (cf/usb) and copy your custom firmware to it.<br>
To fix this issue you can copy the firmware directory to your writeable media (cf/usb) and copy your custom firmware to it.<br />
After reboot Alpine should automatically use the directory on your local storage instead of the loopback device.
After reboot Alpine should automatically use the directory on your local storage instead of the loopback device.
== How do I play my .ogg/.mp3 files? ==
First, the sound card should be recognized (you must have {{path|/dev/snd/*****}} files)
{{pkg|sox}}, {{pkg|mpg123}}, etc all use the oss sound driver, while Alpine uses ALSA drivers.<br>
So you need to load the snd-pcm-oss compatibility module.<br>
While you're at it, you might need {{pkg|aumix}} to turn up the sound volume
{{cmd|echo snd-pcm-oss >> /etc/modules
modprobe snd-pcm-oss
apk_add aumix sox
aumix (set volume settings)
play really_cool_song.mp3}}


== OpenNTPD reports an error with "adjtime" ==
== OpenNTPD reports an error with "adjtime" ==
Line 205: Line 208:
  adjtime failed: Invalid argument     
  adjtime failed: Invalid argument     


{{pkg|openntpd}} is supposed to make small adjustments in the time without causing time jumps.<br>
{{pkg|openntpd}} is supposed to make small adjustments in the time without causing time jumps.<br />
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)
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)


Line 211: Line 214:


== Using a cron job to keep the time in sync ==
== Using a cron job to keep the time in sync ==
Add the following to {{path|/etc/periodic/daily}} (or use another folder under the {{path|/etc/periodic}} heirarchy if you want to run the script more/less frequently)
Add the following to {{path|/etc/periodic/daily}} (or use another folder under the {{path|/etc/periodic}} hierarchy if you want to run the script more/less frequently)


Example: file called {{path|do-ntp}}
Example: file called {{path|do-ntp}}
Line 218: Line 221:
ntpd -d -q -n -p uk.pool.ntp.org</pre>
ntpd -d -q -n -p uk.pool.ntp.org</pre>


This queries the uk time server pool - you can modify this to suit your localisation, or just use ''pool.ntp.org''. More info here: [http://www.pool.ntp.org/zone/@ http://www.pool.ntp.org/zone/@]
This queries the uk time server pool - you can modify this to suit your localisation, or just use ''pool.ntp.org''. More info here: [https://www.pool.ntp.org/zone/@ https://www.pool.ntp.org/zone/@]


== Windows clients reports an error when trying to sync ==
== 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.
{{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 {{pkg|openntpd}} server.
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.
Only thing to do is wait, do something else for 15-20mins and then check.

Latest revision as of 15:36, 3 January 2024

This is a list of frequently asked questions about Alpine Linux.
If your question is not answered on this page, use the search box above to find work in progress pages not linked here, or in case of no answer, edit this page and write down your question.

Tip: Prepare your question. Think it through. Make it simple and understandable.

General

Alpine Linux is used heavily in containers (e.g. Docker images) on servers, so many of its main packages are focused on server services.

Where to start?

The Installation page and the Post Installation section on that page, provide a basic orientation.

A broader overview may be found on the official About page and at the 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 bugtracker, but search it first to see if the issue has already been reported.

Are there any details about the releases available?

Yes, please check the releases page.

How can I contribute?

You can contribute by:

Please visit the Contribute page to read more about this topic.

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

The man command and man pages are not installed by default.

Install the man command:

# apk add mandoc

Install basic manual pages. man-pages package provides the system's core manual pages:

# apk add man-pages

Install the apropos command to search in man pages:

# apk add mandoc-apropos

Once installed, add documentation for the package where you need it. For example, say you installed nftables and you now require its man pages:

# apk add nftables-doc

To always install the documentation companion package add the docs meta package. Keep in mind not all packages have a corresponding documentation package and even when it has one it may not include man pages:

# apk add docs

What is the difference between edge and stable releases?

Stable releases 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.

Edge is more of a rolling-release, with the latest and greatest packages available in the online repositories.
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?

  • aarch64: 64-bit ARM processors (e.g. Raspberry Pi 4)
  • armhf: 32-bit ARMv6 processors with a floating point unit (e.g. Raspberry Pi 1) (armv6hf)
  • armv7: 32-bit ARMv7 processors with a floating point unit (armv7hf)
  • s390x: IBM mainframes using the z/Architecture (z196 minimum)
  • ppc64le: 64-bit little-endian POWER devices (e.g. Raptor Talos II) (POWER8 minimum)
  • x86: 32-bit Intel and AMD processors commonly found in older personal computers (e.g. Pentium M+). Can also run on x86_64 machines (not recommended). Requires SSE2 and CMOV.
  • x86_64: 64-bit Intel and AMD processors commonly found in personal computers (e.g. Core i7, Ryzen 7)

Please check Download page for media availability on each one and check Release Branches page for latest.

What kinds of release of Alpine Linux are available?

Please check the Release Branches page for more information.

Setup

What is the difference between sys, data, and diskless when running setup-alpine or setup-disk?

sys: This mode is a traditional disk install. The following partitions will be created on the disk: /boot/, / (filesystem root) and swap. This mode may be used for development boxes, desktops, virtual servers, etc.

data: This mode uses your disk(s) 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.

diskless: No disks are to be used. Alpine local backup may still be used in this mode.

These modes are explained further on the Installation page.

How do I upgrade Alpine?

To upgrade to a new stable release or edge: apk upgrade --available

Why don't my cron jobs run?

Start service crond and add it to the default runlevel:

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:

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

    chmod +x /etc/periodic/[path/scriptname]

  • Make sure the first line of your script is #!/bin/sh
  • Do not use periods on your script file names - this stops them from working; for example: /etc/periodic/daily/myscript will run, but /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 setup-timezone script.

Packages

Can you build an APK package for ...?

Please create an issue in the 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 repositories you have configured.

Maybe you forgot to add community, testing or unmaintained to /etc/apk/repositories?

Or is the package in a pinned repository and you forgot to suffix the package with the repo tag? Example:

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 apk search $pkgname should get you sorted. If you want to search all repositories have a look at the online pkg oracle

WARNING: Ignoring APKINDEX.xxxx.tar.gz

If you get WARNING: Ignoring APKINDEX.xxxx.tar.gz: No such file or directory while running package related tools, check your /etc/apk/repositories file.

To check the content of the repositories file

cat /etc/apk/repositories

or

setup-apkrepos

Dynamic DNS

How do I schedule a regular dynamic DNS update?

You'll want to install the ez-ipupdate package:

apk add ez-ipupdate

After that, create a new file at /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:

mkdir /var/cache/ez-ipupdate lbu add /var/cache/ez-ipupdate

Then schedule a new cron job with this command:

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!

lbu ci

Terminal

How to enable/fix colors for git?

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

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

apk add less

Additionally, for colorized diff while using verbose commit (git commit -v), add this to shell init scripts (e.g.: ~/.profile):

Contents of ~/.profile

export GIT_EDITOR=vim

Fix lacking lsusb / lspci output

If you launch lsusb or lspci on a minimal installation, there's no device descriptions, and the latter doesn't exist. This can be fixed by installing the hwdata tables, hwdata-usb or hwdata-pci respectively. For lspci, add pciutils.

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 syslinux.cfg.

How do I remove the CD-ROM?

Since the modloop loopback device is on CD-ROM you cannot just run eject. You need to unmount the modloop first.
Unmounting both the modloop and the CDROM in one step can be done by executing:

/etc/init.d/modloop stop

Then it's possible to eject the CD-ROM:

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    

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 /etc/conf.d/ntpd.

Using a cron job to keep the time in sync

Add the following to /etc/periodic/daily (or use another folder under the /etc/periodic hierarchy if you want to run the script more/less frequently)

Example: file called do-ntp

#!/bin/sh
ntpd -d -q -n -p uk.pool.ntp.org

This queries the uk time server pool - you can modify this to suit your localisation, or just use pool.ntp.org. More info here: https://www.pool.ntp.org/zone/@

Windows clients reports an error when trying to sync

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.