Bootstrapping Alpine Linux - Revision history

Prabuanand: fixed wikitags, heading levels and changed some headings

2025-02-23T13:31:07Z

fixed wikitags, heading levels and changed some headings

← Older revision		Revision as of 13:31, 23 February 2025
Line 1:		Line 1:
			This page provides the instructions to bootstrap Alpine Linux on any [https://en.wikipedia.org/wiki/Virtual_private_server VPS].

			== Prerequisite ==

	~~= VPS =~~		Download apk binary file for your architecture or boot from an Alpine live ISO. {{Cmd\|$ wget https://gitlab.alpinelinux.org/api/v4/projects/5/packages/generic/v2.14.6/x86_64/apk.static}}
	~~This section is to provide a means to bootstrap~~ Alpine ~~Linux on any VPS~~.

	~~== Process ==~~		Assuming your alpine rootfs is mounted in '''/tmp/target''' and you downloaded apk binary (not using the live ISO).

	~~=== Prepare ===~~

	~~Download~~ apk binary ~~file for your architecture or boot from an Alpine~~ live ISO.

	~~Hint to download apk :~~
	~~<pre>wget https://gitlab.alpinelinux.org/api/v4/projects/5/packages/generic/v2.14.6/x86_64/apk.static</pre>~~

	~~=== Install ===~~

	~~Assuming your alpine rootfs is mounted in '''/tmp/target''' and you downloaded apk binary (not using the live ISO).~~		== Installation ==

	You may want to replace "latest-stable" from the URL by a specific version of Alpine (e.g. v3.20, v3.21).		You may want to replace "latest-stable" from the URL by a specific version of Alpine (e.g. v3.20, v3.21).
Line 57:		Line 49:
	</pre>		</pre>

	=== Bootloader ===		== Bootloader ==

	~~=== Notes ===~~
	If you have bootstrapped Alpine Linux from an existing system in a different partition and intend to boot into it, you should always include the root filesystem type (rootfstype) in the kernel parameter (bootloader option), since by default kernel does not automatically load any filesystem modules for root partition, unless specified. That way mount will not complain about being unable to mount root partition on /sysroot.		If you have bootstrapped Alpine Linux from an existing system in a different partition and intend to boot into it, you should always include the root filesystem type (rootfstype) in the kernel parameter (bootloader option), since by default kernel does not automatically load any filesystem modules for root partition, unless specified. That way mount will not complain about being unable to mount root partition on /sysroot.

Line 66:		Line 57:
	<code>root=UUID=AAAAAAAA-BBBB-CCCC-DDDD-EEEEEEEEEEEE rw rootfstype=ext4 vfat</code>		<code>root=UUID=AAAAAAAA-BBBB-CCCC-DDDD-EEEEEEEEEEEE rw rootfstype=ext4 vfat</code>

	== ~~References~~ ==		== See also ==

	* [https://www.linode.com/docs/tools-reference/custom-kernels-distros/running-a-custom-linux-distro-on-a-linode-vps Running a Custom Linux Distribution on a Linode]		* [https://www.linode.com/docs/tools-reference/custom-kernels-distros/running-a-custom-linux-distro-on-a-linode-vps Running a Custom Linux Distribution on a Linode]
	* [https://www.linode.com/docs/tools-reference/custom-kernels-distros/run-a-custom-compiled-kernel-with-pvgrub Run a Custom Compiled Kernel with PV-GRUB]		* [https://www.linode.com/docs/tools-reference/custom-kernels-distros/run-a-custom-compiled-kernel-with-pvgrub Run a Custom Compiled Kernel with PV-GRUB]

Ewtoombs: /* Install */ Downloading the public keys without https is a stupid idea.

2025-02-20T11:10:06Z

Install: Downloading the public keys without https is a stupid idea.

← Older revision		Revision as of 11:10, 20 February 2025
Line 19:		Line 19:
	You may want to replace "latest-stable" from the URL by a specific version of Alpine (e.g. v3.20, v3.21).		You may want to replace "latest-stable" from the URL by a specific version of Alpine (e.g. v3.20, v3.21).

	<code>sudo ./apk.static --arch $(arch) -X ~~http~~://dl-cdn.alpinelinux.org/alpine/latest-stable/main/ -U --allow-untrusted --root /tmp/target --initdb add alpine-base</code>		<code>sudo ./apk.static --arch $(arch) -X https://dl-cdn.alpinelinux.org/alpine/latest-stable/main/ -U --allow-untrusted --root /tmp/target --initdb add alpine-base</code>

	* edit /tmp/target/etc/fstab		* edit /tmp/target/etc/fstab

Msleaveamix: /* Install */ added that you can choose the version of alpine to bootstrap.

2024-12-26T08:30:16Z

Install: added that you can choose the version of alpine to bootstrap.

← Older revision		Revision as of 08:30, 26 December 2024
Line 16:		Line 16:

	Assuming your alpine rootfs is mounted in '''/tmp/target''' and you downloaded apk binary (not using the live ISO).		Assuming your alpine rootfs is mounted in '''/tmp/target''' and you downloaded apk binary (not using the live ISO).

			You may want to replace "latest-stable" from the URL by a specific version of Alpine (e.g. v3.20, v3.21).

	<code>sudo ./apk.static --arch $(arch) -X http://dl-cdn.alpinelinux.org/alpine/latest-stable/main/ -U --allow-untrusted --root /tmp/target --initdb add alpine-base</code>		<code>sudo ./apk.static --arch $(arch) -X http://dl-cdn.alpinelinux.org/alpine/latest-stable/main/ -U --allow-untrusted --root /tmp/target --initdb add alpine-base</code>

Msleaveamix: /* Install */ apk.static is downloaded directly in the current directory, add specification that you're not using the live ISO to bootstrap

2024-12-26T08:28:23Z

Install: apk.static is downloaded directly in the current directory, add specification that you're not using the live ISO to bootstrap

← Older revision		Revision as of 08:28, 26 December 2024
Line 15:		Line 15:
	=== Install ===		=== Install ===

	Assuming your alpine rootfs is mounted in '''/tmp/target'''		Assuming your alpine rootfs is mounted in '''/tmp/target''' and you downloaded apk binary (not using the live ISO).

	<code>sudo .~~/sbin~~/apk.static --arch $(arch) -X http://dl-cdn.alpinelinux.org/alpine/latest-stable/main/ -U --allow-untrusted --root /tmp/target --initdb add alpine-base</code>		<code>sudo ./apk.static --arch $(arch) -X http://dl-cdn.alpinelinux.org/alpine/latest-stable/main/ -U --allow-untrusted --root /tmp/target --initdb add alpine-base</code>

	* edit /tmp/target/etc/fstab		* edit /tmp/target/etc/fstab

Msleaveamix: removed useless unpacking, update apk-tool-static to apk binary, update URL, add option to "boot into a live ISO"

2024-12-26T08:25:25Z

removed useless unpacking, update apk-tool-static to apk binary, update URL, add option to "boot into a live ISO"

← Older revision		Revision as of 08:25, 26 December 2024
Line 7:		Line 7:

	=== Prepare ===		=== Prepare ===
	~~<ol>~~
	~~<li>Download apk-tools-static for your architecture.</li>~~
	~~<pre>wget https://gitlab.alpinelinux.org/api/v4/projects/5/packages/generic/v2.14.0/x86_64/apk.static</pre>~~

	~~<li>Unpack .~~apk~~</li>~~		Download apk binary file for your architecture or boot from an Alpine live ISO.
	<pre>tar zxf apk-tools-static-*.~~apk</pre>~~

	</ol>		Hint to download apk :
			<pre>wget https://gitlab.alpinelinux.org/api/v4/projects/5/packages/generic/v2.14.6/x86_64/apk.static</pre>

	=== Install ===		=== Install ===

Zcrayfish: /* References */ Remove red wikilink, remove wikilink to an article that is currently obsolete (but it could be updated and readded here....)

2024-01-13T09:30:59Z

References: Remove red wikilink, remove wikilink to an article that is currently obsolete (but it could be updated and readded here....)

← Older revision		Revision as of 09:30, 13 January 2024
Line 72:		Line 72:
	* [[Replacing non-Alpine Linux with Alpine remotely]]		* [[Replacing non-Alpine Linux with Alpine remotely]]
	* [[Install Alpine on Amazon EC2]]		* [[Install Alpine on Amazon EC2]]
	* [[Install Alpine on coLinux]]
	* [[Install Alpine on Rackspace]]
	* [[Alpine setup scripts]]		* [[Alpine setup scripts]]
	* [https://serverfault.com/questions/98950/how-do-i-chain-boot-from-grub-to-syslinux How do I chain boot from grub to syslinux?]		* [https://serverfault.com/questions/98950/how-do-i-chain-boot-from-grub-to-syslinux How do I chain boot from grub to syslinux?]

Localwikifox: Quick correction for less confusion

2023-12-06T15:42:06Z

Quick correction for less confusion

← Older revision		Revision as of 15:42, 6 December 2023
Line 61:		Line 61:

	=== Notes ===		=== Notes ===
	If you have bootstrapped Alpine Linux from an existing system in a different partition and intend to boot into it, you should always include the filesystem ~~module~~ in the kernel parameter (bootloader option), since by default kernel does not automatically load any filesystem modules, unless specified. That way mount will not complain about being unable to mount root partition on /sysroot.		If you have bootstrapped Alpine Linux from an existing system in a different partition and intend to boot into it, you should always include the root filesystem type (rootfstype) in the kernel parameter (bootloader option), since by default kernel does not automatically load any filesystem modules for root partition, unless specified. That way mount will not complain about being unable to mount root partition on /sysroot.

	Example bootloader option:		Example bootloader option:

Localwikifox: Correction, providing more accurate info after testing

2023-12-06T15:32:35Z

Correction, providing more accurate info after testing

← Older revision		Revision as of 15:32, 6 December 2023
Line 65:		Line 65:
	Example bootloader option:		Example bootloader option:

	<code>root=UUID=AAAAAAAA-BBBB-CCCC-DDDD-EEEEEEEEEEEE rw ext4 vfat</code>		<code>root=UUID=AAAAAAAA-BBBB-CCCC-DDDD-EEEEEEEEEEEE rw rootfstype=ext4 vfat</code>

	== References ==		== References ==

Localwikifox at 22:09, 5 December 2023

2023-12-05T22:09:48Z

← Older revision		Revision as of 22:09, 5 December 2023
Line 60:		Line 60:
	=== Bootloader ===		=== Bootloader ===

			=== Notes ===
			If you have bootstrapped Alpine Linux from an existing system in a different partition and intend to boot into it, you should always include the filesystem module in the kernel parameter (bootloader option), since by default kernel does not automatically load any filesystem modules, unless specified. That way mount will not complain about being unable to mount root partition on /sysroot.

			Example bootloader option:

			<code>root=UUID=AAAAAAAA-BBBB-CCCC-DDDD-EEEEEEEEEEEE rw ext4 vfat</code>

	== References ==		== References ==

Dju92: setup network before setting up repos

2023-08-08T11:31:18Z

setup network before setting up repos

← Older revision		Revision as of 11:31, 8 August 2023
Line 29:		Line 29:
	* chroot into your new installation		* chroot into your new installation
	<pre>chroot /tmp/target /bin/sh</pre>		<pre>chroot /tmp/target /bin/sh</pre>
			* setup hostname
			<pre>setup-hostname</pre>
			* setup network
			<pre>setup-interfaces</pre>
	* setup repos		* setup repos
	<pre>setup-apkrepos -f</pre>		<pre>setup-apkrepos -f</pre>
Line 35:		Line 38:
	<pre>apk update		<pre>apk update
	apk add linux-lts linux-firmware-none acpi mkinitfs</pre>		apk add linux-lts linux-firmware-none acpi mkinitfs</pre>
	* setup hostname
	~~<pre>setup-hostname</pre>~~
	* setup network
	~~<pre>setup-interfaces</pre>~~
	* add services to boot		* add services to boot
	<pre>		<pre>