partstoob¶
Experimental ports archinstoo to run from any Linux host (not just Arch ISOs).
Per distro host:¶
Mostly tested from smallest server type ISOs/cloud images (see
./RUN --script dev.vm cloud fed|deb).
Not fully cooked since it takes a lot of time, but at least all deps should be correct.
Can be found below:
| Logo | Host | arch-install-scripts |
pacman |
Script | Tested |
|---|---|---|---|---|---|
| Debian | V | V | DEB | V | |
| Nix | V | V | NIX | V | |
| Alpine | V | V | ALP | V | |
| Fedora | V | V | FED | V |
Any host:¶
Instead of host packages, --script bootstrap
runs archinstoo inside the Arch bootstrap tarball:
no pacman, keyring or arch-install-scripts on the host.
On aarch64 it takes the Arch Linux Ports tarball instead, see architecture/.
A host only needs:
python3 (>= 3.14) util-linux coreutils libarchive udev gnupg
gnupg is optional on x86_64 (checksum only without it, trusting TLS).
Package names might differ per distro.
libarchive-tools on Debian and Alpine, bsdtar on Fedora.
From Alpine (mdev by default):
apk add python3 util-linux coreutils libarchive-tools gnupg eudev && setup-devd udev
# what follows -- runs inside the root, as given (no args: guided)
./RUN --script bootstrap -- [archinstoo args...]
# the root is reused across runs, BOOT_DIR moves it (default /tmp/A2-boot)
# BOOT_MIRROR picks the x86_64 mirror for the tarball and packages
Everything runs inside the root: the tarball's own pacman, keyring and python,
with archinstoo's deps installed there on the first run.
Scripts that configure the running system (packages) are refused,
the root is thrown away after.
A layout mounted by hand on the host's /mnt is passed through for pre-mounted configs,
and the log path printed is the one the host sees.