Installation: Difference between revisions

From Alpine Linux
(Undo revision 30806 by Dummy account (talk))
Tag: Undo
 
(405 intermediate revisions by 35 users not shown)
Line 1: Line 1:
[[Image:hdd_mount.png|left|link=]]
[[Image:hdd_mount.png|left|link=]]
<br />
<br />


This page exists to provide a basic overview to get started. Before actually installing, it can help to skim through the [[Alpine_Linux:FAQ| Frequently Asked Questions (FAQ)]], as well as to refer to the official installation guide at [https://docs.alpinelinux.org/ docs.alpinelinux.org].


{{Tip|This is a wiki!
If something isn't correct, or is incomplete, you will have to figure it out, or ask for the correct solution in the [https://alpinelinux.org/community/ community].


And then carefully [[Help:Editing|edit]] the wiki page.


This page explains the basics to get started. But before actually installing, it can also help to skim through the [[Alpine_Linux:FAQ| Frequenty Asked Questions (FAQ)]].
Just as those before who did it for you.}}
 


== Minimal Hardware Requirements ==
== Minimal Hardware Requirements ==
{{Main|Requirements}}
* At least 128 MB of RAM. [A graphical desktop system may require up to 512 minimum.]. Note that an installation itself (from ISO) generally requires at least 320 MB during installation.
* At least 0-700 MB space on a writable storage device. [Only required in [[#System Disk Mode|"sys"]] or [[#Data Disk Mode|"data"]] mode installations. It is optional in [[#Diskless Mode|"diskless"]] mode, where it may be used to save newer data and configurations states of a running system.]
* A working internet connection is required to complete [[#System Disk Mode|"sys"]] mode installation or use '''Extended image''' if available for your architecture.


* At least 100 MB of RAM. [A graphical desktop system may require up to 1 GB minimum.]
{{Note|Refer [[#Custom Installation Instructions|custom installation instructions]] for headless system, virtualization etc. Most of the steps outlined on this page applies to all [[Architecture#Architectures_supported|Architectures]] supported by Alpine Linux. For more specific installation instructions, refer to their respective pages.}}
* At least 0-700 MB space on a writable storage device. [Only required in "sys" or "data" mode installations (explained below). It is optional in "diskless" mode, to save newer data states and configurations of a running system.]


== Installation Overview ==
== Installation Overview ==


=== The general course of actions ===
Alpine Linux can be installed and run in [[Setting_up_disks_manually#Alpine_Linux_modes|three modes]]  i.e [[#Diskless_Mode|Diskless Mode]], [[#Data_Disk_Mode|Data Disk Mode]] and [[#System_Disk_Mode|System Disk Mode]]. The installation procedure for Alpine Linux '''requires basic understanding of the three modes''' explained in brief below:
[Note: For single-board-computer (SBC) architectures which can not boot .iso images, see e.g. [[Alpine_on_ARM|Alpine on ARM]] for peculiarities.]


==== Diskless Mode ====
{{Main|Diskless Mode}}
In Diskless mode the entire operating system with all applications are first loaded into RAM and then only run from there. This mode is extremely fast and can save on unnecessary disk spin-ups, power, and wear.  Alpine Linux uses this method to boot the .iso installation images. The [[Alpine_setup_scripts#setup-alpine|<code>setup-alpine</code>]] script configures the installed system to continue to boot like this if "disk=none" is specified.


As usual, the regular installation procedure starts with three basic steps (additional details for all the steps follow [[Installation#additional details|below]]):<br>
==== Data Disk Mode ====
{{Main|Data Disk Mode}}
In Data Disk mode also the operating system  runs from system RAM, thus it enjoys the same accelerated operation speed as "diskless" mode. However, swap storage and the entire {{Path|/var}} directory tree get mounted from a persistent storage device. This mode is useful for having RAM accelerated servers with variable amounts of user-data that exceed the available RAM size.


==== System Disk Mode ====


'''1.)''' Downloading and verifying the proper [http://alpinelinux.org/downloads stable-release ISO installation image-file] for the computer's architecture, and the corresponding <code>sha256</code> (checksum) and <code>GPG</code> (signature) files.  
System or '''sys''' Disk Mode is the traditional hard-disk install. Alpine Linux can be installed to an entire [[#setup-alpine based System Disk Install|'''hard disk''']] using <code>setup-alpine</code> script or to custom partitions using [[Setting_up_disks_manually|<code>setup-disk</code>]]. For further info, refer [[Setting_up_disks_manually|System Disk Mode]].  


'''2.)''' Either burning the ISO image-file onto a blank CD/DVD/Blu-ray disk with a disk burning software, or flashing the installation image onto a bootable storage device (USB-device, CF-/MMC-/SD-card, floppy, ...).
=== General course of action ===


'''3.)''' Booting the computer from the prepared disk or storage device.
It is really helpful for many use cases to [[#Preparing for the installation|prepare]] and complete the [[#Installation Step Details|installation]] until the [[#Base configuration|base configuration]] step, then proceed with installation of the target system with any one of the various [[#Alternative courses of action|alternative]] courses of action.


=== Alternative courses of action ===


The boot process then copies the entire operating system into the RAM, and then runs it completely from RAM. This means that the running command line environment does not depend on reading from the (possibly slow) initial boot media anymore.
Examples of preparation options:


Log-in is possible as the user <code>root</code> with its initially empty password.
* Download some specific driver to configure the hardware, and/or install some software tool that may be missing in the live system by using the Alpine package manager <code>[[Alpine Package Keeper|apk]]</code>. 
* Do a [[Setting up disks manually#Manual partitioning|manual partitioning]] of the hard disk that avoids overwrite of an entire disk.


Then an interactive script called <code>[[Alpine_setup_scripts#setup-alpine|setup-alpine]]</code> is available at the command line, to configure and install the initial Alpine Linux system.
Examples of such options:


If a custom partition layout of the harddisk is desired, it may be configured beforehand. For options to set up RAID, encryption, LVM, etc., see [[Setting_up_disks_manually]]. Partitioning with the preinstalled, most basic tool is possible with <code>fdisk <target device></code>.
* To install Alpine Linux on an '''entire hard disk''' with optional [[Alpine setup scripts#Environment Variables|environment variables]], proceed to [[#setup-alpine based System Disk Install|setup-alpine based System Disk Install]].
* Use {{ic|setup-disk}} script to complete a [[Setting up disks manually|traditional hard disk installation]] on a partition or to [[Dualbooting|dualboot]] or to configure [[Setting up disks manually#RAID|RAID]], [[Setting up disks manually#Encryption|encryption]] or [[Setting up disks manually#LVM|LVM]] for [[#System Disk Mode|"system"]] disk mode or to add a [[#Data Disk Mode|"data"]] mode partition.
* Create a [[Create a Bootable Device#Using setup-bootable|customizable boot media]] i.e a boot device with a writable filesystem for '''[[#Diskless Mode|diskless]]''' or '''[[#Data Disk Mode|data]]''' disk-mode.
* Configure a [[Diskless Mode#Using an internal disk for persistent storage|internal disk for persistent storage]] to save the local configuration state and local package cache for the [[#Diskless Mode|diskless]] system or '''[[#Data Disk Mode|data]]''' disk-mode.


There are also more specific [[Alpine_setup_scripts|setup-scripts]] available. As well as the [[Alpine_Linux_package_management|apk package manager]] to install any tool that may be missing. The command line allows to prepare the system before running the interactive <code>[[Alpine_setup_scripts#setup-alpine|setup-alpine]]</code> script, or, to fine-tune a newly installed system before finally booting it for the first time.
There are many more [[Alpine setup scripts|setup-scripts]] available. All these tools may also be run later to adjust specific configurations. For example, to set up a graphical environment as covered under [[#Post-Installation|Post-Installation]] below.


Note that <code>[[Alpine_setup_scripts#setup-alpine|setup-alpine]]</code> can configure the system to boot into one of three '''Alpinelinux disk modes''', "diskless", "data", and "sys":
== Preparing for the installation ==


==='''Diskless Mode'''===  
=== Downloading installation image ===
This is the default boot mode of the .iso images, and <code>[[Alpine_setup_scripts#setup-alpine|setup-alpine]]</code> configures this if selecting to install to "disk=none". It means that the whole operating system and all applications are loaded into, and then run from, RAM memory. This is extremely fast and can save on unnecessary disk spin-ups, power, and wear.


Customized configurations and package selections may be preserved across reboots, by committing a local backup of the system state to writable storage with <code>[[Alpine_local_backup|lbu commit]]</code>. And booting with additionally installed packages may also be accellerated by enabling a [[Alpine_Linux_package_management#Local_Cache|local package cache]].
Installation image files are available in the '''iso''', '''tar.gz''', and '''img.gz''' formats. Download the [https://alpinelinux.org/downloads/ stable release installation image file] for the target computer's architecture with the corresponding <code>sha256</code> checksum and <code>GPG</code> signature files.
{{Tip|Only download the <code>sha256</code> checksum and <code>GPG</code> signature files from the [https://alpinelinux.org/downloads/ official site] and not from mirrors.}}


[ [https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10473 FIXME-1]: Local configs and package caching still needs [[Alpine_local_backup#Saving_and_loading_ISO_image_customizations| some manual steps]] to prepare a partition before running <code>setup-alpine</code> and to commit this configuration afterwards.]
Now you have three files in the following format:
<pre>
alpine-standard-*.iso
alpine-standard-*.iso.sha256
alpine-standard-*.iso.asc
</pre>


To allow for local backups, <code>setup-alpine</code> can configure to store the configs and the package cache on a writable partition. (That same partition may later also be used by individually configuring some important applications to keep their run-time data on it.)
<code>alpine-standard-{{AlpineLatest}}-x86_64.iso</code> is the '''standard''' image file for version '''{{AlpineLatest}}''' and the '''x86_64''' architecture in the '''iso''' format.


The boot device of the newly configured local system may remain the initial (and possibly read-only) installation media. But it is also possible to copy the boot system to a partition (e.g. /dev/sdXY) with <code>setup-bootable /dev/sdXY</code>.
=== Verifying downloaded image ===


==='''Data Disk Mode'''===
From Security point of view, verify the downloaded image file for both checksum and GPG signature before proceeding further. The three required utilities i.e <code>sha256</code>, <code>curl</code> and <code>gpg</code> or their equivalents are available in every operating system including Linux, windows, Mac and BSD derivaties.  
This mode is still accelerated by running the system from RAM, however swap storage and the whole {{Path|/var}} directory tree gets mounted from a persistent storage device (two newly created partitions). The directory {{Path|/var}} holds e.g. all log files, mailspools, databases, etc., as well as <code>[[Alpine_local_backup|lbu]]</code> backup commits and the package cache. The mode is useful for having RAM accelerated servers with amounts of variable user-data that exceed the available RAM size, and to let the entire current system state (not just the boot state) survive a system crash according to the particular filesystem's guarantees.  


[ [https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10474 FIXME-2]: Setup-alpine can not yet configure to store lbu configs to the "data disk" after configuring the data partition. One must still first select to save configs to "none" in setup-alpine (the new data partition is not listed), and has to manually edit /etc/lbu/lbu.conf to set e.g. LBU_MEDIA=sda2, execute a corresponding <code>echo "/dev/sda2 /media/sda2 vfat rw 0 0" >> /etc/fstab</code> afterwards, and save the config with <code>lbu commit</code> to have the partition (here sda2) mounted when booting.]
{{Tip|Ensure that all the three downloaded files remain in the same folder. If not, adjust the commands accordingly.}}


In data disk mode, the boot device may also remain the initial (and possibly read-only) installation media, or be copied over to a partition (e.g. /dev/sdXY) with <code>setup-bootable /dev/sdXY</code>.
The <code>sha256</code> checksum verifies the integrity of the downloaded image i.e no modifications occurred during download.
{{Cmd|sha256sum -c alpine-*.iso.'''sha256'''}}


==='''System Disk Mode'''===
The <code>GPG</code> signature verifies the link between the downloaded image to the individual who signed it. Signature verification involves two steps:
This is a traditional hard-disk install. If this mode is selected, the <code>[[setup-alpine]]</code> script defaults to create three partitions on the selected storage device, {{Path|/boot}}, {{Path|swap}} and {{Path|/}} (the filesystem root). This mode may be used for generic [[Desktops|desktop]] and development machines, for example.


== Additional Details ==
Step 1. Download and import the gpg signature from official website
{{Cmd|curl https://alpinelinux.org/keys/ncopa.asc &#124; gpg --import ;}}


{{Expand| }}
Step 2. Verify that the image signature matches with the one downloaded in Step 1.
{{Cmd|gpg --verify alpine-*.iso.'''asc''' alpine-*.'''iso'''}}


This "Additional Details" section needs to be consolidated with the work at '''[https://docs.alpinelinux.org https://docs.alpinelinux.org] (not finished)'''
=== Preparing installation media  ===
(Restructuring things there, moving and linking from here or there?).
{{Seealso|Burning ISOs}}


{{Warning|All data currently on the installation media will be '''erased''', when Alpine Linux installation image is written on it. Correctly identify the device name for the installation media using commands <code>lsblk</code> and <code>blkid</code>.}}
If downloaded image file is in '''img.gz''' format, unzip it using the command {{ic|gunzip alpine-rpi-{{AlpineLatest}}-aarch64.img.gz}} to {{ic|alpine-rpi-{{AlpineLatest}}-aarch64.img}} first before using with {{ic|dd}} command. In Linux {{ic|dd}} command can be used to write image files in both '''iso''' and '''img''' format to the installation media.


=== Verifying the downloaded image-file ===
If '''tar.gz''' format image file is downloaded, follow the [[Create a Bootable Device#Manually copying Alpine files|instructions]] to create the installation media.


{| class="wikitable" style="width:95%; align=center"
Modify the input file('''if''')  of the {{ic|dd}} command according to the name and path to your image file and and the target device i.e output file('''of''') should be a device name '''/dev/sdX''' instead of partition like '''/dev/sdbXY''':{{Cmd|# dd if{{=}}alpine-standard-{{AlpineLatest}}-x86_64.iso of{{=}}/dev/sdX bs{{=}}4M status{{=}}progress; eject /dev/sdX}}
|+ Commands to verify the checksum and GPG signature of a downloaded image-file on different systems.
|-
! width=100px |  OS type
!  <code>SHA256</code> check !! <code>SHA256</code> calculation (to be compared manually) !! <code>GPG</code> signature verification
|-
! Linux
| <code>sha256sum -c alpine-*.iso.sha256</code> ||        || <code>curl https://alpinelinux.org/keys/ncopa.asc &#124; gpg --import ;</code>
<code> gpg --verify alpine-<version>.iso.asc alpine-<version>.iso</code>
|-
! MACOS 
| - ? -  || <code>shasum -a 256 alpine-*.iso</code> || - ? -
|-
! BSD 
| - ? - || <code>/usr/local/bin/shasum -a 256 alpine-*.iso</code> || - ? -
|-
! Windows (PowerShell installed)
|                - ? -            || <code>Get-FileHash .\alpine-<image-version>.iso -Algorithm SHA256</code> || - ? -
|}


=== Flashing (direct data writing) the installation image-file onto a device or media  ===
If your version of <code>dd</code> does not support the option "status=progress", remove it. The <code>eject</code> command removes the target device from the system and ensures the write cache is completely flushed.


In Windows and Mac OS, [https://www.balena.io/etcher/  Etcher] can be used to create an installation media.


Under Unix (and thus Linux), "everything is a file" and the data in the image-file can be written onto a device or media with the <code>dd</code> command. Afterwards, <code>eject</code> can remove the target device from the system, to ensure the completion of all writes and clearing of the cache.
===  Verifying Installation media ===


dd if=<iso-file-to-read-in> of=<target-device-node-to-write-out-to> bs=4M oflag=sync status=progress; eject <target-device-node-to-write-out-to>
After detaching and re-attaching the device, a bit-wise comparison can verify the data written to the device (instead of just data buffered in RAM). If the comparison terminates with an end-of-file error on the .iso file side, all the contents from the image have been written (and re-read) successfully:


Be careful to correctly identify the target device to overwrite, because all previous data on it will be lost! All connected "bulk storage devices" can be listed with <code><nowiki>lsblk</nowiki></code> and <code><nowiki>blkid</nowiki></code>.
{{Cmd|# cmp ~/Downloads/alpine-standard-{{AlpineLatest}}-x86_64.iso /dev/sdX
cmp: EOF on alpine-standard-{{AlpineLatest}}-x86_64.iso</Code>}}


# lsblk
=== Booting Installation Media ===
NAME            MAJ:MIN RM  SIZE RO TYPE  MOUNTPOINT
sdX              0:0    0  64,0G  0 disk 
├─sdX1            0:1    0    2G  0 part 
└─sdX2            0:2    0    30G  0 part  /mnt/sdX2
# blkid
/dev/sdX1: LABEL="some" UUID="..." TYPE="vfat"
/dev/sdX2: LABEL="other" UUID="..." TYPE="ext4"


For example, if /dev/sdX is the desired target device to write the image to here, then first make sure to un-mount all mounted partitions of the target device individually. For example sdX1 and sdX2.
Insert the [[#Preparing_installation_media|Installation media]] to a proper drive or port of the computer and turn the machine on, or restart it, if already running.
{{Note| To successfully boot and install Alpine Linux, disable [[UEFI#Secure boot|secure boot]] in the BIOS. Once Alpine Linux is installed, this can be [[UEFI_Secure_Boot|enabled]].}}
If the computer does not automatically boot from the desired device, one needs to bring up the boot menu and choose the media to boot from. Depending on the computer, the menu may be accessed by repeatedly pressing a key quickly when booting starts. Some computers require that you press the button ''before'' starting the computer and hold it down while the computer boots. Typical keys are:  {{key|F9}}-{{key|F12}}, sometimes {{key|F7}} or {{key|F8}}. If these don't bring up the boot menu, it may be necessary to enter the BIOS configuration and adjust the boot settings, for which typical keys are: {{key|Del}} {{key|F1}} {{key|F2}} {{key|F6}} or {{key|Esc}}.


umount  /dev/sdX1  /dev/sdX2
== Installation Step Details ==


=== Boot Process ===


For <code>dd</code>'s out-file (<code>of=</code>), however, do '''not''' specify a partition number. For example, write to sdX and not sdX1:
The boot process of the alpine installation image first copies the entire operating system into the RAM memory, and then starts a complete Alpine Linux system from there. It will initially only provide a basic command line environment that does not depend on reading from any (possibly slow) initial boot media, anymore.


Warning: '''This will completely erase the target device /dev/sdX''', so before executing, make sure to really have a backup of the data if still need.
Local log-in is possible as the user <code>root</code>. Initially, the '''root''' user has no password.


dd if=~/Downloads/alpine-standard-3.00.0-x86_64.iso of=/dev/sdX bs=4M oflag=sync status=progress; eject /dev/sdX
At the command prompt, an interactive script named [[Alpine_setup_scripts#setup-alpine|<code>setup-alpine</code>]] is available to configure and install Alpine Linux. The script can be customized by the optional [[Alpine_setup_scripts#Environment_Variables|environment variables]], in case of [[Installation#Data_Disk_Mode|'''"data"''']] or [[Installation#System_Disk_Mode|'''"sys"''']] mode. For e.g {{Codeline|<code>USE_EFI{{=}}1 BOOT_SIZE{{=}}512 setup-alpine</code>}}, sets the disklabel type to gpt, creates 512MB '''/boot''' partition with '''vfat''' filesystem and uses <code>grub</code> as bootloader.


=== Verifying the written installation media ===
=== Base configuration ===


After detaching and re-attaching the device, a bit-wise comparison can verify what has been written to the device (instead of just data buffered in RAM). If the comparison terminates with an end-of-file error on the .iso file side, all the contents from the image has been written (and read again) successfully:
Launch the Alpine Linux Installation by running the [[Alpine_setup_scripts#setup-alpine|<code>setup-alpine</code>]] script :


# cmp ~/Downloads/alpine-standard-3.00.0-x86_64.iso /dev/sdX
{{Cmd|# setup-alpine}}
cmp: EOF on alpine-standard-3.00.0-x86_64.iso


=== Booting from external devices ===
The question-and-answer dialog of <code>setup-alpine</code> takes care of the base configuration. It sets up a network connection to access Internet to configure the system to boot into one of three different Alpine Linux "disk" modes:  [[Installation#Diskless_Mode|'''"diskless"'''(none)]],  [[Installation#Data_Disk_Mode|'''"data"''']]  or [[Installation#System_Disk_Mode|'''"sys"''']]. If you choose to edit any option, the relevant file is opened in [[BusyBox#vi| '''vi''' editor]] for editing.


Insert the boot media to a proper drive or port of the computer and turn the machine on, or restart it, if already running.
{{Tip| If you have access to a wired network, consider using [https://docs.alpinelinux.org/user-handbook/0.1a/Installing/setup_alpine.html#_setup_alpine_q Quick Mode], to complete the base configuration quickly.}}


If the computer does not automatically boot from the desired device, one needs to bring up the boot menu selection for choosing the media to boot from. Depending on the computer the menu may be accessed by quickly (repeatedly) pressing a key when booting starts, or sometimes it is needed to press the button before starting the computer and keep holding it when it boots. Typical keys are: `F9`-`F12`, sometimes `F7` or `F8`. If these don't bring up the boot menu, it may be necessary to enter the BIOS configuration and adjust the boot settings, for which typical keys are: `Del.` `F1` `F2` `F6` or `Esc.`
[[File:Installation-alpine-alpine-setup-3-setup-scripts.png|350px|thumb|right|Example <code>[[Alpine_setup_scripts#setup-alpine|setup-alpine]]</code> session]]
   
The <code>[[Alpine_setup_scripts#setup-alpine|setup-alpine]]</code> script offers the following configuration options:


=== Custom partitioning of the harddisk ===
# '''Keyboard Layout''' (Local keyboard language and usage mode, e.g. ''us'' and variant of ''us-nodeadkeys''.)
# '''Hostname''' (The name for the computer.)
# '''Network ''' (Set up network connection to access Internet.)
#* Available interfaces are: '''eth0''' '''wlan0'''.(List depends on your hardware.)
#* Which one do you want to initialize? (or '?' or 'done') [eth0] (Enter 'done' after configuring '''atleast''' one interface for Internet access.)
#* Do you want to do any manual network configuration? (y/n) [n] (Default uses "DHCP".) 
# '''DNS Servers''' (If none of the interfaces configured in previous step uses dhcp, set DNS server. If unsure, leave DNS domain name blank and using <code>[https://quad9.net/ 9.9.9.9 2620:fe::fe]</code> for DNS is typically adequate.)
# '''Root password''' (the password used to login to the root account)
# '''Timezone''' (Optionally display times/dates in your local time zone)
# '''HTTP/FTP Proxy''' (Proxy server to use for accessing the web/ftp. Use "none" for direct connections to websites and FTP servers.)
# '''Mirror''' (From where to download packages. Choose the organization you trust giving your usage patterns to.)
# '''Set up a user''' (Setting up a regular user account)
# '''NTP''' (Network Time Protocol client used for keeping the system clock in sync with a time server. Default is "busybox".)
# '''SSH''' (Secure SHell remote access server. "OpenSSH" is part of the default install image. Use "none" to disable remote login, e.g. on laptops.)
# In most cases, either one of following line(s) is displayed as follows:
#: '''No disks found.''' or ''' Available disks are: sda (128.0 GB JMicron  Tech )'''
# '''Disk Mode''' ( A pre-setup of the "diskless" system or base configuration is completed by answering "none" when asked for the following questions.)
#* Which disk(s) would you like to use? (or '?' for help or 'none') '''none'''
#* Enter where to store configs (/media/ or 'none') '''none'''
#* The location of the package cache '''none'''


Custom partitioning may be needed for "diskless" or "data disk" mode installs, to create a partition on the harddisk for committing a local backup of the system state to with <code>[[Alpine_local_backup|lbu commit]]</code>, or to use as the /var mount.  
Base configuration is complete with the above step. Refer to the [[#Alternative courses of action|alternative courses of action]] to proceed further.


For a "sys" install, a custom partitioning is only needed if the wanted scheme differs from using a whole disk and creating the default /boot, swap and root partitions.
=== setup-alpine based System Disk Install === 


See [[Setting_up_disks_manually]] about alpine options for RAID, encryption, LVM, etc.
<code>setup-alpine</code> script based system disk installation, needs an ''' entire hard disk(s)''' for Alpine Linux and uses a partitioning layout with (/)root partition, /boot partition and a swap partition, where [[Alpine_setup_scripts#Environment_Variables|environment variables]] determine filesystem, size of the boot partition and the bootloader used.  If your use case matches the above, at the final step of [[#Base configuration|base configuration]], type the appropriate hard disk '''device name''' instead of '''none'''. If multiple disks are chosen, [[Alpine_setup_scripts#RAID|RAID]] is used.
 
Manual partitioning is possible using <code>fdisk <target device></code> which provides a basic text menu interface. A slightly more sophisticated tool can be installed with <code>apk add cfdisk</code>.
* At the '''Disk Mode''' stage, '''sda''' or relevant disk(s) must be chosen in the below screen:
 
** Which disk(s) would you like to use? (or '?' for help or 'none') '''sda'''
=== Questions asked by <code>setup-alpine</code> ===
** Confirmation for the chosen disk(s) appears. ''The following disk is selected:'' '''sda    (128.0 GB JMicron  Tech ).'''
[[File:Installation-alpine-alpine-setup-3-setup-scripts.png|350px|thumb|right|Example <code>setup-alpine</code> session]]
{{Warning|Pay close attention to the disk name and size. If you enter '''sys''' in the next step, no further questions will be asked and data on the chosen disk(s) will be overwritten!. Enter {{key|Ctrl}}+{{key|c}} to abort the installation process. Proceed only if you are 100% sure.}}
* How would you like to use it? ('sys', 'data', 'lvm' or '?' for help) '''sys'''


The <code>[[setup-alpine]]</code> script offers to configure:
If '''sys''' is chosen, the <code>setup-alpine</code> script will complete the traditional hard-disk installation of Alpine Linux on the chosen disk(s) without further questions.  Once the installation is complete, you can skip the next steps and proceed to [[#Reboot|reboot]] the system to boot into the newly installed Alpine Linux and [[Installation#Post-Installation|configure]] further.


* '''Keyboard Layout''' (Local keyboard language and usage mode, e.g. ''us'' and variant of ''us-nodeadkeys''.)
=== Custom partitioning  ===
* '''Hostname''' (The name for the computer.)
* '''Network''' (For example, automatic IP address discovery with the "DHCP" protocol.)
* '''DNS Servers''' (Domain name servers to query. For privacy reasons it is NOT recommended to route every local request to servers like google's <s>8.8.8.8</s> .)
* '''Timezone'''
* '''Proxy''' (Proxy server to use for accessing the web. Use "none" for direct connections to the internet.)
* '''Mirror''' (From where to download packages. Choose the organization to trust giving your usage patterns.)
* '''SSH''' (Remote login server. The "openssh" is part of the default install images. Use "none" to disable remote logins, e.g. on laptops.)
* '''NTP''' (Client package to use for keeping the system clock in sync. Package "chrony" is part of the default install images.)
* '''Disk Mode''' (Select between diskless (disk="none"), "data" or "sys", as described above.)
  '''The data on a chosen device will be overwritten!'''


[[Setting_up_disks_manually#Manual_partitioning|Manual partitioning]] of the harddisk may be needed to prepare the harddisk for "sys" mode install using [[Setting_up_disks_manually|<code>setup-disk</code>]] and for storing the config file using [[Alpine_local_backup|<code>lbu commit</code>]] and package cache for [[Diskless Mode|Diskless]] and for /var mount for [[Data Disk Mode|Data disk]] mode installs. Refer [[Setting up disks manually|Setting up disks manually]] page for specific configurations related to [[Setting_up_disks_manually#RAID|RAID]], [[Setting_up_disks_manually#Encryption|encryption]], [[Setting_up_disks_manually#LVM|LVM]], etc...


=== Preparing for the first boot ===
=== Preparing for the first boot ===
If [[#System_Disk_Mode|System Disk Mode]] of installation was performed, ignore this section and proceed to [[#Reboot|reboot]].


If the configured disk mode was "sys", then simply removing the installation media should be enough to load the newly installed system on next boot.
If the new local system was configured to run in "diskless" or "data" mode, and you do not want keep booting from the initial (and possibly read-only) [[Installation#Preparing_installation_media|installation media]], create a  [[Create_a_Bootable_Device|customizable boot device]]. Once everything is in place, save your customized configuration with {{ic|lbu commit}} before rebooting.


If the new local system was configured to run in "diskless" or "data" mode, and you don't want to keep it booting from the initial (and possibly read-only) installation media, then the boot system needs to be copied to a partition.
=== Reboot ===


The target partition may be identified using <code><nowiki>lsblk</nowiki></code> (after installing it with <code>apk add lsblk</code>) and/or <code>blkid</code>, similar to previously identifying the initial installation media device.
First, remove the initial installation media from the boot drive, or detach it from the port it's connected to. The system may now be power-cycled or rebooted to confirm everything is working correctly. The relevant commands for this are {{ic|poweroff}} or {{ic|reboot}}. Login into the new system with the root account.


Suppose the target device is /dev/sdXY, then this partition can be prepared for booting with <code>setup-bootable /dev/sdXY</code>.
=== Completing the installation ===


If code>setup-bootable</code> table was successful, the initial installation media needs to be detatched for the next boot.
The installation script installs only the base operating system. '''No''' applications e.g. web server, mail server, desktop environment, or web browsers are installed.


=== Rebooting and testing the new system ===
Please look at [[Installation#Post-Installation|Post-Installation]], for some common things to do after installation.


When everthing is ready, the system may be power-cycled or rebooted to confirm that everything is working.
== Custom Installation Instructions ==
 
The relevant commands for this are <code>reboot</code> or <code>poweroff</code>.
 
 
=== Customizing the installation ===
 
The installation script only installs the base operating system. Applications such as a web server, mail server, desktop environment, or web browser are not installed and <code>root</code> is the only user. Please see the "Post-Install" list of links below, for some instructions on how to proceed after installation.
 
= Further Documentation =
 
=== Installing ===


<!-- COMMENT FOR EDITORS
Specific topics should be kept on separate pages and manageable category-pages only must get listed with direct reference on this general page.
-->
* [[Installation on a headless host]]
* [[Kernels]] ''(kernel selection, e.g. for VMs or RPi)''
* [[How to make a custom ISO image with mkimage]] ''(installation media with its own configuration)''
* [[Directly booting an ISO file]] ''(without flashing it to a disk or device)''
* [[Directly booting an ISO file]] ''(without flashing it to a disk or device)''
* [[Tutorials_and_Howtos#Networking|Setting up Networking]] ''(incl. non-standard configurations)''
* [[Alpine Linux in a chroot]]
* [[Netboot Alpine Linux using iPXE]]
* [[:Category:Virtualization|Virtualization]]
* [[Using an answerfile with setup-alpine]]


Also see other [[:Category:Installation|Installation category]] pages.


=== Post-Install ===
== Post-Installation ==


<!-- If you edit post-install, also consider [[Tutorials_and_Howtos#Post-Install]], [[Developer_Documentation#Package_management]] and the Handbook. Here, first there are only most relevant jumping points listed, not exact list duplicates!!!  -->
{{Tip|Alpine Linux packages stay close to the upstream design. Therefore, all upstream documentation about configuring a software package, as well as good configuration guides from other distributions that stay close to upstream, e.g. those in the [https://wiki.archlinux.org/ ArchWiki], or [https://wiki.gentoo.org/wiki/ Gentoo wiki] are to a large degree, also applicable to configuring the software on Alpine Linux, thus can be very useful.}}


<!-- COMMENT FOR EDITORS
If you edit Post-Install,


* [[Setting up a new user]]
  * Consider that there are already [[Tutorials_and_Howtos#Post-Install]], [[Developer_Documentation#Package_management]] [[Daily driver guide]] and the Handbook, please work towards reducing duplication and providing an overview, and maintaining topic details of considerable size on their own pages.
  * Here, only the most relevant jumping off points are listed, not exact list duplicates!!!
  * Keep short-list of links here, as overview to more detailed topic specific pages.
  * Don't aggregate different topics at yet another place.
Any topic related to configuring Alpine as Desktop workstation i.e as a daily driver must go to the [[Daily driver guide]] or [[Tutorials_and_Howtos#Desktop|Desktop]]section. Links to Tutorial and How To's should be added to [[Tutorials_and_Howtos]] and not added here.
-->
* [[Tutorials_and_Howtos#Desktop|Guide to daily drive]] Alpine Linux as a desktop OS
* [[Tutorials_and_Howtos#Services|Hosting services]] like mail/web/ssh/Firewall/VPN servers
* [[Tutorials_and_Howtos#Virtualization|Virtualization]] guide for using Alpine Linux as both guest and host
* Guide to [[OpenRC|OpenRC]] - Init system used to configure services


* [[Enable Community Repository]] ''(providing additional packages)''
== See also ==
* [[Alpine Linux package management|Package Management (apk)]] ''(general search/add/del packages etc.)''
* [[Alpine setup scripts#setup-xorg-base|<code>setup-xorg-base</code>]] ''(display graphics, if required)''
** [[Xfce_Setup]] / [[Desktop-notes]] / [[Xfce_Desktop]] / [[Gnome_Setup]] / [[KDE]]
* [[How to get regular stuff working]] ''(things one may miss with a too lightweight Alpine )''


* [[Alpine_local_backup|Local backup utility <code>lbu</code>]] ''(persisting RAM system configurations)''
** [[Back Up a Flash Memory Installation]] ''("diskless mode" systems)''
** [[Manually_editing_a_existing_apkovl]] ''(the stored custom configs)''
* [[Alpine Linux Init System|Init System (OpenRC)]] ''(configure a service to automatically boot at next reboot)''
** [[Multiple Instances of Services]]
** [[Writing Init Scripts]]
* [[Hosting services on Alpine]] ''(Links to several mail/web/ssh server setup pages)''
* Runnig programs and services in their own [[Firejail Security Sandbox]]
* [[Alpine_Linux_package_management#Upgrade_a_Running_System|Upgrading Alpine]] ''(checking for and installing updates)''
* [[How to make a custom ISO image with mkimage]] ''(to boot your own distro)''
=== Further Help and Information ===
* [[Comparison with other distros]] ''(how common things are done on alpine)''
* [[Running glibc programs]] ''(installation and development)''
<!-- * [[setup-acf]] ''(configures ACF (webconfiguration) so you can manage your box through https)''
* [[Changing passwords for ACF|Changing passwords]]
-->
* [[FAQ|FAQs]]
* [[Tutorials and Howtos]]
* [[Tutorials and Howtos]]
 
* [[Comparison with other distros]] ''(how common things are done on Alpine)''
* [[Contribute|How to Contribute]]
* [[Developer Documentation]]
* [[Alpine_Linux:Wiki_etiquette|Wiki etiquette]] ''to collaborate on this documentation''
 
 
 
{{Tip| Alpine linux packages stay close to the upstream design. Therefore, all upstream documentation about configuring a software package, as well as good configuration guides from other distributions that stay close to upstream, like e.g. in the [https://wiki.archlinux.org/ Arch Wiki], are to a large degree also well applicable to configure the software on alpine linux, thus can be very useful.}}
 
= Other Guides =
 
There may still be something useful to find and sort out of the newbie's install notes in this wiki, but beware that they can contain highly opinionated content and lack explanations.
 
# [[Newbie_Alpine_Ecosystem]]
# [[Alpine newbie install manual]]
# [[Alpine_newbie#Install|Alpine_newbie Install section]]
# [https://mckayemu.github.io/alpineinstalls/ https://mckayemu.github.io/alpineinstalls/ All informatin for Spanish users]


[[Category:Installation]]
[[Category:Installation]]

Latest revision as of 21:00, 28 August 2025


This page exists to provide a basic overview to get started. Before actually installing, it can help to skim through the Frequently Asked Questions (FAQ), as well as to refer to the official installation guide at docs.alpinelinux.org.

Tip: This is a wiki!

If something isn't correct, or is incomplete, you will have to figure it out, or ask for the correct solution in the community.

And then carefully edit the wiki page.

Just as those before who did it for you.

Minimal Hardware Requirements

Main article: Requirements
  • At least 128 MB of RAM. [A graphical desktop system may require up to 512 minimum.]. Note that an installation itself (from ISO) generally requires at least 320 MB during installation.
  • At least 0-700 MB space on a writable storage device. [Only required in "sys" or "data" mode installations. It is optional in "diskless" mode, where it may be used to save newer data and configurations states of a running system.]
  • A working internet connection is required to complete "sys" mode installation or use Extended image if available for your architecture.
Note: Refer custom installation instructions for headless system, virtualization etc. Most of the steps outlined on this page applies to all Architectures supported by Alpine Linux. For more specific installation instructions, refer to their respective pages.

Installation Overview

Alpine Linux can be installed and run in three modes i.e Diskless Mode, Data Disk Mode and System Disk Mode. The installation procedure for Alpine Linux requires basic understanding of the three modes explained in brief below:

Diskless Mode

Main article: Diskless Mode

In Diskless mode the entire operating system with all applications are first loaded into RAM and then only run from there. This mode is extremely fast and can save on unnecessary disk spin-ups, power, and wear. Alpine Linux uses this method to boot the .iso installation images. The setup-alpine script configures the installed system to continue to boot like this if "disk=none" is specified.

Data Disk Mode

Main article: Data Disk Mode

In Data Disk mode also the operating system runs from system RAM, thus it enjoys the same accelerated operation speed as "diskless" mode. However, swap storage and the entire /var directory tree get mounted from a persistent storage device. This mode is useful for having RAM accelerated servers with variable amounts of user-data that exceed the available RAM size.

System Disk Mode

System or sys Disk Mode is the traditional hard-disk install. Alpine Linux can be installed to an entire hard disk using setup-alpine script or to custom partitions using setup-disk. For further info, refer System Disk Mode.

General course of action

It is really helpful for many use cases to prepare and complete the installation until the base configuration step, then proceed with installation of the target system with any one of the various alternative courses of action.

Alternative courses of action

Examples of preparation options:

  • Download some specific driver to configure the hardware, and/or install some software tool that may be missing in the live system by using the Alpine package manager apk.
  • Do a manual partitioning of the hard disk that avoids overwrite of an entire disk.

Examples of such options:

There are many more setup-scripts available. All these tools may also be run later to adjust specific configurations. For example, to set up a graphical environment as covered under Post-Installation below.

Preparing for the installation

Downloading installation image

Installation image files are available in the iso, tar.gz, and img.gz formats. Download the stable release installation image file for the target computer's architecture with the corresponding sha256 checksum and GPG signature files.

Tip: Only download the sha256 checksum and GPG signature files from the official site and not from mirrors.

Now you have three files in the following format: 

alpine-standard-*.iso
alpine-standard-*.iso.sha256
alpine-standard-*.iso.asc

alpine-standard-3.22.1-x86_64.iso is the standard image file for version 3.22.1 and the x86_64 architecture in the iso format.

Verifying downloaded image

From Security point of view, verify the downloaded image file for both checksum and GPG signature before proceeding further. The three required utilities i.e sha256, curl and gpg or their equivalents are available in every operating system including Linux, windows, Mac and BSD derivaties.

Tip: Ensure that all the three downloaded files remain in the same folder. If not, adjust the commands accordingly.

The sha256 checksum verifies the integrity of the downloaded image i.e no modifications occurred during download.

sha256sum -c alpine-*.iso.sha256

The GPG signature verifies the link between the downloaded image to the individual who signed it. Signature verification involves two steps:

Step 1. Download and import the gpg signature from official website

curl https://alpinelinux.org/keys/ncopa.asc | gpg --import ;

Step 2. Verify that the image signature matches with the one downloaded in Step 1.

gpg --verify alpine-*.iso.asc alpine-*.iso

Preparing installation media

See also: Burning ISOs
Warning: All data currently on the installation media will be erased, when Alpine Linux installation image is written on it. Correctly identify the device name for the installation media using commands lsblk and blkid.


If downloaded image file is in img.gz format, unzip it using the command gunzip alpine-rpi-3.22.1-aarch64.img.gz to alpine-rpi-3.22.1-aarch64.img first before using with dd command. In Linux dd command can be used to write image files in both iso and img format to the installation media.

If tar.gz format image file is downloaded, follow the instructions to create the installation media.

Modify the input file(if) of the dd command according to the name and path to your image file and and the target device i.e output file(of) should be a device name /dev/sdX instead of partition like /dev/sdbXY:

# dd if=alpine-standard-3.22.1-x86_64.iso of=/dev/sdX bs=4M status=progress; eject /dev/sdX

If your version of dd does not support the option "status=progress", remove it. The eject command removes the target device from the system and ensures the write cache is completely flushed.

In Windows and Mac OS, Etcher can be used to create an installation media.

Verifying Installation media

After detaching and re-attaching the device, a bit-wise comparison can verify the data written to the device (instead of just data buffered in RAM). If the comparison terminates with an end-of-file error on the .iso file side, all the contents from the image have been written (and re-read) successfully:

# cmp ~/Downloads/alpine-standard-3.22.1-x86_64.iso /dev/sdX cmp: EOF on alpine-standard-3.22.1-x86_64.iso

Booting Installation Media

Insert the Installation media to a proper drive or port of the computer and turn the machine on, or restart it, if already running.

Note: To successfully boot and install Alpine Linux, disable secure boot in the BIOS. Once Alpine Linux is installed, this can be enabled.

If the computer does not automatically boot from the desired device, one needs to bring up the boot menu and choose the media to boot from. Depending on the computer, the menu may be accessed by repeatedly pressing a key quickly when booting starts. Some computers require that you press the button before starting the computer and hold it down while the computer boots. Typical keys are: F9-F12, sometimes F7 or F8. If these don't bring up the boot menu, it may be necessary to enter the BIOS configuration and adjust the boot settings, for which typical keys are: Del F1 F2 F6 or Esc.

Installation Step Details

Boot Process

The boot process of the alpine installation image first copies the entire operating system into the RAM memory, and then starts a complete Alpine Linux system from there. It will initially only provide a basic command line environment that does not depend on reading from any (possibly slow) initial boot media, anymore.

Local log-in is possible as the user root. Initially, the root user has no password.

At the command prompt, an interactive script named setup-alpine is available to configure and install Alpine Linux. The script can be customized by the optional environment variables, in case of "data" or "sys" mode. For e.g USE_EFI=1 BOOT_SIZE=512 setup-alpine, sets the disklabel type to gpt, creates 512MB /boot partition with vfat filesystem and uses grub as bootloader.

Base configuration

Launch the Alpine Linux Installation by running the setup-alpine script :

# setup-alpine

The question-and-answer dialog of setup-alpine takes care of the base configuration. It sets up a network connection to access Internet to configure the system to boot into one of three different Alpine Linux "disk" modes: "diskless"(none), "data" or "sys". If you choose to edit any option, the relevant file is opened in vi editor for editing.

Tip: If you have access to a wired network, consider using Quick Mode, to complete the base configuration quickly.
Example setup-alpine session

The setup-alpine script offers the following configuration options:

  1. Keyboard Layout (Local keyboard language and usage mode, e.g. us and variant of us-nodeadkeys.)
  2. Hostname (The name for the computer.)
  3. Network (Set up network connection to access Internet.)
    • Available interfaces are: eth0 wlan0.(List depends on your hardware.)
    • Which one do you want to initialize? (or '?' or 'done') [eth0] (Enter 'done' after configuring atleast one interface for Internet access.)
    • Do you want to do any manual network configuration? (y/n) [n] (Default uses "DHCP".)
  4. DNS Servers (If none of the interfaces configured in previous step uses dhcp, set DNS server. If unsure, leave DNS domain name blank and using 9.9.9.9 2620:fe::fe for DNS is typically adequate.)
  5. Root password (the password used to login to the root account)
  6. Timezone (Optionally display times/dates in your local time zone)
  7. HTTP/FTP Proxy (Proxy server to use for accessing the web/ftp. Use "none" for direct connections to websites and FTP servers.)
  8. Mirror (From where to download packages. Choose the organization you trust giving your usage patterns to.)
  9. Set up a user (Setting up a regular user account)
  10. NTP (Network Time Protocol client used for keeping the system clock in sync with a time server. Default is "busybox".)
  11. SSH (Secure SHell remote access server. "OpenSSH" is part of the default install image. Use "none" to disable remote login, e.g. on laptops.)
  12. In most cases, either one of following line(s) is displayed as follows:
    No disks found. or Available disks are: sda (128.0 GB JMicron Tech )
  13. Disk Mode ( A pre-setup of the "diskless" system or base configuration is completed by answering "none" when asked for the following questions.)
    • Which disk(s) would you like to use? (or '?' for help or 'none') none
    • Enter where to store configs (/media/ or 'none') none
    • The location of the package cache none

Base configuration is complete with the above step. Refer to the alternative courses of action to proceed further.

setup-alpine based System Disk Install

setup-alpine script based system disk installation, needs an entire hard disk(s) for Alpine Linux and uses a partitioning layout with (/)root partition, /boot partition and a swap partition, where environment variables determine filesystem, size of the boot partition and the bootloader used. If your use case matches the above, at the final step of base configuration, type the appropriate hard disk device name instead of none. If multiple disks are chosen, RAID is used.

  • At the Disk Mode stage, sda or relevant disk(s) must be chosen in the below screen:
    • Which disk(s) would you like to use? (or '?' for help or 'none') sda
    • Confirmation for the chosen disk(s) appears. The following disk is selected: sda (128.0 GB JMicron Tech ).
Warning: Pay close attention to the disk name and size. If you enter sys in the next step, no further questions will be asked and data on the chosen disk(s) will be overwritten!. Enter Ctrl+c to abort the installation process. Proceed only if you are 100% sure.


  • How would you like to use it? ('sys', 'data', 'lvm' or '?' for help) sys

If sys is chosen, the setup-alpine script will complete the traditional hard-disk installation of Alpine Linux on the chosen disk(s) without further questions. Once the installation is complete, you can skip the next steps and proceed to reboot the system to boot into the newly installed Alpine Linux and configure further.

Custom partitioning

Manual partitioning of the harddisk may be needed to prepare the harddisk for "sys" mode install using setup-disk and for storing the config file using lbu commit and package cache for Diskless and for /var mount for Data disk mode installs. Refer Setting up disks manually page for specific configurations related to RAID, encryption, LVM, etc...

Preparing for the first boot

If System Disk Mode of installation was performed, ignore this section and proceed to reboot.

If the new local system was configured to run in "diskless" or "data" mode, and you do not want keep booting from the initial (and possibly read-only) installation media, create a customizable boot device. Once everything is in place, save your customized configuration with lbu commit before rebooting.

Reboot

First, remove the initial installation media from the boot drive, or detach it from the port it's connected to. The system may now be power-cycled or rebooted to confirm everything is working correctly. The relevant commands for this are poweroff or reboot. Login into the new system with the root account.

Completing the installation

The installation script installs only the base operating system. No applications e.g. web server, mail server, desktop environment, or web browsers are installed.

Please look at Post-Installation, for some common things to do after installation.

Custom Installation Instructions

Also see other Installation category pages.

Post-Installation

Tip: Alpine Linux packages stay close to the upstream design. Therefore, all upstream documentation about configuring a software package, as well as good configuration guides from other distributions that stay close to upstream, e.g. those in the ArchWiki, or Gentoo wiki are to a large degree, also applicable to configuring the software on Alpine Linux, thus can be very useful.

See also

Retrieved from "https://wiki.alpinelinux.org/w/index.php?title=Installation&oldid=30807"