* Renamed all_disks() to all_blockdevices() as it's technically a bit more correct. As it would return partitions as well. And it now distinguishes between BlockDevice() and Partition() when returning values. Also lsblk has been replaced with blkid and glob.glob() on /sys/class/block/
* Added handling of loop devices
* Added device information enrichment
* Removed old code
* Updated the usage of blockdevice.info['type'] to 'DEVTYPE' as per returned by blkid instead of lsblk
* Created a MapperDev() and DMCryptDev() 'disk' classes. This should help differentiate between BlockDevice(), Partition() and crypt-specific devices. Due to some new helper functions (mentioned later) BlockDevice().device_or_backfile has been simplified thanks to the information being pre-existing instead of having to call losetup. BlockDevice().mountpoint has been added as a dummy function. archinstall.enrich_blockdevice_information() has been added to enrich information extracted from blkid. archinstall.uevent() has been created to parse blkdid data when in -o export format, also eats up /sys/class/x/y/uevent data which is of the same format. all_blockdevices() now returns mapper devices found under /dev/mapper/ and properly returns the different types, not just BlockDevice() for everything. archinstall.get_parent_of_partition() has been added, which can translate /dev/sda1 to /dev/sda via strings by using /sys/class/block/ - note here tho that it has to be a blockdevice. Other parents won't return properly. archinstall.find_mountpoint() was created to be able to find mountpoints for a device, rather than the other way around which get_mount_info() handles. find_mountpoint() will convert /dev/sda1 -> /boot for instance, whereas get_mount_info('/boot') will convert /boot -> /dev/sda1. archinstall.get_partitions_in_use() will now properly traverse the entire structure, not just one level deep. This called for the creation of get_all_targets() which will take a dictionary structure and look for 'target': '/path' and return all '/path' values, recursively without being trapped in get_partitions_in_use() which has recursive targets. get_partitions_in_use() now returns a dictionary instead of a list, as it also returns the mountpoint and associated device. It will also prioritize MapperDev over DMCryptDev (as MapperDev is a child of DMCryptDev and can be resolved, other way around is 'trickier').
* Reverted Installer().partitions to return only the partitions. It's a slight speed defecit by not returning the mountpoints directly as {mntpoint: partition}, because the partition.mountpoint is a bit slow. But it avoids breaking legacy code :)
* Fixed a few imports, and added MapperDev.filesystem
* Fixed so that Installer().detect_encryption() uses the new separated logic of MapperDev/DMCryptDev/Partition
* Fixing a translation issue on hostname
* Added DMCryptDev.filesystem
* Added back archinstall.all_disks() for legacy reasons.
* Added a deprecation warning to archinstall.all_disks()
* Added a enrichment check for dm-crypt specific devices, which in turn sets DMCRYPT_NAME on the device information, making it easier to detect and target DMCryptDev when needed. This should avoid issues with loopdevices being detected as DMCryptDev. Also some minor tweaks to variable names on unencrypted setups
* Made debug output hidden without --verbose. Also added get_subvolume_info() which takes a path and returns any 'btrfs subvol show' information on the path
* Partition().subvolumes has been added. Which generates an iterator over potential subvolumes based on mountpoint. Partition().mount_information is now a list of mount-destinations, as one partition should be allowed to be mounted to several places (more commonly used in btrfs subvolumes). BtrfsSubvolume() has been added as a 'device type', which should make it more easy to recognize a BtrfsSubvolume object right out of the gate. Only found from Partition().subvolumes currently.
* Parameter fix for --verbose in log()
* Made sure loopdev devices have a PATH key as well, to make dealing with them as blockdevice as seamless as possible.
* Added backup information grabbing on uninitated devices
* Tweaked backup option if losetup cannot find the blockdev
* looks like losetup doesn't exit with a bad code even when it should. Raising ourselves when information is empty.
* Fixed structure returned from get_blockdevice_uevent()
* Made sure that fallback to blkid and loopdev info returns a PTTYPE (Partition Table Type) that is None, since we can't locate it yet (empty drive). But it's not False either, which is what logic after is looking for
* Deprecated split_bind_name() and added more debugging
* get_partitions_in_use() now only iterates over Partition() objects. And properly checks all mountpoints, not only the first.
* Flipped SysCallError to show the last 500 bytes if data rather than the first, to catch the actual errors.
* Removed anonymous parameters to all_blockdevices()
* Added .mount_information to MapperDev
* Added typing annotations
* Partition().mountpoint is now a @property that will live-report the current mountpoint.
* Removed the need for setting Partition().mountpoint = X when calling .mount() and .unmount(), as it's live-reported instead.
* Added .subvolumes to MapperDev()
* Added debug information
* Muting F841 in helpers.py
* Tweaked debug information in get_mount_info()
* Minimized log output by moving Partition().mountpoint to DEBUG, as partitions are allowed to not be mounted
* Simplified Installer().add_bootloader() to act as a router to the new split function, one for each bootloader type. This since flake8 complained about complexity and I agree that it became to wild.
|
||
|---|---|---|
| .github | ||
| archinstall | ||
| docs | ||
| examples | ||
| profiles | ||
| .editorconfig | ||
| .flake8 | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .pypirc | ||
| .readthedocs.yml | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| PKGBUILD | ||
| README.md | ||
| pyproject.toml | ||
| schema.json | ||
| setup.cfg | ||
| setup.py | ||
README.md
Arch Installer
Just another guided/automated Arch Linux installer with a twist. The installer also doubles as a python library to install Arch Linux and manage services, packages and other things inside the installed system (Usually from a live medium).
- archinstall discord server
- archinstall matrix.org channel
- archinstall #archinstall@irc.libera.chat
- archinstall documentation
Installation & Usage
$ sudo pacman -S archinstall
Or simply git clone the repo as it has no external dependencies (but there are optional ones).
Or use pip install --upgrade archinstall to use as a library.
Running the guided installer
Assuming you are on an Arch Linux live-ISO and booted into EFI mode.
# archinstall
Some additional options that are not needed by most users are hidden behind the --advanced flag.
Running from a declarative configuration file or URL
Prequisites:
- Edit the configuration file according to your requirements.
Assuming you are on a Arch Linux live-ISO and booted into EFI mode.
# archinstall --config <path to config file or URL>
Help?
Submit an issue here on GitHub, or submit a post in the discord help channel.
When doing so, attach the /var/log/archinstall/install.log to the issue ticket. This helps us help you!
Mission Statement
Archinstall promises to ship a guided installer that follows the Arch Principles as well as a library to manage services, packages and other Arch Linux aspects.
The guided installer will provide user-friendly options along the way, but the keyword here is options, they are optional and will never be forced upon anyone. The guided installer itself is also optional to use if so desired and not forced upon anyone.
Archinstall has one fundamental function which is to be a flexible library to manage services, packages and other aspects inside the installed system. This library is in turn used by the provided guided installer but is also for anyone who wants to script their own installations.
Therefore, Archinstall will try its best to not introduce any breaking changes except for major releases which may break backwards compability after notifying about such changes.
Scripting your own installation
You could just copy guided.py as a starting point.
However, assuming you're building your own ISO and want to create an automated installation process, or you want to install virtual machines onto local disk images, here is a minimal example of how to install using archinstall as a Python library:
import archinstall, getpass
# Select a harddrive and a disk password
harddrive = archinstall.select_disk(archinstall.all_blockdevices(partitions=False))
disk_password = getpass.getpass(prompt='Disk password (won\'t echo): ')
# We disable safety precautions in the library that protects the partitions
harddrive.keep_partitions = False
# First, we configure the basic filesystem layout
with archinstall.Filesystem(harddrive, archinstall.GPT) as fs:
# We create a filesystem layout that will use the entire drive
# (this is a helper function, you can partition manually as well)
fs.use_entire_disk(root_filesystem_type='btrfs')
boot = fs.find_partition('/boot')
root = fs.find_partition('/')
boot.format('vfat')
# Set the flag for encrypted to allow for encryption and then encrypt
root.encrypted = True
root.encrypt(password=disk_password)
with archinstall.luks2(root, 'luksloop', disk_password) as unlocked_root:
unlocked_root.format(root.filesystem)
unlocked_root.mount('/mnt')
boot.mount('/mnt/boot')
with archinstall.Installer('/mnt') as installation:
if installation.minimal_installation():
installation.set_hostname('minimal-arch')
installation.add_bootloader()
installation.add_additional_packages(['nano', 'wget', 'git'])
# Optionally, install a profile of choice.
# In this case, we install a minimal profile that is empty
installation.install_profile('minimal')
installation.user_create('devel', 'devel')
installation.user_set_pw('root', 'airoot')
This installer will perform the following:
- Prompt the user to select a disk and disk-password
- Proceed to wipe the selected disk with a
GPTpartition table on a UEFI system and MBR on a BIOS system. - Sets up a default 100% used disk with encryption.
- Installs a basic instance of Arch Linux (base base-devel linux linux-firmware btrfs-progs efibootmgr)
- Installs and configures a bootloader to partition 0 on uefi. On BIOS, it sets the root to partition 0.
- Install additional packages (nano, wget, git)
Creating your own ISO with this script on it: Follow ArchISO's guide on how to create your own ISO or use a pre-built guided ISO to skip the python installation step, or to create auto-installing ISO templates. Further down are examples and cheat sheets on how to create different live ISO's.
Unattended installation based on MAC address
Archinstall comes with an unattended example which will look for a matching profile for the machine it is being run on, based on any local MAC address.
For instance, if the machine that unattended is run on has the MAC address 52:54:00:12:34:56 it will look for a profile called profiles/52-54-00-12-34-56.py.
If it's found, the unattended installation will commence and source that profile as its installation procedure.
Testing
Using a Live ISO Image
If you want to test a commit, branch or bleeding edge release from the repository using the vanilla Arch Live ISO image, you can replace the version of archinstall with a new version and run that with the steps described below:
- You need a working network connection
- Install the build requirements with
pacman -Sy; pacman -S git python-pip(note that this may or may not work depending on your RAM and current state of the squashfs maximum filesystem free space) - Uninstall the previous version of archinstall with
pip uninstall archinstall - Now clone the latest repository with
git clone https://github.com/archlinux/archinstall - Enter the repository with
cd archinstallAt this stage, you can choose to check out a feature branch for instance withgit checkout v2.3.1-rc1 - Build the project and install it using
python setup.py install
After this, running archinstall with python -m archinstall will run against whatever branch you chose in step 5.
Without a Live ISO Image
To test this without a live ISO, the simplest approach is to use a local image and create a loop device.
This can be done by installing pacman -S arch-install-scripts util-linux locally and doing the following:
# truncate -s 20G testimage.img
# losetup -fP ./testimage.img
# losetup -a | grep "testimage.img" | awk -F ":" '{print $1}'
# pip install --upgrade archinstall
# python -m archinstall --script guided
# qemu-system-x86_64 -enable-kvm -machine q35,accel=kvm -device intel-iommu -cpu host -m 4096 -boot order=d -drive file=./testimage.img,format=raw -drive if=pflash,format=raw,readonly,file=/usr/share/ovmf/x64/OVMF_CODE.fd -drive if=pflash,format=raw,readonly,file=/usr/share/ovmf/x64/OVMF_VARS.fd
This will create a 20 GB testimage.img and create a loop device which we can use to format and install to.
archinstall is installed and executed in guided mode. Once the installation is complete, you can use qemu/kvm to boot the test media.
(You'd actually need to do some EFI magic in order to point the EFI vars to the partition 0 in the test medium, so this won't work entirely out of the box, but that gives you a general idea of what we're going for here)
There's also a Building and Testing guide.
It will go through everything from packaging, building and running (with qemu) the installer against a dev branch.