Diskless Mode - Revision history

Prabuanand: added clarification on the need for two media. refer redd.it/1rgyl6p

2026-02-28T11:34:08Z

added clarification on the need for two media. refer redd.it/1rgyl6p

← Older revision		Revision as of 11:34, 28 February 2026
Line 3:		Line 3:
	Diskless mode is extremely fast and can save on unnecessary disk spin-ups, power, and wear and suitable for servers. It is similar to what other linux distributions may call a "frugal" install or boot using a "toram" option.		Diskless mode is extremely fast and can save on unnecessary disk spin-ups, power, and wear and suitable for servers. It is similar to what other linux distributions may call a "frugal" install or boot using a "toram" option.

	Alpine Linux provides [[Alpine_local_backup\|Local Backup Utility]]({{ic\|lbu}}) that allows custom configurations and package installations to be optionally preserved or made to "persist" across reboots as [[#Apkovl\|apkovl]] files.		Alpine Linux provides [[Alpine_local_backup\|Local Backup Utility]]({{ic\|lbu}}) that allows custom configurations and package installations to be optionally preserved or made to "persist" across reboots as [[#Apkovl\|apkovl]] files on persistent storage.

	If additional or updated packages have been added to the system, these may also be made available for automatic (re)installation during the boot phase without any (re)downloading, by enabling a [[#Local package cache\|local package cache]].		If additional or updated packages have been added to the system, these may also be made available for automatic (re)installation during the boot phase without any (re)downloading, by enabling a [[#Local package cache\|local package cache]].
Line 11:		Line 11:
	When running the <code>[[Alpine_setup_scripts#setup-alpine\|setup-alpine]]</code> script, if "disk=none" is specified, then Alpine Linux will continue to run in diskless mode. It invokes <code>[[Alpine_setup_scripts#setup-lbu\|setup-lbu]]</code> and <code>[[Alpine_setup_scripts#setup-apkcache\|setup-apkcache]]</code> to use any available writable filesystem on any media other than the read-only installation media for saving the configuration settings as apkovl file and local package cache.		When running the <code>[[Alpine_setup_scripts#setup-alpine\|setup-alpine]]</code> script, if "disk=none" is specified, then Alpine Linux will continue to run in diskless mode. It invokes <code>[[Alpine_setup_scripts#setup-lbu\|setup-lbu]]</code> and <code>[[Alpine_setup_scripts#setup-apkcache\|setup-apkcache]]</code> to use any available writable filesystem on any media other than the read-only installation media for saving the configuration settings as apkovl file and local package cache.

	{{Tip\|~~For Diskless installations~~, ~~create~~ [[#Using customizable boot device for persistent storage\|customizable boot device]] ~~instead of a~~ read-only installation media.}}		{{Tip\|If you are using a single USB flash drive for a diskless install, use a [[#Using customizable boot device for persistent storage\|customizable boot device]] rather than standard read-only installation media. This allows the drive to host both the OS and your persistent storage.}}

	Complete the below preparatory steps depending on the available persistent storage option for apkovl and local package cache. Persistent storage are configured as read-only in {{Path\|/etc/fstab}}, as [[Alpine_local_backup\|lbu]] can temporarily remount them as writable for their operation.		Complete the below preparatory steps depending on the available persistent storage option for apkovl and local package cache. Persistent storage are configured as read-only in {{Path\|/etc/fstab}}, as [[Alpine_local_backup\|lbu]] can temporarily remount them as writable for their operation.

Prabuanand: Reworded sentence(s) related to bugs, moved customizable boot section, removed repetitive wikilinks

2025-11-28T06:37:49Z

Reworded sentence(s) related to bugs, moved customizable boot section, removed repetitive wikilinks

← Older revision		Revision as of 06:37, 28 November 2025
Line 3:		Line 3:
	Diskless mode is extremely fast and can save on unnecessary disk spin-ups, power, and wear and suitable for servers. It is similar to what other linux distributions may call a "frugal" install or boot using a "toram" option.		Diskless mode is extremely fast and can save on unnecessary disk spin-ups, power, and wear and suitable for servers. It is similar to what other linux distributions may call a "frugal" install or boot using a "toram" option.

	Alpine Linux provides [[Alpine_local_backup\|Local Backup Utility]]({{ic\|lbu}}) that allows custom configurations and package installations to be optionally preserved or made to "persist" across reboots as [[#Apkovl\|apkovl]] files. If additional or updated packages have been added to the system, these may also be made available for automatic (re)installation during the boot phase without any (re)downloading, by enabling a [[#Local package cache\|local package cache]].		Alpine Linux provides [[Alpine_local_backup\|Local Backup Utility]]({{ic\|lbu}}) that allows custom configurations and package installations to be optionally preserved or made to "persist" across reboots as [[#Apkovl\|apkovl]] files.

			If additional or updated packages have been added to the system, these may also be made available for automatic (re)installation during the boot phase without any (re)downloading, by enabling a [[#Local package cache\|local package cache]].

	== Diskless installation ==		== Diskless installation ==

	When running the <code>[[Alpine_setup_scripts#setup-alpine\|setup-alpine]]</code> script, if "disk=none" is specified, then Alpine Linux will continue to run in diskless mode. It invokes <code>[[Alpine_setup_scripts#setup-lbu\|setup-lbu]]</code> and <code>[[Alpine_setup_scripts#setup-apkcache\|setup-apkcache]]</code> to use any available writable filesystem on any media other than the read-only ~~[[Installation#Preparing_installation_media\|~~installation media]] for saving the configuration settings as [[#~~Apkovl~~\|~~apkovl~~]] ~~file~~ and [[~~#Local package cache~~\|~~local package cache~~]].		When running the <code>[[Alpine_setup_scripts#setup-alpine\|setup-alpine]]</code> script, if "disk=none" is specified, then Alpine Linux will continue to run in diskless mode. It invokes <code>[[Alpine_setup_scripts#setup-lbu\|setup-lbu]]</code> and <code>[[Alpine_setup_scripts#setup-apkcache\|setup-apkcache]]</code> to use any available writable filesystem on any media other than the read-only installation media for saving the configuration settings as apkovl file and local package cache.

			{{Tip\|For Diskless installations, create [[#Using customizable boot device for persistent storage\|customizable boot device]] instead of a read-only installation media.}}

			Complete the below preparatory steps depending on the available persistent storage option for apkovl and local package cache. Persistent storage are configured as read-only in {{Path\|/etc/fstab}}, as [[Alpine_local_backup\|lbu]] can temporarily remount them as writable for their operation.

			=== Using customizable boot device for persistent storage ===

	~~{{Tip\|For Diskless installations, create a~~ [[~~Create a Bootable Device~~\|Customizable boot device]] ~~instead of~~ a ~~read~~-~~only installation media~~.}}		A [[Create_a_Bootable_Device\|Customizable boot device]] allows Alpine Linux to boot and run in Diskless mode from a partition with a writable filesystem on USB-Stick/CompactFlash/SDCard or SSD/NVMe harddisk. The [[#Apkovl\|apkovl]] file(s) and [[#Local package cache\|local package cache]] can be stored in this customizable boot device and no other storage is required.

	~~Complete~~ the ~~below preparatory steps depending~~ on the ~~available persistent storage option~~.		# Boot using the [[Create_a_Bootable_Device\|Customizable boot device]].
			# Find out where the customizable boot device is mounted, the location could vary.{{Cmd\|<nowiki># mount \| grep /media
			/dev/sdXY on /media/sdXY type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=utf8,shortname=mixed,errors=remount-ro)
			</nowiki>}}
			# Mount the customizable boot device in rw mode, if required. {{Cmd\|# mount -o remount,rw /media/sdXY}}
			# Proceed to [[#Finishing diskless installation\|Finishing diskless installation]] section without rebooting the computer.

	=== Using an internal disk for persistent storage ===		=== Using an internal disk for persistent storage ===

	~~Due to Bug: [https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10473 #10473] storing~~ local configs on '''internal disks''' requires manual steps, i.e making an entry in {{Path\|/etc/fstab}}, create mountpoint, and mount the partition before running <code>setup-alpine</code> script.		Storing local configs on '''internal disks''' requires manual steps, i.e making an entry in {{Path\|/etc/fstab}}, create mountpoint, and mount the partition before running <code>setup-alpine</code> script due to Issue [https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10473 #10473]. Use only ext4 filesystem partitions on classic drives to store diskless mode states as diskless setup currently doesn't work on btrfs and xfs filesystems, or nvme-based devices as per {{Issue\|11589\|}}.

	# In this case, boot the target diskless system from the ~~[[Installation#Preparing_installation_media\|~~installation media]] and do not proceed after the [[Installation#Boot_Process\|boot process]] stage.		# In this case, boot the target diskless system from the installation media and do not proceed after the [[Installation#Boot_Process\|boot process]] stage.
	# If necessary partition(s) are unavailable, manually [[Setting_up_disks_manually#Creating_partitions\|create]] a partition using <Code>fdisk</Code>. In the below steps, we will use /dev/sdXY as partition number. Adjust the partition identifier as per the output of {{Codeline\|<Code>blkid</Code>}}<br>		# If necessary partition(s) are unavailable, manually [[Setting_up_disks_manually#Creating_partitions\|create]] a partition using <Code>fdisk</Code>. In the below steps, we will use /dev/sdXY as partition number. Adjust the partition identifier as per the output of {{Codeline\|<Code>blkid</Code>}}<br>
	#* Due to Bug: {{Issue\|11589\|The APKOVL loading of diskless setups doesn't work on btrfs and xfs filesystems, or nvme-based devices}}. So use only ext4 filesystem partitions on classic drives to store diskless mode states.
	#* mkfs.ext4 creates ext4 filesystem with 64bit feature enabled by default, but extlinux may not be able to boot with that due to Issue {{Issue\|14895}}. You may need to add "-O ^64bit" to mkfs.ext4 to circumvent this. The below command creates an ext4 partition with disabled journaling, to reduce write operations and allow the disk to spin down after the .apkovl and the packages have been read from the partition during the boot. Install package {{pkg\|<Code>e2fsprogs</code>}} using command {{Codeline\|<Code>apk add e2fsprogs</Code>}}, if the command <Code>mkfs.ext4</Code> is not available.		#* mkfs.ext4 creates ext4 filesystem with 64bit feature enabled by default, but extlinux may not be able to boot with that due to Issue {{Issue\|14895}}. You may need to add "-O ^64bit" to mkfs.ext4 to circumvent this. The below command creates an ext4 partition with disabled journaling, to reduce write operations and allow the disk to spin down after the .apkovl and the packages have been read from the partition during the boot. Install package {{pkg\|<Code>e2fsprogs</code>}} using command {{Codeline\|<Code>apk add e2fsprogs</Code>}}, if the command <Code>mkfs.ext4</Code> is not available.
	#: {{Cmd\|# mkfs.ext4 -O ^has_journal,^64bit /dev/sdXY}}		#: {{Cmd\|# mkfs.ext4 -O ^has_journal,^64bit /dev/sdXY}}
	# ~~Due to a [https://gitlab.alpinelinux.org/alpine/mkinitfs/-/issues/5 bug], the partition can not be mounted to /boot.~~ Configure the /etc/fstab to mount the writable partition to /media/sdXY ~~instead of /boot i.e.~~ conforming to the hot/cold-plug mountpoints.		# Configure the /etc/fstab to mount the writable partition to /media/sdXY conforming to the hot/cold-plug mountpoints.
	#: {{Cmd\|# mkdir /media/sdXY}}		#: {{Cmd\|# mkdir /media/sdXY}}
	#: {{cmd\|# echo "/dev/sdXY /media/sdXY ext4 noatime,ro 0 0" >> /etc/fstab}}		#: {{cmd\|# echo "/dev/sdXY /media/sdXY ext4 noatime,ro 0 0" >> /etc/fstab}}
	~~<!-- Mounting read-only is possible, because the [[Alpine_local_backup\|lbu tools]] can temporarily remount it writable for their operation. -->~~
	# Mount the partitions listed in {{Path\|/etc/fstab}}:{{Cmd\|# <code>mount -a</code>}}		# Mount the partitions listed in {{Path\|/etc/fstab}}:{{Cmd\|# <code>mount -a</code>}}
	# Verify that the changes have been applied correctly by looking at the output of {{Cmd\|$ <code>mount</code>}}		# Verify that the changes have been applied correctly by looking at the output of {{Cmd\|$ <code>mount</code>}}
	~~# Proceed to [[#Finishing diskless installation\|Finishing diskless installation]] section without rebooting the computer.~~

	~~=== Using customizable boot device for persistent storage ===~~

	A [[Create_a_Bootable_Device\|Customizable boot device]] allows Alpine Linux to boot and run in Diskless mode from a partition with a writable filesystem on USB-Stick/CompactFlash/SDCard or SSD/NVMe harddisk. The [[#Apkovl\|apkovl]] file(s) and [[#Local package cache\|local package cache]] can be stored in this customizable boot device and no other storage is required.

	~~# Boot using the [[Create_a_Bootable_Device\|Customizable boot device]].~~
	~~# Find out where the customizable boot device is mounted, the location could vary.{{Cmd\|<nowiki># mount \| grep /media~~
	~~/dev/sdXY on /media/sdXY type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=utf8,shortname=mixed,errors=remount-ro)~~
	~~</nowiki>}}~~
	~~# Mount the customizable boot device in rw mode, if required. {{Cmd\|# mount -o remount,rw /media/sdXY}}~~
	~~<!--~~
	~~# Issue the below commands to create a directory for [[Local_APK_cache\|Local Package Cache]]. {{Cmd\|<nowiki># mkdir /media/sda1/cache~~
	~~# setup-apkcache /media/sda1/cache~~
	~~# ls -l /etc/apk/cache~~
	~~lrwxrwxrwx 1 root root 17 Oct 19 13:16 /etc/apk/cache -> /media/sda1/cache~~
	~~</nowiki>}}-->~~
	# Proceed to [[#Finishing diskless installation\|Finishing diskless installation]] section without rebooting the computer.		# Proceed to [[#Finishing diskless installation\|Finishing diskless installation]] section without rebooting the computer.

Line 51:		Line 45:
	# If <code>setup-alpine</code> has not run before, follow the [[Installation#Installation_Step_Details\|Installation steps]] to complete until the '''Disk & Install''' option appears.		# If <code>setup-alpine</code> has not run before, follow the [[Installation#Installation_Step_Details\|Installation steps]] to complete until the '''Disk & Install''' option appears.
	<!--If asked, there is no need to first unmount the partition, that would only be needed to allow installing on its parent disk.-->		<!--If asked, there is no need to first unmount the partition, that would only be needed to allow installing on its parent disk.-->
	#* When the ''' Disk & Install''' option appears, the preparatory steps done earlier for [[#Using an internal disk for persistent storage\|internal disk]] or [[#Using customizable boot device for persistent storage\|customizable boot device]] should now enable you to choose the partition('''sdXY''') for saving the local configs and package cache. So accept the choices as follows:{{Cmd\|<nowiki>Which disk(s) would you like to use? (or '?' for help or 'none') [none]		# When the ''' Disk & Install''' option appears, the preparatory steps done earlier for [[#Using an internal disk for persistent storage\|internal disk]] or [[#Using customizable boot device for persistent storage\|customizable boot device]] should now enable you to choose the partition('''sdXY''') for saving the local configs and package cache. So accept the choices as follows:{{Cmd\|<nowiki>Which disk(s) would you like to use? (or '?' for help or 'none') [none]
	Enter where to store configs ('floppy', 'sdXY', 'usb' or 'none') [sdXY]:		Enter where to store configs ('floppy', 'sdXY', 'usb' or 'none') [sdXY]:
	Enter apk cache directory (or '?' or 'none') [/media/sdXY/cache]:</nowiki>}}		Enter apk cache directory (or '?' or 'none') [/media/sdXY/cache]:</nowiki>}}
Line 77:		Line 71:
	=== Local package cache ===		=== Local package cache ===
	{{Main\|Local APK cache}}		{{Main\|Local APK cache}}
	When Alpine Linux boots in Diskless Mode, the remote repositories will not be available until after networking has started. That means newer or extra packages not in your local boot media's squashfs image would not be available after a reboot, unless they were made available as [[Local APK cache\|local package cache]] on a writable local storage device. The local package cache can be on the same partition as the '''apkovl''' file.		When Alpine Linux boots in Diskless Mode, the remote repositories will not be available until after networking has started. That means newer or extra packages not in your local boot media's squashfs image would not be available after a reboot, unless they were made available as [[Local APK cache\|local package cache]] on a writable local storage device. The local package cache can be on the same partition as the '''apkovl''' file.

	=== Apkovl ===		=== Apkovl ===

Macmpi: /* Modifying root filesystem size */ rephrase

2025-10-13T09:56:23Z

Modifying root filesystem size: rephrase

← Older revision		Revision as of 09:56, 13 October 2025
Line 73:		Line 73:
	=== Modifying root filesystem size ===		=== Modifying root filesystem size ===

	In Diskless mode, the root filesystem is mounted as <code>tmpfs</code>. By default rootfs is allocated 50% of available RAM (without swap). This may be adjusted to arbitrary value (like 300MB) at boot by setting [https://gitlab.alpinelinux.org/alpine/mkinitfs/-/blob/54bae0769080710e0769370a7bf3e0e158eec152/initramfs-init.in#L809-813 kernel parameter] as <code>rootflags{{=}}size{{=}}300M~~</code>, or temporarily after boot by issuing <code>mount -o remount,size{{=}}300M /~~</code>.		In Diskless mode, the root filesystem is mounted as <code>tmpfs</code>. By default rootfs is allocated 50% of available RAM (without swap). This may be adjusted to arbitrary value (like 300MB) temporarily after boot by issuing <code>mount -o remount,size{{=}}300M /</code>, or permanently at boot by setting [https://gitlab.alpinelinux.org/alpine/mkinitfs/-/blob/54bae0769080710e0769370a7bf3e0e158eec152/initramfs-init.in#L809-813 kernel parameter] as <code>rootflags{{=}}size{{=}}300M</code>.

	=== Local package cache ===		=== Local package cache ===

Prabuanand: minor rewording and added wikilinks

2025-09-29T10:27:18Z

minor rewording and added wikilinks

Prabuanand: added link to upgrading to a new release branch

2025-09-28T08:31:32Z

added link to upgrading to a new release branch

← Older revision		Revision as of 08:31, 28 September 2025
Line 92:		Line 92:
	[[Alpine_Package_Keeper#Upgrade_a_Running_System\|Upgrading a running]] system with [[Diskless Mode\|diskless]] or [[Data Disk Mode\|Data disk]] mode for regular package update requires running the below command from [[Alpine_local_backup\|Local Backup Utility]] after every package update:{{Cmd\|# lbu commit}}		[[Alpine_Package_Keeper#Upgrade_a_Running_System\|Upgrading a running]] system with [[Diskless Mode\|diskless]] or [[Data Disk Mode\|Data disk]] mode for regular package update requires running the below command from [[Alpine_local_backup\|Local Backup Utility]] after every package update:{{Cmd\|# lbu commit}}

	For upgrading the kernel, with its modules and firmware files use [[Diskless Mode#update-kernel script\|update-kernel]] script.		For upgrading the kernel, with its modules and firmware files use [[Diskless Mode#update-kernel script\|update-kernel]] script. For upgrading [[Diskless Mode\|diskless]] or [[Data Disk Mode\|Data disk]] installations to a new release branch refer [[Upgrading Alpine Linux to a new release branch#Upgrading diskless and data disk mode installs to latest release\|Upgrading diskless and data disk mode installs to latest release]].

	=== update-kernel script ===		=== update-kernel script ===

Prabuanand: fixed typo

2025-09-28T08:25:22Z

fixed typo

← Older revision		Revision as of 08:25, 28 September 2025
Line 96:		Line 96:
	=== update-kernel script ===		=== update-kernel script ===

	When kernel packages with its modules and firmware packages are upgraded, the <code>update-kernel</code> script generates initfs images and installs them together with upgraded kernel and updates the boot files~~, when~~ persistent ~~storage~~ like [[Create_a_Bootable_Device\|customizable boot device]] ~~are available~~.		When kernel packages with its modules and firmware packages are upgraded, the <code>update-kernel</code> script generates initfs images and installs them together with upgraded kernel and updates the boot files in persistent storages like [[Create_a_Bootable_Device\|customizable boot device]].

	* Before upgrading, install the {{Pkg\|mkinitfs}} package as this is required for the generation of the initial filesystem used during boot as follows: {{cmd\|# apk add mkinitfs}}		* Before upgrading, install the {{Pkg\|mkinitfs}} package as this is required for the generation of the initial filesystem used during boot as follows: {{cmd\|# apk add mkinitfs}}
Line 111:		Line 111:
	{{Note\|<code>update-kernel</code> run needs at least 8 GB free ram memory to avoid a broken modloop-image. So, in memory constrained devices like [[Raspberry Pi]], use the environment variable <code>TMPDIR</code> to point to a directory on a *nix file system formatted physical device, like a SD-Card or USB-Stick as follows: {{Cmd\|<nowiki># TMPDIR=/media/sdc1/tmp update-kernel /media/mmcblk0p1/boot/</nowiki>}}}}		{{Note\|<code>update-kernel</code> run needs at least 8 GB free ram memory to avoid a broken modloop-image. So, in memory constrained devices like [[Raspberry Pi]], use the environment variable <code>TMPDIR</code> to point to a directory on a *nix file system formatted physical device, like a SD-Card or USB-Stick as follows: {{Cmd\|<nowiki># TMPDIR=/media/sdc1/tmp update-kernel /media/mmcblk0p1/boot/</nowiki>}}}}

	See <code>update-kernel --help</code> for options to manually add additional module or firmware packages.		See <code>update-kernel --help</code> for options to manually add additional module or firmware packages.

	== Documentation on kernel options ==		== Documentation on kernel options ==

Prabuanand: created heading for update-kernel script and minor rewording

2025-09-28T07:50:08Z

created heading for update-kernel script and minor rewording

← Older revision		Revision as of 07:50, 28 September 2025
Line 90:		Line 90:
	== Upgrading a diskless system ==		== Upgrading a diskless system ==

	~~When Alping Linux runs in "~~diskless" or ~~"data"~~ disk mode~~, Upgrading~~ requires ~~few extra steps in addition to~~ the ~~regular~~ [[~~Alpine_Package_Keeper#Upgrade_a_Running_System~~\|~~upgrade steps~~]].		[[Alpine_Package_Keeper#Upgrade_a_Running_System\|Upgrading a running]] system with [[Diskless Mode\|diskless]] or [[Data Disk Mode\|Data disk]] mode for regular package update requires running the below command from [[Alpine_local_backup\|Local Backup Utility]] after every package update:{{Cmd\|# lbu commit}}

	~~If booting a "diskless" system from a read-only device, or as an iso image on writable media, it's not possible to update~~ the ~~boot files (~~kernel, modules, firmware~~, ...) that reside on that device. In this case, a new~~ [[~~Installation~~#~~Preparing_installation_media~~\|~~installation media~~]] ~~must be prepared with the updated [https://alpinelinux.org/downloads/ installation image file]~~.		For upgrading the kernel, with its modules and firmware files use [[Diskless Mode#update-kernel script\|update-kernel]] script.

	~~For [[Create_a_Bootable_Device\|customizable boot device]], It is possible to~~ update ~~the boot files. However, even then, the~~ kernel, with its modules and firmware ~~files, can still not be updated directly through regular~~ packages ~~updates. Instead~~, ~~there is~~ the <code>update-kernel</code> script ~~that can generate~~ initfs images and ~~install~~ them together with upgraded ~~kernels~~.		=== update-kernel script ===

			When kernel packages with its modules and firmware packages are upgraded, the <code>update-kernel</code> script generates initfs images and installs them together with upgraded kernel and updates the boot files, when persistent storage like [[Create_a_Bootable_Device\|customizable boot device]] are available.

	* Before upgrading, install the {{Pkg\|mkinitfs}} package as this is required for the generation of the initial filesystem used during boot as follows: {{cmd\|# apk add mkinitfs}}		* Before upgrading, install the {{Pkg\|mkinitfs}} package as this is required for the generation of the initial filesystem used during boot as follows: {{cmd\|# apk add mkinitfs}}

Prabuanand: additional rewording

2025-09-26T08:27:53Z

additional rewording

← Older revision		Revision as of 08:27, 26 September 2025
Line 34:		Line 34:
	A [[Create_a_Bootable_Device\|Customizable boot device]] allows Alpine Linux to boot and run in Diskless mode from a partition with a writable filesystem on USB-Stick/CompactFlash/SDCard or SSD/NVMe harddisk. The [[#Apkovl\|apkovl]] file(s) and [[#Local package cache\|local package cache]] can be stored in this customizable boot device and no other storage is required.		A [[Create_a_Bootable_Device\|Customizable boot device]] allows Alpine Linux to boot and run in Diskless mode from a partition with a writable filesystem on USB-Stick/CompactFlash/SDCard or SSD/NVMe harddisk. The [[#Apkovl\|apkovl]] file(s) and [[#Local package cache\|local package cache]] can be stored in this customizable boot device and no other storage is required.

	Boot using the [[Create_a_Bootable_Device\|Customizable boot device]] ~~and prepare it to hold local customizations before running the <code>setup-alpine</Code> script to finish the installation~~.		# Boot using the [[Create_a_Bootable_Device\|Customizable boot device]].
			# Find out where the customizable boot device is mounted, the location could vary.{{Cmd\|<nowiki># mount \| grep /media
	# ~~First find~~ out where the customizable boot device is mounted, the location could vary.{{Cmd\|<nowiki># mount \| grep /media		/dev/sdXY on /media/sdXY type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=utf8,shortname=mixed,errors=remount-ro)
	/dev/~~sda1~~ on /media/~~sda1~~ type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=utf8,shortname=mixed,errors=remount-ro)
	</nowiki>}}		</nowiki>}}
	# Mount the customizable boot device in rw mode, if required. {{Cmd\|# mount -o remount,rw /media/~~sda1~~}}		# Mount the customizable boot device in rw mode, if required. {{Cmd\|# mount -o remount,rw /media/sdXY}}
	<!--		<!--
	# Issue the below commands to create a directory for [[Local_APK_cache\|Local Package Cache]]. {{Cmd\|<nowiki># mkdir /media/sda1/cache		# Issue the below commands to create a directory for [[Local_APK_cache\|Local Package Cache]]. {{Cmd\|<nowiki># mkdir /media/sda1/cache

Prabuanand: additional rewording to clarify on the scripts

2025-09-26T08:05:17Z

additional rewording to clarify on the scripts

← Older revision		Revision as of 08:05, 26 September 2025
Line 7:		Line 7:
	== Diskless installation ==		== Diskless installation ==

	~~Alpine Linux can be installed and configured so that the system continue to boot in diskless mode, if "disk=none" is specified while~~ running the <code>[[Alpine_setup_scripts#setup-alpine\|setup-alpine]]</code> script. It ~~also~~ includes ~~the~~ <code>[[Alpine_setup_scripts#setup-lbu\|setup-lbu]]</code> script ~~to save local configs as~~ [[#~~Apkovl~~\|~~apkovl~~]] ~~file~~ to any available writable filesystem on any media other than the read-only [[Installation#Preparing_installation_media\|installation media]]~~. For Diskless installations, using a~~ [[~~Create a Bootable Device~~\|~~Customizable boot device~~]] ~~is recommended instead of a read-only installation media~~.		When running the <code>[[Alpine_setup_scripts#setup-alpine\|setup-alpine]]</code> script, if "disk=none" is specified, then Alpine Linux will continue to run in diskless mode. It includes <code>[[Alpine_setup_scripts#setup-lbu\|setup-lbu]]</code> script and <code>[[Alpine_setup_scripts#setup-apkcache\|setup-apkcache]]</code> scripts to use any available writable filesystem on any media other than the read-only [[Installation#Preparing_installation_media\|installation media]] for saving the configuration settings as [[#Apkovl\|apkovl]] file and [[#Local package cache\|local package cache]].

	The preparatory steps for a Diskless installation ~~differs depending~~ on the ~~writable filesystem used~~.		{{Tip\|For Diskless installations, using a [[Create a Bootable Device\|Customizable boot device]] is recommended instead of a read-only installation media.}}

			The preparatory steps for a Diskless installation depends on the available persistent storage.

	=== Using an internal disk for persistent storage ===		=== Using an internal disk for persistent storage ===
Line 49:		Line 51:

	# If <code>setup-alpine</code> has not run before, follow the [[Installation#Installation_Step_Details\|Installation steps]] to complete the [[Installation#Base_configuration\|base configuration]].		# If <code>setup-alpine</code> has not run before, follow the [[Installation#Installation_Step_Details\|Installation steps]] to complete the [[Installation#Base_configuration\|base configuration]].
	# The preparatory steps done earlier for [[#Using an internal disk for persistent storage\|internal disk]] or [[#Using customizable boot device for persistent storage\|customizable boot device]] should now enable you to choose the partition('''sdXY''') for saving the local configs and package cache.		#* The preparatory steps done earlier for [[#Using an internal disk for persistent storage\|internal disk]] or [[#Using customizable boot device for persistent storage\|customizable boot device]] should now enable you to choose the partition('''sdXY''') for saving the local configs and package cache.
	<!--If asked, there is no need to first unmount the partition, that would only be needed to allow installing on its parent disk.-->		<!--If asked, there is no need to first unmount the partition, that would only be needed to allow installing on its parent disk.-->
	# When the ''' Disk & Install''' option appears, accept the choices as follows:{{Cmd\|<nowiki>Which disk(s) would you like to use? (or '?' for help or 'none') [none]		#* When the ''' Disk & Install''' option appears, accept the choices as follows:{{Cmd\|<nowiki>Which disk(s) would you like to use? (or '?' for help or 'none') [none]
	Enter where to store configs ('floppy', 'sdXY', 'usb' or 'none') [sdXY]:		Enter where to store configs ('floppy', 'sdXY', 'usb' or 'none') [sdXY]:
	Enter apk cache directory (or '?' or 'none') [/media/sdXY/cache]:</nowiki>}}		Enter apk cache directory (or '?' or 'none') [/media/sdXY/cache]:</nowiki>}}
	# If <code>setup-alpine</code> has already been run to configure the diskless system, the storage and package cache settings can be configured as follows:{{cmd\|<nowiki># setup-lbu sdXY		# If <code>setup-alpine</code> has already been run to configure the diskless system, the storage and package cache settings can be configured using the relevant setup-scripts as follows:{{cmd\|<nowiki># setup-lbu sdXY
	# mkdir /media/sdXY/cache		# mkdir /media/sdXY/cache
	# setup-apkcache /media/sdXY/cache</nowiki>}}		# setup-apkcache /media/sdXY/cache</nowiki>}}
	# After the installer finished ~~you~~ can see how many created/modified files are detected and will be added to the backup:{{Cmd\|<nowiki># lbu status		# After the installer finished one can see how many created/modified files are detected and will be added to the backup:{{Cmd\|<nowiki># lbu status
	# lbu status \| wc -l		# lbu status \| wc -l
	59		59

Prabuanand: slight rephrasing

2025-09-26T07:24:01Z

slight rephrasing

← Older revision		Revision as of 07:24, 26 September 2025
Line 7:		Line 7:
	== Diskless installation ==		== Diskless installation ==

	Alpine Linux can be installed and configured so that the system continue to boot in diskless mode, if "disk=none" is specified while running the <code>[[Alpine_setup_scripts#setup-alpine\|setup-alpine]]</code> script. It also includes the <code>[[Alpine_setup_scripts#setup-lbu\|setup-lbu]]</code> script to save local configs as [[#Apkovl\|apkovl]] file to any available writable filesystem on any media other than the read-only [[Installation#Preparing_installation_media\|installation media]]. [[Create a Bootable Device\|Customizable boot device]] is ~~highly~~ recommended ~~for Diskless installations~~.		Alpine Linux can be installed and configured so that the system continue to boot in diskless mode, if "disk=none" is specified while running the <code>[[Alpine_setup_scripts#setup-alpine\|setup-alpine]]</code> script. It also includes the <code>[[Alpine_setup_scripts#setup-lbu\|setup-lbu]]</code> script to save local configs as [[#Apkovl\|apkovl]] file to any available writable filesystem on any media other than the read-only [[Installation#Preparing_installation_media\|installation media]]. For Diskless installations, using a [[Create a Bootable Device\|Customizable boot device]] is recommended instead of a read-only installation media.

	The preparatory steps for a Diskless installation differs depending on the writable filesystem used.		The preparatory steps for a Diskless installation differs depending on the writable filesystem used.
Line 65:		Line 65:
	-rwxr-xr-x 1 root root 9591 Oct 19 15:23 /media/sda1/foo.apkovl.tar.gz		-rwxr-xr-x 1 root root 9591 Oct 19 15:23 /media/sda1/foo.apkovl.tar.gz
	</nowiki>}}		</nowiki>}}
	# Now the diskless installation can be considered complete.		# Now the diskless installation can be considered complete.

	== Configuration ==		== Configuration ==

← Older revision		Revision as of 11:34, 28 February 2026
Line 3:		Line 3:
	Diskless mode is extremely fast and can save on unnecessary disk spin-ups, power, and wear and suitable for servers. It is similar to what other linux distributions may call a "frugal" install or boot using a "toram" option.		Diskless mode is extremely fast and can save on unnecessary disk spin-ups, power, and wear and suitable for servers. It is similar to what other linux distributions may call a "frugal" install or boot using a "toram" option.

	Alpine Linux provides [[Alpine_local_backup\|Local Backup Utility]]({{ic\|lbu}}) that allows custom configurations and package installations to be optionally preserved or made to "persist" across reboots as [[#Apkovl\|apkovl]] files.		Alpine Linux provides [[Alpine_local_backup\|Local Backup Utility]]({{ic\|lbu}}) that allows custom configurations and package installations to be optionally preserved or made to "persist" across reboots as [[#Apkovl\|apkovl]] files on persistent storage.

	If additional or updated packages have been added to the system, these may also be made available for automatic (re)installation during the boot phase without any (re)downloading, by enabling a [[#Local package cache\|local package cache]].		If additional or updated packages have been added to the system, these may also be made available for automatic (re)installation during the boot phase without any (re)downloading, by enabling a [[#Local package cache\|local package cache]].
Line 11:		Line 11:
	When running the <code>[[Alpine_setup_scripts#setup-alpine\|setup-alpine]]</code> script, if "disk=none" is specified, then Alpine Linux will continue to run in diskless mode. It invokes <code>[[Alpine_setup_scripts#setup-lbu\|setup-lbu]]</code> and <code>[[Alpine_setup_scripts#setup-apkcache\|setup-apkcache]]</code> to use any available writable filesystem on any media other than the read-only installation media for saving the configuration settings as apkovl file and local package cache.		When running the <code>[[Alpine_setup_scripts#setup-alpine\|setup-alpine]]</code> script, if "disk=none" is specified, then Alpine Linux will continue to run in diskless mode. It invokes <code>[[Alpine_setup_scripts#setup-lbu\|setup-lbu]]</code> and <code>[[Alpine_setup_scripts#setup-apkcache\|setup-apkcache]]</code> to use any available writable filesystem on any media other than the read-only installation media for saving the configuration settings as apkovl file and local package cache.

	{{Tip\|~~For Diskless installations~~, ~~create~~ [[#Using customizable boot device for persistent storage\|customizable boot device]] ~~instead of a~~ read-only installation media.}}		{{Tip\|If you are using a single USB flash drive for a diskless install, use a [[#Using customizable boot device for persistent storage\|customizable boot device]] rather than standard read-only installation media. This allows the drive to host both the OS and your persistent storage.}}

	Complete the below preparatory steps depending on the available persistent storage option for apkovl and local package cache. Persistent storage are configured as read-only in {{Path\|/etc/fstab}}, as [[Alpine_local_backup\|lbu]] can temporarily remount them as writable for their operation.		Complete the below preparatory steps depending on the available persistent storage option for apkovl and local package cache. Persistent storage are configured as read-only in {{Path\|/etc/fstab}}, as [[Alpine_local_backup\|lbu]] can temporarily remount them as writable for their operation.

← Older revision		Revision as of 06:37, 28 November 2025
Line 3:		Line 3:
	Diskless mode is extremely fast and can save on unnecessary disk spin-ups, power, and wear and suitable for servers. It is similar to what other linux distributions may call a "frugal" install or boot using a "toram" option.		Diskless mode is extremely fast and can save on unnecessary disk spin-ups, power, and wear and suitable for servers. It is similar to what other linux distributions may call a "frugal" install or boot using a "toram" option.

	Alpine Linux provides [[Alpine_local_backup\|Local Backup Utility]]({{ic\|lbu}}) that allows custom configurations and package installations to be optionally preserved or made to "persist" across reboots as [[#Apkovl\|apkovl]] files. If additional or updated packages have been added to the system, these may also be made available for automatic (re)installation during the boot phase without any (re)downloading, by enabling a [[#Local package cache\|local package cache]].		Alpine Linux provides [[Alpine_local_backup\|Local Backup Utility]]({{ic\|lbu}}) that allows custom configurations and package installations to be optionally preserved or made to "persist" across reboots as [[#Apkovl\|apkovl]] files.

			If additional or updated packages have been added to the system, these may also be made available for automatic (re)installation during the boot phase without any (re)downloading, by enabling a [[#Local package cache\|local package cache]].

	== Diskless installation ==		== Diskless installation ==

	When running the <code>[[Alpine_setup_scripts#setup-alpine\|setup-alpine]]</code> script, if "disk=none" is specified, then Alpine Linux will continue to run in diskless mode. It invokes <code>[[Alpine_setup_scripts#setup-lbu\|setup-lbu]]</code> and <code>[[Alpine_setup_scripts#setup-apkcache\|setup-apkcache]]</code> to use any available writable filesystem on any media other than the read-only ~~[[Installation#Preparing_installation_media\|~~installation media]] for saving the configuration settings as [[#~~Apkovl~~\|~~apkovl~~]] ~~file~~ and [[~~#Local package cache~~\|~~local package cache~~]].		When running the <code>[[Alpine_setup_scripts#setup-alpine\|setup-alpine]]</code> script, if "disk=none" is specified, then Alpine Linux will continue to run in diskless mode. It invokes <code>[[Alpine_setup_scripts#setup-lbu\|setup-lbu]]</code> and <code>[[Alpine_setup_scripts#setup-apkcache\|setup-apkcache]]</code> to use any available writable filesystem on any media other than the read-only installation media for saving the configuration settings as apkovl file and local package cache.

			{{Tip\|For Diskless installations, create [[#Using customizable boot device for persistent storage\|customizable boot device]] instead of a read-only installation media.}}

			Complete the below preparatory steps depending on the available persistent storage option for apkovl and local package cache. Persistent storage are configured as read-only in {{Path\|/etc/fstab}}, as [[Alpine_local_backup\|lbu]] can temporarily remount them as writable for their operation.

			=== Using customizable boot device for persistent storage ===

	~~{{Tip\|For Diskless installations, create a~~ [[~~Create a Bootable Device~~\|Customizable boot device]] ~~instead of~~ a ~~read~~-~~only installation media~~.}}		A [[Create_a_Bootable_Device\|Customizable boot device]] allows Alpine Linux to boot and run in Diskless mode from a partition with a writable filesystem on USB-Stick/CompactFlash/SDCard or SSD/NVMe harddisk. The [[#Apkovl\|apkovl]] file(s) and [[#Local package cache\|local package cache]] can be stored in this customizable boot device and no other storage is required.

	~~Complete~~ the ~~below preparatory steps depending~~ on the ~~available persistent storage option~~.		# Boot using the [[Create_a_Bootable_Device\|Customizable boot device]].
			# Find out where the customizable boot device is mounted, the location could vary.{{Cmd\|<nowiki># mount \| grep /media
			/dev/sdXY on /media/sdXY type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=utf8,shortname=mixed,errors=remount-ro)
			</nowiki>}}
			# Mount the customizable boot device in rw mode, if required. {{Cmd\|# mount -o remount,rw /media/sdXY}}
			# Proceed to [[#Finishing diskless installation\|Finishing diskless installation]] section without rebooting the computer.

	=== Using an internal disk for persistent storage ===		=== Using an internal disk for persistent storage ===

	~~Due to Bug: [https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10473 #10473] storing~~ local configs on '''internal disks''' requires manual steps, i.e making an entry in {{Path\|/etc/fstab}}, create mountpoint, and mount the partition before running <code>setup-alpine</code> script.		Storing local configs on '''internal disks''' requires manual steps, i.e making an entry in {{Path\|/etc/fstab}}, create mountpoint, and mount the partition before running <code>setup-alpine</code> script due to Issue [https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10473 #10473]. Use only ext4 filesystem partitions on classic drives to store diskless mode states as diskless setup currently doesn't work on btrfs and xfs filesystems, or nvme-based devices as per {{Issue\|11589\|}}.

	# In this case, boot the target diskless system from the ~~[[Installation#Preparing_installation_media\|~~installation media]] and do not proceed after the [[Installation#Boot_Process\|boot process]] stage.		# In this case, boot the target diskless system from the installation media and do not proceed after the [[Installation#Boot_Process\|boot process]] stage.
	# If necessary partition(s) are unavailable, manually [[Setting_up_disks_manually#Creating_partitions\|create]] a partition using <Code>fdisk</Code>. In the below steps, we will use /dev/sdXY as partition number. Adjust the partition identifier as per the output of {{Codeline\|<Code>blkid</Code>}}<br>		# If necessary partition(s) are unavailable, manually [[Setting_up_disks_manually#Creating_partitions\|create]] a partition using <Code>fdisk</Code>. In the below steps, we will use /dev/sdXY as partition number. Adjust the partition identifier as per the output of {{Codeline\|<Code>blkid</Code>}}<br>
	#* Due to Bug: {{Issue\|11589\|The APKOVL loading of diskless setups doesn't work on btrfs and xfs filesystems, or nvme-based devices}}. So use only ext4 filesystem partitions on classic drives to store diskless mode states.
	#* mkfs.ext4 creates ext4 filesystem with 64bit feature enabled by default, but extlinux may not be able to boot with that due to Issue {{Issue\|14895}}. You may need to add "-O ^64bit" to mkfs.ext4 to circumvent this. The below command creates an ext4 partition with disabled journaling, to reduce write operations and allow the disk to spin down after the .apkovl and the packages have been read from the partition during the boot. Install package {{pkg\|<Code>e2fsprogs</code>}} using command {{Codeline\|<Code>apk add e2fsprogs</Code>}}, if the command <Code>mkfs.ext4</Code> is not available.		#* mkfs.ext4 creates ext4 filesystem with 64bit feature enabled by default, but extlinux may not be able to boot with that due to Issue {{Issue\|14895}}. You may need to add "-O ^64bit" to mkfs.ext4 to circumvent this. The below command creates an ext4 partition with disabled journaling, to reduce write operations and allow the disk to spin down after the .apkovl and the packages have been read from the partition during the boot. Install package {{pkg\|<Code>e2fsprogs</code>}} using command {{Codeline\|<Code>apk add e2fsprogs</Code>}}, if the command <Code>mkfs.ext4</Code> is not available.
	#: {{Cmd\|# mkfs.ext4 -O ^has_journal,^64bit /dev/sdXY}}		#: {{Cmd\|# mkfs.ext4 -O ^has_journal,^64bit /dev/sdXY}}
	# ~~Due to a [https://gitlab.alpinelinux.org/alpine/mkinitfs/-/issues/5 bug], the partition can not be mounted to /boot.~~ Configure the /etc/fstab to mount the writable partition to /media/sdXY ~~instead of /boot i.e.~~ conforming to the hot/cold-plug mountpoints.		# Configure the /etc/fstab to mount the writable partition to /media/sdXY conforming to the hot/cold-plug mountpoints.
	#: {{Cmd\|# mkdir /media/sdXY}}		#: {{Cmd\|# mkdir /media/sdXY}}
	#: {{cmd\|# echo "/dev/sdXY /media/sdXY ext4 noatime,ro 0 0" >> /etc/fstab}}		#: {{cmd\|# echo "/dev/sdXY /media/sdXY ext4 noatime,ro 0 0" >> /etc/fstab}}
	~~<!-- Mounting read-only is possible, because the [[Alpine_local_backup\|lbu tools]] can temporarily remount it writable for their operation. -->~~
	# Mount the partitions listed in {{Path\|/etc/fstab}}:{{Cmd\|# <code>mount -a</code>}}		# Mount the partitions listed in {{Path\|/etc/fstab}}:{{Cmd\|# <code>mount -a</code>}}
	# Verify that the changes have been applied correctly by looking at the output of {{Cmd\|$ <code>mount</code>}}		# Verify that the changes have been applied correctly by looking at the output of {{Cmd\|$ <code>mount</code>}}
	~~# Proceed to [[#Finishing diskless installation\|Finishing diskless installation]] section without rebooting the computer.~~

	~~=== Using customizable boot device for persistent storage ===~~

	A [[Create_a_Bootable_Device\|Customizable boot device]] allows Alpine Linux to boot and run in Diskless mode from a partition with a writable filesystem on USB-Stick/CompactFlash/SDCard or SSD/NVMe harddisk. The [[#Apkovl\|apkovl]] file(s) and [[#Local package cache\|local package cache]] can be stored in this customizable boot device and no other storage is required.

	~~# Boot using the [[Create_a_Bootable_Device\|Customizable boot device]].~~
	~~# Find out where the customizable boot device is mounted, the location could vary.{{Cmd\|<nowiki># mount \| grep /media~~
	~~/dev/sdXY on /media/sdXY type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=utf8,shortname=mixed,errors=remount-ro)~~
	~~</nowiki>}}~~
	~~# Mount the customizable boot device in rw mode, if required. {{Cmd\|# mount -o remount,rw /media/sdXY}}~~
	~~<!--~~
	~~# Issue the below commands to create a directory for [[Local_APK_cache\|Local Package Cache]]. {{Cmd\|<nowiki># mkdir /media/sda1/cache~~
	~~# setup-apkcache /media/sda1/cache~~
	~~# ls -l /etc/apk/cache~~
	~~lrwxrwxrwx 1 root root 17 Oct 19 13:16 /etc/apk/cache -> /media/sda1/cache~~
	~~</nowiki>}}-->~~
	# Proceed to [[#Finishing diskless installation\|Finishing diskless installation]] section without rebooting the computer.		# Proceed to [[#Finishing diskless installation\|Finishing diskless installation]] section without rebooting the computer.

Line 51:		Line 45:
	# If <code>setup-alpine</code> has not run before, follow the [[Installation#Installation_Step_Details\|Installation steps]] to complete until the '''Disk & Install''' option appears.		# If <code>setup-alpine</code> has not run before, follow the [[Installation#Installation_Step_Details\|Installation steps]] to complete until the '''Disk & Install''' option appears.
	<!--If asked, there is no need to first unmount the partition, that would only be needed to allow installing on its parent disk.-->		<!--If asked, there is no need to first unmount the partition, that would only be needed to allow installing on its parent disk.-->
	#* When the ''' Disk & Install''' option appears, the preparatory steps done earlier for [[#Using an internal disk for persistent storage\|internal disk]] or [[#Using customizable boot device for persistent storage\|customizable boot device]] should now enable you to choose the partition('''sdXY''') for saving the local configs and package cache. So accept the choices as follows:{{Cmd\|<nowiki>Which disk(s) would you like to use? (or '?' for help or 'none') [none]		# When the ''' Disk & Install''' option appears, the preparatory steps done earlier for [[#Using an internal disk for persistent storage\|internal disk]] or [[#Using customizable boot device for persistent storage\|customizable boot device]] should now enable you to choose the partition('''sdXY''') for saving the local configs and package cache. So accept the choices as follows:{{Cmd\|<nowiki>Which disk(s) would you like to use? (or '?' for help or 'none') [none]
	Enter where to store configs ('floppy', 'sdXY', 'usb' or 'none') [sdXY]:		Enter where to store configs ('floppy', 'sdXY', 'usb' or 'none') [sdXY]:
	Enter apk cache directory (or '?' or 'none') [/media/sdXY/cache]:</nowiki>}}		Enter apk cache directory (or '?' or 'none') [/media/sdXY/cache]:</nowiki>}}
Line 77:		Line 71:
	=== Local package cache ===		=== Local package cache ===
	{{Main\|Local APK cache}}		{{Main\|Local APK cache}}
	When Alpine Linux boots in Diskless Mode, the remote repositories will not be available until after networking has started. That means newer or extra packages not in your local boot media's squashfs image would not be available after a reboot, unless they were made available as [[Local APK cache\|local package cache]] on a writable local storage device. The local package cache can be on the same partition as the '''apkovl''' file.		When Alpine Linux boots in Diskless Mode, the remote repositories will not be available until after networking has started. That means newer or extra packages not in your local boot media's squashfs image would not be available after a reboot, unless they were made available as [[Local APK cache\|local package cache]] on a writable local storage device. The local package cache can be on the same partition as the '''apkovl''' file.

	=== Apkovl ===		=== Apkovl ===

← Older revision		Revision as of 07:50, 28 September 2025
Line 90:		Line 90:
	== Upgrading a diskless system ==		== Upgrading a diskless system ==

	~~When Alping Linux runs in "~~diskless" or ~~"data"~~ disk mode~~, Upgrading~~ requires ~~few extra steps in addition to~~ the ~~regular~~ [[~~Alpine_Package_Keeper#Upgrade_a_Running_System~~\|~~upgrade steps~~]].		[[Alpine_Package_Keeper#Upgrade_a_Running_System\|Upgrading a running]] system with [[Diskless Mode\|diskless]] or [[Data Disk Mode\|Data disk]] mode for regular package update requires running the below command from [[Alpine_local_backup\|Local Backup Utility]] after every package update:{{Cmd\|# lbu commit}}

	~~If booting a "diskless" system from a read-only device, or as an iso image on writable media, it's not possible to update~~ the ~~boot files (~~kernel, modules, firmware~~, ...) that reside on that device. In this case, a new~~ [[~~Installation~~#~~Preparing_installation_media~~\|~~installation media~~]] ~~must be prepared with the updated [https://alpinelinux.org/downloads/ installation image file]~~.		For upgrading the kernel, with its modules and firmware files use [[Diskless Mode#update-kernel script\|update-kernel]] script.

	~~For [[Create_a_Bootable_Device\|customizable boot device]], It is possible to~~ update ~~the boot files. However, even then, the~~ kernel, with its modules and firmware ~~files, can still not be updated directly through regular~~ packages ~~updates. Instead~~, ~~there is~~ the <code>update-kernel</code> script ~~that can generate~~ initfs images and ~~install~~ them together with upgraded ~~kernels~~.		=== update-kernel script ===

			When kernel packages with its modules and firmware packages are upgraded, the <code>update-kernel</code> script generates initfs images and installs them together with upgraded kernel and updates the boot files, when persistent storage like [[Create_a_Bootable_Device\|customizable boot device]] are available.

	* Before upgrading, install the {{Pkg\|mkinitfs}} package as this is required for the generation of the initial filesystem used during boot as follows: {{cmd\|# apk add mkinitfs}}		* Before upgrading, install the {{Pkg\|mkinitfs}} package as this is required for the generation of the initial filesystem used during boot as follows: {{cmd\|# apk add mkinitfs}}

← Older revision		Revision as of 10:27, 29 September 2025
Line 7:		Line 7:
	== Diskless installation ==		== Diskless installation ==

	When running the <code>[[Alpine_setup_scripts#setup-alpine\|setup-alpine]]</code> script, if "disk=none" is specified, then Alpine Linux will continue to run in diskless mode. It ~~includes~~ <code>[[Alpine_setup_scripts#setup-lbu\|setup-lbu]]</code> ~~script~~ and <code>[[Alpine_setup_scripts#setup-apkcache\|setup-apkcache]]</code> ~~scripts~~ to use any available writable filesystem on any media other than the read-only [[Installation#Preparing_installation_media\|installation media]] for saving the configuration settings as [[#Apkovl\|apkovl]] file and [[#Local package cache\|local package cache]].		When running the <code>[[Alpine_setup_scripts#setup-alpine\|setup-alpine]]</code> script, if "disk=none" is specified, then Alpine Linux will continue to run in diskless mode. It invokes <code>[[Alpine_setup_scripts#setup-lbu\|setup-lbu]]</code> and <code>[[Alpine_setup_scripts#setup-apkcache\|setup-apkcache]]</code> to use any available writable filesystem on any media other than the read-only [[Installation#Preparing_installation_media\|installation media]] for saving the configuration settings as [[#Apkovl\|apkovl]] file and [[#Local package cache\|local package cache]].

	{{Tip\|For Diskless installations, ~~using~~ a [[Create a Bootable Device\|Customizable boot device]] ~~is recommended~~ instead of a read-only installation media.}}		{{Tip\|For Diskless installations, create a [[Create a Bootable Device\|Customizable boot device]] instead of a read-only installation media.}}

	~~The~~ preparatory steps ~~for a Diskless installation depends~~ on the available persistent storage.		Complete the below preparatory steps depending on the available persistent storage option.

	=== Using an internal disk for persistent storage ===		=== Using an internal disk for persistent storage ===
Line 49:		Line 49:
	=== Finishing diskless installation ===		=== Finishing diskless installation ===

	# If <code>setup-alpine</code> has not run before, follow the [[Installation#Installation_Step_Details\|Installation steps]] to complete the ~~[[Installation#Base_configuration\|base configuration]].~~		# If <code>setup-alpine</code> has not run before, follow the [[Installation#Installation_Step_Details\|Installation steps]] to complete until the '''Disk & Install''' option appears.
	#* The preparatory steps done earlier for [[#Using an internal disk for persistent storage\|internal disk]] or [[#Using customizable boot device for persistent storage\|customizable boot device]] should now enable you to choose the partition('''~~sdXY~~'''~~) for saving the local configs and package cache~~.
	<!--If asked, there is no need to first unmount the partition, that would only be needed to allow installing on its parent disk.-->		<!--If asked, there is no need to first unmount the partition, that would only be needed to allow installing on its parent disk.-->
	#* When the ''' Disk & Install''' option appears, accept the choices as follows:{{Cmd\|<nowiki>Which disk(s) would you like to use? (or '?' for help or 'none') [none]		#* When the ''' Disk & Install''' option appears, the preparatory steps done earlier for [[#Using an internal disk for persistent storage\|internal disk]] or [[#Using customizable boot device for persistent storage\|customizable boot device]] should now enable you to choose the partition('''sdXY''') for saving the local configs and package cache. So accept the choices as follows:{{Cmd\|<nowiki>Which disk(s) would you like to use? (or '?' for help or 'none') [none]
	Enter where to store configs ('floppy', 'sdXY', 'usb' or 'none') [sdXY]:		Enter where to store configs ('floppy', 'sdXY', 'usb' or 'none') [sdXY]:
	Enter apk cache directory (or '?' or 'none') [/media/sdXY/cache]:</nowiki>}}		Enter apk cache directory (or '?' or 'none') [/media/sdXY/cache]:</nowiki>}}
	# If <code>setup-alpine</code> has already been run to configure the diskless system, the storage and package cache settings can be configured using the ~~relevant~~ setup-~~scripts~~ as follows:{{cmd\|<nowiki># setup-lbu sdXY		# If <code>setup-alpine</code> has already been run to configure the diskless system, the storage and package cache settings can be configured using the <code>[[Alpine_setup_scripts#setup-lbu\|setup-lbu]]</code> and <code>[[Alpine_setup_scripts#setup-apkcache\|setup-apkcache]]</code> as follows:{{cmd\|<nowiki># setup-lbu sdXY
	# mkdir /media/sdXY/cache		# mkdir /media/sdXY/cache
	# setup-apkcache /media/sdXY/cache</nowiki>}}		# setup-apkcache /media/sdXY/cache</nowiki>}}