How to make a custom ISO image: Difference between revisions

From Alpine Linux
mNo edit summary
mNo edit summary
(43 intermediate revisions by 12 users not shown)
Line 1: Line 1:
This document explains how to build a custom ISO image using the alpine-iso scripts.


First make sure we have the needed tools
One way to completely re-build custom images is to use a script like [https://github.com/alpinelinux/alpine-make-vm-image alpine-make-vm-image].
{{Cmd|apk add alpine-sdk}}


Then we clone (or update) the [http://git.alpinelinux.org/cgit/alpine-iso.git/ alpine-iso git repository].
* If you want to make a customized installer, you need to create <code>.default_boot_services</code> which will cause <code>mkinitfs</code> to create the defaults for the live image.
{{Cmd|git clone git://git.alpinelinux.org/alpine-iso}}


The alpine-iso scripts is a simple makefile which you need to feed with a ''<name>.conf.mk'' file and a ''<name>.packages''.
== An alternative ==


In the ''<name>.conf.mk'' we specify
It's possible to [[Alpine_local_backup#|commit and load ISO image customizations]] to and from disk.


;ALPINE_NAME
:name of iso image


;ALPINE_VERSION
:(optional) version string. Will default to todays date.


;KERNEL_FLAVOR
== Booting an ISO image with local customizations ==
:(optional) either ''grsec'', ''vserver'' or ''pae''. Will default to grsec.


;MODLOOP_EXTRA
* From a dedicated boot media, obviously.
:(optional) Extra kernel module packages for the modloop image. For example: ''dahdi-linux-vserver''
* [[Directly_booting_an_ISO_file]]


The ''<name>.packages'' is just a plaintext list of packages that should be included in the ISO image. You should always add ''alpine-base'' in there or the CD might not be able to boot. The dependencies for the packages will automatically be pulled in.
[[Category:Package Manager]]
 
[[Category:ISO]]
== A rescue CD example ==
As an example, let us make a rescue ISO image with packages needed for rescue operations. We call it ''alpine-rescue''
 
We create the ''alpine-rescue.conf.mk'' as follows:
ALPINE_NAME  := alpine-rescue
KERNEL_FLAVOR := grsec
MODLOOP_EXTRA :=
 
If you are going to use a custom kernel, don't forget to specify KERNEL_FLAVOR_DEFAULT which will set the default kernel to boot.
 
And then the ''alpine-rescue.packages'' as:
alpine-base
bkeymaps
openssh
e2fsprogs
mdadm
lvm2
parted
debootstrap
ntfs-3g
 
{{Tip| Make sure your public keys are placed in /etc/apk/keys/ (example: root-xxxxxxxx.rsa.pub):
{{Cmd|ls /etc/apk/keys/}}
 
Learn apk-tools to find your home-built apk's:
{{Cmd|echo "~/.cache/apks" >> /etc/apk/repositories}}
}}
 
Make sure the apk index is up to date (so apk finds the packages):
{{Cmd|apk update}}
 
We create the ISO image by telling the makefile the profile name. The makefile target is ''iso''.
{{Cmd|<nowiki>make PROFILE=alpine-rescue iso</nowiki>}}
 
To generate the sha1 sum we use the ''sha1'' make target.
{{Cmd|<nowiki>make PROFILE=alpine-rescue sha1</nowiki>}}
 
== Package lists ==
 
Beside the plaintext package lists in the git repository, there are more documented package lists contributed by Alpine users. Those lists can be transformed into a plaintext to use with <tt>alpine-iso</tt> list with the simple python-based <tt>[http://git.alpinelinux.org/cgit/fab/alpine-iso/tree/config-builder.py]</tt> script.
 
So far the lists below are available:
 
* [[Alpine_mini|Alpine Mini]]
* [[Alpine_rescue|Alpine Rescue]]
* [[Alpine_security|Alpine Security]]
 
== Testing your ISO image ==
 
[[Qemu#Live_mode| Qemu]] is useful for a quick test of your created ISO image.

Revision as of 18:43, 9 May 2020

One way to completely re-build custom images is to use a script like alpine-make-vm-image.

  • If you want to make a customized installer, you need to create .default_boot_services which will cause mkinitfs to create the defaults for the live image.

An alternative

It's possible to commit and load ISO image customizations to and from disk.


Booting an ISO image with local customizations